Main Page

<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.11/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.11/ http://www.mediawiki.org/xml/export-0.11.xsd" version="0.11" xml:lang="en">
  <siteinfo>
    <sitename>SlackWiki</sitename>
    <dbname>swikidb</dbname>
    <base>https://www.slackwiki.com/Main_Page</base>
    <generator>MediaWiki 1.40.0</generator>
    <case>first-letter</case>
    <namespaces>
      <namespace key="-2" case="first-letter">Media</namespace>
      <namespace key="-1" case="first-letter">Special</namespace>
      <namespace key="0" case="first-letter" />
      <namespace key="1" case="first-letter">Talk</namespace>
      <namespace key="2" case="first-letter">User</namespace>
      <namespace key="3" case="first-letter">User talk</namespace>
      <namespace key="4" case="first-letter">SlackWiki</namespace>
      <namespace key="5" case="first-letter">SlackWiki talk</namespace>
      <namespace key="6" case="first-letter">File</namespace>
      <namespace key="7" case="first-letter">File talk</namespace>
      <namespace key="8" case="first-letter">MediaWiki</namespace>
      <namespace key="9" case="first-letter">MediaWiki talk</namespace>
      <namespace key="10" case="first-letter">Template</namespace>
      <namespace key="11" case="first-letter">Template talk</namespace>
      <namespace key="12" case="first-letter">Help</namespace>
      <namespace key="13" case="first-letter">Help talk</namespace>
      <namespace key="14" case="first-letter">Category</namespace>
      <namespace key="15" case="first-letter">Category talk</namespace>
    </namespaces>
  </siteinfo>
<page arvcontinue="">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>1</id>
    <timestamp>2009-05-24T17:46:17Z</timestamp>
    <contributor>
      <username>MediaWiki default</username>
      <id>0</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="449" xml:space="preserve">&lt;big&gt;'''MediaWiki has been successfully installed.'''&lt;/big&gt;

Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]</text>
    <sha1>bd962048d95fbb6b6b514885867811db20a5476b</sha1>
  </revision>
  <revision>
    <id>2</id>
    <parentid>1</parentid>
    <timestamp>2009-05-24T17:56:03Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3111" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>4ba83ac81d0d82c96dc0d480b6547fe731b1ba9c</sha1>
  </revision>
  <revision>
    <id>3</id>
    <parentid>2</parentid>
    <timestamp>2009-05-24T18:27:07Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3505" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==NOTICE==
After a long time and numerous upgrades, the DB finally caved in on itself. This is a fresh start. [http://slackwiki.org/old/ The old Wiki can be found here.] Don't bother trying to log in to the old Wiki or creating new users. The data is still there, you need to use the Search box to find it. Any help copying the old data over here to the new Wiki would be greatly appreciated.

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>6e149165aa3721cc94cb42a609aded6fcc517a4d</sha1>
  </revision>
  <revision>
    <id>40</id>
    <parentid>3</parentid>
    <timestamp>2009-05-28T23:59:01Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Main Page]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3505" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==NOTICE==
After a long time and numerous upgrades, the DB finally caved in on itself. This is a fresh start. [http://slackwiki.org/old/ The old Wiki can be found here.] Don't bother trying to log in to the old Wiki or creating new users. The data is still there, you need to use the Search box to find it. Any help copying the old data over here to the new Wiki would be greatly appreciated.

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>6e149165aa3721cc94cb42a609aded6fcc517a4d</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>User:Erik</title>
  <ns>2</ns>
  <id>2</id>
  <revision>
    <id>4</id>
    <timestamp>2009-05-24T18:37:55Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Creating my user page.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="197" xml:space="preserve">Real Name: Erik Hanson&lt;br&gt;
EMail: [mailto:erik@slackbuilds.org erik@slackbuilds.org]&lt;br&gt;
IRC: erik @ [irc://frop.taphouse.org/ Taphouse Cabal] and [irc://chat.freenode.net The Freenode Network]&lt;br&gt;</text>
    <sha1>24429ee81cdb6c9bc029cbf76178404e9f4da624</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Links</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>5</id>
    <timestamp>2009-05-24T18:39:14Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4817" xml:space="preserve">==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.com - our ugly mugs :)
* ftp://termserver.niesc.org/pub/sandman1 - Packages mostly by [[User:Sandman1|Sandman1]]
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://fredemmott.co.uk/rss.php - RSS feeds for slackware 10 patches and the slackware-current ChangeLog
* http://slackware.it/en/rss - RSS feeds for stable Slackware release and -current ChangeLog
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://uselesstree.org/ - The Complete Slacker
* http://shilo.is-a-geek.com/ - Shilo's tutorial
* http://www.linuxquestions.org/questions/forumdisplay.php?forumid=14 - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://www.slackware-peru.org - Slackware Peruvian Community - by [[User:R1CHARD|R1CHARD]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs
* http://www.themedepot.org/ - Generalized theme site for X11 based programs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://www.audioslack.com/packages/ Audioslack.com] Audio software packages
* [http://straterra.info/Packages/ http://straterra.info/Packages/] Straterra's packages
* [http://www.sekurity.com/packages/ Sekurity.com] dadexter's packages
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current
* [ftp://termserver.niesc.org/ ftp://termserver.niesc.org] Sandman1's packages

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://contrib.slamd64.com - [http://contrib.slamd64.com buildcontrib] can build and fetch these packages for you. Primarily for Slamd64, but work on x86 as well
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://slackbuilds.rlworkman.net - robw810's SlackBuild scripts
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://textlinux.slackadelic.com/slackbuilds/ - A repository dedicated to command line (friendly) applications
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/index.php/Main_Page BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki</text>
    <sha1>8271d339b511427cd1e362edd6dcc24261818372</sha1>
  </revision>
  <revision>
    <id>35</id>
    <parentid>5</parentid>
    <timestamp>2009-05-28T21:38:59Z</timestamp>
    <contributor>
      <username>94.192.0.60</username>
      <id>0</id>
    </contributor>
    <comment>/* Slackware Links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4937" xml:space="preserve">==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.com - our ugly mugs :)
* ftp://termserver.niesc.org/pub/sandman1 - Packages mostly by [[User:Sandman1|Sandman1]]
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://fredemmott.co.uk/rss.php - RSS feeds for slackware 10 patches and the slackware-current ChangeLog
* http://slackware.it/en/rss - RSS feeds for stable Slackware release and -current ChangeLog
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://uselesstree.org/ - The Complete Slacker
* http://shilo.is-a-geek.com/ - Shilo's tutorial
* http://www.linuxquestions.org/questions/forumdisplay.php?forumid=14 - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://www.slackware-peru.org - Slackware Peruvian Community - by [[User:R1CHARD|R1CHARD]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs
* http://www.themedepot.org/ - Generalized theme site for X11 based programs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://www.audioslack.com/packages/ Audioslack.com] Audio software packages
* [http://straterra.info/Packages/ http://straterra.info/Packages/] Straterra's packages
* [http://www.sekurity.com/packages/ Sekurity.com] dadexter's packages
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current
* [ftp://termserver.niesc.org/ ftp://termserver.niesc.org] Sandman1's packages

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://contrib.slamd64.com - [http://contrib.slamd64.com buildcontrib] can build and fetch these packages for you. Primarily for Slamd64, but work on x86 as well
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://slackbuilds.rlworkman.net - robw810's SlackBuild scripts
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://textlinux.slackadelic.com/slackbuilds/ - A repository dedicated to command line (friendly) applications
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/index.php/Main_Page BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki</text>
    <sha1>6eaac0eab73d62a30ee370f4ebd309a261a2ab26</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>6</id>
    <timestamp>2009-05-24T18:40:55Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1343" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please post a message on my [[User_talk:FredEmmott|user talk]] page if you think you'd be a suitable admin.</text>
    <sha1>5adf8b6c951b7ab01e0a5121ec4bc936da384364</sha1>
  </revision>
  <revision>
    <id>20</id>
    <parentid>6</parentid>
    <timestamp>2009-05-28T11:57:58Z</timestamp>
    <contributor>
      <username>Chopp</username>
      <id>10</id>
    </contributor>
    <minor/>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1366" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:chopp|chopp]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please post a message on my [[User_talk:FredEmmott|user talk]] page if you think you'd be a suitable admin.</text>
    <sha1>aaee4553956c07f975dedb6ea969992f44bf59fa</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Category:Information</title>
  <ns>14</ns>
  <id>5</id>
  <revision>
    <id>7</id>
    <timestamp>2009-05-24T19:25:33Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="124" xml:space="preserve">Pages containing general information related to Slackware.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>2f0e70b3d25250b938b437fac06c9aa25fdfc655</sha1>
  </revision>
  <revision>
    <id>45</id>
    <parentid>7</parentid>
    <timestamp>2009-05-29T00:01:45Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="223" xml:space="preserve">Pages containing general information related to Slackware. If you create a page and want it listed in this category, add [[Category:Information]] to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>308bd427685341bd64adceb68a9c7c438e23bbb0</sha1>
  </revision>
  <revision>
    <id>46</id>
    <parentid>45</parentid>
    <timestamp>2009-05-29T00:03:03Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Undo revision 45 by [[Special:Contributions/Erik|Erik]] ([[User talk:Erik|Talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="240" xml:space="preserve">Pages containing general information related to Slackware. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Information]]&lt;/nowiki&gt; to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>a38debf8c9fa35c7d4c7c9482db299754b86e857</sha1>
  </revision>
  <revision>
    <id>47</id>
    <parentid>46</parentid>
    <timestamp>2009-05-29T00:03:14Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Category:Information]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="240" xml:space="preserve">Pages containing general information related to Slackware. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Information]]&lt;/nowiki&gt; to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>a38debf8c9fa35c7d4c7c9482db299754b86e857</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Category:Tutorials</title>
  <ns>14</ns>
  <id>6</id>
  <revision>
    <id>8</id>
    <timestamp>2009-05-24T19:26:05Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="211" xml:space="preserve">This is the spot for Tutorials. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Tutorials]]&lt;/nowiki&gt; to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>59c03b97d7b902729522b0351f98efe234613913</sha1>
  </revision>
  <revision>
    <id>12</id>
    <parentid>8</parentid>
    <timestamp>2009-05-28T08:42:07Z</timestamp>
    <contributor>
      <username>Ibm5 25</username>
      <id>8</id>
    </contributor>
    <comment>Added CPU Freq Scale</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="238" xml:space="preserve">This is the spot for Tutorials. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Tutorials]]&lt;/nowiki&gt; to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

[[CPU Frequency Scaling]]</text>
    <sha1>96174eef54122de4d7998d37f28dd0a36080dab1</sha1>
  </revision>
  <revision>
    <id>14</id>
    <parentid>12</parentid>
    <timestamp>2009-05-28T08:43:11Z</timestamp>
    <contributor>
      <username>Ibm5 25</username>
      <id>8</id>
    </contributor>
    <comment>CPU Freq Scale, 2x</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="211" xml:space="preserve">This is the spot for Tutorials. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Tutorials]]&lt;/nowiki&gt; to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>59c03b97d7b902729522b0351f98efe234613913</sha1>
  </revision>
  <revision>
    <id>41</id>
    <parentid>14</parentid>
    <timestamp>2009-05-28T23:59:17Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Category:Tutorials]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="211" xml:space="preserve">This is the spot for Tutorials. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Tutorials]]&lt;/nowiki&gt; to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>59c03b97d7b902729522b0351f98efe234613913</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Category:Tips</title>
  <ns>14</ns>
  <id>7</id>
  <revision>
    <id>9</id>
    <timestamp>2009-05-24T19:26:32Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">This is the spot for Tips and other bits of useful information. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Tips]]&lt;/nowiki&gt; to the top.</text>
    <sha1>03866c694922986b45916c5c5a98b7d62a077894</sha1>
  </revision>
  <revision>
    <id>42</id>
    <parentid>9</parentid>
    <timestamp>2009-05-28T23:59:39Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Category:Tips]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="172" xml:space="preserve">This is the spot for Tips and other bits of useful information. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Tips]]&lt;/nowiki&gt; to the top.</text>
    <sha1>03866c694922986b45916c5c5a98b7d62a077894</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Category:Security</title>
  <ns>14</ns>
  <id>8</id>
  <revision>
    <id>10</id>
    <timestamp>2009-05-24T19:27:05Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="271" xml:space="preserve">Security related articles and Iptables scripts. No scripts generated by tools here please (unless of course you made it yourself, in which case, please only one). Add &lt;nowiki&gt;[[Category:Security]]&lt;/nowiki&gt; to the very bottom of your script to have it appear on this page.</text>
    <sha1>1070b9940e92c80b49a252e273ccc1e1a583b721</sha1>
  </revision>
  <revision>
    <id>43</id>
    <parentid>10</parentid>
    <timestamp>2009-05-28T23:59:54Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Category:Security]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="271" xml:space="preserve">Security related articles and Iptables scripts. No scripts generated by tools here please (unless of course you made it yourself, in which case, please only one). Add &lt;nowiki&gt;[[Category:Security]]&lt;/nowiki&gt; to the very bottom of your script to have it appear on this page.</text>
    <sha1>1070b9940e92c80b49a252e273ccc1e1a583b721</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Category:Hardware</title>
  <ns>14</ns>
  <id>9</id>
  <revision>
    <id>11</id>
    <timestamp>2009-05-24T19:27:33Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="325" xml:space="preserve">This is the spot for Hardware and other related bits of useful information regarding installing and/ or configuring Slackware on certain hardware. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Hardware]]&lt;/nowiki&gt; to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>eb4b86de8b7554049a855e39a0fc4a2bb8c55e50</sha1>
  </revision>
  <revision>
    <id>44</id>
    <parentid>11</parentid>
    <timestamp>2009-05-29T00:00:11Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Protected "[[Category:Hardware]]" ([edit=sysop] (indefinite) [move=sysop] (indefinite))</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="325" xml:space="preserve">This is the spot for Hardware and other related bits of useful information regarding installing and/ or configuring Slackware on certain hardware. If you create a page and want it listed in this category, add &lt;nowiki&gt;[[Category:Hardware]]&lt;/nowiki&gt; to the top.

Please [[Special:Userlogin|LOG IN]] before adding/editing pages.</text>
    <sha1>eb4b86de8b7554049a855e39a0fc4a2bb8c55e50</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>CPU Frequency Scaling</title>
  <ns>0</ns>
  <id>10</id>
  <revision>
    <id>13</id>
    <timestamp>2009-05-28T08:42:37Z</timestamp>
    <contributor>
      <username>Ibm5 25</username>
      <id>8</id>
    </contributor>
    <comment>Copied from /old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5748" xml:space="preserve">The CPU frequency scaling feature present in modern computers allows lowering and increasing the processor speed dynamically in runtime so as to save energy while having the possibility of increasing the performance and power consumption if needed. Activating CPU frequency scaling under Slackware is very easy, and requires loading a minimum of two kernel modules and running a simple command. On the one hand, you need to load a specific CPU driver that will activate the frequency scaling feature in your platform. Second, you need to choose a CPU frequency scaling governor, a module that will decide how and when to change the internal processor speed. There are governors to always run at full speed, governors to always run at low speed, governors to increase and decrease the speed based on the CPU load, etc.

It's usually desired to activate CPU frequency scaling as early as possible in the boot process, eventhough a few seconds running at full power are not that important. The easier way is, however, to enable it from the boot script &lt;tt&gt;/etc/rc.d/rc.local&lt;/tt&gt;, which is executed right at the end of the boot process. Other approaches need more intrusive changes. You could load the required modules and run the commands from a modified init script of an initial RAM disk. You could do the same from a personal &lt;tt&gt;/etc/rc.d/rc.modules.local&lt;/tt&gt;, or also from the already mentioned &lt;tt&gt;rc.local&lt;/tt&gt;. It's up to you to decide when and where to load and activate the feature.

= Loading CPU specific drivers =

You first need to load one of the available CPU powersaving modules. They are included in the typical kernel module packages, and depend on the type of CPU you have. Every available module will be located in &lt;tt&gt;/lib/modules/$( uname -r )/kernel/arch/i386/kernel/cpu/cpufreq&lt;/tt&gt;. For example, my CPU is a K8 processor and I use the &lt;tt&gt;powernow-k8&lt;/tt&gt; module. Inside that directory you will see a lot of module files ending with &lt;tt&gt;.ko&lt;/tt&gt;. To load them, use &lt;tt&gt;/sbin/modprobe&lt;/tt&gt; followed by the name before the suffix, from any location. Example:

  /sbin/modprobe powernow-k8

If you're not sure about which driver you need, proceed by trial and error. Load one module with a command like the previous one and then check the last lines of &lt;tt&gt;dmesg&lt;/tt&gt; with the command &lt;tt&gt;dmesg | tail&lt;/tt&gt;. If you see a successful detection, that's the module you need. If not, unload the module with &lt;tt&gt;/sbin/modprobe -r&lt;/tt&gt; (example: &lt;tt&gt;/sbin/modprobe -r powernow-k8&lt;/tt&gt;) and try another one. This is an example of successful output as printed by &lt;tt&gt;dmesg | tail&lt;/tt&gt;:

  powernow-k8: Found 1 Mobile AMD Sempron(tm) Processor 3000+ processors (version 2.00.00)
  powernow-k8:    0 : fid 0xa (1800 MHz), vid 0x8
  powernow-k8:    1 : fid 0x8 (1600 MHz), vid 0xa
  powernow-k8:    2 : fid 0x0 (800 MHz), vid 0x13

= Loading a governor module =

The second step is to load a governor module. The governor most people will want to load is the one named &lt;em&gt;ondemand&lt;/em&gt;, that will always use the lowest frequency available to fullfill the processing requirements. If your computer is idle, it will put the processor in the lowest possible speed. If you perform a very CPU-intensive task, it will increase the frequency accordingly. It's also the governor that Intel recommends to use in its laptops. All the available governor modules are located in &lt;tt&gt;/lib/modules/$( uname -r )/kernel/drivers/cpufreq&lt;/tt&gt;. To use a governor, the first step is to load its corresponding module as we did previously with the CPU module. Example:

  /sbin/modprobe cpufreq_ondemand

Notice how the governor is called &lt;em&gt;ondemand&lt;/em&gt;, yet its module is called &lt;em&gt;cpufreq_ondemand&lt;/em&gt;.

= Setting the CPU scaling governor =

Loading a governor module doesn't mean it's going to be used immediately. In fact, you can load all governor modules if you want. To decide which governor will be used in a given moment, you need to set it at runtime. Each CPU can have its own governor. That is, if you have a dual core machine, you can put one of the cores in low power and other one in full power if you need it. However, the most usual case is to use the same governor in all CPUs. Each CPU has its own configuration file in the &lt;tt&gt;/sys&lt;/tt&gt; filesystem. For example, the file for the first CPU is called &lt;tt&gt;/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor&lt;/tt&gt;. For other CPUs, increase the digit in &lt;tt&gt;cpu0&lt;/tt&gt;. You can set a governor name for all of them at the same time using a shell loop like the one in this example, that sets the &lt;em&gt;ondemand&lt;/em&gt; governor for every CPU:

  for config_file in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do
      echo ondemand &gt;$config_file
  done

To confirm you have successfully set the governor, see if it scales the CPU frequency. From an idle system, run &lt;tt&gt;grep '^cpu MHz' /proc/cpuinfo&lt;/tt&gt;. You should see one or more lines like:

  cpu MHz         : 800.000

Then, launch a CPU intensive task from a different terminal, like &lt;tt&gt;yes &gt;/dev/null&lt;/tt&gt; and then run the previous command again. You should now see a higher number (1800.000 in my case) in at least one of the output lines. If you see the same number wait 5 seconds and try again.

= Putting it all together =

This can be made as sophisticated as you decide, but let's suppose you opt for the simple approach of setting everything up from &lt;tt&gt;rc.local&lt;/tt&gt;. You would add the following commands if your CPU needed the module &lt;em&gt;powernow-k8&lt;/em&gt; and you wanted to set the &lt;em&gt;ondemand&lt;/em&gt; governor:

  /sbin/modprobe powernow-k8
  /sbin/modprobe cpufreq_ondemand
  for config_file in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do
      echo ondemand &gt;$config_file
  done

[[Category:Tutorials]]</text>
    <sha1>5eb801f9de521638190518da9fc1842c9b05d0f0</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>User talk:Ibm5 25</title>
  <ns>3</ns>
  <id>11</id>
  <revision>
    <id>15</id>
    <timestamp>2009-05-28T08:45:40Z</timestamp>
    <contributor>
      <username>Ibm5 25</username>
      <id>8</id>
    </contributor>
    <comment>Created page with '[[ThinkPad X61s]]'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17" xml:space="preserve">[[ThinkPad X61s]]</text>
    <sha1>385af5e4906f196500a0c7e91212474e1eeb3f78</sha1>
  </revision>
  <revision>
    <id>17</id>
    <parentid>15</parentid>
    <timestamp>2009-05-28T08:47:16Z</timestamp>
    <contributor>
      <username>Ibm5 25</username>
      <id>8</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">[[Minimal_System]]</text>
    <sha1>adfbd76592ebe95aaed9e000115f4f829af148c7</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>ThinkPad X61s</title>
  <ns>0</ns>
  <id>12</id>
  <revision>
    <id>16</id>
    <timestamp>2009-05-28T08:46:01Z</timestamp>
    <contributor>
      <username>Ibm5 25</username>
      <id>8</id>
    </contributor>
    <comment>from /old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14075" xml:space="preserve">[[Category:Hardware]]

== Specs ==

Note: There are several different models, and Lenovo offer customization in some countries. This is just what I have. Bus IDs are provided when I can't find more details on the model.

* CPU: Intel Core 2 Duo L7500 @ 1.60Ghz
* RAM: 1GB PC2-3500 DDR2
* Graphics: Intel Graphics Media Accelerator X3100 (i965)
* Display: 12.1" 1024x768 TFT
* Hard Drive: 120GB Hitatchi SATA drive
* Audio: AD1984 Intel HD Audio
* LAN: Intel 82566MM Gigabit Ethernet
* WLAN: Intel 3945 ABG
* WWAN: Sierra Wireless (Internal USB, ID: 1199:6813)
* Bluetooth: Broadcom Corp. (Internal USB, ID: 0a5c:2110)
* Fingerprint reader: SGS Thomson Microelectronics Fingerprint Reader
* USB: 4 UHCI controllers, 2 EHCI controllers, 3 ports. Intel 82801H (ICH8 Family)
* Firewire: Ricoh Co Limited - Unknown device (PCI ID: 1180:0832)
* SD Card reader: Ricoh Co Ltd R5C822
* Pointing device: TrackPoint - "nipple mouse"

== Notes ==

If you plan on keeping Vista, don't use it's built in NTFS resizer. This will only free up around 30GB of space, instead of the more than 60 you can free up with other tools. I used a proprietary Windows application, [http://www.partition-manager.com Paragon Partition Manager], however Parted and ntfs_resize are reported to have no problems. I'd advise not using Partition Magic, as it officially doesn't support Vista.

I would advise not deleting the first partition, as it is the recovery partition. I would also advise not installing your bootloader to the MBR without backing up the MBR first, as it isn't a standard MBR.

CDMA WWAN devices *MUST* be activated from Windows; GSM/UMTS devices don't need activating. For both types of WWAN, the on-screen 'activation information' isn't complete - the full information is on a sticker on the underside of the laptop.

If when running lilo, you get an error out the partition table being invalid, and asking you to FIX or IGNORE, "lilo -P fix" worked for me, and I can still boot Windows fine. "lilo -P ignore" is safer, but may not work.

Also, I installed Slamd64, not Slackware. I will note anywhere where I believe there's likely to be a difference.

== Installing ==

There's 4 choices:

* Normal install from UltraBay DVD drive in UltraBase (docking station)
* Normal install from USB DVD drive - there's reportedly been mixed success with this though
* PXE + NFS install
* USB + NFS install

I created the USB/PXE installer initrd for Slamd64 (Slackware 12.0 includes one already), and went for the PXE + NFS option. There is already good documentation for how to install Slackware like this. You should start the installer with the hugesmp.s kernel, and install it, until you've made a suitable initrd for booting from another kernel.

== Kernel ==

I'd strongly recommend going for the latest kernel from kernel.org - this is a very new laptop, and not properly supported in older kernels. You also probably want to patch it a bit. I used 2.6.22.2

=== Patches ===

Some of these were hard to find, so I've put them at [http://files.fredemmott.co.uk/X61s].

* hdaps_protect-2.6.19.patch.gz - allows userspace to park the hard disk heads. Required for the accelerometer-based hard-drive shock protection to work
* thinkpad-acpi-0.15-20070723_x2.6.22.1.patch.gz - required for advanced power management, bluetooth, and the soundcard - doesn't quite apply cleanly, find -name "*.rej" in your source tree and apply the remaining changes manually.
* alsa-git-2007-07-20.patch.gz - required for the sound card
* enablec3.patch.gz - allows the CPU to enter a lower CPU sleep state

If you have in-built WWAN, you also will need to do minor changes to drivers/usb/serial/sierra.c:

# Find the two lines containing: &lt;pre&gt;USB_DEVICE(0x1199, 0x6812)&lt;/pre&gt;
# Copy them to the next line, changing 0x6812 to 0x6813
# Change the comment to something descriptive, like: &lt;pre&gt;/* Thinkpad X61s unknown card */&lt;/pre&gt;

=== Config ===

I based mine off hugesmp.s's config:

&lt;pre&gt;
zcat /proc/config.gz &gt; .config
make oldconfig &lt;/dev/null
&lt;/pre&gt;

I also turned on the following options (paths given are for the tree structure in menuconfig):

* Processor type and features/Support for suspend on SMP and hot-pluggable CPUs - CONFIG_HOTPLUG_CPU; this is required for suspend to RAM to function correctly, and lets you turn off the second core to save power.
* Networking/Wireless/Generic IEEE 802.11 Networking Stack (mac80211) - CONFIG_MAC80211; this is required for the newer of the two WLAN drivers. I recommend making this a module.
* Device drivers/Misc devices/ThinkPad ACPI Laptop Extras - CONFIG_THINKPAD_ACPI; this is required for sound, bluetooth, and advanced power saving, and used to be "ibm-acpi" instead of "thinkpad-acpi". I recommend making this a module, and turning on 'Enable input layer support by default' (CONFIG_THINKPAD_ACPI_INPUT_ENABLED).

== rc.modules.local ==

Unless noted otherwise, this is where modules should be loaded from. Keep in mind that if this file is present and +x, rc.modules is not called. For this reason, my rc.modules.local starts with:

&lt;pre&gt;
#!/bin/sh
if [ -x /etc/rc.d/rc.modules ]; then
  /etc/rc.d/rc.modules
fi
&lt;/pre&gt;

This file should be +x, and belongs in /etc/rc.d/.

== Hard Drive Impact Protection ==

The laptop contains hardware to detect a fall, and to park the hard disk drive heads. You need the a kernel patched with the hdaps_protect patch described above.

# Download [http://sourceforge.net/project/showfiles.php?group_id=1212 tp_smapi]
# Extract it
# make HDAPS=1
# make install HDAPS=1

Add the following to /etc/rc.d/rc.modules.local:
&lt;pre&gt;
/sbin/modprobe hdaps
/sbin/modprobe tp-smapi
&lt;/pre&gt;

If you wish to use the joystick device provided by the tilt sensors, one of the axis is inverted. This can be fixed by changing the function 'transform_axes' in hdaps.c to the following, before running 'make':
&lt;pre&gt;
static void transform_axes(int *x, int *y)
{
  if (hdaps_invert)
    *x = -*x;
  else
    *y = -*y;
}
&lt;/pre&gt;

Impact protection requires a user-space daemon, hdapsd:

# Download [http://files.fredemmott.co.uk/X61s/hdapsd-20070524.c hdapsd-20070524.c]
# gcc -o /usr/local/sbin/hdapsd hdapsd-20070524.c
# Add the following to /etc/rc.d/rc.local: &lt;pre&gt;/usr/local/sbin/hdapsd -d sda -s 30 -b&lt;/pre&gt;

=== KHDAPSMonitor ===

KHDAPSMonitor is a KDE system-tray applet that indicates the status of the hard disk parking. Eric Hameleers has made [http://www.slackware.com/~alien/slackbuilds/khdapsmonitor/pkg/12.0/ a package] and [http://www.slackware.com/~alien/slackbuilds/khdapsmonitor/build/ SlackBuild script].

== XOrg ==

xorgconfig should give you a working configuration. You want to use the 'intel' graphics driver.

=== Multiple Monitors ===

xrandr 1.2 can handle this fine; there's two "gotchas":

* You must provide a large enough virtual screen - I have 'Virtual 3000 1600' in my "Display" Subsection
* Only modes with horizontal and vertical refresh rates in the ranges specified in your xorg.conf screen section will be accepted. Making these ranges really large appears to have no ill effects. (I'm currently using HorizSync 10-100, and VertRefresh 30-70).

Once you've got the above done, and restarted X, it's easy to add enough screen once X is running:

* xrandr --output TV --off
* xrandr # get a list of modes
* xrandr --output VGA --mode XRESxYRES

For example, "xrandr --output VGA --mode 1280x1024".

If you want Xinerama, instead of cloning, replace the last line with:

* xrandr --output VGA --mode XRESxYRES --left-of LVDS

Other valid options are --right-of, --above, and --below.

=== DRI ===

This works fine, as long as you've upgraded mesa; it's unstable and crashes with the version included in Slackware, however, upgrading to mesa 7.0.1 fixes this.

== TrackPoint ==

The TrackPoint 'just works' as a basic mouse, however, it can do better :) For enhanced support:

Add the following to /etc/rc.d/rc.modules.local (the psmouse driver doesn't recognize it as a TrackPoint the first time):
&lt;pre&gt;
/sbin/rmmod psmouse
/sbin/modprobe psmouse
&lt;/pre&gt;

Add the following to /etc/rc.d/rc/local: &lt;pre&gt;echo 1 &gt; /sys/devices/platform/i8042/serio1/press_to_select&lt;/pre&gt;

I have the following as the relevant "InputDevice" section in my xorg.conf, which lets you hold down the middle mouse button to scroll:
&lt;pre&gt;
Section "InputDevice"
  Identifier "Mouse1"
  Driver "mouse"
  Option "Protocol" "ExplorerPS/2" # IMPS/2 is not recommend for TrackPoints
  Option "Device" "/dev/input/mice"
  Option "EmulateWheel" "on"
  Option "EmulateWheelTimeout" "200"
  Option "EmulateWheelButton" "2"
  Option "YAxisMapping" "4 5"
  Option "XAxisMapping" "6 7"
EndSection
&lt;/pre&gt;

== Card Reader ==

Add the following to rc.modules.local:
&lt;pre&gt;
/sbin/modprobe sdhci
/sbin/modprobe mmc-block
&lt;/pre&gt;

This card reader is compatible with HAL's media insertion/removal support.

== Sound ==

This uses the snd-hda-intel driver, which should be automatically loaded by udev. If you get silence, check that Speaker output is enabled, and check /proc/acpi/ibm/volume.

Without the thinkpad-acpi module loaded, audio is corrupted.

== Gigabit Ethernet ==

This uses the e1000 driver.

== Wireless LAN (802.11) ==

I used the [http://intellinuxwireless.org new iwlwifi driver], version 1.0, and the corresponding iwlwifi-3945-ucode, version 2.14.1.5. Ignore the documentation saying you need to download mac80211 and patch the kernel, this is included in recent kernels.

# Download the ucode tarball
# Extract it somewhere
# Copy iwlwifi-3945-1.ucode to /lib/firmware/iwlwifi-3945.ucode - note the filename change
# Download the iwlwifi driver tarball
# Extract it
# make; make install

Add the following to rc.modules.local:
&lt;pre&gt;
/sbin/modprobe iwl3945
&lt;/pre&gt;

When this module is loaded, the WLAN device is wlan0.

== Wireless WAN (EVDO/UMTS) ==

These instructions based on the UK Vodafone 3G card. I believe the US Cingular/Verizon cards should be very similar; check the USB IDs though.

Add the following to rc.modules.local: &lt;pre&gt;/sbin/modprobe usbserial vendor=0x1199 product=0x6813&lt;/pre&gt;

You should now have /dev/ttyUSB[0-2].

I have [http://files.fredemmott.co.uk/X61s/ppp-peers.tar.bz2 modified] the pppd peers scripts that [http://www.sierrawireless.com/faq/ShowFAQ.aspx?ID=601 Sierra provides]. Untar these to /etc/ppp, creating 4 files in /etc/ppp/peers. "gsm" and "gsm_chat" are for GSM/UMTS connections, "cdma" and "cdma_chat" are for CDMA devices. For GSM/UMTS, if you aren't using Vodafone, you must change the APN in gsm_chat. I am unsure about the configuration of CDMA.

To connect, type "pppd call gsm" for GSM/UMTS, or "pppd call cdma" for cdma.

== ACPI ==

I'm assuming you've patched your kernel and build thinkpad-acpi as a module.

To enable basic ACPI functionality, add the following to /etc/rc.d/rc.modules.local:

&lt;pre&gt;
/sbin/modprobe nvram
/sbin/modprobe ac
/sbin/modprobe battery
/sbin/modprobe button
/sbin/modprobe acpi-cpufreq
/sbin/modprobe cpufreq-ondemand
/sbin/modprobe thinkpad-acpi
&lt;/pre&gt;

If you wish to use any of the ACPI action scripts below:

#Download [http://files.fredemmott.co.uk/X61s/acpi_handler.sh] as /etc/acpi/acpi_handler.sh
#&lt;pre&gt;chmod +x /etc/acpi/acpi_handler.sh&lt;/pre&gt;

=== CPU Frequency Scaling ===

To enable on-demand frequency scaling:
&lt;pre&gt;echo ondemand &gt; /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor&lt;/pre&gt;

Changing the cpufreq settings for one core affects both. cpu1's cpufreq directory is actually a symlink to cpu0's.

Intel recommend ondemand, and believe it to be more power-efficient than 'powersave'.

=== Suspend to RAM ===

Add the following to the Linux section of your /etc/lilo.conf, otherwise you'll have a black screen when resuming:
&lt;pre&gt;append = "acpi_sleep=s3_bios"&lt;/pre&gt;

Run lilo and reboot.

To sleep, download [http://files.fredemmott.co.uk/X61s/sleep]. This script is based on one from [http://www.thinkwiki.org ThinkWiki].

If you want to go to sleep based on ACPI events, such as closing the lid or pressing the sleep button (Fn-F4):
# Save the above 'sleep' script as /etc/acpi/actions/sleep
# &lt;pre&gt;chmod +x /etc/acpi/actions/sleep&lt;/pre&gt;
# For Fn-F4 to work, run the following and add it to /etc/rc.d/rc.local: &lt;pre&gt;echo 808 &gt; /proc/acpi/ibm/hotkey&lt;/pre&gt; 808 is a modification of the default bitmask, telling thinkpad-acpi to pass the Fn-F4 event to the ACPI userspace, instead of dealing with it itself, AKA ignoring it.

=== Suspend to Disk ===

This works fine, just change the above 'sleep' script to echo "disk" instead of echo "ram".

=== Adjust Screen Brightness on AC Status Change ===
# Download [http://files.fredemmott.co.uk/X61s/ac] as /etc/acpi/actions/ac
# chmod +x /etc/acpi/actions/ac

The brightness levels used on battery and ac are adjusted by two variables at the top of that script.

You might also want to add /etc/acpi/actions/ac to /etc/rc.d/rc.local, so that the appropriate brightness is set on boot.

== PCMCIA/CardBus ==

This works fine, and should 'just work'. It uses the yenta_socket driver.

=== Fingerprint Reader ===

This works fine on a PAMified system, using the 'thinkfinger' driver. I've not tried the closed source driver.

You can also use it instead of a BIOS password if you configure it from Windows.

== Not Tested ==

=== Firewire ===

I don't have any firewire devices, so I've not tested this. It is however detected by the kernel, and appears to be supported.

=== BlueTooth ===

I've just not got round to testing this yet.

/proc/acpi/ibm/bluetooth enables/disabled it. When it's disabled, it doesn't appear on the USB bus. When enabled, and the wireless kill switch is off, it is detected by the hciusb driver.

=== UltraBase/UltraBay DVD Drive ===

I don't own this hardware. Reportedly it's a standard IDE drive, and hotplugging works.

=== Modem ===

Got no use for it.

== Not Working ==

=== Screen Brightness Buttons ===

Screen brightness can be controlled via /proc/acpi/ibm/brightness

== External sources ==
* [http://www.thinkwiki.org/ ThinkWiki - Linux Thinkpad Wiki] - Tons of information about installing various Linux distributions on IBM/Lenovo Thinkpads</text>
    <sha1>4764ce8d9fb4fa4e586c0cc8f28cc2159826d8a8</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Minimal System</title>
  <ns>0</ns>
  <id>13</id>
  <revision>
    <id>18</id>
    <timestamp>2009-05-28T08:47:43Z</timestamp>
    <contributor>
      <username>Ibm5 25</username>
      <id>8</id>
    </contributor>
    <comment>Created page with '[[Category:Tutorials]]  ''by Niki Kovacs, September 2007''   === Introduction ===  Once in a while, the question arises on AOLS or in some forum: what packages should I install t...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="52563" xml:space="preserve">[[Category:Tutorials]]

''by Niki Kovacs, September 2007'' 

=== Introduction ===

Once in a while, the question arises on AOLS or in some forum: what packages should I install to have a ''base system''? Well, one could argue about what is meant. While some folks run no more than a kernel, a libc and a handful of packages on their servers stripped down to the bare bones, others might find such a configuration useful in the sense that chickens fly and horses swim. 

Some facts and figures:

* A "base" install of [http://www.linuxfromscratch.org Linux From Scratch] consists of a little more than 50 packages. 
* [http://www.archlinux.org Arch Linux]' [base] system has exactly 92 packages. 
* A "minimal" install of [http://www.centos.org CentOS 5.0] (all software categories unselected) counts as much as 393 packages.

Conclusion: "''Il y a fagots et fagots''" (Molière, Le Médecin Malgré Lui)

The package choice suggested on this page is of course highly subjective. It's also the result of a simple pragmatic approach. So far, I'm using Slackware in the following situations:

* Database server
* Web server (Apache/PHP/MySQL)
* File server
* CUPS print server
* SANED scanner server
* Streaming media server (MPD/Icecast)

Here, the "base system" would simply boil down to the common denominator of packages installed in all these different scenarios. Something like:

* A bootable, coherent system (no missing libs or scripts)
* A Bash shell
* A SMP kernel and what's necessary to rebuild it.
* Development tools to build the odd package from source
* Networking
* A selection of tools for system administration
* No graphical environment
* No sound

Once the base system is installed, it's easy to manually add the few needed packages depending on the needs: CUPS, Apache, MySQL, ALSA, whatever.

Now here's my working base configuration:

&amp;nbsp;

=== Package group [A] ===

{| border="1" cellspacing="0" cellpadding="5"
! Package
! Short Description
! Long Description
|-
| '''aaa_base''' 
| Basic Linux filesystem package
| Sets up the empty directory tree for Slackware and adds an email to root's mailbox welcoming them to Linux. :)  This package should be installed first, and never uninstalled.
|-
| '''aaa_elflibs''' 
| Shared libraries needed by many programs
| This is a collection of shared libraries needed to run Linux programs. ELF (Executable and Linking Format) is the standard Linux binary format. These libraries are gathered from other Slackware packages and are intended to give a fairly complete initial set of libraries. This package should be not upgraded or reinstalled (it could copy over newer library versions).
|-
| '''aaa_terminfo''' 
| A basic collection of terminfo entries
| This is a starter set of files from the terminfo database, which should be enough in most cases.  The complete set (from which this is derived) can be found in the ncurses package. The terminfo database describes the characteristics of terminals, so don't try to log in without this package.  :-)
|-
| '''acl''' 
| Tools for using POSIX Access Control Lists
| This package contains a set of tools and libraries for manipulating POSIX Access Control Lists.  POSIX Access Control Lists (defined in POSIX 1003.1e draft standard 17) are used to define more fine-grained discretionary access rights for files and directories.
|-
| '''acpid''' 
| ACPI daemon
| Most modern computers support the Advanced Configuration and Power Interface (ACPI) standard to allow intelligent power management. This package contains acpid, which is the user-space daemon needed in order to make the Linux ACPI support completely functional. ACPI must be compiled into the kernel to run acpid.
|-
| '''apmd''' 
| Advanced Power Management daemon
| apmd is an APM monitoring daemon, and works in conjunction with the APM BIOS driver in the kernel.  Apmd (and the included tools) handle tasks such as automatically putting a laptop into suspend when the power level drop below a certain point.  This package also includes the graphical power management tools xapm and xbattery. 
|-
| '''attr''' 
| Tools for using extended attributes on filesystems
| This package contains a set of tools for manipulating extended attributes (name:value pairs associated permanently with files and directories) on filesystem objects, and the library and header files needed to develop programs which make use of extended attributes. Extended attributes are used to provide additional functionality to a filesystem.  For example, Access Control Lists ([[ACL]]s) are implemented using extended attributes.
|-
| '''bash''' 
| sh-compatible shell
| The GNU Bourne-Again SHell.  Bash is a sh-compatible command interpreter that executes commands read from the standard input or from a file.  Bash also incorporates useful features from the Korn and C shells (ksh and csh).  Bash is ultimately intended to be a conformant implementation of the IEEE Posix Shell and Tools specification (IEEE Working Group 1003.2). Bash must be present for the system to boot properly.
|-
| '''bin'''
| Some command-line utilities
| The bin package is a collection of miscellaneous command-line utilities.  Some of these (such as 'tempfile') are used in system scripts.
|-
| '''bzip2'''
| A block-sorting file compressor
| Bzip2 compresses files using the Burrows-Wheeler block sorting text compression algorithm, and Huffman coding.  Compression is generally considerably better than that achieved by more conventional LZ77/LZ78-based compressors, and approaches the performance of the PPM family of statistical compressors. 
|-
| '''coreutils'''
| Core GNU utilities
| These are the GNU core utilities, the basic command line programs such as 'mkdir', 'ls', and 'rm' that are needed for the system to run.  This package is the union of the GNU fileutils, sh-utils, and textutils packages.  Most of these programs have significant advantages over their Unix counterparts, such as greater speed, additional options, and fewer arbitrary limits.
|-
| '''cpio'''
| Backup and archiving utility
| This is GNU cpio, a program to manage archives of files. This package also includes mt, a tape drive control program. cpio copies files into or out of a cpio or tar archive, which is a file that contains other files plus information about them, such as their pathname, owner, timestamps, and access permissions. The archive can be another file on the disk, a magnetic tape, or a pipe.
|-
| '''cryptsetup'''
| Utility for setting up encrypted filesystems
| LUKS is a standard for cross-platform hard disk encryption. It provides secure management of multiple userpasswords and stores setup information in the partition header. LUKS for dm-crypt is now implemented in cryptsetup replacing the original cryptsetup. It provides all the functionally of the original version plus all LUKS features.
|-
| '''cxxlibs'''
| C++ shared library compatibility package
| This package contains the shared libraries needed to run dynamically linked C++ binaries linked with older versions of libstdc++.
|-
| '''dcron'''
| Dillon's Cron daemon
| The cron daemon runs in the background and executes tasks on behalf of users at the appropriate time.  Many timed system tasks are started with cron, such as the nightly indexing with updatedb.
|-
| '''device-mapper'''
| Device mapper for logical volume management
| The goal of device-mapper is to support volume management.  The driver enables the definition of new block devices composed of ranges of sectors of existing devices.  This can be used to define disk partitions or logical volumes. device-mapper is required by LVM2, the Logical Volume Manager.
|-
| '''devs'''
| System device files
| This package creates special files in the /dev directory that represent your system's hardware, and a tool (/dev/MAKEDEV) for creating new device files.  These files are required to access hardware on a Linux system.
|-
| '''dialog'''
| Display dialog boxes from shell scripts
| Dialog is a program to present a variety of questions or display messages using dialog boxes from a shell script.  The Slackware package management script "pkgtool" uses this, as do various other menu-driven console scripts.
|-
| '''dosfstools'''
| Tools for working with FAT filesystems
| Utilities for creating FAT filesystems (mkdosfs), and for checking and repairing them (dosfsck).
|-
| '''e2fsprogs'''
| ---
| Utilities needed to create and maintain ext2 and ext3 filesystems.
|-
| '''eject'''
| A tool to eject removable media
| Eject allows removable media (typically a DVD, CD, floppy disk, tape, etc.) to be ejected under software control.  The command can also control some multi-disc changers, the auto-eject feature supported by some devices, and can close the disc tray of some drives.
|-
| '''elvis'''
| ---
| Elvis is a text editor.  It is intended to be a modern replacement for the classic ex/vi editor of UNIX fame.  Elvis supports many new features, including multiple edit buffers, multiple windows, and a variety of display modes.
|-
| '''etc'''
| System configuration files
| System configuration files.  The /etc directory is traditionally the location where configuration files are found.
|-
| '''file'''
| A utility to determine file type
| This is Ian F. Darwin's 'file' utility, used to identify files.
|-
| '''findutils'''
| Utilities to locate files
| This package contains the GNU find and xargs programs.  The find and xargs implementations comply with POSIX 1003.2.  They also support some additional options, some borrowed from Unix and some unique to GNU.
|-
| '''floppy'''
| Floppy disk utilities
| Contains fdutils-5.4, tools to test and format floppy disks; and mtools-3.9.8, a collection of utilities for using DOS/Windows floppy disks with Linux.
|-
| '''gawk'''
| Pattern scanning and processing language
| Gawk is the GNU Project's implementation of the AWK programming language.  It conforms to the definition of the language in the POSIX 1003.2 Command Language And Utilities Standard.  This version in turn is based on the description in The AWK Programming Language, by Aho, Kernighan, and Weinberger, with the additional features found in the System V Release 4 version of UNIX awk.  Gawk also provides more recent Bell Labs awk extensions, and some GNU-specific extensions.
|-
| '''gettext'''
| ---
| The GNU gettext package contains "gettext" and "ngettext", programs that are used to internationalize the messages given by shell scripts.
|-
| '''glibc-solibs'''
| Shared GNU C libraries
| This package contains the shared libraries, binaries, and support files required to run most Linux applications linked with glibc.
|-
| '''glibc-zoneinfo'''
| Timezone database
| This package allows you to configure your time zone. Use the timeconfig utility to set your local time zone.
|-
| '''grep'''
| Print lines matching a pattern
| This is GNU grep, the "fastest grep in the west" (we hope).  Grep searches through textual input for lines which contain a match to a specified pattern and then prints the matching lines.
|-
| '''gzip'''
| File compression utility
| Gzip reduces the size of the named files using Lempel-Ziv coding (LZ77).  Whenever possible, each file is replaced by one with the extension .gz, while keeping the same ownership modes, access and modification times.
|-
| '''hdparm'''
| Read/set hard drive parameters
| hdparm provides a command line interface to various hard disk ioctls supported by the Linux ATA/IDE device driver subsystem.  This may be required to enable higher-performing disk modes.
|-
| '''infozip'''
| Info-ZIP's zip and unzip utilities
| zip is a compression and file packaging utility for Unix, VMS, MSDOS, OS/2, Windows NT, Minix, Atari and Macintosh, Amiga and Acorn RISC OS. It is analogous to a combination of the UNIX commands tar(1) and compress(1) and is compatible with PKZIP (Phil Katz's ZIP).  A companion program  unzip(1L)), unpacks zip archives.
|-
| '''isapnptools'''
| ISA Plug-And-Play tools
| These programs allow ISA Plug-And-Play devices to be configured on a Linux machine.
|-
| '''kbd'''
| Keyboard maps and console fonts
| Load and save keyboard mappings.  Needed if you are not using the US keyboard map.  This package also contains utilities to change your console fonts - if you install it you'll get a menu later on that lets you select from many different fonts.  If you like one, you can make it your default font.  A new default font can be chosen at any time by typing 'setconsolefont'.
|-
| '''kernel-huge-smp'''
| A fully-loaded SMP Linux kernel
| This is a Linux kernel with built-in support for most disk controllers.  If you're looking for a more stripped down kernel (this one contains everything but the kitchen sink ;-), then install the kernel-generic-smp in the /boot directory along with an initrd to load support for your boot device and filesystem.  For instructions on the initrd, see README.initrd in the /boot directory. SMP is "Symmetric multiprocessing", or multiple CPU/core support.
|-
| '''kernel-modules-smp'''
| SMP Linux kernel modules
| A kernel module is a piece of object code that can be dynamically loaded into the Linux kernel to provide new kernel functions.  Most of these modules provide support for devices such as CD-ROM drives, tape drives, and ethernet cards.  You can choose which modules to load by editing /etc/rc.d/rc.modules.
|-
| '''less'''
| File pager
| Less is a paginator similar to more (1), but which allows backward movement in the file as well as forward movement. Also, less does not have to read the entire input file before starting, so with large input files it starts up faster than text editors like vi (1).
|-
| '''lilo'''
| Linux Loader
| Generic Boot Loader for Linux ('LInux LOader') by Werner Almesberger. LILO boots Linux from your hard drive. It can also boot other operating systems such as MS-DOS and OS/2, and can even boot DOS from the second hard drive. LILO comes with utilities and documentation that make it easier to install, such as 'liloconfig' and 'QuickStart'. NOTE: Installing boot loaders is inherently dangerous. Be sure to have some means to boot your system from a different media if you install LILO on your hard disk.
|-
| '''logrotate''' 
| System log rotation tool
| The logrotate utility is designed to simplify the administration of log files on a system which generates a lot of log files. Logrotate allows for the automatic rotation compression, removal and mailing of log files.  Logrotate can be set to handle a log file daily, weekly, monthly or when the log file gets to a certain size.  Normally, logrotate runs as a daily cron job.
|-
| '''lvm2'''
| Logical Volume Manager version 2
| Heinz Mauelshagen's LVM (Logical Volume Manager) for Linux. LVM adds an additional layer between the physical peripherals and the low-level I/O interface to get a logical view of disks.  This allows the concatenation of several disks (so-called physical volumes or PVs) to form a storage pool (so-called Volume Group or VG) with allocation units called physical extents (called PE).  With LVM, you can extend, resize, or relocate storage dynamically.
|-
| '''mdadm'''
| Manage RAID arrays
| mdadm is a utility program for creating, managing, and monitoring Linux MD (Software RAID) devices.  Unlike the older raidtools package, mdadm is a single program (which should make it easier to use).
|-
| '''module-init-tools'''
| Kernel module utilities
| Utilities to load and unload kernel modules.  These are used on Linux to load extra drivers or other features into the running kernel.
|-
| '''openssl-solibs'''
| OpenSSL shared libraries
| These shared libraries provide encryption routines required by programs such as openssh.  They are also used by KDE's Konqueror web browser to provide secure web connections.
|-
| '''patch'''
| Apply a diff file to an original file or files
| Patch is a utility used to apply diffs (or patches) to files, which are usually source code.
|-
| '''pciutils'''
| PCI utilities
| lspci displays detailed information about all PCI buses and devices in the system, replacing the original /proc/pci interface. setpci allows reading from and writing to PCI device configuration registers.  For example, you can adjust the latency timers with it.
|-
| '''pcmciautils'''
| Utilities for using PCMCIA cards with 2.6+ kernels
| This package provides PCMCIA tools that replace the pcmcia-cs tools used with the 2.4.x Linux kernel.  PCMCIA cards are commonly used in laptops to provide expanded capabilities such as network connections, modems, increased memory, and more.
|-
| '''pkgtools'''
| The Slackware package maintenance system
| This package contains utilities for handling Slackware packages. Included are the command line utilities 'installpkg', 'removepkg', 'makepkg', 'explodepkg', and 'upgradepkg' that install, remove, build, examine, and upgrade software packages.  Also included are  'pkgtool', a menu based program for installing packages, removing packages, or viewing the packages that are installed on the system, documentation (man pages), and a few other system admin scripts.
|-
| '''procps'''
| Utilities for displaying process information
| The procps package provides the classic set of utilities used to display information about the processes currently running on the machine.
|-
| '''quota'''
| Linux disk quota utilities
| An implementation of the diskquota system for the Linux operating system to keep those greedy users from gobbling up 100% of the hard drive space.  Works with ext2, ext3, reiserfs, and xfs filesystems.
|-
| '''reiserfsprogs'''
| ---
| These utilities are used for Reiserfs.  Reiserfs is a file system based on balanced tree algorithms.
|-
| '''rpm2tgz'''
| A tool for converting an RPM archive into a tar+gz one
| Converts RPM format to Slackware's GNU tar + GNU zip format.  (view converted packages with "less", install and remove with "installpkg", "removepkg", "pkgtool", or manually with "tar"). Converted packages come with no warranty.  ;-)
|-
| '''sdparm'''
| Fetch and change SCSI attributes
| sdparm is a utility for listing and potentially changing SCSI disk parameters.  More generally it can be used on any device that uses a SCSI command set.  Apart from SCSI disks, examples of devices that use SCSI command sets are ATAPI CD/DVD drives, SCSI and ATAPI tape drives and SCSI enclosures.
|-
| '''sed'''
| Stream editor
| This is the GNU version of sed, a stream editor.  A stream editor is used to perform basic text transformations on an input stream (a file or input from a pipeline).  It is sed's ability to filter text in a pipeline which distinguishes it from other types of editors. sed is a required package (it is needed by many system scripts).
|-
| '''shadow'''
| Shadow password suite
| This set of login related programs utilizes an alternate, non-readable file to contain the actual encrypted passwords.  This is presumed to increase system security by increasing the difficulty with which system crackers obtain encrypted passwords. This package provides 'login', which is needed to log into the system.
|-
| '''slocate''' 
| Secure Locate
| Slocate is an enhanced version of locate, a command to help you locate files on the system.  Like the original version of locate, Slocate maintains a database of files on the system, updating it nightly. Unlike the original, Slocate indexes every file on the machine rather than only the ones that can be seen by everyone.  The "secure" part of slocate is that it will only return matches if the user is allowed to see the files.
|-
| '''smartmontools'''
| Hard drive monitoring utilities
| SMARTMONTOOLS contains utilities that control and monitor storage devices using the Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) system build into ATA and SCSI Hard Drives. This is used to check the reliability of the hard drive and to predict drive failures.  SMARTMONTOOLS Version 5.x is designed to comply to the ATA/ATAPI-5 specification (Revision 1).  Future releases of SMARTMONTOOLS (Versions 6.x and 7.x) will comply with the ATA/ATAPI-6 and ATA/ATAPI-7 specifications.
|-
| '''sysfsutils'''
| Utilities for the sysfs filesystem
| The purpose of this package is to provide a set of utilities for interfacing with sysfs, a virtual filesystem in Linux kernel versions 2.6+ that provides a tree of system devices.  While a filesystem is a very useful interface, a library (libsysfs) is also included that will hopefully make it easier for applications to query system devices and their attributes.
|-
| '''sysklogd'''
| Linux system logging utilities
| Dr. Greg Wettstein and Stephen Tweedie's syslogd/klogd. This package contains a modified version of syslogd for the Linux environment.  An additional utility, klogd, is included which allows kernel logging to be directed through the syslogd facility. Syslogd and klogd are started when your system boots.
|-
| '''syslinux'''
| SYSLINUX/PXELINUX/ISOLINUX boot loaders
| SYSLINUX is a boot loader for the Linux operating system which operates off an MS-DOS/Windows FAT filesystem.  This is used by the Slackware makebootdisk script to create system boot floppies. Also included are PXELINUX and ISOLINUX, boot loaders for booting from a network server or CD-ROM.
|-
| '''sysvinit'''
| init, the parent of all processes
| System V style init programs by Miquel van Smoorenburg that control the booting and shutdown of your system.  These support a number of system runlevels, each with a specific set of utilities spawned. For example, the normal system runlevel is 3, which starts agetty on virtual consoles tty1 - tty6.  Runlevel 4 starts xdm. Runlevel 0 shuts the system down.
|-
| '''sysvinit-functions'''
| /etc/init.d/functions
| This is the /etc/init.d/functions file, the typical sysvinit-style directories, and a few supporting binaries.  Using this system, subdirectories of /etc/rc.d/ are searched for scripts (which are usually symlinks to the script in /etc/init.d/ or /etc/rc.d/init.d/). The links must start with S to start a script or K to stop (kill) it. For the most part, these are useful for running software developed for other versions of Linux.
|-
| '''sysvinit-scripts'''
| The basic scripts used to boot your machine
| These are the Slackware boot scripts, which are needed to start the machine.  Sysvinit looks for these in /etc/rc.d/.
|-
| '''tar'''
| Archiving utility
| This is the GNU version of tar, an archiving program designed to store and extract files from an archive file known as a tarfile.  A tarfile may be made on a tape drive, however, it is also common to write a tarfile to a normal file. Slackware's package system uses tarfiles compressed with GNU gzip.
|-
| '''time'''
| The GNU time command for measuring program resource use
| The `time' command runs another program, then displays information about the resources used by that program, collected by the system while the program was running. 
|-
| '''tree'''
| A program to display a directory tree
| Tree is a recursive directory listing program that produces a depth indented listing of files, which is colorized ala dircolors if the LS_COLORS environment variable is set and output is to tty.  With no arguments, tree lists the files in the current directory.
|-
| '''udev'''
| Dynamic device directory system
| udev provides a dynamic device directory containing only the files for the devices which are actually present.  It creates or removes device node files usually located in the /dev directory.
|-
| '''usbutils'''
| USB utilities
| lsusb displays detailed information about all USB buses and devices in the system. usbmodules lists the kernel modules for a plugged in USB device.
|-
| '''utempter'''
| utmp updating library and utility
| The utempter package provides a utility and shared library that allows terminal applications such as xterm and screen to update /var/run/utmp and /var/log/wtmp without requiring root privileges.
|-
| '''util-linux'''
| A huge collection of essential utilities
| The util-linux package is a huge collection of random utilities that are essential to run a Linux system.  This package includes the util-linux package from ftp.kernel.org, plus some related programs from other sources such as adjtimex, bsdstrings, net-tools (only for 'hostname', a complete version is in the tcpip package), schedutils, setserial, and ziptool.
|-
| '''which'''
| Shows the full path to shell commands
| GNU 'which' takes one or more arguments.  For each of its arguments it prints to stdout the full path of the executables that would have been executed when this argument had been entered at the shell prompt.  It does this by searching for an executable or script in the directories listed in the environment variable PATH using the same algorithm as bash(1).  'Which' is a built-in function in many shells.
|-
| '''xfsprogs'''
| Tools to use the XFS filesystem
| XFS is a high performance journaling filesystem which originated on the SGI IRIX platform.  It is completely multi-threaded, can support large files and large filesystems, extended attributes, variable block sizes, is extent based, and makes extensive use of Btrees (directories, extents, free space) to aid both performance and scalability.
|-
|}

=== Package group [AP] ===

{| border="1" cellspacing="0" cellpadding="5"
! Package
! Short Description
! Long Description
|-
| '''at'''
| Delayed command execution
| at and batch read shell commands from standard input (or a specified file) storing them as a job to be scheduled for execution at a later time.
|-
| '''cdrdao'''
| CD burning utility
| cdrdao burns proper disc-at-once (DAO) audio discs.  In DAO mode the disc is written in one shot, so you don't have to have irritating 2 second gaps interrupting a live recording.
|-
| '''cdrtools'''
| Tools for mastering and writing compact discs.
| cdda2wav -- CD audio sampling utility. cdrecord -- burn discs in most ATAPI and SCSI CD-R drives. mkisofs  -- create ISO9660/HFS/Joliet CD-ROM images. mkzftree -- compress a file tree to make a compressed CD-ROM.
|-
| '''diffutils'''
| Finds differences between files
| The GNU diff utilities finds differences between files.  A major use for this package is to make source code patches.
|-
| '''dmapi'''
| Data Management API library
| A library required to use the Data Management API (DMAPI). This interface is defined in the X/Open document 'Systems Management: Data Storage Managment (XDSM) API' dated February 1997. The DMAPI library is used by the xfsdump utility.
|-
| '''dmidecode'''
| DMI table decoder
| dmidecode is a tool for dumping a computer's DMI table (some say SMBIOS) contents in a human-readable format.  This table contains a description of the system's hardware components, as well as other useful pieces of information such as serial numbers and BIOS revision.
|-
| '''dvd+rw-tools'''
| ---
| A collection of tools to master DVD+RW/+R/-R/-RW media.
|-
| '''groff'''
| Document formatting system
| The GNU groff package provides versions of troff, nroff, eqn, tbl, and other Unix text-formatting utilities.  Groff is used to 'compile' man pages stored in groff/nroff format into a form which can be printed or displayed on the screen.  These man pages are stored in compressed form in the /usr/man/man? directories.
|-
| '''lm_sensors'''
| Hardware monitoring package
| lm_sensors provides tools for monitoring the temperatures, voltages, and fans of Linux systems with hardware monitoring devices.  Included are text-based tools for sensor reporting, and a library for sensors access called libsensors.  It also contains tools for sensor hardware identification and I2C bus probing. IMPORTANT NOTE:  If you have a Thinkpad, please read the warnings in the README.thinkpad file.  [http://www.thinkwiki.org/wiki/Problem_with_lm-sensors lm_sensors has been known to cause damage to some Thinkpads].
|-
| '''lsof'''
| List open files
| Lsof is a Unix-specific tool.  Its name stands for "LiSt Open Files", and it does just that.  It lists information about files that are open by the processes running on the system.
|-
| '''lsscsi'''
| List SCSI devices or hosts, and their attributes
| Uses information in sysfs to list scsi devices (or hosts) currently attached to the system.  Options can be used to control the amount and form of information provided for each device.
|-
| '''man'''
| Format and display the on-line manual pages
| The man package is a collection of tools used for searching and reading the online system documentation.  In fact, on most UNIX-like operating systems it is the primary means of finding out how programs on the system work.  For example, 'man man' will display the documentation for man itself. Man requires the groff text processing package.
|-
| '''man-pages'''
| System documentation
| Man pages are online documentation for Linux.  This package includes many section 1, 2, 3, 4, 5, 7, and 8 man pages for Linux.
|-
| '''mc'''
| Midnight Commander file manager
| The Midnight Commander is a Norton Commander clone, a program that manipulates and manages files and directories.  Useful, fast, and has color displays on the Linux console.  Mouse support is provided through the gpm mouse server.  This is a lightweight compilation of mc for use on the text console or in an xterm.
|-
| '''most'''
| Another pager, like 'more' and 'less'
| most is a paging program that displays, one windowful at a time,  the contents of a file on a terminal.  Unlike other well-known paging programs, most supports multiple windows and can scroll left and right.  Why settle for less?
|-
| '''screen'''
| Screen manager with VT100/ANSI terminal emulation
| Screen is a full-screen window manager that multiplexes a physical terminal between several processes (typically interactive shells). Each virtual terminal provides the functions of a DEC VT100 terminal and several control functions from the ISO 6492 (ECMA 48, ANSI X3.64) and ISO 2022 standards (e.g. insert/delete line and support for multiple character sets).  There is a scrollback history buffer for each virtual terminal and a copy-and-paste mechanism that allows moving text regions between windows.
|-
| '''sudo'''
| Give limited root privileges to certain users
| 'sudo' is a command that allows users to execute some commands as root.  The /etc/sudoers file (edited with 'visudo') specifies which users have access to sudo and which commands they can run.  'sudo' logs all its activities to /var/log/ so the system administrator can keep an eye on things.
|-
| '''sysstat'''
| System performance monitoring tools
| The sysstat utilities are a collection of performance monitoring tools for Linux.  These include sar, sadf, mpstat, iostat and sa tools.
|-
| '''texinfo'''
| GNU software documentation system
| 'Texinfo' is a documentation system that uses a single source file to produce both on-line information and printed output.  Using Texinfo, you can create a printed document with the normal features of a book, including chapters, sections, cross references, and indices.  From the same Texinfo source file, you can create a menu-driven, on-line Info file with nodes, menus, cross references, and indices. This package is needed to read the documentation files in /usr/info.
|-
| '''vim'''
| Vi IMproved
| Vim is an almost compatible version of the UNIX editor vi.  Many new features have been added:  multi level undo, command line history, filename completion, block operations, and more. Vim's development is led by Bram Moolenaar. This package also contains the Exuberant Ctags program written by Darren Hiebert.
|-
| '''xfsdump'''
| Backup tools for the XFS filesystem
| The xfsdump package contains the xfsdump and xfsrestore utilities for backing up and restoring XFS partitions.  xfsdump examines files in a filesystem, determines which need to be backed up, and copies those files to a specified disk, tape or other storage medium.  xfsrestore performs the inverse function of xfsdump; it can restore a full or incremental backup of a filesystem.
|-
|}

&amp;nbsp;

=== Package group [D] ===

{| border="1" cellspacing="0" cellpadding="5"
! Package
! Short Description
! Long Description
|-
| '''autoconf'''
| Generate configuration scripts
| GNU autoconf is an extensible package of m4 macros that produce shell scripts to automatically configure software source code packages. These scripts can adapt the packages to many kinds of UNIX-like systems without manual user intervention.  Autoconf creates a configuration script for a package from a template file that lists the operating system features that the package can use, in the form of m4 macro calls.  You must install the "m4" package to be able to use autoconf.
|-
| '''automake'''
| A Makefile generator
| This is Automake, a Makefile generator.  It was inspired by the 4.4BSD make and include files, but aims to be portable and to conform to the GNU standards for Makefile variables and targets.  Automake is a Perl script.  The input files are called Makefile.am.  The output files are called Makefile.in; they are intended for use with Autoconf.  Automake requires certain things to be done in your configure.in.  You must install the "m4" and "perl" packages to be able to use automake.
|-
| '''binutils'''
| GNU binary development tools
| Binutils is a collection of binary utilities.  It includes "as" (the portable GNU assembler), "ld" (the GNU linker), and other utilities for creating and working with binary programs. These utilities are REQUIRED to compile C, C++, Objective-C, Fortran, and most other programming languages.
|-
| '''bison'''
| Parser generator similar to yacc
| GNU "Bison" is a general-purpose parser generator that converts a grammar description for an LALR(1) context-free grammar into a C program to parse that grammar. Bison is upward compatible with Yacc:  all properly-written Yacc grammars ought to work with Bison with no change.  Anyone familiar with Yacc should be able to use Bison with little trouble.
|-
| '''doxygen'''
| Documentation generator
| Doxygen is a documentation system for C++, C, Java, IDL, and to some extent PHP and C#.  Doxygen generates project documentation using special documentation blocks in the source code, easing the process of keeping docs and code in sync.  Doxygen produces documentation in several output formats, including HTML, LaTeX, man pages, RTF, XML, compressed HTML, PostScript, and PDF.
|-
| '''flex'''
| fast lexical analyzer generator
| flex is a tool for generating programs that perform pattern matching on text.  flex is a rewrite of the AT&amp;T Unix lex tool (the two implementations do not share any code, though), with some extensions (and incompatibilities).
|-
| '''gcc'''
| Base GCC package with C support
| This package contains those parts of the compiler collection needed to compile C code.  Other packages add C++, Fortran, Objective-C, and Java support to the compiler core.
|-
| '''gcc-g++'''
| C++ for GCC
| C++ support for the GNU Compiler Collection. This package contains those parts of the compiler collection needed to compile C++ code.  The base gcc package is also required.
|-
| '''gettext-tools'''
| ---
| The GNU gettext-tools package is useful for authors and maintainers of internationalized software, or for anyone compiling programs that use the gettext functions.  This package provides the needed tools and library functions for the handling of messages in different languages. Some other GNU packages use the gettext program (included in this package) to internationalize the messages given by shell scripts.
|-
| '''kernel-headers'''
| Linux kernel include files
| These are the include files from the Linux kernel. You'll need these to compile most system software for Linux.
|-
| '''libtool'''
| A generic library support script
| This is GNU Libtool, a generic library support script. Libtool hides the complexity of using shared libraries behind a consistent, portable interface.  To use libtool, add the new generic library building commands to your Makefile, Makefile.in, or Makefile.am.  See the documentation for details. You must install the "m4" package to be able to use libtool.
|-
| '''m4'''
| An implementation of the UNIX macro processor
| This is GNU m4, a program which copies its input to the output, expanding macros as it goes.  m4 has built-in functions for including named files, running commands, doing integer arithmetic, manipulating text in various ways, recursion, etc...  Macros can also be user-defined, and can take any number of arguments.
|-
| '''make'''
| GNU make utility to maintain groups of programs
| This is the GNU implementation of make, which was written by Richard Stallman and Roland McGrath.  The purpose of the make utility is to determine automatically which pieces of a large program need to be recompiled, and issue the commands to recompile them. This is needed to compile just about any major C program, including the Linux kernel.
|-
| '''perl'''
| Practical Extraction and Report Language
| Larry Wall's "Practical Extraction and Report Language".  Perl is a language optimized for scanning arbitrary text files, extracting information from those text files, and printing reports based on that information.  It's also a good language for many system management tasks.  The language is intended to be practical (easy to use, efficient, complete) rather than beautiful (tiny, elegant, minimal).
|-
| '''pkg-config'''
| ---
| pkg-config is a system for managing library compile/link flags that works with automake and autoconf.  It replaces the ubiquitous *-config scripts you may have seen with a single tool.  See the man page that comes with pkg-config for full documentation.
|-
|}

&amp;nbsp;

=== Package group [F] ===

{| border="1" cellspacing="0" cellpadding="5"
! Package
! Short Description
! Long Description
|-
| '''linux-faqs'''
| Linux FAQ collection from ibiblio.org
| Frequently Asked Questions (and answers!) on many Linux topics. Some of the FAQs included in this package: ATAPI-FAQ, AfterStep-FAQ, BLFAQ (Brief Linux FAQ), Ftape-FAQ, GCC-SIG11-FAQ, Joe-Command-Reference, the Linux-FAQ, PPP-FAQ, SMP-FAQ, and the Threads-FAQ. These FAQs will be installed under /usr/doc/Linux-FAQs/.
|-
| '''linux-howtos'''
| HOWTOs from the Linux Documentation Project
| Documentation on many tasks relating to Linux setup and operation. These documents will be installed in /usr/doc/Linux-HOWTOs/.
|-
|}

&amp;nbsp;

=== Package group [K] ===

{| border="1" cellspacing="0" cellpadding="5"
! Package
! Short Description
! Long Description
|-
| '''kernel-source'''
| Linux kernel source
| Source code for Linus Torvalds' Linux kernel. This is the complete and unmodified source code for the Linux kernel.
|-
|}

&amp;nbsp;

&amp;nbsp;

&amp;nbsp;

=== Package group [L] ===

{| border="1" cellspacing="0" cellpadding="5"
! Package
! Short Description
! Long Description
|-
| '''db42'''
| Berkeley database library version 4.2.x
| The Berkeley Database (Berkeley DB) library provides embedded database support for both traditional and client/server applications. This package should be installed if compatibility is needed with databases created with the Berkeley DB version 4.2.x.
|-
| '''db44'''
| Berkeley database library version 4.4.x
| The Berkeley Database (Berkeley DB) library provides embedded database support for both traditional and client/server applications. This package should be installed if compatibility is needed with databases created with the Berkeley DB version 4.4.x.
|-
| '''gdbm'''
| GNU database routines
| GNU dbm is a set of database routines that work similar to the standard UNIX dbm routines.
|-
| '''glibc'''
| GNU C libraries
| This package contains the GNU C libraries and header files.  The GNU C library was written originally by Roland McGrath, and is currently maintained by Ulrich Drepper.  Some parts of the library were contributed or worked on by other people. You'll need this package to compile programs.
|-
| '''glibc-i18n'''
| locale files from glibc
| These files go in /usr/lib/locale and /usr/share/i18n/ to provide internationalization support.  You'll need this package unless you will be using US English only.
|-
| '''libusb'''
| USB library
| This is libusb, a library which allows userspace application access to USB devices.  It is used to connect to USB devices like scanners.
|-
| '''lzo'''
| LZO Compression Library
| LZO is a portable lossless data compression library written in ANSI C. It offers pretty fast compression and very fast decompression.
|-
| '''ncurses'''
| ---
| The ncurses (new curses) library is a free software emulation of curses in System V Release 4.0, and more.  It uses terminfo format, supports pads and color and multiple highlights and forms characters and function-key mapping, and has all the other SYSV-curses enhancements over BSD curses.
|-
| '''pcre'''
| Perl-compatible regular expression library
| The pcre  library is a set of functions that implement regular expression pattern matching using the same syntax and semantics as Perl 5, with just a few differences (documented in the man page).
|-
| '''popt'''
| Command line parsing library
| popt  is a C library for parsing command line parameters.  popt  was heavily influenced by the getopt() and getopt_long() functions, but it improves on them by allowing more powerful argument expansion.  popt can parse arbitrary argv[] style arrays and automatically set variables based on command line arguments.  popt  allows command line arguments to be aliased via configuration files and includes utility functions for parsing arbitrary strings into argv[] arrays using shell-like rules.
|-
| '''readline'''
| line input library with editing features
| The GNU Readline library provides a set of functions for use by applications that allow users to edit command lines as they are typed in.  Both Emacs and vi editing modes are available.  The Readline library includes additional functions to maintain a list of previously entered command lines, to recall and perhaps edit those lines, and perform csh-like history expansion on previous commands.
|-
| '''zlib'''
| Compression library
| zlib is a general purpose thread safe data compression library.
|-
|}

&amp;nbsp;

=== Package group [N] ===

{| border="1" cellspacing="0" cellpadding="5"
! Package
! Short Description
! Long Description
|-
| '''bitchx'''
| Chat client
| BitchX is an advanced Internet Relay Chat (IRC) client.
|-
| '''dhcpcd'''
| DHCP client daemon
| The DHCP client program dhcpcd is used to connect to a network by contacting a DHCP server.  dhcpcd gets an IP address and other information from a corresponding DHCP server, configures the network interface automatically, and tries to renew the lease time according to RFC2131 or RFC1541 depending on the command line option.
|-
| '''inetd'''
| Internet super-server
| This is a program to listen for connections on certain Internet sockets and invokes a program to service the request.  Essentially, inetd allows running one daemon to invoke several others, reducing load on the system.  Many of the network services are run through inetd, so you'll probably need it. This version of inetd was ported from OpenBSD.
|-
| '''iproute2'''
| IP routing utilities
| These are tools used to administer many advanced IP routing features in the kernel.  See Configure.help in the kernel documentation (search for iproute2) for more information on which kernel options these tools are used with.
|-
| '''iptables'''
| IP packet filter administration
| Iptables can be used to build internet firewalls based on stateless and stateful packet filtering, use NAT and masquerading for sharing internet access if you don't have enough public IP addresses, use NAT to implement transparent proxies, aid the tc and iproute2 systems used to build sophisticated QoS and policy routers, do further packet manipulation (mangling) like altering the TOS/DSCP/ECN bits of the IP header, and much more.
|-
| '''iptraf'''
| ---
| IPTraf is a console-based network monitoring program for Linux that displays information about IP traffic such as:  Current TCP connections, types of IP packets, packet and byte counts, TCP/UDP counts by ports, packet counts by packet sizes, packet and byte counts by IP address, interface activity, flag statuses on TCP packets, and other LAN station statistics.
|-
| '''iputils''' 
| a collection of common network tools
| The iputils package contains network tools found on nearly all *NIX systems, along with an extra or two.  Some of the utilities found here include arping, clockdiff, ping, ping6, rarpd, rdisc, tracepath, tracepath6, and traceroute6.
|-
| '''lftp'''
| Command line file transfer program
| lftp is a program that allows sophisticated ftp and http connections to other hosts.  lftp can handle many file access methods including ftp, ftps, http, https, hftp, fish and file.  Every operation in lftp is reliable, that is any non-fatal error is ignored and the operation is retried.  lftp has shell-like command syntax.  lftp has a built in mirror feature which can download or upload a whole directory tree. To learn about many more features of lftp, see 'man lftp'.
|-
| '''libgcrypt'''
| General purpose crypto library
| libgcrypt  is a general purpose crypto library based on the code used in GnuPG.
|-
| '''libgpg-error'''
| GnuPG Error Definitions Library
| This is a library that defines common error values for all GnuPG components.  Among these are GPG, GPGSM, GPGME, GPG-Agent, libgcrypt , Libksba, DirMngr, Pinentry, SmartCard Daemon, and more.
|-
| '''lynx'''
| Text mode browser
| Lynx is a distributed hypertext browser with full World Wide Web capabilities.  Lynx can be used to access information on the World Wide Web, or to build information systems intended primarily for local access.  For example, Lynx has been used to build several Campus Wide Information Systems (CWIS).  
|-
| '''mtr'''
| A network diagnostic tool
| mtr combines the functionality of the 'traceroute' and 'ping' programs in a single network diagnostic tool.
|-
| '''net-tools'''
| Base Linux networking utilities
| This is the core collection of tools such as "ifconfig" and "route" used to configure networking on Linux.  You won't be able to do much networking without this package and the network-scripts.
|-
| '''netkit-ftp'''
| The old BSD FTP client
| Ftp is the user interface to the Internet standard File Transfer Protocol.  The program allows a user to transfer files to and from a remote network site. This is a program of mostly historical value.  For a more powerful command-line FTP client, look at something like lftp.
|-
| '''netket-rsh'''
| The BSD rsh/rcp/rlogin clients and daemon
| The old BSD rsh suite.  Note that none of these programs provide encryption or strong authentication of network connections.  As such, their use is discouraged.  The "ssh" protocol and package is a cryptographically secure replacement.
|-
| '''netwatch'''
| ---
| Netwatch allows a user (superuser) to monitor activity on the network. The monitor includes statistics on transmitted and received packets, bytes, protocol, and more.
|-
| '''network-scripts'''
| Scripts to configure a network
| These are the basic scripts and files used to define a network and configure network interfaces on Linux.  Most of the original /etc files were written by Fred N. van Kempen, or borrowed from BSD. The rc.inet1 and rc.inet2 scripts were mostly written by Patrick Volkerding, with suggestions and fixes from hundreds of contributors over the years.
|-
| '''nmap''' 
| Network scanner
| Nmap ("Network Mapper") is an open source utility for network exploration or security auditing.  It was designed to rapidly scan large networks, although it works fine against single hosts.  Nmap uses raw IP packets in novel ways to determine what hosts are available on the network, what services (ports) they are offering, what operating system (and OS version) they are running, what type of packet filters/firewalls are in use, and dozens of other characteristics.  Nmap runs on most types of computers, and both console and graphical versions are available.
|-
| '''ntp'''
| Network Time Protocol daemon
| The Network Time Protocol (NTP) is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio or satellite receiver or modem. It provides client accuracies typically within a millisecond on LANs and up to a few tens of milliseconds on WANs relative to a primary server synchronized to Coordinated Universal Time (UTC) via a Global Positioning Service (GPS) receiver, for example.
|-
| '''openssh'''
| Secure Shell daemon and clients
| ssh (Secure Shell) is a program for logging into a remote machine and for executing commands on a remote machine.  It is intended to replace rlogin and rsh, and provide secure encrypted communications between two untrusted hosts over an insecure network.  sshd (SSH Daemon) is the daemon program for ssh.
|-
| '''openssl'''
| Secure Sockets Layer toolkit
| The OpenSSL certificate management tool and the shared libraries that provide various encryption and decryption algorithms and protocols.
|-
| '''tcp_wrappers'''
| TCP/IP daemon wrapper library and utilities
| With this package you can monitor and filter incoming requests for network services for access control, and detection things like host name spoofing and host address spoofing.  Nearly all the network daemons on Slackware are "wrapped" using this library, and most daemons in /etc/inetd.conf use tcp_wrappers' tcpd wrapper daemon. If you plan to do much networking, you will need tcp_wrappers.
|-
| '''telnet'''
| The telnet client and daemon
| telnet supports the original DARPA telnet interactive communication protocol.  As connecting to a telnetd server transmits your password over the network in cleartext, telnet's use as a login protocol has been mostly superceded by the use of ssh and sshd.  However, the telnet client is still a very handy tool, and telnetd may still have some uses on networks that are known to be secure. telnet and telnetd were ported from BSD.
|-
| '''traceroute'''
| IP packet route tracing utility
| The traceroute utility displays the route used by IP packets on their way to a specified network host.  Traceroute will display the IP number and host name (if possible) of all the machines along the route taken by the packets.  If you're having network connectivity problems, traceroute can show you where the trouble is located.
|-
| '''wget'''
| A non-interactive network retriever
| GNU Wget is a free network utility to retrieve files from the World Wide Web using HTTP and FTP, the two most widely used Internet protocols.  It works non-interactively, thus enabling work in the background after having logged off.
|-
| '''whois'''
| whois directory client
| This is an enhanced whois (RFC 954) client derived from the BSD and RIPE whois programs.  It can automatically select the appropriate whois server for most queries.
|-
| '''wireless-tools'''
| Utilities for wireless networking
| This package contains tools and a library used for configuring wireless networking interfaces: iwconfig (the main wireless tool), iwlist (display more detailed information than iwconfig), iwspy (get stats per MAC address and more), iwpriv (set driver private ioctls), iwgetid (show the ESSID or NWID of a device), iwevent (display wireless events), ifrename (rename a network interface).
|-
| '''wpa_supplicant'''
| WPA/WPA2/IEEE 802.1X Supplicant
| wpa_supplicant is a WPA Supplicant for Linux with support for WPA and WPA2 (IEEE 802.11i / RSN). Supplicant is the IEEE 802.1X/WPA component that is used in the client stations. It implements key negotiation with a WPA Authenticator and it controls the roaming and IEEE 802.11 authentication/association of the wlan driver.
|}

&amp;nbsp;

=== How to install this minimal system ===

You only need the first Slackware CD to do this. 

* Install Slackware as you would do normally. 

* In the '''PACKAGE SERIES SELECTION''' screen, select package sets '''A''', '''AP''', '''D''', '''F''', '''K''', '''L''' and '''N'''. 

Now you have two choices:

* '''Manual selection''': at the next screen ('''SELECT PROMPTING MODE'''), choose the '''expert''' option, and manually select (or unselect) every single package.

* '''Using tagfiles''': this method is described in detail [http://www.slackbasics.org/html/chap-pkgmgmt.html#chap-pkgmgmt-tagfiles here]. I provide a set of tagfiles which spares you the chore of manual package selection. You can download it [http://www.kikinovak.net/tagfiles/base.tar.bz2 here].

&amp;nbsp;</text>
    <sha1>78c83d9a72d5dc6be7c4e2d9637f6d8591552f34</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>User:Alienbob</title>
  <ns>2</ns>
  <id>14</id>
  <revision>
    <id>19</id>
    <timestamp>2009-05-28T11:23:49Z</timestamp>
    <contributor>
      <username>Alienbob</username>
      <id>9</id>
    </contributor>
    <comment>Alien introduction</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="741" xml:space="preserve">* Real Name: Eric Hameleers
* IRC Nickname: alienBOB
* E-Mail: alien(.AT.)slackware.com
* My Homepage: http://slackware.com/~alien/
* My Wiki: http://alien.slackbook.org/
* My Blog: http://alien.slackbook.org/blog/

I have a lot of SlackBuilds and Slackware packages in my repository.
This is a list of URLs where you can find these:
* [http://slackware.com/~alien/slackbuilds/ master site] ([http://slackware.com/~alien/slackbuilds/ChangeLog.rss RSS feed])
** [http://slackware.org.uk/people/alien/slackbuilds/ UK mirror]
* [http://slackware.org.uk/people/alien/restricted_slackbuilds/ packages with export restrictions] ([http://slackware.org.uk/people/alien/restricted_slackbuilds/ChangeLog.rss RSS feed]). Think of lame, faac, libdvdcss.</text>
    <sha1>5f02c8bb3d95567b2c0c1ec34c255ce32e1ff3d2</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>SlackBuild Scripts</title>
  <ns>0</ns>
  <id>15</id>
  <revision>
    <id>21</id>
    <timestamp>2009-05-28T17:37:32Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Created page with 'SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source.   While not necessary to compile and create packages on Slack...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2966" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5790ce4393af0df4fbef5d93d3a01eb0177d0d87</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Writing A SlackBuild Script</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>22</id>
    <timestamp>2009-05-28T17:39:45Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Created page with '[[Category:Tutorials]]  = Introduction =   Originally written by Florian Mueller jjdm@jjdm.org  Substantial cleanup and enhancement by Robby Workman (rworkman)  If you use slackw...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19436" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.

 #!/bin/sh

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/</text>
    <sha1>fe66c82092eb710e5a3f0fe9014afee62a7232f2</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Slack-desc</title>
  <ns>0</ns>
  <id>17</id>
  <revision>
    <id>23</id>
    <timestamp>2009-05-28T17:46:19Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Created page with '[[Category:Tutorials]]  = Introduction =   Originally written by Florian Mueller jjdm@jjdm.org  Substantial cleanup and enhancement by Robby Workman (rworkman)  If you use slackw...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19436" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.

 #!/bin/sh

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/</text>
    <sha1>fe66c82092eb710e5a3f0fe9014afee62a7232f2</sha1>
  </revision>
  <revision>
    <id>24</id>
    <parentid>23</parentid>
    <timestamp>2009-05-28T17:47:48Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1618" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: Summary of application name and function (one line only)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname: 
 appname: It's a good idea to include a link to the application's homepage too.
 appname: 

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>c24c887449d4942b75d125ca6278c76190d4c962</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Packages</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>25</id>
    <timestamp>2009-05-28T20:07:13Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1946" xml:space="preserve">Slackware's package management system utilizes .tgz tarballs as its standard package format. These tarballs are  tar.gz archives which contain Slackware built binaries, support files, a description file and installation script. Although they can be unzipped and untarred like a normal archive, they are (usually) binary-only packages intended to be installed through Slackware's provided package management tools.

Information about a package is stored in two ways, in the filename of the package and a description file inside that package.

==Package Tools==
See the respective manual pages for more information on each of the following commands.

&lt;code&gt;pkgtool&lt;/code&gt;

&lt;code&gt;installpkg&lt;/code&gt;

&lt;code&gt;removepkg&lt;/code&gt;

&lt;code&gt;explodepkg&lt;/code&gt;

&lt;code&gt;makepkg&lt;/code&gt;

&lt;code&gt;upgradepkg&lt;/code&gt;

==Slackware Package Layout==
A typical Slackware package is laid out as such:
 ./
 ./install/doinst.sh
 ./install/slack-desc
 [./usr/bin]
 [./usr/lib]
 [...]

The install directory as well as the files within it will be deleted after the installation of the package to the root install directory (usually '/'). The install directory is not necessarily required for the most basic packages but allows additional functionality: [[slack-desc]] contains the package description, and [[doinst.sh]] contains post-installation instructions such as creating symbolic links.

Every other file within the package is simply untarred (extracted) to the root directory. Most of these files are in standard locations. 

There are other special files within packages: 

'''usr/doc/&lt;appname&gt;&lt;version&gt;'''
All documentation included with the package (such as README, INSTALL, ChangeLog, docs/, etcetera) should be placed in this directory. Some of the files in this directory should be manually copied from the source archive, since Makefiles usually don't copy these documentation files to the package build tree.

==Making Slackware Packages==
See [[Building A Package]]</text>
    <sha1>94daaefc38da7411307d08fa34c43d2683e04278</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Doinst.sh</title>
  <ns>0</ns>
  <id>19</id>
  <revision>
    <id>26</id>
    <timestamp>2009-05-28T20:09:56Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2360" xml:space="preserve">This script is usually included under ./install within Slackware [[packages]] and contains post-install actions.

Usually automatically created by [[makepkg]] for cleaning up and recreating symbolic links, advanced packagers may wish to include further configuration instructions here to be executed after files have been extracted from the .tgz package.

== Files ==

Within packages, doinst.sh is located in install/.

After installation, the doinst.sh scripts are placed in /var/log/scripts, and renamed into the package name.

== Examples ==

=== Handling symbolic links ===

The package 'udev-064-i486-2' (from Slackware 10.2), contains a doinst.sh script which includes the following:

 ( cd etc/hotplug.d/default ; rm -rf 10-udev.hotplug )
 ( cd etc/hotplug.d/default ; ln -sf /sbin/udevsend 10-udev.hotplug )
 ( cd usr/man/man8 ; rm -rf udevsend.8.gz )
 ( cd usr/man/man8 ; ln -sf udevd.8.gz udevsend.8.gz )

Thus, during installation of this package, it will delete 'etc/hotplug.d/default/10-udev.hotplug' and 'usr/man/man8/udevsend.8.gz', then immediately recreate them using symbolic links.

This part of doinst.sh scripts is the most common, and is almost always generated by [[makepkg]] automatically during the creation of the package. In fact, 'makepkg' strongly suggests handling symbolic links using the doinst.sh script this way.

=== Configuration Files ===

The package 'vim-7.0.109-i486-1' (from Slackware 11.0), contains a doinst.sh script which includes the following:

 config() {
  NEW="$1"
  OLD="$(dirname $NEW)/$(basename $NEW .new)"
  # If there's no config file by that name, mv it over:
  if [ ! -r $OLD ]; then
    mv $NEW $OLD
  elif [ "$(cat $OLD | md5sum)" = "$(cat $NEW | md5sum)" ]; then # toss the redundant copy
    rm $NEW
  fi
  # Otherwise, we leave the .new copy for the admin to consider...
 }
 config usr/share/vim/vimrc.new

The config() function checks whether the configuration file in the package (vimrc) already exists on the system, or is exactly the same as the new one included in the package; if it exists and is not the same as the package's copy, it will not overwrite the old one but instead will be copied with a .new file extension (vimrc.new).

This is a common, and the preferred, way of dealing with configuration files in Slackware packages.

== See Also ==
* [[Packages]]
* [[Building A Package]]</text>
    <sha1>62ca7fa7ad16df9a866b1bcecd06a6c410d0a590</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Build Environment</title>
  <ns>0</ns>
  <id>20</id>
  <revision>
    <id>27</id>
    <timestamp>2009-05-28T20:12:40Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2747" xml:space="preserve">= Introduction =
The purpose of this document is to give you several ideas on how to set up a good building environment (directory structure and such) for making Slackware packages from SlackBuild scripts.

Hopefully, you can see what works for several different people here.  The definition of "good" is largely dependent upon personal preference, but all of these would be classified as "good" for the individuals using them.

= Individual Setups =

== jjdm ==

My directory structure is as follows:

'''/home/slackware/'''
The slackware home directory. This directory (and all subdirectories) are owned by the group "packager" (of which root and my user account are members on my system). 

'''/home/slackware/source'''
In this directory I've placed the whole slackware-source because maybe I have to temporarily build another package to build a new one because of header files and stuff. 

'''/home/slackware/source/myslackware/'''
This is where I build all my packages. Now they are unorganized but you can organize them in different topics like they're in Slackware. 

'''/home/slackware/source/myslackware/&lt;package&gt;'''
In this directory you build your package &lt;package&gt;. 

'''/home/slackware/packages'''
Place where the built packages are. 

You don't have to use such a building environment. You can place everything in your home-folder, in /root or somewhere else. The only important thing is that you always keep track of your files and packages.

BTW: You can get the Slackware source packages from your Slackware-mirror of choice. It's placed in source/.

== robw810 ==

=== Directory Structure ===
My setup is something like this:
 /shared/os_files/slackware/slackware-(version)/source/...
 /home/rworkman/build/source
 /home/rworkman/build/packages

=== Explanation of Directory Structure ===
The [code] /shared/os_files/slackware/slackware-(version)/source/ [/code] directory contains all of the source files (it's copied directly from the cdroms) from that release of Slackware.

The [code]/home/rworkman/build/source[/code] directory contains all of the sources for my SlackBuild scripts and such (it's set up basically identical to what the Slackware source directory contains).

The [code]/home/rworkman/build/packages[/code] directory contains all of the packages compiled from my sources.

=== Integration of Directory Structure with Executing SlackBuild Scripts ===

With some good environment variables declared in your SlackBuild scripts, it's relatively easy to manage this setup:
 PKG_OUT=/home/rworkman/build/packages

=== Final Thoughts ===
As always, what works for me may not be ideal for you, so adjust your expectations accordingly :)

= Other Resources =

* [[Writing_A_SlackBuild_Script]]
* [[SlackBuild_Scripts]]</text>
    <sha1>463d490fdd4bdf80295d52d2ceecb4c5d62a22c3</sha1>
  </revision>
  <revision>
    <id>28</id>
    <parentid>27</parentid>
    <timestamp>2009-05-28T20:17:15Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <minor/>
    <comment>Replaced [CODE] tags (which weren't displaying properly)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2724" xml:space="preserve">= Introduction =
The purpose of this document is to give you several ideas on how to set up a good building environment (directory structure and such) for making Slackware packages from SlackBuild scripts.

Hopefully, you can see what works for several different people here.  The definition of "good" is largely dependent upon personal preference, but all of these would be classified as "good" for the individuals using them.

= Individual Setups =

== jjdm ==

My directory structure is as follows:

'''/home/slackware/'''
The slackware home directory. This directory (and all subdirectories) are owned by the group "packager" (of which root and my user account are members on my system). 

'''/home/slackware/source'''
In this directory I've placed the whole slackware-source because maybe I have to temporarily build another package to build a new one because of header files and stuff. 

'''/home/slackware/source/myslackware/'''
This is where I build all my packages. Now they are unorganized but you can organize them in different topics like they're in Slackware. 

'''/home/slackware/source/myslackware/&lt;package&gt;'''
In this directory you build your package &lt;package&gt;. 

'''/home/slackware/packages'''
Place where the built packages are. 

You don't have to use such a building environment. You can place everything in your home-folder, in /root or somewhere else. The only important thing is that you always keep track of your files and packages.

BTW: You can get the Slackware source packages from your Slackware-mirror of choice. It's placed in source/.

== robw810 ==

=== Directory Structure ===
My setup is something like this:
 /shared/os_files/slackware/slackware-(version)/source/...
 /home/rworkman/build/source
 /home/rworkman/build/packages

=== Explanation of Directory Structure ===
The '''/shared/os_files/slackware/slackware-(version)/source/''' directory contains all of the source files (it's copied directly from the cdroms) from that release of Slackware.

The '''/home/rworkman/build/source''' directory contains all of the sources for my SlackBuild scripts and such (it's set up basically identical to what the Slackware source directory contains).

The '''/home/rworkman/build/packages''' directory contains all of the packages compiled from my sources.

=== Integration of Directory Structure with Executing SlackBuild Scripts ===

With some good environment variables declared in your SlackBuild scripts, it's relatively easy to manage this setup:
 PKG_OUT=/home/rworkman/build/packages

=== Final Thoughts ===
As always, what works for me may not be ideal for you, so adjust your expectations accordingly :)

= Other Resources =

* [[Writing_A_SlackBuild_Script]]
* [[SlackBuild_Scripts]]</text>
    <sha1>0e4ccf2eb4c3122c1246de05c4d2b8c2abea8b7b</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Contest</title>
  <ns>0</ns>
  <id>21</id>
  <revision>
    <id>29</id>
    <timestamp>2009-05-28T20:19:39Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2074" xml:space="preserve">'''This contest is completed; congratulations to Marcus'''

This page is here for those of you who wanted to create logos for slackwiki.org's contest.
Have at it!!!

From [[User:FredEmmott|Fred87]] Can i have SVGs and/or png's please :)

From [[User:erik|erik]] Mine is a png :)
----
Submitted by: [[User:Dominian|Dominian]] on Nov. 17, 2004&lt;br&gt;
http://home.insightbb.com/~mhayes/images/slackwiki_logo.png

-----------------------------------------

Submitted by: [[User:jjdm|jjdm]] on Nov. 20, 2004&lt;br/&gt;
Repainted [http://us.aminet.net/pix/trace/BOOK.jpg this book] with sodipodi, repainted the slackware-logo and added a third-party svg-tux. You can get the SVG-file at [http://mufl.politux.org/logo.svg]. If you like the logo, but not the colors, feel free to edit the SVG-file. I meen, _please_ edit the SVG if you are good in colors because I'm a little colorblind. Thanks.&lt;br/&gt;
http://mufl.politux.org/logo.png

-----------------------------------------

Submitted by: [[User:erik|erik]] on Nov. 21, 2004&lt;br/&gt;
The Wings of Slack, not mine, original from [http://subgenius.com/ The Church of the Subgenius].&lt;br/&gt;
Should fit right over the old logo (135x135), transparent bg will blend with current bg.&lt;br/&gt;
http://sl1200.org/WingsOfSlack.png

-----------------------------------------

Submitted by: [[User:buzzedlightyear|buzzedlightyear]] on Nov. 23, 2004&lt;br/&gt;
Slackware logo, cropped it from a background i found and added text.&lt;br/&gt;
http://www.slackwaregallery.com/albums/userpics/10157/slackwikilogo.png

-----------------------------------------

Submitted by: [[User:tewmten|tewmten]] on Dec. 14, 2004&lt;br/&gt;
A little penguin writing a book wich has the Slackware S on it.&lt;br/&gt;
135x135 with transparent background.&lt;br/&gt;
http://irda.mine.nu/~tewmten/SlackWiki-tew.png


----

Submitted by: [[User:v3ctor|v3ctor]] on Dec. 15, 2004&lt;br/&gt;
Just a little something.&lt;/br&gt;
http://www.geocities.com/thelucid99/slackwiki.png

----
Submitted by: [[User:Marcus|Marcus]] on Dec. 25, 2004&lt;br/&gt;

Feel free to use it:

http://www.gnulinux.de/images/personal/slackwiki/slackwiki.gif</text>
    <sha1>4b30e3f522f06075538cc0bcfb3c200c1e503bcc</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Different Approach To Buildscripts</title>
  <ns>0</ns>
  <id>22</id>
  <revision>
    <id>30</id>
    <timestamp>2009-05-28T20:23:32Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7034" xml:space="preserve">[[Category:Tutorials]]
Pretty much everyone can have their own way of writing Slackware buildscripts. I also have mine, which just makes it easier for me to package software.

In here, I'm going to explain mine. To start, let's look at one I wrote this morning while drinking coffee cup #1:

    #!/bin/bash
    
    #############################################################################
    ## Name: jpilot                                                            ##
    ## Version: 0.99.8                                                         ##
    ## Packager: Martin Lefebvre (dadexter@gmail.com)                          ##
    ## Homepage: http://www.jpilot.org                                         ##
    #############################################################################
    
    PKGNAME=jpilot
    VERSION=0.99.8
    LOC="http://jpilot.org/$PKGNAME-$VERSION.tar.gz"
    ARCH=`uname -m`
    
    START=`pwd`
    PKG=$START/pkg
    SRC=$START/work
    
    build() {
            mkdir -p $PKG $SRC
            cd $SRC
            wget $LOC
            tar -zxvf $PKGNAME-$VERSION.tar.gz
            cd $PKGNAME-$VERSION
            ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
            --enable-gtk2 --enable-prometheon
            
            patch -p0 &lt; patch.0.99.8-memory
            patch -p0 &lt; patch.jpilot-sync
            make
            make DESTDIR=$PKG install
            mkdir -p $PKG/usr/doc/$PKGNAME-$VERSION
            cp -r ABOUT-NLS AUTHORS BUGS COPYING ChangeLog ChangeLog.cvs INSTALL \
            NEWS README TODO UPGRADING docs $PKG/usr/doc/$PKGNAME-$VERSION
            
            cp KeyRing/README.txt $PKG/usr/doc/$PKGNAME-$VERSION/README.keyring
            cp dialer/README $PKG/usr/doc/$PKGNAME-$VERSION/README.dialer
            cp icons/README $PKG/usr/doc/$PKGNAME-$VERSION/README.icons
    }
    
    package() {
            cd $PKG
            find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "current ar archive" | cut -f 1 -d : | \
            xargs strip --strip-debug 2&gt; /dev/null
            chown -R root:root usr/bin
            gzip -p $PKG/usr/man/man*/*
            mkdir $PKG/install
            cp $START/slack-desc $PKG/install/slack-desc
            cd $PKG
            makepkg -l y -c n $START/$PKGNAME-$VERSION-$ARCH-1.tgz
    }
    
    build
    package


The top section is just comments identifying the piece of software we're going to build, and the name of the script's author. Then we have the following lines:

    PKGNAME=jpilot
    VERSION=0.99.8
    LOC="http://jpilot.org/$PKGNAME-$VERSION.tar.gz"
    ARCH=`uname -m`
    
    START=`pwd`
    PKG=$START/pkg
    SRC=$START/work

They set the program's name, version, download URL, build and package directories. Since I usually don't specify anything related to the cpu or architecture, it auto detects the architecture. So, the $ARCH variable *should be* accurate.

    build() {
            mkdir -p $PKG $SRC
            cd $SRC
            wget $LOC
            tar -zxvf $PKGNAME-$VERSION.tar.gz
            cd $PKGNAME-$VERSION
            ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
            --enable-gtk2 --enable-prometheon
            
            patch -p0 &lt; patch.0.99.8-memory
            patch -p0 &lt; patch.jpilot-sync
            make
            make DESTDIR=$PKG install
            mkdir -p $PKG/usr/doc/$PKGNAME-$VERSION
            cp -r ABOUT-NLS AUTHORS BUGS COPYING ChangeLog ChangeLog.cvs INSTALL \
            NEWS README TODO UPGRADING docs $PKG/usr/doc/$PKGNAME-$VERSION
            
            cp KeyRing/README.txt $PKG/usr/doc/$PKGNAME-$VERSION/README.keyring
            cp dialer/README $PKG/usr/doc/$PKGNAME-$VERSION/README.dialer
            cp icons/README $PKG/usr/doc/$PKGNAME-$VERSION/README.icons
    }

The is the main build function. This contains the code required to build the software. First, we create the build and package directories. The next 3 lines change to the building diirectory, uses wget to fetch the source file and extracts it.

The lines after that are what you would normally type at your command line to build the software:

* Change to the source directory.
* Run ./configure with all the options you want.
* Apply two patches required (in this case) to fix bugs with the software.
* Run make
* Install the software in the package directory defined by $PKG
* Create the standard Slackware Software Documentation directory in the package
* Copy the standard documentation.


The next section is the packaging part:

    package() {
            cd $PKG
            find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "current ar archive" | cut -f 1 -d : | \
            xargs strip --strip-debug 2&gt; /dev/null
            chown -R root:root usr/bin
            gzip -p $PKG/usr/man/man*/*
            mkdir $PKG/install
            cp $START/slack-desc $PKG/install/slack-desc
            cd $PKG
            makepkg -l y -c n $START/$PKGNAME-$VERSION-$ARCH-1.tgz
    }

* We change to the package directory
* Strip executables and libraries in order to decrease size.
* As a Slackware standard, we change the ownership of the executables to root:root (to be done for every bin/ and sbin/ directory)
* We compress the manpages
* Create install/ and copy the slack-desc file from the start directory
* Finally, change back to the package folder and create the package tarball.


In this example, the slack-desc and some patch files are distributed with the SlackBuild. This also makes it easier to ship the build script with patches that might be required for the software to work on Slackware (patch to remove PAM stuff).

The slack-desc file format is described here: [http://www.linuxpackages.net/howto.php?page=slack-desc&amp;title=Slackware+Desc+Files LinuxPackages.net]


Additional files:

Some people use slapt-get (like me). slapt-get supports additional features such as
* Dependencies
* Conflicts
* Suggestions

Not everyone wants those features, so building a package with those files will not interfere with the normal pkgtools process. For more info on these optional files, go here: [http://www.linuxpackages.net/howto.php?page=perfect-package&amp;title=Perfect+Package#Optional LinuxPackages.net]

If you decide to use those files, you will then have to repeat these lines:

    cp $START/slack-desc $PKG/install/slack-desc

for slack-required, slack-conflicts, and slack-suggests.


----
See also [[SlackBuild_Scripts]] and [[Writing A SlackBuild Script]]
----</text>
    <sha1>00c1d139fe473abbcd7fd5f55290127ea0189736</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Building A Package</title>
  <ns>0</ns>
  <id>23</id>
  <revision>
    <id>31</id>
    <timestamp>2009-05-28T20:24:50Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2386" xml:space="preserve">[[Category:Tutorials]]

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

----

Configure and compile the source as you usually do:
 ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
 make

Make a temporary destination directory available:
 mkdir /tmp/build

Install into the temporary directory:
 make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
 strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in &lt;tt&gt;/usr/man&lt;/tt&gt; is gzipped before you make the package:
 gzip -9 /tmp/build/usr/man/man?/*.?

Create the &lt;tt&gt;install&lt;/tt&gt; directory, this is where the description and install script will be stored:
 cd /tmp/build
 mkdir install
 cd install

Using a text editor, create a file called &lt;tt&gt;slack-desc&lt;/tt&gt; and fill it with the following contents:

    |-----handy-ruler------------------------------------------------------|
 app: Application Name (Short/Brief description)
 app:
 app: Enter a description of the package you are building.
 app: All 11 "app:" lines must be present
 app: "app" needs to be your application name.
 app: The handy-ruler is there to help you, these lines should not exceed
 app: 79 characters.
 app:
 app:
 app:
 app:

Create the actual package:
 cd /tmp/build
 makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc.  Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say &lt;tt&gt;yes&lt;/tt&gt;&lt;br&gt;
When prompted to reset permissions, say &lt;tt&gt;no&lt;/tt&gt;

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
 cd ..
 installpkg app-version-arch-tag.tgz


----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----</text>
    <sha1>7a323271780fdaeb613b6e71ec01f41ef6fbdc6c</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Checkinstall</title>
  <ns>0</ns>
  <id>24</id>
  <revision>
    <id>32</id>
    <timestamp>2009-05-28T20:27:22Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki. AND GOT RID OF SPAM.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1275" xml:space="preserve">Checkinstall is actually really easy to use. Like it's told in [[compiling]] tutorial, you first do:&lt;br&gt;

&lt;pre&gt;./configure (--option=argument/path)&lt;/pre&gt;&lt;br&gt;

then when configure has finished you write&lt;br&gt;

&lt;pre&gt;make&lt;/pre&gt;&lt;br&gt;

after compiling you simply write&lt;br&gt;

&lt;pre&gt;checkinstall -y -S&lt;/pre&gt;&lt;br&gt;

and you don't have to worry about it. This command makes a package and installs it. Also it leaves copy of this package to current directory in case you need it. If you want to remove package you go to /var/log/packages and write:&lt;br&gt;

&lt;pre&gt;removepkg pkgname&lt;/pre&gt;&lt;br&gt;

'''Configuration'''

Checkinstall also works with a config file: /etc/checkinstall/checkinstallrc. In this file, the options that are especially
interesting to a SlackWare user are:
&lt;pre&gt;
ARCHITECTURE="i686"
INSTYPE="S"
PAK_DIR="/usr/src"
SHOW_SLACK_INSTALL=0
&lt;/pre&gt;

"ARCHITECTURE" sets your architecture (if blank, it will auto guess)

"INSTYPE" specifies the type of package to create (S for Slackware)

"PAK_DIR" is the location where the finished packages will be moved to

"SHOW_SLACK_INSTALL" specifies wether the slackware package info will be shown when it's installed

That's it.


== External Links ==
Checkinstall home page: http://asic-linux.com.mx/~izto/checkinstall/
[[Category:Tutorials]]</text>
    <sha1>0cb0a9c6a0c097e78977c7b67d7df4a83db4b3c9</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Compiling</title>
  <ns>0</ns>
  <id>25</id>
  <revision>
    <id>33</id>
    <timestamp>2009-05-28T20:28:32Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2165" xml:space="preserve">Well compiling a program can be a pain, but it's pretty fun. First you need to get the source you're compiling and read the INSTALL and README files on any weird install techniques. We first need to extract the source:

: &lt;code&gt;tar zxvf file.tar.gz&lt;/code&gt;

You will now see a bunch of files on your screen, that means it's extracting, now half the programs have a configure script, this means you can enable, disable and tell the program where to install to:

: &lt;code&gt;./configure --help&lt;/code&gt;

This gives you a list of the options you can compile in or disable options. Now this is a normal compile line:

: &lt;code&gt;./configure --prefix=/usr&lt;/code&gt;

Now this installs the program in /usr so you don't need to edit the $PATH to launch it, Now 2 other options that you might want to add to some programs are:

: &lt;code&gt;--sysconfdir=/etc&lt;/code&gt;
: &lt;code&gt;--localstatedir=/var&lt;/code&gt;

These are pretty self explanatory. You may or may not need to edit these. Some source say $PREFIX/etc or something similar for the --sysconfdir and you might not want that, this is an example of when you need the --sysconfdir=/etc. Now when we have the source configured, you want to compile it:

: &lt;code&gt;make&lt;/code&gt;

This compiles the actual program. It might take some time, it might not, depending on the source. 

If make succeeds without errors, the program is now technically compiled. Some simpler programs can be run directly after compiling, without having to be installed, but most programs need to be fully installed before they can properly run. 

To install, one can simply proceed as such: 

: &lt;code&gt;su&lt;/code&gt;

: &lt;code&gt;make install&lt;/code&gt;

However, the above method does not take advantage of Slackware's package management system, which will make upgrading or uninstalling this program in the future much easier.  The preferred way to install programs is through packages-- thus, at this point, the program should be packaged instead of simply running "make install" as root. See [[Building_A_Package]] and [[Checkinstall]].

This is just a basic way to compile a program and it's pretty easy to do. Now you know how to compile a program. Good luck.

[[Category:Tutorials]]</text>
    <sha1>d4ae7fce4be0a82bb09e133470f0ebab32b32777</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>LCD Monitor Configuration In X.Org</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>34</id>
    <timestamp>2009-05-28T20:36:03Z</timestamp>
    <contributor>
      <username>Dugan</username>
      <id>12</id>
    </contributor>
    <comment>Migrated from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15024" xml:space="preserve">[[Category:Tutorials]]
==DISCLAIMER==

If there is nothing wrong with your display, please don't go mucking about with your ~/.fonts.conf file (at least, back it up first). If you do have problems with your LCD display, then this is a good bet to try. If you have any success or failure, please do report this back, and changes, if any, that you made to your .fonts.conf file and any other file (perhaps /etc/X11/xorg.conf?) Comments, corrections and thoughts are always welcome.

This may well also work with XFree86 &gt; 4.3, since they use the same font configuration files as this. Older versions have a non-XML font configuration setup (I don't know when the switch over was made though), and will not be covered.

WARNING - Parts of this article are out of date, and there are a few changes required for modular X. These will be added soon.

==Introduction==

LCD/TFTs display fonts very differently to a CRT. Unfortunately with Slackware's default settings on X.Org/FreeType, the results for fonts on an LCD are painful to say the least. This is further compounded by the fact that all the 'helpful' HOWTOs out there are badly out of date, referring to ancient versions of the now defunct XFree86. Whilst there are a few sites out there with bits of information, putting into a workable solution is quite a challenge.

This exists, therefore, to show the naysayers that they're wrong, and that you _can_ enjoy nice looking fonts in Slackware.

(Please note, this is _not_ an exhaustive HOWTO, and it is _not_ a HOWTO about .fonts.conf (please see the Bibliography for a site detailing the tags available in .fonts.conf). This HOWTO is only about configuring an LCD monitor and what works best for one)

==What You'll Need==

*Your favourite text editor
*X.Org (or a later edition of XFree86 &gt;4.3. This has only been tested on Slackware 10.1 and above).
*An LCD/TFT monitor (most of this may also apply to an LCD monitor on a laptop).

==Physical Setup==

===The Monitor===

(I humbly apologise in advance for this section, but better safe than sorry.)

(Standalone Monitors only) Plug up your LCD. Where possible, use the DVI-D (i.e. The digital, not analogue VGA) connector, if both your monitor and your graphics card have one. If not, use an analogue VGA cable and connection (where possible, avoid using DVI-D to VGA adaptors.) Then, ensure the viewing angle of your LCD is correct. Play around with it until you are happy.

==Settings==

===X===

As far as I know, there is no special configuration of X needed for an LCD monitor. Just create the necessary entry for a monitor in /etc/X11/xorg.conf with the correct refresh rates as normal and enjoy (the monitor itself may even be able to give you these, mine does.) I won't cover this in any more detail, as it's pretty standard and covered better elsewhere.

X will also detect the correct sub-pixel alignment, so you don't need to deal with that either.

===Fonts and FreeType===

The real problems begins with font rendering in X. If you are switching over on your machine from a CRT to an LCD, what is facing you at first sight will be unpleasant to say the least.

Of course, this isn't down to X, as in all modern X servers from X.Org (and the later ones from XFree86) FreeType is responsible for all font rendering (any other modules loaded in your /etc/X11/xorg.conf for font rendering are anachronisms: they are no longer used, and X tells you they don't exist). Something I've seen a lot is that “fonts looked better on 9.0” or earlier versions of Slackware, and there is good reason for this. With the changeover to FreeType2, due to various Apple patents in the US and Japan, the 'bytecode interpreter' is now disabled by default. (Plus, IMHO, the Bitstream fonts that ship with Slackware aren't very good). With a CRT, this isn't much of a problem, but it does make a lot of difference on an LCD and is nearly illegible.

There are two ways round this, either:

#Make alterations to .fonts.conf to try and make the Bitstream fonts render better on an LCD.
#Rebuild FreeType with the bytecode interpreter, and use the properly hinted MS fonts (Arial, et al) to get cleaner, crisper looking fonts on the LCD.

Both of these solutions give different results (though I prefer the second).

====Common====

For both alternatives, there are some common settings that must be made.

If you're using KDE or GNOME, you'll find they have tools for doing some of what I'm going to describe. However, I would recommend _against_ using them. I've found their attempts at generating and editing a .fonts.conf file to be dubious to say the least. It is much more preferable to edit the file yourself, and since it is now done through a well defined XML file, this isn't as bad as it once appeared to be (judging from some of those ancient HOWTOs).

Crank up your editor and load ~/.fonts.conf (or /etc/fonts/local.conf)

If it exists: Just add these sections to it, inside the &lt;fontconfig&gt;&lt;/fontconfig&gt; tags.
If it doesn't exist: Use my ~/.fonts.conf skeleton from Appendix A as your .fonts.conf and edit as necessary.

1. Ensure that the sub pixel order is _not_ specified.

X knows the sub pixel order already, and if this is enabled as well, FreeType produces some very strange results. However, if you do still have problems, consider replacing 'none' with 'rgb' (the standard for LCD monitors), 'bgr' (unusual), 'vrgb' (vertical rgb, if you have a monitor that has been rotated by 90 degrees[1]), 'vgbr' (as vrgb, but very rare).

 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="rgba" &gt;
   &lt;const&gt;none&lt;/const&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

2. Enable sub-pixel hinting

This is what really starts to make the difference. Visit http://grc.com/ctwhat.htm for the technical explanation of why we're doing all of this.

 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="hinting" &gt;
   &lt;bool&gt;true&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

3. Set the hinting amount

Usually, this should be full. Valid options are 'none', 'hintslight', 'hintmedium' and 'hintfull' which should be fairly self explanatory if you've read the article at the link above.

 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="hintstyle" &gt;
   &lt;const&gt;hintfull&lt;/const&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

====Option 1) The 'Easy' Way====

Essentially, we're going to enable FreeType's non-patented autohinter and antialiasing to improve the appeareance of the default Bitstream fonts.

Add the following to ~/.fonts.conf. 

#Enable anti aliasing

This makes the fonts start to look nice, but some of the shapes will be distorted, so we need the FreeType autohinter (see next part). 

 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="antialias" &gt;
   &lt;bool&gt;true&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

Fluxbox only:

You may need to enable anti alias separately on Fluxbox before it takes notice of the changes:

fluxbox menu --&gt; Configure --&gt; AntiAlias

#Enable the FreeType autohinter

The autohinter is not turned on automatically, so we have to do this manually.

Please note that OpenOffice.org binaries from the OOo website are built against the bytecode interpreter, so even if you have compiled FreeType with the bytecode interpreter and override it with the autohinter, OOo will still use the bytecode interpreter.

 &lt;match target="pattern" &gt;
  &lt;edit mode="assign" name="autohint" &gt;
   &lt;bool&gt;true&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

====Option 2) The 'Hard' Way====

This is my ([[User:Cathectic]]) preferred solution, as I believe it gives better results. This involves rebuilding FreeType with the bytecode interpreter enabled, and then using the properly hinted fonts 'Core Fonts For the Web' from Microsoft.

For this, you will need to:

#Get a copy of FreeType that has the bytecode interpreter enabled.
##Download the Freetype sources from your local Slackware mirror (slackware-$VERSION/source/l/freetype)
##In freetype.SlackBuild, uncomment the line to apply the bytecode enabling patch
##Run the SlackBuild
##Replace your old freetype package with the new one you've just built.

'''32bit X Applications (Slamd64 only)''': To enable 32bit applications in Slamd64 to use the bytecode interpreter, you need to install a 32bit bytecode enabled FreeType.

#Download and install the 'Microsoft Core Fonts for the Web' (if you have a Windows installation, you could import the fonts from that instead. This tutorial assumes you do not) from either:
##LinuxPackages (install CabExtract, then CoreFonts)
##Or, From the 'Core Fonts for the Web' at http://prdownloads.sourceforge.net/corefonts/ 
###Get all the *.exe files
###Get the CabExtract source RPM, rpm2tgz it, untar, build and install
###Use CabExtract to extract the *.ttf's from the *.exe's you downloaded, and then move the fonts to /usr/X11/lib/X11/fonts/TTF (/usr/share/fonts/TTF for X.Org 7 or newer).

Now add the following to ~/.fonts.conf

1. Disable the autohinter

This isn't strictly necessary – the autohinter is not enabled by default, and if it's not enabled, the bytecode interpreter is used by default. However, it's better safe than sorry.

 &lt;!-- Disable autohinter - using bytecode interpreter instead --&gt;
 &lt;match target="pattern" &gt;
  &lt;edit mode="assign" name="autohint" &gt;
   &lt;bool&gt;false&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

2. Set the MS fonts as defaults

 &lt;!-- Set sans-serif as Arial --&gt;
 &lt;match target="pattern" name="family" &gt;
  &lt;test name="family" qual="any" &gt;
   &lt;string&gt;sans-serif&lt;/string&gt;
  &lt;/test&gt;
  &lt;edit mode="assign" name="family" &gt;
   &lt;string&gt;Arial&lt;/string&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

 &lt;!-- Set monospace as Courier New --&gt;
 &lt;match target="pattern" name="family" &gt;
  &lt;test name="family" qual="any" &gt;
   &lt;string&gt;monospace&lt;/string&gt;
  &lt;/test&gt;
  &lt;edit mode="assign" name="family" &gt;
   &lt;string&gt;Courier New&lt;/string&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

 &lt;!-- Set serif to Times New Roman --&gt;
 &lt;match target="pattern" name="family" &gt;
  &lt;test name="family" qual="any" &gt;
   &lt;string&gt;serif&lt;/string&gt;
  &lt;/test&gt;
  &lt;edit mode="assign" name="family" &gt;
   &lt;string&gt;Times New Roman&lt;/string&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

(I would also recommend using the template in Appendix B to replace all the Bitstream and Luxi fonts with the MS equivalents (or set them to use serif, sans-serif, monospace instead)).

====Testing====

Just load any application up (I'd recommend a Gtk one, KDE will probably need a restart for the changes to take affect everywhere), and the changes should be immediately obvious (I used Mozilla Firefox, by opening and closing it after every tweak of ~/.fonts.conf, I was able to see the changes immediately).

====Apply System Wide====

You can apply these changes system wide, using /etc/fonts/local.conf

If it exists, just append the sections you added above to it.
If it doesn't, use your .fonts.conf as /etc/fonts/local.conf, and edit it as necessary

(The order of precedence for processing is /etc/fonts/fonts.conf (automatically generated, don't edit it), /etc/fonts/local.conf then ~/.fonts.conf - meaning your ~/.fonts.conf will always override the system settings).

===Application Specific Settings===

Qt and Gtk settings need to be changed. 

====Gtk====

For gtk, edit .gtkrc-2.0 and set the fonts either to the generic 'serif', 'sans-serif', etc (now aliased to the MS fonts), or specify the MS fonts outright.

====Qt====
For qt, edit .kde/kderc and .qt/qtrc

==Suggestions==

===Non TrueType fonts===

Non TrueType fonts don't render well on LCDs as they don't support hinting. For these fonts (e.g. Helvetica), it is recommended that you specify an alternative TrueType font (that is hopefully similar, but it doesn't have to be!) to use instead (in this case, whatever the default sans-serif font on the system is):

 &lt;match target="pattern" name="family" &gt;
  &lt;test name="family" qual="any" &gt;
   &lt;string&gt;Helvetica&lt;/string&gt;
  &lt;/test&gt;
  &lt;edit mode="assign" name="family" &gt;
   &lt;string&gt;sans-serif&lt;/string&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

You can easily reuse this for other fonts. Just copy and paste, then replace 'Helvetica' with the font to replace, and 'sans-serif' with the font you want to replace it with (or you can use the generic descriptions 'serif', 'sans-serif' or 'monospace').

===Old Gtk/Qt===

Some programs (usually older ones) using these libraries may not always use anti aliased fonts, even if you've specified them in .fonts.conf. This can fixed by:

Gtk: Add the following to /etc/profile: 
export GDK_USE_XFT='1'

qt: In ~/.qt/qtrc, ensure the following entry is present under [General]: 
enableXft=true
useXft=true

Programs coded using Gtk 1.x don't appear to support anti aliasing properly – you may want to consider replacing them with ones that use Gtk 2.x (e.g. Replacing XMMS with its Gtk2 fork, Beep Media Player)

===OpenOffice.org===

OpenOffice.org binaries are built against the bytecode interpreter. If you install a bytecode enabled FreeType, OOo will always use it, regardless of any system settings enabling the autohinter. Also, OpenOffice.org fonts have to be changed manually.

Tools &gt; Options &gt; OpenOffice.org &gt; 'Use system font for user interface' (make sure this is checked).

==Appendix A==

The following is a ~/.fonts.conf / /etc/fonts/local.conf skeleton. Use this to put together a working configuration for your system.

 &lt;?xml version="1.0"?&gt;
 &lt;!DOCTYPE fontconfig SYSTEM "fonts.dtd"&gt;
 &lt;fontconfig&gt;
 
 &lt;!-- Settings go between fontconfig tags --&gt;
 
 &lt;/fontconfig&gt;

==Appendix B==

This section is a recommendation only. Some fonts are not TrueType, which means they don't support anti aliasing and look dreadful on an LCD. The way round this is to tell FreeType to replace any such fonts with a properly hinted TrueType equivalent. All of the Bitstream and Luxi fonts should be aliased in this way (some sites, such as Gnome's home page, use these fonts, and they don't render correctly with the bytecode interpreter).

You can copy, paste and edit the following example for Helvetica for any other fonts you want to replace. (Just replace 'Helvetica' with the font to replace, and 'sans-serif' with the font you want it to be replaced with. Generic font descriptions serif, sans-serif and monospace are valid entries, as well as specific font names.)

 &lt;!-- Replace Helvetica with default sans-serif --&gt;
  &lt;match target="pattern" name="family" &gt;
   &lt;test name="family" qual="any" &gt;
    &lt;string&gt;Helvetica&lt;/string&gt;
   &lt;/test&gt;
   &lt;edit mode="assign" name="family" &gt;
    &lt;string&gt;sans-serif&lt;/string&gt;
   &lt;/edit&gt;
  &lt;/match&gt;
 &lt;alias&gt;

==Footnotes==

[1] Apparently, there are some monitors where the screen can be rotated. If so, perhaps the vrgb/vbgr settings might be better for you (but only when the screen is rotated) If you can test this, please report back the results. 

==Bibliography==

Man Page of fonts.conf - http://www.fontconfig.org/fontconfig-user.html&lt;br /&gt;
XFree86 Font Configuration - http://www.xfree86.org/current/fonts2.html&lt;br /&gt;
Explanation of Sub Pixel Hinting - http://grc.com/ctwhat.htm&lt;br /&gt;
Gentoo Xorg &amp; Fonts (And how to fix Konsole Linux fonts problem) - http://gentoo-wiki.com/HOWTO_Xorg_and_Fonts&lt;br /&gt;
If you're running an old version of XFree http://www.tldp.org/HOWTO/FDU/index.html</text>
    <sha1>b75d482f6194791191e0b023a6c8931212c85ab1</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Burning CD/DVD</title>
  <ns>0</ns>
  <id>27</id>
  <revision>
    <id>36</id>
    <timestamp>2009-05-28T22:21:33Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2692" xml:space="preserve">[[Category:Tutorials]]
Random information about burning CD/DVD's with slack (and linux in general). Feel free to tack on any insight you might have on the subject.

==The Basics==

In most modern situations, you will not have to tell the software which device to use (unless you have more than one device). In case you have older hardware or software, it may be necessary to pass the device info. On a 2.6 kernel, you can use:

 cdrecord dev=/dev/someDevice

On a 2.4 kernel, you use one of these commands:

 cdrdao scanbus
 cdrecord -scanbus dev=ATA
This should present you with some information:
 ATA:1,0,0            DVDRW   , IDE1004         , 0151
 1,0,0   100) 'DVDRW   ' 'IDE1004         ' '0151' Removable CD-ROM
To pass this device (1,0,0) to cdrdao or cdrecord:
 cdrdao --device 1,0,0
 cdrecord dev=ATA:1,0,0
These will be SCSI ID's if you have a SCSI burner, or are using ide-scsi (no-longer necessary)

==CDR==
===Creating an image===
====From a disc====
 readcd dev=ATA:1,0,0 f=image.iso
 dd if=/dev/cdrom of=image.iso
====From a directory of files====
-r provides Rock Ridge extension (for posix)&lt;br&gt;
-J provides Joliet extension (for windows)
 mkisofs -o image.iso -J -r /path/to/files/
===Burning an image===
 cdrdao write image.cue
 cdrecord -dao driveropts=burnfree dev=/dev/cdrom image.iso 

==DVDR==
===From an image===
 growisofs -dvd-compat -Z /dev/dvd=dvd.iso
===A directory of files===
-R provides Rock Ridge extension (for posix)&lt;br&gt;
-J provides Joliet extension (for windows)
 growisofs -dvd-compat -Z /dev/dvd -J -R /path/to/files/
===A DVD Video===
This path must be structured like a DVD, see Authoring.
 growisofs -Z /dev/dvd -dvd-video /path/to/dvd/files/

==Blanking==
===Quick===
 cdrdao blank --blank-mode minimal
 dvd+rw-format -blank /dev/dvd
===Full===
 cdrdao blank --blank-mode full
 dvd+rw-format -blank=full /dev/dvd

==Links==
===Burning Software===
; DVD+RW-Tools : http://fy.chalmers.se/~appro/linux/DVD+RW/
; CDRDAO : http://cdrdao.sourceforge.net/
; Cdrtools : http://www.fokus.fhg.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html

===GUI Frontends===
; X-CD-Roast : http://www.xcdroast.org/
; Gnome CD Master : http://cdrdao.sourceforge.net/gcdmaster/index.html
; Gnome Toaster : http://gnometoaster.rulez.org/
; Nautilus-CD-Burner : http://www.gnome.org/projects/nautilus/
; K3B : http://www.k3b.org/

===Authoring Tools===
; dvdauthor : http://dvdauthor.sourceforge.net/
; DVDStyler : http://dvdstyler.sourceforge.net/
; &amp;lsquo;Q&amp;lsquo; DVD-Author : http://qdvdauthor.sourceforge.net/

===Format Converters===
; CCD2ISO : http://ccd2iso.sourceforge.net/
; NRG2ISO : http://gregory.kokanosky.free.fr/v4/linux/nrg2iso.en.html</text>
    <sha1>1702ede72a6539ac8a9aae2d495e755219fe204f</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>SSH Keys</title>
  <ns>0</ns>
  <id>28</id>
  <revision>
    <id>37</id>
    <timestamp>2009-05-28T23:54:54Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="998" xml:space="preserve">Having to type an SSH password everytime may get annoying in some cases. Well there is thing called password-less SSH logins. First we need to create a key by issuing the following command from the local client machine:

 ssh-keygen -t dsa

Now press enter on the location and the pass-phrase. Now we have made the actual key, so we can copy the key over to the remote server:

 ssh-copy-id -i ~/.ssh/id_dsa.pub user@host

Now 'user' is the actual user of the remote server, and 'host' you replace with the servers IP or Hostname. Now it might ask if you wish to continue, you make sure you hit yes, and the password you type is the password for the user on the remote server. Now lets login:

 ssh user@host

You will log right into the server without typing in a password. It will also not ask for a password when you are going to scp a file over, too.

To copy your key to another remote server, simply run the ssh-copy-id command again with another $USER@$HOST specified.
[[Category:Tutorials]]</text>
    <sha1>db3940ba0fdcac805c0e46b234d29db40caf4f1a</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Scroll Wheel</title>
  <ns>0</ns>
  <id>29</id>
  <revision>
    <id>38</id>
    <timestamp>2009-05-28T23:56:05Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7342" xml:space="preserve">[[Category:Tutorials]]
__TOC__
Many people wonder how to enable scrolling on their Mouse, This
tutorial is going to describe how to enable it on X-Windows. First you
must figure out what Slackware version you are running. This is needed
to tell if you edit the XF86Config or the xorg.conf file.  The first
step is to su into root:

 su

Then you must edit the X config, On slackware 9.1 it is:

 vi /etc/X11/XF86Config

And on Slackware 10.0 you must edit xorg.conf:

 vi /etc/X11/xorg.conf

==3 and 5 button mice==

I used "vi" to edit my files because that's my editor of choice, But if
you want to use pico, or anything else feel free to do so. Now you
must search for the following items in the config:

 Section "InputDevice"
 Identifier "Mouse0"

Now below that you must add the following items:

 Option "Buttons" "5"
 Option "ZAxisMapping" "4 5"

And I had to change the mouse protocol, so if it doesn't work you
should change it to IMPS/2:

 Option "Protocol" "IMPS/2"

Summing it up, below is the entire section:

 Section "InputDevice"
        Identifier            "Mouse0"
        Driver "mouse"
        Option "Device"       "/dev/input/mice"
        Option "Protocol"     "IMPS/2"
        Option "Buttons"      "5"
        Option "ZAxisMapping" "4 5"
 EndSection

The last step is saving the file and restarting X, you now should have
a scrolling mouse:)

==7 button mice==

You can use the command  `X -version`  to find your version of X.&lt;br&gt;
Here is a section of xorg.conf for 7 button mouse (MX-700) will most likely work for others..
 Section "InputDevice"
        Identifier            "Mouse0"
        Driver "mouse"
        Option "Device"       "/dev/input/mice"
        Option "Protocol"     "ExplorerPS/2"
        Option "Buttons"      "7"
        Option "ZAxisMapping" "6 7"
 EndSection

You then need to use Xmodmap to remap the scroll wheel, this can be ~/.Xmodmap or /etc/X11/xinit/.Xmodmap or even just `xmodmap -e` in whatever X startup script you're using. The extra 2 buttons (usually forward/back) will be mapped in most web browsers like galeon and firefox. If you need to map them for other applications, look at imwheel http://imwheel.sourceforge.net/
 pointer = 1 2 3 6 7 4 5


Xorg 6.9 (Slackware-current as of May 30th, 2006) has a known issue with correctly exposing the number of mouse buttons present.  The presence of this problem may be verified by running xmodmap -pp and noting the presence of 11 buttons instead of 7.  (xev was handy in determining what number each button was being read as.)

This may be corrected by using the following Xmodmap:
 pointer = 1 2 3 8 9 4 5 6 7 10 11

==Multi-Button Mice==
Recent versions of the XOrg server include a ButtonMapping option that allows you to remap mouse buttons in a specific order.  This is particularly useful for users of multi-button mice such as the Razer DeathAdder and MS Intellimouse Explorer.  The following section of an xorg.conf file (modified from [http://linux.wordpress.com/2006/06/06/tip-my-logitech-mx700-mouse-with-linux-and-firefox/ this blog post]) allows you to use the additional "thumb buttons" under X as you would on MS Windows provided applications support that functionality (the expected behavior is the default for Firefox, the additional buttons seem to do nothing in Konqueror by default).
 Section "InputDevice"
    Identifier     "Mouse1"
    Driver         "mouse"
    Option         "Name" "Razer Deathadder"
    Option         "Device" "/dev/mouse"
    Option         "Vendor" "Razer"
    Option         "CorePointer"
    Option         "Protocol" "ExplorerPS/2"
    Option         "Buttons"  "7"
    Option         "ZAxisMapping" "4 5"  
    Option         "ButtonMapping" "1 2 3 6 7"
 EndSection

Each mouse is different, so you should use xev to verify that the additional buttons are working in the manner that they ought.

==MX1000==

Here is my Logitech MX1000 configuration, it allows ALL buttons on this mouse to work with X11 (X.org 6.8.2 + evdev patches).

xorg.conf
 Section "InputDevice"
        Identifier                "MX1000"
        Driver  "mouse"
        Option  "CorePointer"
        Option  "Protocol"        "evdev"
        Option  "Dev Name"        "Logitech USB Receiver"
        Option  "Buttons"         "12"
        Option  "ZAxisMapping"    "11 12 10 9"
        Option  "Resolution"      "800"
        Option  "Emulate3Buttons" "false"
 EndSection

Xmodmap
 ! MX1000
 pointer = 1 2 3 8 9 10 11 12 6 7 4 5

xbindkeysrc
[http://hocwp.free.fr/xbindkeys/xbindkeys.html xbindkeys]
[http://homepage3.nifty.com/tsato/xvkbd/ xvkbd]
 # Backward and Forward buttons
 "xvkbd -text "\[Alt_L]\[Left]""
   m:0x10 + b:8
 "xvkbd -text "\[Alt_L]\[Right]""
   m:0x10 + b:9
 # "Cruise Control"
 "xvkbd -text "\[Page_Up]""
   m:0x10 + b:11
 "xvkbd -text "\[Page_Down]""
   m:0x10 + b:12

==EvDev==

This info will help you get your MX1000 or other evdev device working with X.org 6.9/7.0. This version of X.org has the evdev driver and does not need to be patched.

First, edit (or create) your /etc/udev/rules.d/10-local.rules file and add the following line:
 KERNEL=="event*", SYSFS{../manufacturer}=="Logitech",  SYSFS{../product}=="USB Receiver", NAME="input/mx1000", MODE="664", GROUP="plugdev"
This gives you a /dev/input/mx1000 node after running udevstart or rebooting. If your mouse is different, dig through sysfs and use lsusb and udevinfo to find your manufacturer and product. They need to match.

Next edit your /etc/X11/xorg.conf, add/change your mouse section to this:
 Section "InputDevice"
        Identifier      "Logitech MX1000"
        Driver          "evdev"
        Option          "Device" "/dev/input/mx1000"
 EndSection
NOTE that you no-longer specify "ZAxisMapping" or "Buttons", the evdev driver takes care of this for you.

Your ServerLayout section should be adjusted if you changed the Identifier line above:
 InputDevice "Logitech MX1000" "CorePointer"
You no-longer need Xmodmap to remap the scroll wheel buttons. Remove any system-wide and user Xmodmap/.Xmodmap files (or sections you have in those files pertaining to your mouse).

You still need xbindkeys and xvkbd as listed above to bind forward/back and pageup/down buttons.

(This info was gathered from a much better and thorough guide, you should check it out. http://floam.sh.nu/index.xhtml?page=guides&amp;section=mx1000)

==X.org 7.1==
You do not need to use the udev tricks above, this just makes things more difficult. Instead, now X will read your evdev device in a much more sane way. Here is my config for an MX1000 and X.org 7.2. This will work for nearly all USB mice, and is the preferred Driver since it eliminates the need to specify  Buttons, ZAxisMapping, Xmodmap, etc. All of your buttons will work and be mapped correctly.

 Section "InputDevice"
         Identifier      "MX1000"
         Driver          "evdev"
         Option          "Name"          "Logitech USB Receiver"
         Option          "CorePointer"
 EndSection

You may have to use "Dev Name" if "Name" does not work. You can find the "Name" by doing &lt;code&gt;cat /proc/bus/input/devices&lt;/code&gt;

 I: Bus=0003 Vendor=046d Product=c50e Version=2500
 N: Name="Logitech USB Receiver"
 P: Phys=usb-0000:00:1d.3-1/input0
 S: Sysfs=/class/input/input2
 H: Handlers=mouse0 event2 
 B: EV=7
 B: KEY=ffff0000 0 0 0 0 0 0 0 0
 B: REL=143</text>
    <sha1>36e04878c2607be548ff37b3512553b20300c84f</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Permissions and Umasks</title>
  <ns>0</ns>
  <id>30</id>
  <revision>
    <id>39</id>
    <timestamp>2009-05-28T23:56:59Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old data.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3543" xml:space="preserve">==Normal Permissions==

On *nix-like systems, traditionally every file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).

You can change the owner of a file with the "chown" command:

: &lt;code&gt;fred@linux:~&gt; chown someUser foo&lt;/code&gt;

You can change the group of a file with the "chgrp" command:

: &lt;code&gt;fred@linux:~&gt; chgrp someGroup foo&lt;/code&gt;

Alternatively, you can do both at once:

: fred@linux:~&gt; &lt;code&gt;chown someUser.someGroup foo&lt;/code&gt;

or:

: fred@linux:~&gt; &lt;code&gt;chown someUser:someGroup foo&lt;/code&gt;

For every file, you can set the following for the User, Group, and Others: r - can read w - can write x - can execute

These are set with the "chmod" command:

: fred@linux:~&gt; &lt;code&gt;chmod u=rwx,g=rx,o=r foo&lt;/code&gt;
: fred@linux:~&gt; &lt;code&gt;ls -l foo&lt;/code&gt;
: -rwxr-xr--  1 fred users 0 2004-10-26 11:38 foo

You don't need to set all the permissions - you can just modify them, for example, to make a file executable:

: fred@linux:~&gt; &lt;code&gt;chmod +x foo&lt;/code&gt;

You can also change the permissions just for either the User, Group, or Others:

: fred@linux:~&gt; &lt;code&gt;chmod o-x foo&lt;/code&gt;

==Octal Permissions==

You can also specify permissions with a number. To find out which numbers, add up the numbers from this table:

 r w x
 4 2 1

For example, rwxr-xr-- would be:

 U  G  O
 4  4  4
 +2 +0 +0
 +1 +1 +0
 =7 =5 =4

So to give a file rwxr-xr-- permissions:

: fred@linux:~&gt; &lt;code&gt;chmod 754 foo&lt;/code&gt;

==Umasks==

umasks define which permissions can not be set (in octal). For example, the default umask on slackware is 0022:

: fred@laptop:~$ &lt;code&gt;umask&lt;/code&gt;
: 0022

Ignoring the first digit, this means that the owner can do anything, but group and others are unable to write (2 == w). A more secure umask (possibly more suitable for your ~/) is 0077, meaning that group and others have no access to your files.

==More Umask==

The following is based on [[User:Sandman1|Sandman1]]'s Umask tutorial.

Well first this is a pretty boring topic to write about, So im going to get right to the point. When you set a umask you set what permission NOT to set. So when you create a file it uses the umask to set the file permissions. All of this might not make sense now but it will later. Now type:

: &lt;code&gt;umask&lt;/code&gt;

Now on slackware you will get "0022", First ignore the first 0. Now we have 022. The first 0 makes sure the owner has ALL the permissions of a file. You can tell that becuase you have no permissions you want to turn off. Now the next two numbers you have a 2 for. The 2 indicates that you NEVER want to set write permissions.

Now that method above of trying to find a umask is a bit confusing. All you do is set the number what you DON'T want the user to have. Now there is an easier way of finding out a umask. You can subtract the permission from 777. Example:

 777 - 750 = 027

That is the umask of the 750 permission. Now you may be asking yourself what is this usefull for. Well you can set the umask by typing "umask 027" in bash and when you create a file/directory it goes by umask 027 instead of the 0022.

Now another reason for setting a umask is becuase you want to access a filesystem such as NTFS,VFAT,Samba,etc as a regular user. You can set the umask and allow regular users to write to the filesytem. It is really easy, in the fstab all you add is "umask=027" and remount the filesystem.
See [[Windows_Partitions]] for more information (and a potentially better option than setting umask options).

[[Category:Tutorials]]</text>
    <sha1>a733e385a9bde5877ec30fda985673302ca6c137</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Resource Limits</title>
  <ns>0</ns>
  <id>31</id>
  <revision>
    <id>48</id>
    <timestamp>2009-05-29T00:17:30Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Move from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2662" xml:space="preserve">= Purpose =

This page does not attempt to explain the different types of system resource limits or when it is (or is not) appropriate to change them; see '''man ulimit''' and [[http://google.com Google]] for that discussion.

However, some users run into problems with the linux kernel's default limit settings, so we'll attempt to explain how to modify them to suit special needs.

= Overview =

The default settings provided by the kernel are sane values for most multi-user machines.  Issuing the command '''ulimit -Hn''' should show the following:
 user@host:~$ ulimit -Hn
 1024
and '''ulimit -n''' should show this:
 user@host:~$ ulimit -n
 1024

The first command shows the hard limit set by the kernel, and the second command shows the soft limit set by the user.  An unprivileged user can increase the soft limit (up to the hard limit value), and he is also able to lower the hard limit (but then is unable to increase it, as an unprivileged user cannot raise the hard limit at all).

There are some situations which might require a larger hard limit for users, and the obvious "solution" is to add a line in /etc/profile to increase it.  However, this will not work, because normal users cannot increase their hard limits (as indicated above).

= Solution =

To increase the hard limits for users, you will need to create '''/sbin/initscript''' and place appropriate commands inside it.  The easiest way is to copy the file '''/sbin/initscript.sample''' to '''/sbin/initscript''' and edit the copy, but you are certainly free to "roll your own."  If you decide to create your own, make sure it is executable or it will not work.  

Using the following '''/sbin/initscript''' file:

 PATH=/bin:/sbin:/usr/bin:/usr/sbin
 export PATH
 
 # Increase the hardlimit for open files
 ulimit -Hn 4096
 
 # Execute the program.
 eval exec "$4"

You should get the following after a reboot:
 user@host:~$ ulimit -Hn
 4096
 
 user@host:~$ ulimit -n
 1024

Notice that the hardlimit is now 4096 (as specified in /sbin/initscript), but the softlimit is still 1024.  In other words, you will still need to use /etc/profile (or some other shell init file - see below for recommendation) to raise the desired users' softlimits.  With some creative scripting, you can be more selective about which users have what limits.

Rather than editing the system /etc/profile, it's recommended to create a custom file in /etc/profile.d and make it executable.  This way, you don't have to worry about trying to merge your changes to /etc/profile when doing Slackware upgrades to new versions.

= Other Resources =

* '''man initscript'''
* '''man ulimit'''

[[Category:Tutorials]]</text>
    <sha1>7a3550a5c0730a78ccebae57e4fab68cb1393f29</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>Windows Partitions</title>
  <ns>0</ns>
  <id>32</id>
  <revision>
    <id>49</id>
    <timestamp>2009-05-29T00:19:35Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Moved from old wiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2709" xml:space="preserve">One of the frequent questions on ##slackware is something along the lines of "How can I allow normal users to access my Windows partition?"  There are *at least* two different ways of doing this.

For a FAT partition, you *could* add umask=0000 to /etc/fstab's options, but I personally don't recommend doing that.  It's *your* computer, so you make the call, but I would do something along these lines:
1. If you want *every* user to be able to read and write to the partition, then you can add dmask=0000 and fmask=0111 to /etc/fstab's options and be done with it - problem solved.

 /dev/hda1     /mnt/win98     vfat     rw,dmask=0000,fmask=0111     0   0

The reason for dmask/fmask as opposed to umask is quite obvious (though I hadn't thought about it until elohim on ##slackware pointed it out):  The FAT and NTFS file systems don't "understand" the executable (-x) bit, so it's automatically present on every file in such a filesystem.  There's no need for normal files to be executable (and it can indeed be a security risk), so we use fmask to turn off those permissions.

2. If you only want some users to be able to read and write to the partition, but you want *every* user to have read access, then you'll want something along these lines.  First, create a special group called "windows" (change the name if you wish) by adding it to /etc/group using your favorite editor and add to this group the users you want to have write access.  

 nogroup:x:99:
 users:x:100:
 console:x:101:
 windows:x:102:user1,user2,user3

Next, edit your /etc/fstab line for that partition and specify that it be mounted with group ownership of the "windows" group, and that write access be removed from others.

 /dev/hda1     /mnt/win98     vfat     rw,gid=102,dmask=0002,fmask=0113     0   0

An NTFS partition will be mounted read-only, so you won't have write access for anyone, but the central idea is the same.

If you don't want everyone else to even have read access to the partition, you can easily do that with the above fstab line modified a bit:

 /dev/hda1     /mnt/winXP     ntfs     ro,gid=102,dmask=0227,fmask=0337     0   0

If you prefer write access to the partition, then you can use ntfs-3g instead and something like this:
All users can read the partition; only members of gid 102 can write:
 /dev/hda1     /mnt/win98     ntfs-3g     rw,gid=102,dmask=0002,fmask=0113     0   0
Users of gid can read and write; nobody else can do anything:
 /dev/hda1     /mnt/winXP     ntfs-3g     rw,gid=102,dmask=0007,fmask=0117     0   0

For more information, see the [[Permissions and Umasks]] and [[Fstab]] pages.

--rworkman (thanks to Erik for the pointers about dmask and fmask)

[[Category:Tutorials]]</text>
    <sha1>6e47018ae54c8b5bd08edc300568e012b97465bc</sha1>
  </revision>
</page>
<page arvcontinue="">
  <title>User:Rworkman</title>
  <ns>2</ns>
  <id>33</id>
  <revision>
    <id>50</id>
    <timestamp>2009-05-29T00:20:50Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Added talk page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="53" xml:space="preserve">http://slackware.com/~rworkman/
http://rlworkman.net/</text>
    <sha1>ec5b5dedb4f8fc93827f7e35cca099280fbce09c</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>User:Rworkman</title>
  <ns>2</ns>
  <id>33</id>
  <revision>
    <id>51</id>
    <parentid>50</parentid>
    <timestamp>2009-05-29T00:21:28Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="55" xml:space="preserve"> http://slackware.com/~rworkman/
 http://rlworkman.net/</text>
    <sha1>aeafff34f91018979591ed5612cd9896cf89821f</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Links</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>52</id>
    <parentid>35</parentid>
    <timestamp>2009-05-29T00:36:32Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Removed one of my links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4871" xml:space="preserve">==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.com - our ugly mugs :)
* ftp://termserver.niesc.org/pub/sandman1 - Packages mostly by [[User:Sandman1|Sandman1]]
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://fredemmott.co.uk/rss.php - RSS feeds for slackware 10 patches and the slackware-current ChangeLog
* http://slackware.it/en/rss - RSS feeds for stable Slackware release and -current ChangeLog
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://uselesstree.org/ - The Complete Slacker
* http://shilo.is-a-geek.com/ - Shilo's tutorial
* http://www.linuxquestions.org/questions/forumdisplay.php?forumid=14 - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://www.slackware-peru.org - Slackware Peruvian Community - by [[User:R1CHARD|R1CHARD]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs
* http://www.themedepot.org/ - Generalized theme site for X11 based programs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://www.audioslack.com/packages/ Audioslack.com] Audio software packages
* [http://straterra.info/Packages/ http://straterra.info/Packages/] Straterra's packages
* [http://www.sekurity.com/packages/ Sekurity.com] dadexter's packages
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current
* [ftp://termserver.niesc.org/ ftp://termserver.niesc.org] Sandman1's packages

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://contrib.slamd64.com - [http://contrib.slamd64.com buildcontrib] can build and fetch these packages for you. Primarily for Slamd64, but work on x86 as well
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://textlinux.slackadelic.com/slackbuilds/ - A repository dedicated to command line (friendly) applications
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/index.php/Main_Page BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki</text>
    <sha1>c16a3719679499acf0fcff976ee18ac592ac96bf</sha1>
  </revision>
  <revision>
    <id>53</id>
    <parentid>52</parentid>
    <timestamp>2009-05-29T02:33:21Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Removed dead, porn, and otherwise redirecting links. Also fixed a few.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3780" xml:space="preserve">==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.org - our ugly mugs :)
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/ BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki</text>
    <sha1>5a3f2c00982d8ab7975ed42adf92d609725dbf50</sha1>
  </revision>
  <revision>
    <id>54</id>
    <parentid>53</parentid>
    <timestamp>2009-05-29T02:36:07Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Added RSS section and Category tag</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3905" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.org - our ugly mugs :)
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/ BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for 8.1 through -current</text>
    <sha1>37fa00faf563afe117c1e44d3933f409e71cc3bf</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>3ware 3DM2</title>
  <ns>0</ns>
  <id>34</id>
  <revision>
    <id>55</id>
    <timestamp>2009-06-02T02:57:02Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5077" xml:space="preserve">[[Category:Tutorials]]
==3DM2==

3DM2 is 3ware's web-based interface for controlling and status checks for their RAID cards.  It contains a small web server that allows configuration and maintenance to the RAID array and provides status reports.  It has an email notification feature that reports RAID problems and glitches.


==Installing 3DM2 On A Slackware Box==
(written from a 3DM2 V9.3.0.7 and Slackware 11 perspective)

1) Gunzip and un-tar the 3DM2 archive.

2) As root, run &lt;code&gt;install.3dm install&lt;/code&gt; to install.

::This script does four things-

:::a) It complains that you aren't running RedHat or Suse and therefore will not automatically install the 3DM2 init scripts in the &lt;code&gt;/etc/rc.d&lt;/code&gt; directory.  You have to manually do this, this is explained later in this instruction.

:::b) It makes a &lt;code&gt;/tmp/3ware&lt;/code&gt; directory and un-compresses the 3DM2 files there.

:::c) It copies the &lt;code&gt;3dm2&lt;/code&gt; binary to &lt;code&gt;/usr/sbin&lt;/code&gt;.

:::d) It makes a &lt;code&gt;/etc/3dm2&lt;/code&gt; directory.

::''NOTE: the &lt;code&gt;/tmp/3ware&lt;/code&gt; directory is NOT removed after install.  It is not necessary to keep but, you may want to keep the &lt;code&gt;install.3dm2&lt;/code&gt; binary in case you ever want to uninstall 3DM2.''

3) Edit &lt;code&gt;/etc/rc.d/rc.local&lt;/code&gt; and add the following line:
::&lt;code&gt;/usr/sbin/3dm2&lt;/code&gt;

4) ''If you are running a restrictive firewall'', open port 888.

5) Start 3DM2 by: &lt;code&gt;3dm2&lt;/code&gt;

6) Using a web browser, browse to your RAID machine, port 888.

::'''If your web-browser is on the same box as your RAID array'''- click here:[https://localhost:888 http'''s'''://localhost:888]

::'''If your web-broswer is NOT on the same box as your RAID array'''-
::::a) Edit your &lt;code&gt;/etc/3dm2/3dm2.conf&lt;/code&gt; file and change the &lt;code&gt;RemoteAccess 0&lt;/code&gt; to &lt;code&gt;RemoteAccess 1&lt;/code&gt;
::::b) Browse to your machine using HTTPS and port 888-
::::::EXAMPLE: &lt;code&gt; https://192.186.1.2:888&lt;/code&gt;
::::::::or &lt;code&gt;https://server.mydomain.net:888&lt;/code&gt;

7) Once the web interface loads up, log in as ADMINISTRATOR (default password is "3ware") and complete the configuration.

8) To activate the help files, you'll need to copy them to the correct location.
::::a) View your /etc/3dm2/3dm2.conf file.  
::::b) Make a note of the Help entry.

9) Go to /tmp/3ware/.

10) Untar the file 3dm-help.tgz.  A directory corresponding to your language with all the help files in it will be created.  For this example (English), the directory was called en.

11) Copy the en directory into the location you made a note of in 8b above.  Copy the whole directory, not just the files inside the directory.

12) Now when you are logged in to the 3dm2 application inside a browser and you click on help, you will get the help screens.


--------------------------------------------------------------------------------------------
(written from a 3DM2-Linux-9.3.0.4 and Slackware '''12.0''' perspective)

Using the 3DM2-Linux-9.3.0.4 seems to be ideal for slackware.  I have it running on

 Slackware 10.2
 Slackware 11.0 (2.4 and 2.6 kernels)
 Slackware 12.0 (Defult 2.6 kernel)

with the following cards:

 7006-2 Series
 8006-2LP Serise
 9500S Series

The directions I found to work best are as follows.

  1a) Download 3DM2-Linux-9.3.0.4.tgz from:
  http://www.3ware.com/support/download.asp

  2a) Please select your 3ware product. = $YOUR_CARD_MODEL

  3a) Please Select Item = *LEAVE BLANK*

  4a) Latest = 9.3.0.4

  5a) Please select the item to download = 3DMD2 Management Utility

6a) Then select Linux as your OS, select 3DM2-Linux-9.3.0.4.tgz to download, read the EULA, and 
download somewhere reachable by your Linux OS.  For the sake of instructions, we'll say /usr/src/3ware.

01) cd /usr/src/3ware

02) tar xfvz 3DM2-Linux-9.3.0.4.tgz

03) run: ./install -i

This extracts files to: /tmp/3ware

...moves the appropriate binary to:
/usr/sbin/3dm2

...and creates the directory:
/etc/3dm2

Now we need to create another directory.  For the sake of instructions, we'll say /3ware/.

04) mkdir /3ware

05) run: cp -rf /tmp/3ware/* /3ware/

06) run: cp /usr/src/3ware/3dm-lnx.tgz /3ware/

07) run: cd /3ware

08) run: ./install

To the following questions, answer the defaults:

 Was RPM used to install the Escalade driver and/or 3dm?? (Y/N) [N]
 Please enter the location of the help documentation. [/usr/local/doc/3dm]

Now you will get what appears to be an error. "3dm binary missing. Installation stopping."  Don't worry, the binary file is already in place.  If you notice though, the /etc/3dm2 directory is empty.

09) run: /usr/sbin/3dm2

This will populate that directory with the default config file, that you may edit to your satisfaction.  If you leave the config file as is, you should be able to connect to your server from the local host at https://localhost:888 (*https* is very important).

In order to connect from another PC, edit /etc/3dmd2/3dmd2.conf line

 RemoteAccess 0
     to
 RemoteAccess 1

1b) run: killall 3dm2

2b) run: /usr/sbin/3dm2

 The default password for both "USER" and "ADMINISTRATOR" = "3ware"</text>
    <sha1>29c316149f72ed7db953c6f461ea8685902079c9</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>ALSA</title>
  <ns>0</ns>
  <id>35</id>
  <revision>
    <id>56</id>
    <timestamp>2009-06-02T02:58:03Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2971" xml:space="preserve">[[Category:Tutorials]]
==Non-USB Cards==
I'm sure that everyone has had their share of audio problems in Slackware, Well I'm going to try and get that audio working for you. First you want to know what kind of sound card you have, usually PCI so type this in:

: &lt;code&gt;/sbin/lspci&lt;/code&gt;

This will let you know the audio card you have, now that you have it written down we are going to run a program to configure your card:

: &lt;code&gt;/usr/sbin/alsaconf&lt;/code&gt;

This will configure your sound and hopefully detect it. Well there are many reasons of why it wouldn't have detected your card, so I'm just going to make a list for you:

# alsa-driver's package isn't compiled for the kernel you are running.
# If you don't have alsa-drivers package, then your 2.6 kernel (hopefully because 2.4 doesn't have built in drivers for alsa) doesn't have the drivers compiled in.
# Your modules are screwed up :)

==All Cards==

Now that we have all of that together, try to play an MP3 sound file as root:

: &lt;code&gt;mpg321 file.mp3&lt;/code&gt;

Now if that plays you are good to go, but if it doesn't then you might want to check on the things above. If it doesn't work then you type this in:

: &lt;code&gt;cat /proc/asound/cards&lt;/code&gt;

Now this will show all the cards that alsa has loaded modules for and what alsa detected. Now with one driver you will see a modem occupying sound device 0. We do not want that because it will conflict. The module for the sound card is snd-intel8x0. Now we need to add the module for the modem to the blacklist:

: &lt;code&gt;echo "snd-intel8x0m" &gt;&gt; /etc/hotplug/blacklist&lt;/code&gt;

Now make sure you use two &gt;'s because if you use only 1, it will overwrite the file and we do not want that. Now restart your machine and you will now have a non conflicting sound module for the intel 8x0 cards. Now we also want to change permissions:

: &lt;code&gt;chmod 666 /dev/dsp*&lt;/code&gt;
: &lt;code&gt;chmod 666 /dev/snd/*&lt;/code&gt;

Now this will make sure OSS and ALSA have permission for everyone to access the sound devices, Now in slackware 10 you just add yourself to the audio group, but Slackware 9.1 doesn't have that option. Now say you want to change the volume levels?

: &lt;code&gt;alsamixer&lt;/code&gt;

When you type that you will get an ncurses based mixer program:) This is great for changing volumes and muting certain things. Per default all channels are muted (alsaconf will unmute a few though). You can unmute them with M. Channels that you should watch are PCM and Master. Those often control the sound level. 
Now say you have the sound mixers perfect and you want to save them:

: &lt;code&gt;alsactl store&lt;/code&gt;

This stores the config and is restored at bootup. You can also restore later on if you screw them up to by typing the following:

: &lt;code&gt;alsactl restore&lt;/code&gt;

There is one tip for the Sound Baster 5.1 cards, sometimes you want to MUTE digital out so you can hear on all the speakers, in alsamixer you just press M on the &lt;tt&gt;Analog/Digital Output Jack&lt;/tt&gt; item.</text>
    <sha1>15044c77be56287862303eb3ed26100ead7e4696</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>ATI Graphics</title>
  <ns>0</ns>
  <id>36</id>
  <revision>
    <id>57</id>
    <timestamp>2009-06-02T02:58:40Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6397" xml:space="preserve">[[Category:Hardware]]
===Introduction===

ATI drivers come in two flavours:

1) X.Org open source 'radeon' driver - full support (accelerated 2D and 3D) for the Radeon 9200 and earlier. (Also supported for the 9200 - X850 for Slackware -current, or any Slackware newer than 11.0)

2) ATI's proprietary closed source 'fglrx' driver - support for the 9500 and above (all support for earlier cards has now been dropped). This is the only driver with any support, either 2D or 3D, for the X1xxx series of cards (R500 and newer).

====Kernel====

AGPGART: If you have an AGP card, you should ensure AGPGART and support for your specific GART are built in the kernel (built in or module is fine)

PCI Express: If you have a PCI Express card, you should ensure PCI Express support is built in the kernel.

==Seting up the 'radeon' driver==

===Preparing Your System===

====Kernel====

Direct Rendering Manager (DRM): Module or built in, plus the module under this for "ATI Radeon"

===Initial Setup===
Edit /etc/X11/xorg.conf

In Section "Module" add:

 Load "glx"
 Load "dri"

At the end of the file, add

 Section "DRI"
   Mode 0666
 EndSection

(Or use 'Xorg -configure' to generate a new xorg.conf to autodetect the ATi card)

===Tweaking===

To increase performance for Radeon users (in particular, R300 and R400), you may also want to add the following under the "Device" section for the radeon:

====AGP users====
 
 Option "AGPMode" "8" # Modify accordingly if you don't have an AGP 8x card 
 Option "AGPFastWrite" "true" # This one has big warnings all over it, so test it first! 

====Mobility card users====
 
 Option "DynamicClocks" "true" # The equivalent of ATi's PowerPlay 
 Option "BIOSHotkeys" "true" # You _might_ need this for some special function keys on your laptop 

====All users====
 
 Option "EnablePageFlip" "true" 
 Option "ColorTiling" "true" 

===Final Check===

Run 'glxinfo | grep render'. It will return something like the following (the last line will vary depending on R300/ R400, PCI/ PCIE or AGP, etc). The important thing is that this reports "direct rendering: yes".

 direct rendering: Yes
 OpenGL renderer string: Mesa DRI R300 20060815 AGP 8x x86/MMX+/3DNow!+/SSE TCL

===Notes===

'''R300 - R400:'''

Please note that these cards do not have accelerated hardware support in X.Org &lt; 6.9 (i.e. Slackware 11.0 or older)

'''R500 (X1xxx and above)'''

Sorry, there is no open source accelerated support in X for these cards. Either use fglrx or vesa.

==Setting up the 'fglrx' driver==

===Preparing Your System===

====Libraries====

The fglrx driver requires that you have the package cxxlibs installed on your system to build it.

'''(Slamd64)''': You will also need the 32 bit compatibility libraries from c/

====Kernel====

Direct Rendering Manager (DRM): Must *not* be built into the kernel - it should be a module (and not loaded) or not built.

Frame Buffer: Must *not* be built into the kernel - it should be a module or not built (it is not compatible with the current fglrx drivers).

===Installing the Driver===

You will need to download the 'ATI Driver Installer' package (the RPM packages do not have support for X.Org 6.9).

Once you have downloaded the installer, run it (I reccommend using sudo, as you need root permissions but also need access to the X server. You could use xhost+ and then su, but this is not safe).

 sudo sh ati-driver-installer-$VERSION-$ARCH.run

You need to select the 'Install driver' (the ATI installer cannot generate a Slackware package), and then it is reccommended you choose "automatic" on the next screen. The driver will now install itself.

Make sure that you mount tmpfs for 3D acceleration, or you can get unexpected results.

ie: 
 'FGLTexMgr: open of shared memory object failed (Function not implemented)
 __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
 fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!'
 
Add the following to /etc/fstab:
 tmpfs     /dev/shm           tmpfs        defaults            0 0
then 'mount /dev/shm' on a console

===Patching the Driver===

If you are running the latest kernel, more often than not you will need to patch the fglrx driver. At the very least, you will need to manually rebuild it if you change your kernel - follow instruction 1 if necessary, then 2 and 3.

There is no central repository of these, so it is not possible to point you to a specific place to check for them (although the [http://ati.cchtml.com Unofficial ATI Bugzilla] or [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D Linux Drivers forum] are good places to check).

Once you have downloaded the patches:

1. Apply them in /lib/modules/fglrx (or /lib/modules/fglrx/build_mod)

 cd /lib/modules/fglrx/build_mod
 cat somepatch.diff | patch -p1

2. Rebuild the fglrx module

 sh /lib/modules/fglrx/build_mod/make.sh

N.B. Modules built are kernel specific - you can only build a module for the kernel you are currently running.

3. Install the module

 sh /lib/modules/fglrx/make_install.sh

===Configuring the X server===

If you have not installed the fglrx driver before, run:

 aticonfig --initial --input=/etc/X11/xorg.conf
 aticonfig --ovt=Xv

This will add an fglrx 'Section "Device"' to /etc/X11/xorg.conf and enable video overlay (enables video playback)

Edit /etc/X11/xorg.conf (you need to do this with root permissions)

Find:

1) A 'Section "Device"' that contains fglrx
2) 'Section "Screen"'

Then:

1) Under the Section "Device" that contains fglrx&lt;br /&gt;
1A). Make a note of the value of "Indentifier"&lt;br /&gt;

2) Under Section "Screen", replace the value of "Device" with the value you just noted from fglrx

At the end of /etc/X11/xorg.conf, add this section (This allows all users to access the direct rendering mode - without it, you can't use acceleration as a user):

 Section "DRI"
        Mode         0666
 EndSection

Restart the X server

===Final Check===

To check that fglrx has been installed and setup correctly, run 'fglrxinfo' in a terminal under X. It should return something like:

 display: :0.0  screen: 0
 OpenGL vendor string: ATI Technologies Inc.
 OpenGL renderer string: MOBILITY RADEON X700 Generic
 OpenGL version string: 2.0.5642 (8.22.5)

(The 'renderer' string will vary depending on the chip your card actually has).

===Uninstalling the driver===

With root permissions, run:

 sh /usr/share/fglrx/fglrx-uninstall.sh</text>
    <sha1>90c3b73913e0ef4ca26f28edd33eec0b61daa08d</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Acer Aspire 502x(WLMi)</title>
  <ns>0</ns>
  <id>37</id>
  <revision>
    <id>58</id>
    <timestamp>2009-06-02T02:59:26Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13717" xml:space="preserve">[[Category:Hardware]]
==Slackware on an Acer Aspire 5020 series==

This article is based on an Aspire 5021WLMi. The 5021WLMi is an an AMD Turion 64 based laptop - it mainly differs from other laptops of the 5020 series only in the specific processor model and some other models come with built in bluetooth - the 5021 has an ML-28 and no bluetooth, I believe the 5024 uses an ML-34 and does have built in bluetooth, so most of this should apply to the 502x series as well. (This is a work in progress, and therefore far from finished).

I have installed my own bluetooth module into the 5021 - this is not very difficult to do (just rather fiddly), but the instructions for operating the bluetooth apply to any 5020 series laptop with bluetooth installed.

Also, this was done using Slamd64 - where anything differs from a normal Slackware install, it will be prefixed with 'Slamd64'.

==Hardware==
Output of lspci:&lt;pre&gt;
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
00:02.0 PCI bridge: ATI Technologies Inc RS480 PCI-X Root Port
00:07.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)
00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev 02)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE)
06:05.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
06:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
06:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
06:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
06:06.4 Class 0805: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
&lt;/pre&gt;

===Overview===

* AMD Turion 64 ML-28 at 1.6 GHz with 128 KB L1 cache and 512 KB L2 cache
* 512 MB of DDR333 memory
* 15.4" Samsung LTN154X3-L01 WXGA LCD panel (1280 x 800)
* ATi Mobility Radeon X700 (128MB dedicated memory)
* 80GB (4200 RPM) (P)ATA Hard Drive ([http://www.seagate.com/cda/products/discsales/marketing/detail/0,1081,638,00.html Seagate Momentus 4200.2 - ST9808210A])
* Slot DVD Writer (DVD-R/RW, DVD+R/RW, DVD+R Dual Layer)
* Texas Instruments (TI7421) 6-in-1 card reader
* Gigabit Ethernet (Realtek RTL-8169 chipset?)
* 802.11 b/g Wireless LAN (Broadcom AirForce One 54g (BCM4318))
* ATi SB400 AC'97 Soundcard + Modem
* 1 x IR port
* 1 x IEEE-1394 (Firewire) port
* 4 x USB ports
* 1 x S-Video port
* 1 x VGA port
* 1 x PCMCIA slot

===Working===

* Video Card: ATI Mobility X700 (1280x800 - fglrx and radeon &amp; r300)
* Broadcom Wireless LAN Card (acer_acpi + ndiswrapper with bcmwl564.sys driver, available as 80211g.zip from Acer driver download area. Slamd64 - need Windows XP 64 driver).
* Soundcard (snd-atiixp as of alsa-driver-1.0.9b or kernel)
* Function/Hot Keys (have not tried all though; extra configuration required for 'multimedia' keys)
* Touchpad (Doesn't need a driver for basic functions)
* USB
* CD/RW, DVD+/-RW
* Ethernet card (works with Realtek 8169 driver)
* Battery Status
* PCMCIA
* 6-in-1 card reader (SD/ MMC &amp; MemoryStick/ Pro only at the moment - [http://tifmxx.berlios.de/ driver in progress])
* Bluetooth

===Not Tested, but probably works===

* Firewire
* Infra Red
* VGA out

==Kernel Configuration==

You will need to use a 2.6.19 or newer kernel to get this laptop to work properly in Linux without any extra kernel patching (see Troubleshooting for more information).

I would *strongly* recommend you always use the latest stable 2.6.x kernel with this laptop, since there are a lot of fixes going in that relate to this laptop (ATI chipset, apic, yenta socket, wireless drivers (b43), etc).

This should be very similar to any other AMD64 laptop with an ATi chipset (like the Acer Ferrari 4000 series- enable anything with 'ATI IXP', plus the relevant ACPI options. I'll put up more here about any necessary specific options later. However, I have *disabled* the framebuffer, as it doesn't play well with the X video drivers.

When building a new kernel make sure that you use the following options, if you want to use the ATI/fglrx driver:&lt;br&gt;
use '/dev/agpgart' as module&lt;br&gt;
turn off, the 'Direct Render Manager'&lt;br&gt;
(so you dont select 'radeon'..)&lt;br&gt;

==Hardware Package and Software Dependencies==
===Graphics===

Follow the instructions here [http://slackwiki.org/ATI_Graphics on the SlackWiki ATI Graphics Chip] to install and set up your video driver, using either radeon &amp; r300 or fglrx (both work fine on this laptop). It is also recommended that you enable the powersaving features of the driver of your choice, to reduce power consumption (particularly important when running from battery).

Note: These options do not work when you use dual-head (CRT+LCD)

====fglrx====

Use the latest versions, as these have support for ATi's "PowerPlay", allowing you to switch to low power modes (these modes trade off speed for reduced power consumption). The Mobility X700 has three; state 1 is the most energy efficient, state 3 the least efficient but best performing.

You can list the available and currently selected powerstate modes with (while running X):

 aticonfig --list-powerstates

and change the powestate with (again, while running X):

 aticonfig --set-powerstate=2 --effective=now

Generally, state 2 should be adequate for most of your needs (a lower state also helps keep the heat down on the laptop), state 1 for running off battery.

Be aware that you cannot set the powerstate dynamically with fglrx - ATI recommend you change it instead using ACPI events and shell scripts (Working examples required).

====radeon====

Edit /etc/X11/xorg.conf, add this to your radeon device section and restart X:

 Option      "DynamicClocks" "on"

Unfortunately, DynamicClocks is not as good at saving power as fglrx, and you have no control over the power states.

===Mouse===

To get advanced features, you will need to install the [http://web.telia.com/~u89404340/touchpad/ Synaptics Mousepad driver for X] and change your mouse driver in xorg.conf to use 'synaptics'. (I use the Synaptics driver mostly to disable 'Tap-to-Click')

To ensure the touchpad always has the same device name, create /etc/udev/rules.d/local.rules (if it doesn't exist) and add the following:

 BUS=="serio", SYSFS{description}=="i8042 Aux-3 Port", KERNEL=="mouse*", NAME="input/%k",SYMLINK+="input/touchpad"

You can now point xorg.conf towards /dev/input/touchpad for the touchpad (/dev/input/touchpad will always be a symlink to whichever device the touchpad is - this can vary depending on whether you plug another mouse into the system before or after booting).

===xorg.conf===

TBA

===Modem===
          
This is a Conexant HSF modem - it is incompatible with slmodemd (you therefore do _not_ need snd-atiixp-modem). The only drivers available for this modem are from [http://www.linuxant.com Linuxant] (the free-of-charge drivers are limited to 14.4K, you will need to pay if you want full 56.6K speeds and fax).

===Wireless===

To use the built in wireless, you need to firstly switch on the wireless, then load the b43 driver. You will also need to obtain the firmware for this card - see [http://linuxwireless.org/en/users/Drivers/b43#devicefirmware Linux Wireless] on where to get it from.

1. Enable Wireless

'''2.6.24:'''

* Download, build and install [http://code.google.com/p/aceracpi acer_acpi]
* Load acer_acpi: modprobe acer_acpi wireless=1

'''2.6.25 or newer:'''

* echo 1 &gt; /sys/devices/platform/acer-wmi/wireless
* Or create /etc/modprobe.d/acer-wmi and add "options acer-wmi wireless=1" to do this at boot time

2. Install b43 firmware

* Download, build and install b43-fwcutter - use the [http://www.slackbuilds.org SlackBuilds.org] Slackbuild for thos
* Follow the instructions on [http://linuxwireless.org/en/users/Drivers/b43#devicefirmware Linux Wireless] for your kernel version to extract the firmware and install it to /lib/firmware

(The orange light for the wireless at the front should turn on now)

3. Configure the wireless in /etc/rc.d/rc.inet1.conf

Note: I deleted rc.wireless.conf as it is unecessary and keeps trying to override rc.inet1.conf (besides, configuring wireless in rc.inet1.conf is the future).

===Bluetooth===

The bluetooth is an internal USB dongle. To turn it on:

'''2.6.24:'''

* Download, build and install [http://code.google.com/p/aceracpi acer_acpi]
* Load acer_acpi: modprobe acer_acpi bluetooth=1

'''2.6.25 or newer:'''

* echo 1 &gt; /sys/devices/platform/acer-wmi/bluetooth
* Or create /etc/modprobe.d/acer-wmi and add "options acer-wmi bluetooth=1" to do this at boot time

The bluetooth device can now be seen with lsusb (it is not visible when bluetooth if you don't enable it through acer_acpi/ acer-wmi).

===Special Keys===

There is a keymap for the special keys available [http://www.fwconsult.com/acer-install/index.html here].

However, I have had problems with it on my UK layout keyboard so would not recommend using it at the moment.

===Special Keys with X===

====HAL====

You will need, at a minimum, HAL 0.5.10 and hal-info 20070725. The Aspire 5020 has been submitted to HAL as part of their keyboard quirk project, so the extra keys which generated dmesg messages, will now generate proper keycodes.

====X====

There is now a generic acer_laptop keyboard layout in upstream xkeyboard-config (which works in tandem with HAL to map the extra keys). This will be in the next xkeyboard-config release after 1.0 (it is therefore unlikely to make the next X.Org release).

You can also use the evdev layout instead.

===Hardware Monitoring===

Unfortunately, the extent of 'hardware monitoring' on this system comes through 3 thermal zones provided by ACPI.

You can play around with using I2C to access the SMBus, but the hardware on the other end of it appears to be a National Semiconductors chip of sorts that is not supported under Linux (and based on comments on the lm_sensors mailing list, due to various problems, is not very likely to be either).

===Suspend===

Suspend does work on this laptop (assuming you don't have any funny PCMCIA, USB or Firewire devices attached that will break it).

'''In a terminal'''

You will need either vbetool or a 2.6.17-rc (or newer) kernel with s2ram (found in [http://suspend.sourceforge.net suspend]).

Using s2ram:
 s2ram -f -p

Using swusp (run this command after resuming):
  vbetool post

'''In X'''

Works with either radeon or fglrx (you don't need to run s2ram if you suspend from X).

===Card Reader===

This card reader is not fully supported in Linux yet. There is an in development driver, [http://tifmxx.berlios.de tifmxx], that currently supports MMC/ SD, and Memory Stick/ Pro. If you want to help out the project, hardware donations are welcome for unsupported hardware (be aware that the developer's card reader can not physically support SmartMedia cards).

==Troubleshooting==

===HPET===

Not available on this laptop - locks hard with hpet=force (I suspect HPET's are only available on the newer SB480 chipsets).

===DVDs will not play back===

You need to set the DVD region before you can play any DVDs. The 'regionset' tool for Linux will let you do this (otherwise you will have lots of strange error messages in dmesg).

===Suspend/ Resume does not work===

Please be aware that kernel updates can break this. If that's the case, I will try and update this page to reflect that.

Otherwise, go back and make sure you have applied the necessary patch specified earlier in "Suspend" to your kernel. Also, try unplugging any devices attached to the laptop, rebooting (some drivers can be a bit funny otherwise) and then try suspend/ resume. If it now works, then one of your devices or a driver somewhere is breaking suspend - in which case, you should report the bug to the relevant person/ place.

==Contributors==

*[http://slackwiki.org/User:Cathectic Carlos Corbacho (aka cathectic)]
*[http://slackwiki.org/User:Funmain Funmain]

==External Links/ References==
* [http://forums.slamd64.com/viewtopic.php?t=27 fglrx on Slamd64]
* [http://www.fwconsult.com/acer-install/index.html Installing Gentoo (2005.0) on an Acer 5021NWLCi]
* [http://gentoo-wiki.com/HARDWARE_Gentoo_Acer_Ferrari_4005WLMi_Manual Gentoo Acer Ferrari 4005WLMi Manual]
* [http://website.lineone.net/~bryanrpoole/atiixp-modem.html ATI-IXP MC97 Modem Development / Configuration Information]
* [http://bugzilla.kernel.org/show_bug.cgi?id=3927 Kernel Bugzilla entry for AMD64/ ATi timer running fast problem]
* [http://doube.net/3023wlmi.html Linux and Windows on an Acer Aspire 3023WLMi]</text>
    <sha1>c8242f398c29fa85440c90f09aa6c83436c5c0b0</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Administration (General)</title>
  <ns>0</ns>
  <id>38</id>
  <revision>
    <id>59</id>
    <timestamp>2009-06-02T03:00:21Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="883" xml:space="preserve">== Hostname ==

You can change a Slackware box's &lt;code&gt;hostname&lt;/code&gt; by two methods:

1) Edit &lt;code&gt;/etc/HOSTNAME&lt;/code&gt;

2) Use the hostname command-

:On any running Linux system you can change its hostname with the command ‘hostname‘.

::'''&lt;code&gt;#hostname&lt;/code&gt;''' without any parameter it will output the current hostname of the system.

::'''&lt;code&gt;hostname –fqd&lt;/code&gt;''' will output the fully qualified domain name (or FQDN) of the system.

::'''&lt;code&gt;hostname NEW_NAME&lt;/code&gt;''' will set the hostname of the system to NEW_NAME. This is active right away and will remain like that until the system will be rebooted (because at system boot it will set this from some particular file configurations - see bellow how to set this permanently). You will most probably need to exit the current shell in order to see the change in your shell prompt.


[[Category:Tutorials]]</text>
    <sha1>dad382dc6f1776b651312404979a0d67f0bd1425</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Anti-Torrent Activity Block</title>
  <ns>0</ns>
  <id>39</id>
  <revision>
    <id>60</id>
    <timestamp>2009-06-02T03:01:01Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="740" xml:space="preserve">[[Category:Tips]]

Many ISP's have recently begun to actively seek out and stop torrents from seeding, legal or otherwise. The most notorious offender is Comcast, who blocks torrents by sending a Terminate signal to one of the clients; these packets tell the Bit Torrent client to close the connection.

In the interest of being able to share legal media, such as linux iso's, you may add the following to your IP tables to have these malicious packets dropped:

&lt;pre&gt;iptables -A INPUT -p tcp --dport &lt;YOUR TORRENT PORT&gt; --tcp-flags RST RST -j DROP&lt;/pre&gt;


Credit goes to user "James" in the comments section of a Reg newspost, which you can find here: http://www.theregister.com/2007/10/20/comcast_denies_bittorrent_busting_again/comments/</text>
    <sha1>2224bb3cb6353681f4a25dcd282256c53e545057</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Apache-cgi</title>
  <ns>0</ns>
  <id>40</id>
  <revision>
    <id>61</id>
    <timestamp>2009-06-02T03:02:50Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tips</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1147" xml:space="preserve">[[Category:Tips]]

==To enable a cgi directory for each user==

In order to give each user their own cgi-bin directory, edit the:

:Apache1 (Slackware pre-12.0): &lt;code&gt;/etc/httpd/httpd.conf&lt;/code&gt; file&lt;br&gt;
:Apache2 (Slackware 12.0+): &lt;code&gt;/etc/httpd/extra/httpd-users.conf&lt;/code&gt; file&lt;br&gt;

::...and add:

:&lt;code&gt;&lt;Directory /home/*/public_html/cgi-bin/&gt;&lt;/code&gt;
:&lt;code&gt;Options ExecCGI&lt;/code&gt;
:&lt;code&gt;SetHandler cgi-script&lt;/code&gt;
:&lt;code&gt;&lt;/Directory&gt;&lt;/code&gt;

Then, presuming that UserDir is set to public_html, a cgi program example.cgi could be loaded from that directory as:

::&lt;code&gt;http&amp;#58;//example.com/~rbowen/cgi-bin/example.cgi&lt;/code&gt;


==To enable a cgi directory for each virtual host==

In the Virtual Host section of your apache config file (&lt;code&gt;/etc/apache/httpd.conf&lt;/code&gt;) add the &lt;code&gt;ScriptAlias&lt;/code&gt; line below.

:&lt;code&gt;&lt;VirtualHost *:80&gt;&lt;/code&gt;
:::&lt;code&gt;ServerName www.''MyDomain''.org&lt;/code&gt;
:::&lt;code&gt;DocumentRoot /home/''MyDomain''/public_html&lt;/code&gt;
:::&lt;code&gt;ErrorLog /var/log/''MyDomain''/error.log&lt;/code&gt;
:::&lt;code&gt;&lt;b&gt;ScriptAlias /cgi-bin/ "/home/''MyDomain''/public_html/cgi-bin/"&lt;/b&gt;&lt;/code&gt;
:&lt;code&gt;&lt;/VirtualHost&gt;&lt;/code&gt;</text>
    <sha1>f9fd21516915f636a94ec865ddb7fdfd624926f5</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Bash Autocompletion</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>62</id>
    <timestamp>2009-06-02T03:03:48Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2591" xml:space="preserve">[[Category:Tips]]

Did you know that Bash has a really powerful autocompletion system, which can and usually will make your life easier? If you have used ZSH, you probably know what I'm talking about.

For example, you can type

   svn co''&lt;TAB&gt;&lt;TAB&gt;''

and bash will attempt to auto complete as it does normally with paths and variables, but instead it will output:

  ismael@damned_02:~/src/chkout$ svn co''&lt;TAB&gt;&lt;TAB&gt;''
  co      commit  copy    
  ismael@damned_02:~/src/chkout$ svn co

Then you can type:

  ismael@damned_02:~/src/chkout$ svn com''&lt;TAB&gt;''

and BASH will auto complete to:

  ismael@damned_02:~/src/chkout$ svn commit

Or if you're running as root and want to get rid of that *$@&amp; module wich keeps crashing your machine:

   root@damned_02:~# rmmod n''&lt;TAB&gt;''
   root@damned_02:~# rmmod nvidia


If you think all that is neat, all that you have to do to enable this kind of auto completion in Slackware is to install the bash-completion package, which can be found under [http://slackware.osuosl.org/slackware-11.0/extra/bash-completion/bash-completion-20060301-noarch-1.tgz /extra]:

   root@damned_02:~# mount /mnt/cdrom
   root@damned_02:~# installpkg /mnt/cdrom/extra/bash-completion/bash-completion-20060301-noarch-1.tgz
   ...

(BTW, bash-completion also autocompletes ''installpkg, upgradepkg'' and ''removepkg'' with .tgz files and installed packages for ''removepkg''. It can also fill mount commands with data from fstab).

Then you can just logout and login again or

   source /etc/bash_completion

and ''voila''!


You can see which commands have autocompletion by issuing:

  complete -p | sed -e's/.* \([^ ]\+\)/\1/' | sort | less

You can also add your own commands at /etc/bash_completion.d/ You may want to see the available completions to understand how they work.

For your own personal user account you can edit your ~/.bash_completion file.

Here is a sample BASH completion function I made to give the script 'test' 3 completion
options:

&lt;pre&gt;
_test ()
{
         local cur
         cur=${COMP_WORDS[COMP_CWORD]}

         if [[ "$cur" == -* ]]; then
         COMPREPLY=( $( compgen -W '-option -test -foobar' -- $cur ))

         else
             _filedir
         fi
}

complete -F _test test
&lt;/pre&gt;

I put that into my ~/.bash_completion file and now

  $ test -&lt;tab&gt;
  -foobar  -option  -test

brings up those three options (-option,-test and -foobar). You have to reload your terminal first to see the changes or re-source /etc/bash_completion

  $ . /etc/bash_completion

or just re-source your ~/.bash_completion

  $ . ./.bash_completion</text>
    <sha1>adcb7eb632105ef5e55cac606464c718f3a83a79</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Booting</title>
  <ns>0</ns>
  <id>42</id>
  <revision>
    <id>63</id>
    <timestamp>2009-06-02T03:04:36Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="636" xml:space="preserve">[[Category:Tips]]

==How To Boot Into Single User Mode==
During your LILO startup where it pauses for 5 or 30 seconds, at the &lt;code&gt;boot:&lt;/code&gt; prompt, if you type &lt;code&gt;&lt;i&gt;image_name&lt;/i&gt; 1&lt;/code&gt;, the boot will continue but you will be in [[Single User Mode]].

:EXAMPLE: On my dual boot system, my Linux image is named "Linux" and my Windows image is named "windoz".  To boot into single user mode, at the &lt;code&gt;boot:&lt;/code&gt; prompt I would type: &lt;code&gt;boot: &lt;b&gt;linux 1&lt;/b&gt;&lt;/code&gt;

TIP: If you did not install your system with a pause, you should really run [[liloconfig]] and put at least a 5 second pause in.  Sometimes it's useful.</text>
    <sha1>764cbb264d3c9ae59342df38de141e9306b287d1</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Captive NTFS</title>
  <ns>0</ns>
  <id>43</id>
  <revision>
    <id>64</id>
    <timestamp>2009-06-02T03:06:00Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4448" xml:space="preserve">[[Category:Tutorials]]

[http://www.jankratochvil.net/project/captive/ Captive NTFS] project implements the first full read/write free access to NTFS disk drives. You can mount your Microsoft Windows NT, 200x or XP partition as a transparently accessible volume for your GNU/Linux.

Tutorial written by Thomas York
straterra@gmail.com

'''Read through the whole thing several times before attempting!'''

===Step 1: Download these files===

You will need to download several files.

 A: http://www.jankratochvil.net/project/captive/dist/lufs-0.9.7captive8.tar.gz
 B: http://www.jankratochvil.net/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2.tar.gz
 C: http://www.jankratochvil.net/project/captive/dist/captive-1.1.5.tar.gz
 D: http://linux-ntfs.sourceforge.net/snapshots/ntfsprogs-200510151016.tar.bz2

Note, if you cannot download the ntfsprogs file, browse http://linux-ntfs.sourceforge.net/snapshots/ and pick up the latest snapshot

===Step 2: Uncompress the archives.===

We will now uncompress the archives to get ready for compiling. If you do not know how to do this, You can use the commands below.

 1: tar xzvf lufs-0.9.7captive8.tar.gz
 2: tar xzvf gnome-vfs-httpcaptive-2.3.8captive2.tar.gz
 3: tar xzvf captive-1.1.5.tar.gz
 4: tar xjvf ntfsprogs-200503060058.tar.bz2

Step 3: Compiling

===A. NTFS Programs package===

We will now start by compiling the most necessary of packages first. You need to start with ntfsprogs. Use the example below.

 1: cd ntfsprogs-200503060058
 2: ./configure --prefix=/usr
 3: make
 4: su

Now, here is where you have to make a decision. It is highly advised that you make a package over using 'make install.' If you wish to make a package, merely run :

 1: checkinstall

If you wish to use the 'make install' method, just run :

 1: make install

===B. Gnome VFS package===

Next, we will compile Gnome VFS for the graphical installer. Run the command below :

 1: exit
 2: cd ..
 3: cd gnome-vfs-httpcaptive-2.3.8captive2
 4: ./configure --prefix=/usr
 5: make
 6: su

Again, you must make a decision. It is HIGHLY recommended that you use checkinstall to create a package. If you want to create a package, run :

 1: checkinstall

If you wish to use the 'make install' method, merely run :

 2: make install

BUG FIX. If when you run make, you have an Error 1, try using this patch: http://bugs.gentoo.org/attachment.cgi?id=48015

===C. LUFS Package===

BUG FIX. If you use a 2.6 kernel later than 2.6.9, then you need to follow the instructions located at http://www.jankratochvil.net/pipermail/captive-list/2004-December/000645.html before trying to compile LUFS. Thank you!

Now, we make the tool that will provide interaction between the kernel and Captive! This is the most important package, so pay attention. Run the commands below :

 1: exit
 2: cd ..
 3: cd lufs-0.9.7captive8
 4: ./configure --prefix=/usr
 5: make
 6: su

Again, you must decide on checkinstall or 'make install'. Either run :

 1: checkinstall

Or :

 1: make install

===D. Captive NTFS Package===

This also is the most important package because without the Captive package, nothing will work! Now we need to setup the environment for captive..Run these commands!

 1: groupadd captive
 2: useradd -d /dev/null -g captive -s /dev/null captive
 3: exit
 4: cd ..
 5: cd captive-1.1.5
 6: ./configure --prefix=/usr --enable-install-pkg=yes
 7: make
 8: su

Again, checkinstall or make install..you get the jist by now..Either :

 1: checkinstall

Or :

 1: make install

Now everything should be ready. Make sure you have your NTFS partition mounted already using the kernel's NTFS driver. If you do not know how to do this, try this command and play with it:

 1: mount -t ntfs /dev/hda1 /mnt/windows

Now, while you have X running, run these commands:

 1: exit
 2: xhost +localhost
 3: su
 4: captive-install-acquire

When you run the captive-install-acquire command, you need to hit Forward, Hit Skip, Click Browse.. and point it to the mounted location of your NTFS partition (should already be mounted), hit Skip, Hit OK, and finally hit OK again. Then, continue with the command below.

 1: captive-install-fstab --add

Now, you should unmount the NTFS partition and remount it with captive-ntfs

 1: umount /mnt/windows
 2: mount -t captive-ntfs /dev/hda1 /mnt/windows

By now, everything should be setup correctly and working. If you have ANY troubles, talk to me on irc.freenode.net ##slackware.</text>
    <sha1>94a82aa83f23442ceb321dfaf81053f6d67647f9</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Changes 10.2 11.0</title>
  <ns>0</ns>
  <id>44</id>
  <revision>
    <id>65</id>
    <timestamp>2009-06-02T03:06:45Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10132" xml:space="preserve">= Purpose =

The purpose of this file is to document the new packages (Package 
Additions) and removed packages (Package Removals) during the 
development cycle from Slackware 10.2 through Slackware 11.0, as
well as to point out some potential "gotchas" that can users can
avoid by arming themselves with a little knowledge.


=  Package Additions Since 10.2 =

* a/pcmciautils
* a/sharutils (split from bin)
* a/acl (split from xfsprogs)
* a/attr (split from xfsprogs)
* a/sysfsutils
* a/sysstat
* ap/diffstat
* ap/dmapi (split from xfsprogs)
* ap/linuxdoc-tools
* ap/lm_sensors
* ap/xfsdump (split from xfsprogs)
* d/git
* d/mercurial
* d/ruby
* kde/amarok
* kde/qca
* kde/qca-tls
* l/apr
* l/apr-util
* l/cairo
* l/db42 (for backwards compatibility)
* l/db44 (upgrade from db4; see 'Package Removals' and 'Other Concerns' for more information)
* l/desktop-file-utils
* l/freetype (split from x11) - see note in "Other Concerns" below
* l/gd
* l/gnome-icon-theme
* l/hicolor-icon-theme
* l/libgpod
* l/libmtp
* l/libmusicbrainz
* l/libnjb
* l/libtheora
* l/libtunepimp
* l/libvisual (library only, no plugins yet - but this should allow for compiling audio visualization plugins for amarok without a recompile of amarok itself)
* l/mm (split from apache)
* l/mpfr (split from gmp)
* l/neon (split from subversion)
* l/slang1 (renamed from slang)
* l/slang (Added slang 2)
* n/mailx (renamed from nail)
* n/rdesktop
* x/dejavu-ttf 
* x/fontconfig (split from x11) - see note in "Other Concerns" below
* x/ttf-indic-fonts - see note in "Other Concerns" below
* xap/seamonkey
* xap/vim-gvim (renamed from xvim) - this package now depends on ap/vim
* kernels/huge26.s/* - added a 2.6.17.13 kernel to the official (supported) package set.  The user will be given a choice of whether to install the 2.4.33.3 or 2.6.17.13 kernel.  If a 2.6 kernel is used, additional packages must be added after the installation -- at the very least the kernel-modules package.  Possibly also the kernel-headers to provide /usr/include/sound used to compile ALSA applications.
* extra/linux-smp-2.6.17.13/* - added a 2.6.17.13 kernel, modules, and headers with SMP and hyperthreading support, optimized for i686 or better cores (including dual core CPUs).


=  Package Removals Since 10.2 =
* ap/sgml-tools (replaced with linuxdoc-tools)
* d/python-demo (merged with python package)
* d/python-tools (merged with python package)
* l/db3 (moved to /pasture)
* l/db31 (moved to /pasture)
* l/db4-* (moved to /pasture)
* n/nail (renamed to mailx - see "Package Additions")
* xap/abiword (became a pure Gnome app)
* xap/mozilla (replaced with seamonkey)
* xap/xvim (renamed to vim-gvim) - see note above in "Package Additions"


=  Other Concerns =

First of all, if you did not *upgrade* (in other words, you have a fresh installation), most of this is not relevant to you; you won't need to merge any config files or anything along those lines.  However, this is still worth reading, as it gives you an idea of things to look for in future upgrades.
 
* Both the 2.4.x and 2.6.x kernels included are now compiled with high memory support
* Many old bison and db packages were pasture-ized from d/ and extra/ and so on; after upgrading/installing Slackware 11.0, you should have *one* bison package and *two* db packages (the db packages are listed in the package additions above)
* n/php now depends on l/freetype (l/freetype was split from x/x11)
* n/apache now depends on l/mm (l/mm was split from apache)
* xap/xine-lib now depends on l/libtheora if you want to play ogg-files in xine (and Amarok using the xine engine)
* a/devs was upgraded during the -current development cycle.  You CANNOT upgrade this package while udev is running - you'll need to chmod -x /etc/rc.d/rc.udev, reboot, upgrade the devs package, and then reboot again.  Actually, you don't *have* to reboot again, but if you know that, then you likely know how to go about it that way :)
If you don't know the trick, here's how to do it (no secrets here):
  sh /etc/rc.d/rc.udev stop
  umount /dev/pts
  umount /dev/shm
  umount -l /dev
  installpkg devs*.tgz
  sh /etc/rc.d/rc.udev start
  mount -av
Thanks to Richard Hoyle for this information on doing it without a reboot.
* So long as we're on the subject of a/devs, be aware that this package is still *required* in order to boot, even if you're using a 2.6 kernel and udev, so don't remove it.
* a/lilo and a/kernel-* were upgraded during the -current development cycle, so be sure to run /sbin/lilo prior to rebooting.
* glibc was upgraded during the -current development cycle, so be sure to follow the instructions in [http://slackware.osuosl.org/slackware-11.0/UPGRADE.TXT UPGRADE.TXT] when upgrading (do the upgrade in runlevel 1).
* There was a major upgrade to a/udev and a/sysvinit - make *sure* you merge the *.new scripts in /etc/rc.d prior to rebooting or you *will* have problems.
* If you're having trouble with udev, make sure you've syncronized all of the .new config files and init scripts first.  According to Pat Volkerding (the Slackware maintainer), most of these issues can "be fixed with a little bit of fine tuning, such as blacklisting unwanted modules in /etc/modprobe.d/blacklist and loading the desired replacements in /etc/rc.d/rc.modules," but simply blacklisting them will often result in udev loading the correct modules.  Also, keep in mind that newer versions of udev (084+) require at least a 2.6.15.x kernel.  Experiment with it before resorting to this, but if you simply must have one of them, there are alternate versions of udev in /extra.
* If you're running a 2.6 kernel and new udev (084+) on a router, you'll probably need to uncomment (and possibly edit to suit) the rules in /etc/udev/rules.d/network-devices.rules to make your interfaces always get the same names assigned.  Hotplugging events are generated (and processed) in random order by udev, so there's no guarantee that your current eth0 will *always* be eth0 unless you uncomment (and possibly edit) those rules.
* If you need custom udev rules, DO NOT edit the default udev.rules file - any changes you make will be clobbered with the next udev upgrade.  The correct way is to add a custom file to the /etc/udev/rules.d/ directory - most people use '10-local.rules' - and add your custom rules there.  If there is some reason that one of the default rules needs changed, mail PiterPunk and/or Pat with an explanation.
* The psmouse module is blacklisted by default in the /etc/modprobe.d/blacklist file due to problems with the default kernel options used when it loads; this allows you to load it (from rc.modules, for example) with option "proto=imps" if you need it, or you are certainly free to comment it out in the blacklist file if it works fine for you with the kernel defaults.
* As indicated in the Package Additions section, freetype and fontconfig were split out of the main X11 packages.  You need to upgrade the main x11 package first, then install fontconfig and freetype, then upgrade the remainder of the x11 packs; otherwise, they give an error during postinstall about not being able to load fontconfig libs.
* xap/seamonkey was chosen to provide the Mozilla development environment (primarily because the official binaries are used for the Firefox package, and these do not contain the development headers).  At this time, only GAIM links with SeaMonkey's libraries, but if you are planning to compile something needing "Mozilla" libraries and headers, be sure SeaMonkey is installed.
* There have been quite a few reports that fonts are 'ugly' after upgrading; one way to fix it is to remove /etc/fonts/local.conf if it exists.  If it doesn't exist, or that doesn't work, go into KControl's font settings, uncheck the box for antialiasing, and apply the changes.  Then, recheck the box and apply the changes.  This should create a $HOME/.fonts.conf file.  Thanks to Pat for the initial suggestion with KControl, and thanks to ananke for working out exactly what changes are necessary to fix it.
* Slackware's vim package now includes a $VIM/vimrc file (in this case, /usr/share/vim/vimrc) for vim's default configuration. This default should provide a suitable start for most and your ~/.vimrc will override it if not, but if you had previously not explicitly set, e.g., 'backup', because vim's compiled-in default resulted in no backups and that suited you, the $VIM/vimrc includes 'set backup' and you will suddenly be keeping backups. These settings can be overridden individually (in this case with 'set nobackup') but one of several ways to avoid having $VIM/vimrc affecting your configuration at all is to put this at the top of your ~/.vimrc, overriding everything in $VIM/vimrc:
 set all&amp; " reset all options to compiled in defaults (thanks to deryni in #vim)
 unmap Q " remove mapping to gq
 syntax off " turn syntax off
 filetype plugin indent off " turn filetype detection off
 augroup! vimrcEx " delete the autocommand group that wraps text, etc.
* If you have an ati radeon card and are experiencing problems with it locking up, there is a patched set of ati modules at /extra/x11-radeon-patched/ - if you are not experiencing problems, then don't install this, as it does tend to cause problems if you weren't already having them...
* The ttf-indic-fonts package supports Bengali, Devanagari, Gujarati, Kannada, Malayalam, Oriya, Punjabi, Tamil, and Telugu.  For information about fully enabling Indic support (including input), see: /usr/doc/Linux-HOWTOs/Indic-Fonts-HOWTO.
* As part of the upgrade to nfs-utils and portmap, the /etc/rc.d/rc.portmap script has been replaced by /etc/rc.d/rc.rpc.  The rc.rpc script does not have to be executable unless you plan on mounting nfs shares &lt;b&gt;manually&lt;/b&gt;, as it will be run by other init scripts if any nfs shares or mounts are detected.
* php5 and lvm2 are available in /extra if you would like to use them
* cairo-1.2.4, flex-2.5.33, fontconfig-2.4.1, gutenprint-5.0.0, hplip-1.6.9, iptables-1.3.6, and wpa_supplicant-0.4.9 are available in /testing if you need/want them

[http://www.slackforum.de/wiki/Aenderungen102110 german version]</text>
    <sha1>13e19ada68315b7579510342fd63c10e6eb83701</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Changes 9.1 10.0</title>
  <ns>0</ns>
  <id>45</id>
  <revision>
    <id>66</id>
    <timestamp>2009-06-02T03:07:22Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3601" xml:space="preserve">= Purpose =
The purpose of this page is to document the new packages (Package Additions) and removed packages (Package Removals) during the release cycle from Slackware 9.1 to 10.0, as well as any other relevant information for the upgrade.

= Package Additions Since 9.1 =

* a/udev-025-i486-1.tgz:  Added udev-0.25
* ap/bpe-2.01.00-i486-1.tgz: (split from bin package)
* ap/rzip-2.0-i486-1.tgz:  Added rzip-2.0 (suggested by Daniel de Kok)
* ap/mdadm-1.5.0-i486-1.tgz:  Added mdadm-1.5.0
* ap/normalize-0.7.6-i486-1.tgz:  Added normalize-0.7.6
* ap/sgml-tools-1.0.9-i486-11.tgz:  Added docbook-utils-0.6.14
* ap/sgml-tools-1.0.9-i486-10.tgz:  Added gtk-doc-1.2
* d/doxygen-1.3.4-i486-1.tgz:  Added doxygen-1.3.4 (used by KDevelop)
* gnome/gpdf-0.131-i486-1.tgz:  Added gpdf-0.131
* gnome/epiphany-extensions-0.8.2-i486-1.tgz:  Added epiphany-extensions-0.8.2
* gnome/gnome-keyring-0.2.1-i486-1.tgz:  Added gnome-keyring-0.2.1
* gnome/gnome-netstatus-2.6.1-i486-1.tgz:  Added gnome-netstatus-2.6.1
* gnome/gnome-themes-extras-0.7-i486-1.tgz:  Added gnome-themes-extras-0.7
* gnome/gok-0.10.2-i486-1.tgz:  Added gok-0.10.2
* gnome/hicolor-icon-theme-0.5-noarch-1.tgz:  Added hicolor-icon-theme-0.5
* gnome/libcroco-0.5.1-i486-1.tgz:  Added libcroco-0.5.1
* gnome/libxklavier-1.02-i486-1.tgz:  Added libxklavier-1.02
* gnome/metacity-2.8.1-i486-1.tgz:  Added metacity-2.8.1
* gnome/shared-mime-info-0.14-i486-1.tgz:  Added shared-mime-info-0.14
* gnome/totem-0.99.11-i486-1.tgz:  Added totem-0.99.11
* l/mhash-0.9.1-i486-1.tgz:  Added mhash-0.9.1
* l/db4-4.2.52-i486-1.tgz:  Added db-4.2.52
* l/db31-3.1.17-i486-1.tgz: Added for compatibility
* l/libcaca-0.9-i486-1.tgz:  Added libcaca-0.9 (Colour AsCii Art library)
* l/netpbm-10.18.12-i486-1.tgz:  Added netpbm-10.18.12 (this replaces libgr)
* l/lcms-1.12-i486-1.tgz:  Added lcms-1.12
* l/taglib-1.0-i486-1.tgz:  Added taglib-1.0
* l/libwmf-0.2.8.2-i486-1.tgz:  Added libwmf-0.2.8.2
* l/libwmf-docs-0.2.8.2-noarch-1.tgz:  Added docs package for libwmf-0.2.8.2
* kde/kdeaccessibility-3.2.0-i486-1.tgz:  Added kdeaccessibility-3.2.0
* kde/wv2-0.2.1-i486-1.tgz:  Added wv2-0.2.1 (used by KWord to import various MS document formats)
* n/dnsmasq-2.6-i486-1.tgz:  Added dnsmasq-2.6
* n/irssi-0.8.9-i486-1.tgz:  Added irssi-0.8.9
* n/iproute2-2.6.7_ss040608-i486-1.tgz (moved from /extra into mainline)
* n/whois-4.6.16-i486-1.tgz: (split from tcpip package)
* xap/gkrellm-2.2.0test1-i486-1.tgz:  Added gkrellm-2.2.0-test1


= Package Removals Since 9.1 =

* a/devfsd-1.3.25-i486-3.tgz:  Obsolete, and retired to /pasture
* ap/oggutils-1.0-i386-3.tgz:  Removed.
* gnome/acme-2.4.2-i486-1.tgz:  Removed.
* gnome/gal2-2.1.4-i486-1.tgz:  Removed.
* gnome/gnome-extra-themes-1.0.1-noarch-1.tgz:  Removed (no need for theme bloat).
* gnome/linc-1.0.3-i486-1.tgz:  Removed.
* l/db1-1.85-i386-1.tgz:  Removed.  (off to /pasture)
* l/db2-2.4.14-i386-1.tgz:  Removed.  (off to /pasture)
* freetype-1.3.1, gcl-2.4.4, libxml-1.8.17, and xview-3.2p1.4 - moved to pasture


=  Other Concerns =

* a/utempter-1.1.1-i486-1.tgz:  Moved from the L series
* gnome/abiword-2.0.0-i486-1.tgz:  Moved from XAP since version 2.0.0 now depends on several GNOME libraries
* x/:  Switched to X11R6.7.0 from X.Org. 
* extra/k3b/k3b-0.11.11-i486-1.tgz:  k3b was added to /extra


= DISCLAIMER =
I wasn't running Slackware (I didn't even know what linux was at the time) during the 9.1 --&gt; 10.0 jump, so this document was created by scanning the ChangeLog and double-checking with grep usage.  If I've missed something important, I'm sorry, but that's the way it goes...  :)  --robw810</text>
    <sha1>9330060c3505af2875123c3a5bb655be4d24722f</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Church of the SubGenius</title>
  <ns>0</ns>
  <id>46</id>
  <revision>
    <id>67</id>
    <timestamp>2009-06-02T03:07:59Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1681" xml:space="preserve">There have been many stories, legends, and rumors involving the religious organization known as the Church of the SubGenius.  The founder of the Church, J.R. "Bob" Dobbs, was assassinated in San Francisco in 1984; yet members of the Church claim that he has returned from the dead many times since then.

As for the relationship between Slackware Linux and the Church of the SubGenius: Patrick "The Man" Volkerding is an ordained Church minister.  The term "Slack" itself stems from the SubGenius phrase "[[Slack]]."  This was the intent of Slackware: to achieve "Slack" through ease of use, reliability, durability, and the rejection of unnecessary, mainstream "flash and sizzle" utilities.

The Church of the SubGenius has long endorsed and promoted Slackware.

"Bob" and the Church have declared an apocalyptic prophecy that the end of the world will occur on the morning of July 5th, 1998.  On this date (which has apparently not arrived yet, according to the Church), a fleet of alien flying saucers will arrive to destroy the "normal" civilization of Earth.  Only the members of the Church of the SubGenius will be saved from the carnage, according to "Bob."

Members of the Church gather in a festival campground in upstate New York at the beginning of July to celebrate the impending apocalypse, or "X-Day."  Pat Volkerding himself is among the attendees each year, and he (along with other Church members) gladly greets all pilgrims and Church members who travel to New York to attend the festivities.

=== External Links ===

* http://www.subgenius.com -- Official home page of the Church of the SubGenius
* http://www.modemac.com/x-day -- X-Day

[[Category:Information]]</text>
    <sha1>ab38d4c296381944a114bdd4cf48d2e7b348a42d</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Compiz</title>
  <ns>0</ns>
  <id>47</id>
  <revision>
    <id>68</id>
    <timestamp>2009-06-02T03:08:31Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2310" xml:space="preserve">[[Category:Tutorials]]

== Configuring X ==


== Compiz Setup ==

After you've configured X Properly, you can start setting up Compiz's configuration files.
These configuration files are generated automatically by Compiz, given 2 conditions.

1. The existance of a .compiz directory in home

     &lt;sub&gt;mkdir ~/.compiz&lt;/sub&gt;

2. Running Compiz, calling to read configuration files (although not present, yet)

     &lt;sub&gt;compiz --replace ini decoration &amp; kde-window-decorator &amp;&lt;/sub&gt;

This loads compiz up, creating default configuration files in "~/.compiz/options/", while enabling
two plugins "ini" and "decoration". Ini to allow read/write of configuration files, and "decoration"
to use window decorations (the title bar of programs).

== Configuring Compiz ==

Once you've successfully loaded compiz and created config files in, you can now configure plugins.
Open up ~/.compiz/options/general-allscreens.conf for editing.

     &lt;sub&gt;pico ~/.compiz/options/general-allscreens.conf&lt;/sub&gt;

Edit the first line to include Plugins you will want to use. Plugins are stored in /usr/lib/compiz/ as
lib* files.
My plugins line:
     &lt;sub&gt;active_plugins=ini,decoration,svg,png,wobbly,fade,minimize,cube,move,place,resize,rotate,scale,switcher,water,zoom,screenshot&lt;/sub&gt;
Save this file, now edit ~/.compiz/options/decoration-allscreens.conf
and alter the line "command=" to look like this:
     &lt;sub&gt;command=kde-window-decorator&lt;/sub&gt;
Save and exit.
Test your work, (and also create more config files) like this:
     &lt;sub&gt;killall -9 kde-window-decorator ; killall -9 compiz ; compiz --replace ini &amp; &lt;/sub&gt;
You'll notice ~/.compiz/options/ is now populated with more configuration files. Filled with keybindings and behavior definitions.
I'll leave figuring these out to you.

Anytime you change and save a configuration file. Restart compiz to test.
     &lt;sub&gt;compiz --replace ini &amp;&lt;/sub&gt;

Here are a few interesting config options.

In general-screen0.conf
     &lt;sub&gt;hsize=4&lt;/sub&gt;
Change 4 to anything from 1 to 10 to change the number of sides of the "cube".
In cube-screen0.conf image files are read from /usr/share/compiz/:
     &lt;sub&gt;images=picture&lt;/sub&gt;
This loads "picture.png" on the top of the cube, while :
     &lt;sub&gt;skydome_image=picture&lt;/sub&gt;
Loads "picture.png" as the background image behind the cube.</text>
    <sha1>2161006c60837be7acb553c582964042efc3cf01</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Console-Only Communication</title>
  <ns>0</ns>
  <id>48</id>
  <revision>
    <id>69</id>
    <timestamp>2009-06-02T03:09:42Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8910" xml:space="preserve">HOWTO: access on-line resorces on the internet using only console-based tools.

== Overview ==
Many times, particularly when things aren't working as expected, you may find yourself restricted to a console-only (non-X or non-graphical) session. If you have networking running, you can still access on-line support tools through your console. This tutorial shows you how to:

* Use virtual consoles to increase the number of consoles you can use simultaneously;
* Use the &lt;tt&gt;screen&lt;/tt&gt; to create sessions that are persistant even after you close the console;
* Use &lt;tt&gt;irssi&lt;/tt&gt; to access the irc network and ##slackware on irc.freenode.org;
* Use &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; to access HTTP (web) server information;
* Use &lt;tt&gt;lynx&lt;/tt&gt; to pastebin a file when you need to send configuration information to an IRC channel, and;
* Use &lt;tt&gt;wget&lt;/tt&gt; to download a pastebin file to your local machine.

== Prerequisites ==
This tutorial will assume you are comfortable with the following concepts:
* Basic file management operations (&lt;tt&gt;cp&lt;/tt&gt;,&lt;tt&gt;rm&lt;/tt&gt;,etc);
* Using a console-based file editor (&lt;tt&gt;pico&lt;/tt&gt;,&lt;tt&gt;vi&lt;/tt&gt;,etc);

== Virtual Consoles ==
One of the handiest features if you're relegated to working from a console is the use of virtual consoles. This allows you to start multiple login sessions from the same console keyboard, mouse, and monitor. That way, you can have one virtual console logged into IRC so you can talk to ##slackware, one that you can use for web access, and another that you can use to test commands. 

Using virtual consoles is easy. Simply hold the ALT key while hitting the F2 key (ALT+F2) to switch to the second console. To switch back to the first console, use ALT+F1. You have virtual consoles available on F1 through F6.

If you're using X, you can still access one of the virtual consoles, which is useful if X is hung up for some reason (especially if X won't restart using ctrl+alt+backspace). To access this virtual console, hold CTRL *and* ALT while pressing the F6 key (CTRL+ALT+F6). To switch back to your X session, press CTRL+ALT+F7.

== Using &lt;tt&gt;screen&lt;/tt&gt; ==
The &lt;tt&gt;screen&lt;/tt&gt; utility allows you to start a console session which is persistent across login and logout. This is useful, for example, if you're using IRC -- perhaps you want to stay logged into your IRC channel even after you have logged out of your console session. The concept is straightforward: when you run screen, it gives you a bash prompt "inside of" the screen session. At this new bash prompt you can start your IRC session. When you wish to log out, you can detach from screen and log out -- but screen continues to run in the background. When you log back in, you can re-attach to your screen session and resume your IRC session.

Visit [[Screen|this page]] for the specifics on attaching and detaching sessions using &lt;tt&gt;screen&lt;/tt&gt;.

== Using &lt;tt&gt;irssi&lt;/tt&gt; ==
The &lt;tt&gt;irssi&lt;/tt&gt; program is a console-based IRC client. Using irssi, you can access the ##slackware IRC channel on irc.freenode.net. 

*WARNING*: Whenever you are using any type of IRC client on any type of machine, make sure that you are not doing so as the superuser (root). Doing so is a security risk, since if for some reason an attacker is able to successfully attack your IRC client, the attacker will have root access to your machine.

To access the ##slackware channel on irc.freenode.org using &lt;tt&gt;irssi&lt;/tt&gt;, perform the following steps:

* Start irssi:
 user@slackbox:~$ irssi
* At the (status) prompt, connect to irc.freenode.org:
 [(status)] /connect irc.freenode.org
* Once connected, set your nick:
 [(status)] /nick Myl33tNick
* Join the ##slackware channel:
 [(status)] /join ##slackware
* To exit irssi:
 [(status)] /quit
Visit [[Irssi|this page]] for more information on using irssi.

== Using &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; ==
You can use &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; to access http (web) servers from your console session. Lynx allows you to access a web site interactively, much like using a graphical browser such as Firefox, but through a text-only console session. &lt;tt&gt;Wget&lt;/tt&gt; allows you to retrieve documents from web servers non-interactively, which is handy when you need to retrieve a certain document (say a tarball or a script file) from a web server in a very quick way.

To start using lynx, from a bash prompt simply type:
 user@slackbox:~$ lynx "http://www.slackware.com"
to visit Slackware's official website. To exit lynx, use CTRL+C. In the example above, the double-quotes are not strictly required. However, many URLs contain characters which have special meaning to the bash interpreter (such as the ampersand), and the double-quotes stop bash from trying to interpret those characters.

Although wget has a wide array of options (visit man wget sometime), its basic use is very simple. For example, to download the latest kernel patch (as of this writing) from kernel.org, simply do:
 user@slackbox:~$ wget "http://www.kernel.org/pub/linux/kernel/v2.6/patch-2.6.20.3.bz2"
Again, the quotes here are not strictly required for this URL, but are required for certain URLs. It's good to get in the habit of always double-quoting URLs from a bash prompt.

== Using &lt;tt&gt;lynx&lt;/tt&gt; in conjuction with pastebin ==
You may find yourself on ##slackware and another channel member may ask you to "pastebin" information to them. The purpose of pastebin is so that you can share technical information (for example, the contents of a configuration file) with the other channel members, without pasting that information directly into IRC itself (which is generally disliked by other IRC members and will get you banned if you try it). "Pastebin" is a generic term for a web site which offers this sort of service. There are many pastebin sites out there; for simplicity's sake, this tutorial uses [http://pastebin.ca pastebin.ca].

You can use lynx to access the pastebin site, but what if you need to pastebin the contents of an entire file? You can do this using the &lt;tt&gt;lynx&lt;/tt&gt; program:
* use &lt;tt&gt;lynx&lt;/tt&gt; to access pastebin.ca:
 user@slackbox:~$ lynx "http://pastebin.ca"
* Page down until you see the large textbox area, move your cursor to the first line (where you see the X below):
 Create a New Pastebin Post
 
    Welcome  to the Pastebin. For information on what this is, take a look
    at  the  What  is This? page. You may also want to see the most recent
    post to the pastebin.
  
    Please enter your new post below (or upload a file instead):
 
 paste below
 
 
    X_____________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
 (NORMAL LINK)   Use right-arrow or &lt;return&gt; to activate.
   Arrow keys: Up and Down to move.  Right to follow a link; Left to go back.
  H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list
* Press Ctrl+X, then i, and enter the location of the file you wish to pastebin.
  Enter a filename: /etc/ssh/sshd_config
* Page down until you see the "Submit Post" link, select it (it will turn yellow), and press the enter key.
* On the next page, scroll down until you find the URL to your pastebin file. It will look something like this:
 paste added to database
 
   Your  paste  has  been  accepted an added to the database. You will be
   redirected to it momentarily. The URL for it is:
 
   http://pastebin.ca/398871
 
   You may use that URL for referencing your submission from now on.
* Give this URL to the person who requested the information on IRC.

== Using &lt;tt&gt;wget&lt;/tt&gt; in conjunction with pastebin ==
Every pastebin site should have a way to request any pastebin file in "raw" format, meaning without the added HTML code so that the pastebin information displays properly in a browser. Accessing the "raw" format means you can access exactly what was pastebinned, with nothing else added. This is useful if you want to download a configuration file from pastebin. If you know the raw URL of the pastebin page you need, you can use wget to retrieve the file.
* Find the raw URL associated with the pastebin page. For pastebin.ca, this is just the regular URL with an extra "raw" directory inserted. For example, if your regular pastebin url is http://pastebin.ca/398871, then the raw version is at http://pastebin.ca/raw/398871.
* use wget to retrieve the file, but rename it so that it's not named 398871 (in this example, the output is named "this.cfg"):
 user@slackbox:~$ wget "http://pastebin.ca/raw/398871" -O this.cfg
You'll find you'll use commands like wget over and over again this way, even when you have access to a fully graphical web browser.
[[Category:Tutorials]]</text>
    <sha1>efcf19613488e16a82ad6d20051d7720972495f4</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Creating a Current ISO</title>
  <ns>0</ns>
  <id>49</id>
  <revision>
    <id>70</id>
    <timestamp>2009-06-02T03:10:22Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1621" xml:space="preserve">The following was taken from: http://www.backslider.net/wordpress/?page_id=3

== Creating a Slackware-current iso: how-to ==

=== Step numero uno: ===
Download slackware-current, grab it from ftp.nluug.nl. To save time and space, don’t bother downloading bootdisks/, extra/, pasture/, source/, testing/, zipslack/ and then within slackware, leave out gnome/, kde/ and kdei/. This will keep our image below 700MB. If you plan on installing KDE, go ahead and grab it now.

=== Step numero dos: ===
Run the following command to create the iso. You will need mkisofs installed via the cdrtools package.

&lt;code&gt;mkisofs -o /somedir/slackware-current.iso -R -V “Slackware Install” -v -d -D -N -no-emul-boot -boot-load-size 4 -boot-info-table -b isolinux.bin -c isolinux.boot -A “Slackware Install CD”&lt;/code&gt;

If you did download kde/ or one of those other directories, you’ll need to exclude it from the mkisofs command like so, -x kde/.

=== Step numero tres: ===
Assuming I haven’t given bad advice, you now have a slackware-current iso that you can burn to cd now. You should be able to boot and then install off of it. I may check into how to create that second cd that would contain the gnome and kde packages, so check back at this page at a later time.

== Update 5/14/2005 ==
You can download unofficial current isos here:

ftp://ftp.slackware.no/pub/linux/ISO-images/slackware/Current-ISO-build/

This should save you some time for those of you who don’t need to customize your own iso. Please note that slackware.no only makes -current isos once a week every Tuesday at 0400 UTC

[[Category:Tutorials]]</text>
    <sha1>5318de152f4de8e57b8d58f5e8e0e783dd4b902f</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Antivirus</title>
  <ns>0</ns>
  <id>52</id>
  <revision>
    <id>73</id>
    <timestamp>2009-06-02T03:16:09Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6727" xml:space="preserve">= Antivirus =


Why would you want antivirus software on a Linux box, when there are so few Linux viruses out there?  Maybe you don't want to spread them to Windows boxes, or maybe you're worried about getting windows viruses via Windows emulation software, or maybe you want a little extra insurance.  The next question is which one?  Depends on what you're looking for.  A good thread on this is [http://www.linuxquestions.org/questions/slackware-14/antivirus-636562/?highlight=antivirus].  I'll talk about  installing 2 antivirus programs, Clam and Antivir.

'''Clam''': I haven't used it, but it has a command line scanner and a manual updater.  Go to [http://www.slackbuilds.org] and search for clamav.  Follow the instructions.

'''Antivir''':  The good: updates virus definitions automatically, and scans files in realtime on open/close (can also scan on execute).  You can run scans manually from the command line, and there's a GUI if you want to use it.  The bad:  complicated setup, I don't think the free version scans samba shares, has spyware protection, and it won't automatically scan archive files until you extract them.

The rest of this tutorial helps you setup Antivir for Slackware 12.1 and Slackware 12.0.  This is a compilation of information from dazuko.org, the Antivir user manual, and my own personal experience.


==You need:==

#latest dazuko kernel module from [http://www.dazuko.org/indexold.shtml]
#antivir from [http://www.avira.com]
#some time to kill


==Slackware 12.1==

===Dazuko===

*Extract dazuko somewhere: &lt;code&gt;tar xzvf dazuko-2.3.4.tar.gz&lt;/code&gt;.  There are 2 ways to install the kernel module, either via LSM or syscall hooks.  The recommended way is via LSM, but I wasn't able to configure the Slackware 2.6.24.5 kernel to compile capabilities as a module (make menuconfig-&gt;Security Options-&gt;Default Linux Capabilities).  I was able to do this with the old kernel in Slackware 12.0, but not the new one.  View the FAQ at dazuko.org for more info.  Also view &lt;dazuko_dir&gt;/README.linux26 for info on using syscall hooks.

*Recompile the kernel (Tested).  You only need to do this if you're using an SMP (multi-processor capable) kernel.  I won't go into detail on how to recompile the kernel, as that's covered here [http://slackwiki.org/Kernel_Compilation].  Anyway, before you make the kernel, &lt;code&gt;cd /usr/src/linux&lt;/code&gt;, and patch the kernel like this:
**&lt;code&gt;patch fs/dcache.c &lt;dazuko_dir&gt;/patch_dpath.diff&lt;/code&gt;
**Finish recompiling the kernel, make sure everything boots up OK.
**&lt;code&gt;cd &lt;dazuko_dir&gt;&lt;/code&gt;
**&lt;code&gt;./configure --enable-syscalls --mapfile=/boot/System.map --disable-local-dpath&lt;/code&gt;
*if you don't need to recompile the kernel (non-SMP), do this:
**&lt;code&gt;./configure --enable-syscalls --mapfile=/boot/System.map&lt;/code&gt;
*Don't recompile the kernel, and pass in different flags to &lt;code&gt;./configure&lt;/code&gt; (Untested).  I'm not totally sure if you lose any functionality by doing this, but up to you.
**&lt;code&gt;cd &lt;dazuko_dir&gt;&lt;/code&gt;
**&lt;code&gt;./configure --enable-syscalls --mapfile=/boot/System.map --disable-chroot-support&lt;/code&gt;
*&lt;code&gt;make&lt;/code&gt;
*&lt;code&gt;cd example_c&lt;/code&gt;
*&lt;code&gt;make&lt;/code&gt;
*&lt;code&gt;example /tmp&lt;/code&gt;
*in another terminal, create a test file in your /tmp directory.  if you see output from example, dazuko is working correctly.
*&lt;code&gt;cd ..&lt;/code&gt;
*&lt;code&gt;make test&lt;/code&gt;
*&lt;code&gt;make install&lt;/code&gt;


===Antivir===

*Extract antivir somewhere.  There is documentation under &lt;code&gt;&lt;antivir_dir&gt;/doc/avserver_en.pdf&lt;/code&gt;, along with some readmes.
*Install with &lt;code&gt;./install&lt;/code&gt;.    Make sure that you specify to let antivir load the dazuko module (easier).  The path to it is &lt;code&gt;/lib/modules/`uname -r`/extra/dazuko.ko&lt;/code&gt;.  You probably want the default options, including the 2 hr updates.
*add users to the antivir group.  &lt;code&gt;vim /etc/group&lt;/code&gt;, and add usernames to the antivir group.
*my personal preference is to move infected files to /home/quarantine.  here's how you set it up:
**&lt;code&gt;mkdir /home/quarantine&lt;/code&gt;
**&lt;code&gt;chown nobody:antivir /home/quarantine&lt;/code&gt;
**&lt;code&gt;chmod 775 /home/quarantine&lt;/code&gt;
*under &lt;code&gt;/etc/avguard.conf&lt;/code&gt;, add/edit these lines:
**&lt;code&gt;MoveConcerningFilesTo /home/quarantine&lt;/code&gt;
**&lt;code&gt;IncludePath /opt/downloads&lt;/code&gt; (where I put all my downloads, /home already scanned by default)
*restart avguard with &lt;code&gt;/usr/sbin/avguard restart&lt;/code&gt;
*test that it works by going to [http://www.eicar.org].  There's a link for downloading sample viruses.  If everything works, the file should be moved immediately to &lt;code&gt;/home/quarantine&lt;/code&gt;.  For archive files (.zip, .tar, etc.), you will have to extract them before antivir will catch them.  Lame free restriction.
*files to remember:
**&lt;code&gt;/etc/avguard.conf&lt;/code&gt;
**&lt;code&gt;/etc/avupdater.conf&lt;/code&gt;
**&lt;code&gt;/var/log/avguard.log&lt;/code&gt;
**&lt;code&gt;/var/log/avupdater.log&lt;/code&gt;
**&lt;code&gt;/usr/bin/antivir&lt;/code&gt;
**&lt;code&gt;/usr/bin/antivir-gui&lt;/code&gt;
**&lt;code&gt;/usr/sbin/avguard&lt;/code&gt;
**&lt;code&gt;/usr/sbin/avupdater&lt;/code&gt;
*commands to remember
**to do a manual update
***&lt;code&gt;antivir --update&lt;/code&gt;
**to scan a directory manually, and all subdirectories, extracting archive files
***&lt;code&gt;antivir --allfiles -s -z --moveto=/home/quarantine &lt;directory_to_scan&gt;&lt;/code&gt;

==Slackware 12.0==

===Dazuko===

*Extract dazuko somewhere: tar xzvf dazuko-2.3.4.tar.gz.  We can install this the recommended way, via LSM.  You shouldn't need to recompile the kernel, as capabilities should be a module.  To check, do this:
**&lt;code&gt;lsmod | grep capab&lt;/code&gt;
**If you see it there, you're in luck.  Otherwise you need to recompile the kernel with this option:
***make menuconfig-&gt;Security Options-&gt;&lt;M&gt;Default Linux Capabilities.
*&lt;code&gt;cd &lt;dazuko_dir&gt;&lt;/code&gt;
*&lt;code&gt;./configure&lt;/code&gt;
*&lt;code&gt;make&lt;/code&gt; (probably need to be root)
*&lt;code&gt;rmmod capability&lt;/code&gt; (unload this for a second so we can try out dazuko).
*&lt;code&gt;make test&lt;/code&gt;
*&lt;code&gt;cd example_c&lt;/code&gt;
*&lt;code&gt;make&lt;/code&gt;
*&lt;code&gt;example /tmp&lt;/code&gt;
*in another terminal, create a test file in your /tmp directory.  if you see output from example, dazuko is working correctly.
*&lt;code&gt;cd ..&lt;/code&gt;
*&lt;code&gt;make install&lt;/code&gt;
*&lt;code&gt;modprobe capability&lt;/code&gt; (reload into memory)
*edit &lt;code&gt;/etc/rc.d/rc.modules&lt;/code&gt;, and add this line before the capability module is loaded:
**&lt;code&gt;/sbin/modprobe dazuko&lt;/code&gt;
*There is an issue when the capability module is loaded first.  The steps above load the dazuko module first, which should fix the problem.


===Antivir===

*Same as above, except tell antivir that the kernel will load the module.  This is so that you can load dazuko before capabilities in &lt;code&gt;/etc/rc.d/rc.modules&lt;/code&gt;.

[[Category:Tutorials]]</text>
    <sha1>d45861ea8ad02a74e185994e5ab99ab218ba03e4</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Apache 2.0.x installation</title>
  <ns>0</ns>
  <id>53</id>
  <revision>
    <id>74</id>
    <timestamp>2009-06-02T03:16:38Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2991" xml:space="preserve">= Notice =

This article is obsolete; Slackware 12.0 includes Apache 2 by default (the httpd package). This information is kept here for users of older versions of Slackware.

= Introduction =
Sometimes one needs Apache 2.0.x in Slackware, which comes with Apache 1.3.x by default. Apache 2.0.x is necessary for example for Subversion repository setup or for recent mod_python modules.

'''Prerequisites:'''
*checkinstall (from &lt;tt&gt;extra&lt;/tt&gt;)
*mm from http://www.ossp.org/pkg/lib/mm/

So, first go to http://httpd.apache.org/download.cgi and grab the latest &lt;tt&gt;httpd-2.0.x.tar.bz2&lt;/tt&gt; file and unpack it:
 tar xfvj httpd-2.0.x.tar.bz2

Execute following script in directory just above your unpacked httpd-2.0.

&lt;pre&gt;
#!/bin/sh

build_apache() {

cd httpd-*

cat &gt;&gt; config.layout &lt;&lt;EOF
#   Layout for Slackware Linux
&lt;Layout Slackware&gt;
    prefix:        /usr
    exec_prefix:   \${prefix}
    bindir:        \${prefix}/bin
    sbindir:       \${prefix}/sbin
    libdir:        \${prefix}/lib
    libexecdir:    \${prefix}/lib/apache2
    mandir:        \${prefix}/man
    sysconfdir:    /etc/apache2
    datadir:       /var/www
    iconsdir:      \${datadir}/icons
    htdocsdir:     \${datadir}/htdocs
    manualdir:     \${datadir}/manual
    cgidir:        \${datadir}/cgi-bin
    includedir:    \${prefix}/include/apache2
    localstatedir: /var
    runtimedir:    \${localstatedir}/run
    logfiledir:    \${localstatedir}/log/apache2
    proxycachedir: \${localstatedir}/cache/apache2
    infodir:       \${exec_prefix}/share/info
    installbuilddir: \${datadir}/build
    errordir:      \${datadir}/error
&lt;/Layout&gt;
EOF
./configure --enable-layout=Slackware \
            --enable-module=most \
        --enable-mods-shared=most \
        --enable-ssl=shared \
                --enable-mime-magic \
                --enable-expires \
                --enable-headers \
                --enable-usertrack \
                --enable-cgi \
                --enable-vhost-alias \
                --enable-speling \
                --enable-so \
                --enable-rewrite \
                --enable-deflate \
                --enable-dav \
                --enable-dav-fs \
                --enable-proxy

make clean
time nice make

su -c "checkinstall -y"
}
create_scripts() {
cat &gt; rc.httpd &lt;&lt;EOF
#!/bin/sh
#
# Start the Apache web server
#

case "\$1" in
   'start')
      /usr/sbin/apachectl start ;;
   'stop')
      /usr/sbin/apachectl stop ;;
   'restart')
      /usr/sbin/apachectl restart ;;
   *)
      echo "usage \$0 start|stop|restart" ;;
esac
EOF
chmod 755 rc.httpd

cat &gt; apache2 &lt;&lt;EOF
/var/log/apache2/*_log {
    sharedscripts
    monthly
    rotate 6
    create
    compress
    postrotate
    /bin/kill -HUP `cat /var/run/httpd.pid 2&gt; /dev/null` 2&gt; /dev/null || true
    endscript
}
EOF
}

build_apache
create_scripts
&lt;/pre&gt;

This script will get the job done. It will compile and install Apache 2.0.x together with the startup scripts.

[[Category:Tutorials]]</text>
    <sha1>b79dc78497ebb1463dc74fb1d0ce6f0b670ddd2a</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Automating tasks with BASH</title>
  <ns>0</ns>
  <id>54</id>
  <revision>
    <id>75</id>
    <timestamp>2009-06-02T03:18:06Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3196" xml:space="preserve">[[Category:Tips]]
Often you will want to automate certain commands with BASH. The easiest way to do this is by using file globbing with wildcards otherwise called expansion. For example say I have a directory with the following files in it

  $ ls
  file1.txt  file2.txt  file3.txt

If I type

  $ ls *.txt
  file1.txt  file2.txt  file3.txt

The Shell will expand *.txt to match any file that matches the pattern of any number of characters followed by a .txt   it then sends this list to the ls command. The ls command takes that list as a set and displays the directory listing  for each one. Now most commands will work with file globbing but sometimes there are problems. For example if I wish to convert a heap of .jpeg files to 800x600 resolution with one line:

  $ ls *.jpeg
  img_2992.jpeg  img_2994.jpeg  img_2996.jpeg  img_2998.jpeg  img_3000.jpeg  img_3002.jpeg
  img_2993.jpeg  img_2995.jpeg  img_2997.jpeg  img_2999.jpeg  img_3001.jpeg

  $ convert *.jpeg -resize 800x600 *.jpeg

  $ ls *.jpeg
  img_2992.jpeg  img_2998.jpeg   img_3002-10.jpeg  img_3002-16.jpeg  img_3002-3.jpeg  img_3002-9.jpeg
  img_2993.jpeg  img_2999.jpeg   img_3002-11.jpeg  img_3002-17.jpeg  img_3002-4.jpeg  img_3002.jpeg
  img_2994.jpeg  img_3000.jpeg   img_3002-12.jpeg  img_3002-18.jpeg  img_3002-5.jpeg
  img_2995.jpeg  img_3001.jpeg   img_3002-13.jpeg  img_3002-19.jpeg  img_3002-6.jpeg
  img_2996.jpeg  img_3002-0.jpeg  img_3002-14.jpeg  img_3002-2.jpeg   img_3002-7.jpeg
  img_2997.jpeg  img_3002-1.jpeg  img_3002-15.jpeg  img_3002-20.jpeg  img_3002-8.jpeg

Of course that was not what we expected. There is an easier solution to this and that is to use BASH's for loop command.

  $ for var1 in *.jpeg; do convert $var1 -resize 800x600 $var1; done

  $ ls *.jpeg
  img_2992.jpeg  img_2994.jpeg  img_2996.jpeg  img_2998.jpeg  img_3000.jpeg  img_3002.jpeg
  img_2993.jpeg  img_2995.jpeg  img_2997.jpeg  img_2999.jpeg  img_3001.jpeg

What this command does is loop through all the .jpeg files in the directory and for each file it stores the name of that file in the variable $var1 which is then used as two arguments to convert, the input and output file names respectively.

Basically it looks to the system like this

  convert img_2992.jpeg -resize 800x600 img_2992.jpeg
  convert img_2993.jpeg -resize 800x600 img_2993.jpeg
  convert img_2994.jpeg -resize 800x600 img_2994.jpeg
  convert img_2995.jpeg -resize 800x600 img_2995.jpeg
  convert img_2996.jpeg -resize 800x600 img_2996.jpeg
  convert img_2997.jpeg -resize 800x600 img_2997.jpeg
  convert img_2998.jpeg -resize 800x600 img_2998.jpeg
  convert img_2999.jpeg -resize 800x600 img_2999.jpeg
  convert img_3000.jpeg -resize 800x600 img_3000.jpeg
  convert img_3001.jpeg -resize 800x600 img_3001.jpeg
  convert img_3002.jpeg -resize 800x600 img_3002.jpeg

You can play with this by echoing the output of the expansion to the console.

  $ for var2 in *.txt; do echo $var2 ;done
  file1.txt
  file2.txt
  file3.txt

  $ echo *.txt
  file1.txt file2.txt file3.txt

Those are similar expansions but not exactly the same.

Note: var1 and var2 are random variable names that I have picked. You can use other variable names like images or textfiles.</text>
    <sha1>07fc4adfd087a317380a312f53b65e4d6664b0ae</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Bootsplash (old)</title>
  <ns>0</ns>
  <id>55</id>
  <revision>
    <id>76</id>
    <timestamp>2009-06-02T03:18:48Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12340" xml:space="preserve">[[Category:Tutorials]]

== Prerequisites ==
* kernel source
* a bootsplash patch for your kernel version [http://www.stadtwald21.de/mcbeister/bootsplash/index.html] bootsplash patch.
* A bootsplash theme [http://kde-look.org/index.php?xcontentmode=61 kde-look themes]
* Bootsplash utilites [http://www.yzzerdd.net/slackware/files/bootsplash/bootsplash-3.1.tar.bz2 download]

== Setup ==
Start by patching and building a new kernel.

Assuming Stock kernel configuration/source. And all your downloads are in /home/username/Downloads.

  &lt;sub&gt; cd /usr/src/linux
        patch -p1&lt;/home/username/Downloads/bootsplash*.diff
        rm .config
        zcat /proc/config.gz &gt; .config
        make menuconfig&lt;/sub&gt;

   *Note: If you insist on using the generic kernel. And are currently using it.
        Check to see if the .config in your /usr/src/linux directory matches /proc/config.gz
          &lt;sub&gt; zdiff /proc/config.gz /usr/src/linux/.config &lt;/sub&gt;
        If they match, skip the "rm .config &amp;&amp; zcat ..." part above
        You'll also want to converge your initrd.gz and bootsplash's initrd. More on that below.

Edit these 2 options:

  &lt;sub&gt;  Device Drivers ---&gt;
             Graphics support ---&gt;
                  Logo configuration ---&gt;
                      [ ] Bootup logo
                  Bootsplash configuration ---&gt;
                      [*] Bootup splash screen&lt;/sub&gt;
* If you aren't using a stock kernel configuration, or on another distro check these settings whileyou are still in the kernel configuration dialog:
  &lt;sub&gt;&lt;nowiki&gt;  Device Drivers ---&gt;
            Block devices ---&gt;
                   &lt;*&gt; RAM disk support
            Graphics support ---&gt;
                   &lt;*&gt; Support for frame buffer devices&lt;/nowiki&gt;&lt;/sub&gt;
Now to make the patched kernel and install it

  &lt;sub&gt; make ; cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;
For slamd64, thats:
  &lt;sub&gt; make ; cp /usr/src/linux/arch/x86_64/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;

On to making a new bootsplash initrd.
Compile and install the splash utility.
  &lt;sub&gt; cd /home/username/Downloads
        tar xf bootsplash-3.0.7.tar.bz2
        cd bootsplash-3.0.7/Utilities/
        make splash
        cp splash /usr/bin/ &lt;/sub&gt;
And use it to build your new initrd.
Untar the theme file you downloaded, and check to see if it has a config directory and an image/s directory.
Look in the config directory for an appropriately sized config file (usually bootsplash-1024x768.cfg).
Edit this file, changing the directory it looks for images in (jpeg= option and silentjpeg= option) to point to the correct directory of the images for that theme. Example: /home/username/Downloads/bootsplashtheme/images/foo-bar.jpg
Finish by making the initrd with splash:
  &lt;sub&gt; splash -s -f /home/username/Downloads/bootsplashtheme/config/bootsplash-1024x768.cfg &gt;&gt; /boot/initrd.splash &lt;/sub&gt;
    For generic kernel users, you'll have to converge your stock initrd.gz and the bootsplash initrds.
       &lt;sub&gt;mkinitrd
            cp /boot/initrd.splash /boot/initrd-tree/
       &lt;/sub&gt;
After putting the initrd-splash into the mkinitrd's initrd-tree you'll need to run mkinitrd again with some computer specific options. Example:
      &lt;sub&gt;mkinitrd -c -m reiserfs&lt;/sub&gt;
Remember to do this every time you make a new initrd.splash.
Now edit /etc/lilo.conf with your favorite editor, adding the new kernel and bootsplash options.
Sample:
  &lt;sub&gt; boot = /dev/hda
        message = /boot/boot_message.txt
        prompt
        timeout = 300
        change-rules
         reset
        vga = 791
        image = /boot/vmlinuz
          root = /dev/hda1
          label = Linux
          read-only
        image = /boot/vmlinuz-bootsplash
          root = /dev/hda1
          label = Bootsplash
          initrd=/boot/initrd.splash
          append="splash=silent" &lt;/sub&gt;
Substitue "initrd=/boot/initrd.gz" if you had to run mkinitrd for a generic kernel, then run lilo to update and you're set.
  &lt;sub&gt;root@slackware:~# lilo
       Added Linux
       Added Bootsplash &lt;/sub&gt;
Now you can Reboot to test everything. If boot fails for some reason. You still have your stock kernel and entry in lilo to boot into without worries.

== Progressbar - rc.progress ==
Theres no set way to do this, you just need init to update /proc/splash correctly.
The way I do it (with help from LinuxQuestiosn forums):
create a new file in /etc/rc.d/ named rc.progress
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.progress &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
#rc.progress  This file has a common subroutine used to update a
#             bootsplash progress bar.
#

# Count the number of times the progress bar is likely to gbe increased
numu=$((`cat /etc/rc.d/rc.* | grep -c "^progressup"`));
numd=$((`cat /etc/rc.d/rc.* | grep -c "^progressdown"`));

function progressup(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress+1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numu ))" &gt; /proc/splash
}

function progressdown(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress-1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numd ))" &gt; /proc/splash
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.progress &lt;/sub&gt;
The . tells your system to include the functionality described in /etc/rc.d/rc.progress.
Now scroll through and add "progressup" (the defined trigger in rc.progress) on a new line
at the end of every subroutine where you want the progressbar to incriment up.
Example section of my rc.S:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.S:  System initialization script.
#
# Mostly written by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.progress
PATH=/sbin:/usr/sbin:/bin:/usr/bin

# Mount /proc right away: 
  &lt;/nowiki&gt;&lt;/sub&gt;
Don't add progressup till after your partition is mounted read/write
it'll be at the end of a long segment of echo .. echo.. echo like this.
  &lt;sub&gt;&lt;nowiki&gt;  echo -n "Press ENTER to continue. "
  read junk;
fi # Done checking root filesystem
progressup
  &lt;/nowiki&gt;&lt;/sub&gt;
Do the same for /etc/rc.d/rc.6 adding progressdown instead of progressup.
After you've finished that, you need to delete your temporary progressbar output cache.
Since rc.local is run last during startup, it's best to accomplish this here.
Edit rc.local:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

rm -fr /var/run/progressbar &lt;/nowiki&gt;&lt;/sub&gt;

== Progressbar - rc.bootsplash ==
An alternate script can also be used if you should have problems implementing the rc.progress script.
In my case the prior script was not able to delete its progressbar file, and adding progressdown entries to rc.6 resulted in odd behaviors even during bootup when rc.6 should not of been a factor. 
Create a new file in /etc/rc.d/ named rc.bootsplash
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.bootsplash &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# /etc/rc.d/rc.bootsplash: bootsplash functions.
# This file does nothing if run, and is called by other rc.
# files in order to make the progress bar and animations works.

function progressbar()
{
        if [ $# != 1 ]
                then
                echo "Usage: progressbar {progress}"
                exit 1
        fi
        if [ -a /proc/splash ] ; then
                echo "show $(( 65534 * $1 / 100 ))" &gt; /proc/splash
        fi
}
#
function animate()
{
        if [ $# = 0 ]
                then
                echo "Usage: animate {hook}"
                exit 1
        fi
        splash "$*"
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.bootsplash &lt;/sub&gt;
Now scroll through and add "progressbar X" (where X is a number representing the percent to incriment to) on a new line
at the end of every subroutine where you want the progressbar to incriment up. 0 is not a valid incriment. Only 1 - 100 are valid. 

Example rc.S
  &lt;sub&gt;&lt;nowiki&gt;
# Scan for new volume groups:
  /sbin/vgscan --mknodes --ignorelockingfailure 2&gt; /dev/null
  if [ $? = 0 ]; then
    # Make volume groups available to the kernel.
    # This should also make logical volumes available.
    /sbin/vgchange -ay --ignorelockingfailure
  fi
fi
progressbar 5

# Open any volumes created by cryptsetup:
if [ -f /etc/crypttab -a -x /sbin/cryptsetup.static ]; then
  # First, check for device-mapper support.
  if ! grep -wq device-mapper /proc/devices ; then
    # If device-mapper exists as a module, try to load it.
    # Try to load a device-mapper kernel module:
    /sbin/modprobe -q dm-mod
  fi
  cat /etc/crypttab | grep -v "^#" | grep -v "^$" | while read line; do
    LUKS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f1 -d' ')
    DEV=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f2 -d' ')
    PASS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f3 -d' ')
    OPTS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f4 -d' ')
    LUKSOPTS=""
    if echo $OPTS | grep -wq ro ; then LUKSOPTS="${LUKSOPTS} --readonly" ; fi

    # NOTE: we only support LUKS formatted volumes (except for swap)!
    if /sbin/cryptsetup.static isLuks $DEV 2&gt;/dev/null ; then
      echo "Unlocking LUKS crypt volume '${LUKS}' on device '$DEV':"
      if [ -n "${PASS}" ]; then
        if [ -f ${PASS} ]; then
          /sbin/cryptsetup.static ${LUKSOPTS} --key-file=${PASS} luksOpen $DEV $LUKS
        elif [ "${PASS}" != "none" ]; then
          echo "${PASS}" | /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS
        fi
      else
        for i in seq 1 3 ; do
          /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS &lt;/dev/tty0 &gt;/dev/tty0 2&gt;&amp;1
          [ $? -eq 0 ] &amp;&amp; break
        done
      fi
    elif echo $OPTS | grep -wq swap ; then
      # If any of the volumes is to be used as encrypted swap,
      # then encrypt it using a random key and run mkswap:
      echo "Creating encrypted swap on device '$DEV' mapped to '${LUKS}':"
      /sbin/cryptsetup.static --cipher=aes --key-file=/dev/urandom --key-size=256 create $LUKS $DEV
      mkswap /dev/mapper/$LUKS
    fi
  done
fi

# Enable swapping:
/sbin/swapon -a
progressbar 10
&lt;/nowiki&gt;&lt;/sub&gt;

Continue adding "progressbar X" entries in both rc.S and rc.M

Do the same for rc.6 but instead incrimenting down 'X'. 

Example rc.6
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# rc.6          This file is executed by init when it goes into runlevel
#               0 (halt) or runlevel 6 (reboot). It kills all processes,
#               unmounts file systems and then either halts or reboots.
#
# Version:      @(#)/etc/rc.d/rc.6      2.47 Sat Jan 13 13:37:26 PST 2001
#
# Author:       Miquel van Smoorenburg &lt;miquels@drinkel.nl.mugnet.org&gt;
# Modified by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.bootsplash

# Set the path.
PATH=/sbin:/etc:/bin:/usr/bin
progressbar 100

# If there are SystemV init scripts for this runlevel, run them.
if [ -x /etc/rc.d/rc.sysvinit ]; then
  . /etc/rc.d/rc.sysvinit
fi
progressbar 90

# Set linefeed mode to avoid staircase effect.
/bin/stty onlcr

echo "Running shutdown script $0:"

# Find out how we were called.
case "$0" in
        *0)
                command="halt"
                ;;
        *6)
                command=reboot
                ;;
        *)
                echo "$0: call me as \"rc.0\" or \"rc.6\" please!"
                exit 1
                ;;
esac

# Save the system time to the hardware clock using hwclock --systohc.
if [ -x /sbin/hwclock ]; then
  # Check for a broken motherboard RTC clock (where ioports for rtc are
  # unknown) to prevent hwclock causing a hang:
  if ! grep -q -w rtc /proc/ioports ; then
    CLOCK_OPT="--directisa"
  fi
  if grep -q "^UTC" /etc/hardwareclock 2&gt; /dev/null ; then
    echo "Saving system time to the hardware clock (UTC)."
    /sbin/hwclock $CLOCK_OPT --utc --systohc
  else
    echo "Saving system time to the hardware clock (localtime)."
    /sbin/hwclock  $CLOCK_OPT --localtime --systohc
  fi
fi
progressbar 80
&lt;/nowiki&gt;&lt;/sub&gt;</text>
    <sha1>6d57a57211dc8013b3497e5c44ab1d5c10ddc57c</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>CPU User Limiting</title>
  <ns>0</ns>
  <id>56</id>
  <revision>
    <id>77</id>
    <timestamp>2009-06-02T03:19:51Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1218" xml:space="preserve">[[Category:Tips]]

== CPU / Performance Limits ==

To set limits on users (e.g. CPU usage), use &lt;code&gt;ulimit&lt;/code&gt;.

EXAMPLE: &lt;code&gt;ulimit -t;&lt;/code&gt;

From the manpage:
&lt;code&gt;-a&lt;/code&gt; All current limits are reported&lt;br&gt;
&lt;code&gt;-c&lt;/code&gt; The maximum size of core files created&lt;br&gt;
&lt;code&gt;-d&lt;/code&gt; The maximum size of a process's data segment&lt;br&gt;
&lt;code&gt;-f&lt;/code&gt; The maximum size of files created by the shell&lt;br&gt;
&lt;code&gt;-i&lt;/code&gt; The maximum number of pending signals&lt;br&gt;
&lt;code&gt;-l&lt;/code&gt; The maximum size that may be locked into memory&lt;br&gt;
&lt;code&gt;-m&lt;/code&gt; The maximum resident set size&lt;br&gt;
&lt;code&gt;-n&lt;/code&gt; The maximum number of open file descriptors (most systems do not allow this value to be set)&lt;br&gt;
&lt;code&gt;-p&lt;/code&gt; The pipe size in 512-byte blocks (this may not be set)&lt;br&gt;
&lt;code&gt;-q&lt;/code&gt; The maximum number of bytes in POSIX message queues&lt;br&gt;
&lt;code&gt;-s&lt;/code&gt; The maximum stack size&lt;br&gt;
&lt;code&gt;-t&lt;/code&gt; The maximum amount of cpu time in seconds&lt;br&gt;
&lt;code&gt;-u&lt;/code&gt; The maximum number of processes available to a single user&lt;br&gt;
&lt;code&gt;-v&lt;/code&gt; The maximum amount of virtual memory available to the shell&lt;br&gt;
&lt;code&gt;-x&lt;/code&gt; The maximum number of file locks&lt;br&gt;


== Disk Space Limits ==

Use &lt;code&gt;quota&lt;/code&gt;.</text>
    <sha1>e89f1dd55c86ffae9e859b1031dd1455ae8efc43</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Changes 10.0 10.1</title>
  <ns>0</ns>
  <id>57</id>
  <revision>
    <id>78</id>
    <timestamp>2009-06-02T03:20:35Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="497" xml:space="preserve">= Purpose =
The purpose of this page is to document the new packages (Package Additions) and removed packages (Package Removals) during the release cycle from Slackware 10.0 to Slackware 10.1.

= Package Additions From 10.0 to 10.1 =

* l/libidn
* n/vsftpd 

= Package Removals From 10.0 to 10.1 =

* gnome/epiphany
* gnome/epiphany-extensions 
* gnome/galeon

= Other Concerns =

These packages were sent to ./pasture:

* pasture/fvwm95
* pasture/apsfilter
* pasture/ifhp
* pasture/fluxbox-0.1.14</text>
    <sha1>41171411643c1af5220345dd2480c0ca3957d1b6</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Changes 10.2 current</title>
  <ns>0</ns>
  <id>58</id>
  <revision>
    <id>79</id>
    <timestamp>2009-06-02T03:21:25Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, SOMEONE SHOULD WORK ON THESE!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10132" xml:space="preserve">= Purpose =

The purpose of this file is to document the new packages (Package 
Additions) and removed packages (Package Removals) during the 
development cycle from Slackware 10.2 through Slackware 11.0, as
well as to point out some potential "gotchas" that can users can
avoid by arming themselves with a little knowledge.


=  Package Additions Since 10.2 =

* a/pcmciautils
* a/sharutils (split from bin)
* a/acl (split from xfsprogs)
* a/attr (split from xfsprogs)
* a/sysfsutils
* a/sysstat
* ap/diffstat
* ap/dmapi (split from xfsprogs)
* ap/linuxdoc-tools
* ap/lm_sensors
* ap/xfsdump (split from xfsprogs)
* d/git
* d/mercurial
* d/ruby
* kde/amarok
* kde/qca
* kde/qca-tls
* l/apr
* l/apr-util
* l/cairo
* l/db42 (for backwards compatibility)
* l/db44 (upgrade from db4; see 'Package Removals' and 'Other Concerns' for more information)
* l/desktop-file-utils
* l/freetype (split from x11) - see note in "Other Concerns" below
* l/gd
* l/gnome-icon-theme
* l/hicolor-icon-theme
* l/libgpod
* l/libmtp
* l/libmusicbrainz
* l/libnjb
* l/libtheora
* l/libtunepimp
* l/libvisual (library only, no plugins yet - but this should allow for compiling audio visualization plugins for amarok without a recompile of amarok itself)
* l/mm (split from apache)
* l/mpfr (split from gmp)
* l/neon (split from subversion)
* l/slang1 (renamed from slang)
* l/slang (Added slang 2)
* n/mailx (renamed from nail)
* n/rdesktop
* x/dejavu-ttf 
* x/fontconfig (split from x11) - see note in "Other Concerns" below
* x/ttf-indic-fonts - see note in "Other Concerns" below
* xap/seamonkey
* xap/vim-gvim (renamed from xvim) - this package now depends on ap/vim
* kernels/huge26.s/* - added a 2.6.17.13 kernel to the official (supported) package set.  The user will be given a choice of whether to install the 2.4.33.3 or 2.6.17.13 kernel.  If a 2.6 kernel is used, additional packages must be added after the installation -- at the very least the kernel-modules package.  Possibly also the kernel-headers to provide /usr/include/sound used to compile ALSA applications.
* extra/linux-smp-2.6.17.13/* - added a 2.6.17.13 kernel, modules, and headers with SMP and hyperthreading support, optimized for i686 or better cores (including dual core CPUs).


=  Package Removals Since 10.2 =
* ap/sgml-tools (replaced with linuxdoc-tools)
* d/python-demo (merged with python package)
* d/python-tools (merged with python package)
* l/db3 (moved to /pasture)
* l/db31 (moved to /pasture)
* l/db4-* (moved to /pasture)
* n/nail (renamed to mailx - see "Package Additions")
* xap/abiword (became a pure Gnome app)
* xap/mozilla (replaced with seamonkey)
* xap/xvim (renamed to vim-gvim) - see note above in "Package Additions"


=  Other Concerns =

First of all, if you did not *upgrade* (in other words, you have a fresh installation), most of this is not relevant to you; you won't need to merge any config files or anything along those lines.  However, this is still worth reading, as it gives you an idea of things to look for in future upgrades.
 
* Both the 2.4.x and 2.6.x kernels included are now compiled with high memory support
* Many old bison and db packages were pasture-ized from d/ and extra/ and so on; after upgrading/installing Slackware 11.0, you should have *one* bison package and *two* db packages (the db packages are listed in the package additions above)
* n/php now depends on l/freetype (l/freetype was split from x/x11)
* n/apache now depends on l/mm (l/mm was split from apache)
* xap/xine-lib now depends on l/libtheora if you want to play ogg-files in xine (and Amarok using the xine engine)
* a/devs was upgraded during the -current development cycle.  You CANNOT upgrade this package while udev is running - you'll need to chmod -x /etc/rc.d/rc.udev, reboot, upgrade the devs package, and then reboot again.  Actually, you don't *have* to reboot again, but if you know that, then you likely know how to go about it that way :)
If you don't know the trick, here's how to do it (no secrets here):
  sh /etc/rc.d/rc.udev stop
  umount /dev/pts
  umount /dev/shm
  umount -l /dev
  installpkg devs*.tgz
  sh /etc/rc.d/rc.udev start
  mount -av
Thanks to Richard Hoyle for this information on doing it without a reboot.
* So long as we're on the subject of a/devs, be aware that this package is still *required* in order to boot, even if you're using a 2.6 kernel and udev, so don't remove it.
* a/lilo and a/kernel-* were upgraded during the -current development cycle, so be sure to run /sbin/lilo prior to rebooting.
* glibc was upgraded during the -current development cycle, so be sure to follow the instructions in [http://slackware.osuosl.org/slackware-11.0/UPGRADE.TXT UPGRADE.TXT] when upgrading (do the upgrade in runlevel 1).
* There was a major upgrade to a/udev and a/sysvinit - make *sure* you merge the *.new scripts in /etc/rc.d prior to rebooting or you *will* have problems.
* If you're having trouble with udev, make sure you've syncronized all of the .new config files and init scripts first.  According to Pat Volkerding (the Slackware maintainer), most of these issues can "be fixed with a little bit of fine tuning, such as blacklisting unwanted modules in /etc/modprobe.d/blacklist and loading the desired replacements in /etc/rc.d/rc.modules," but simply blacklisting them will often result in udev loading the correct modules.  Also, keep in mind that newer versions of udev (084+) require at least a 2.6.15.x kernel.  Experiment with it before resorting to this, but if you simply must have one of them, there are alternate versions of udev in /extra.
* If you're running a 2.6 kernel and new udev (084+) on a router, you'll probably need to uncomment (and possibly edit to suit) the rules in /etc/udev/rules.d/network-devices.rules to make your interfaces always get the same names assigned.  Hotplugging events are generated (and processed) in random order by udev, so there's no guarantee that your current eth0 will *always* be eth0 unless you uncomment (and possibly edit) those rules.
* If you need custom udev rules, DO NOT edit the default udev.rules file - any changes you make will be clobbered with the next udev upgrade.  The correct way is to add a custom file to the /etc/udev/rules.d/ directory - most people use '10-local.rules' - and add your custom rules there.  If there is some reason that one of the default rules needs changed, mail PiterPunk and/or Pat with an explanation.
* The psmouse module is blacklisted by default in the /etc/modprobe.d/blacklist file due to problems with the default kernel options used when it loads; this allows you to load it (from rc.modules, for example) with option "proto=imps" if you need it, or you are certainly free to comment it out in the blacklist file if it works fine for you with the kernel defaults.
* As indicated in the Package Additions section, freetype and fontconfig were split out of the main X11 packages.  You need to upgrade the main x11 package first, then install fontconfig and freetype, then upgrade the remainder of the x11 packs; otherwise, they give an error during postinstall about not being able to load fontconfig libs.
* xap/seamonkey was chosen to provide the Mozilla development environment (primarily because the official binaries are used for the Firefox package, and these do not contain the development headers).  At this time, only GAIM links with SeaMonkey's libraries, but if you are planning to compile something needing "Mozilla" libraries and headers, be sure SeaMonkey is installed.
* There have been quite a few reports that fonts are 'ugly' after upgrading; one way to fix it is to remove /etc/fonts/local.conf if it exists.  If it doesn't exist, or that doesn't work, go into KControl's font settings, uncheck the box for antialiasing, and apply the changes.  Then, recheck the box and apply the changes.  This should create a $HOME/.fonts.conf file.  Thanks to Pat for the initial suggestion with KControl, and thanks to ananke for working out exactly what changes are necessary to fix it.
* Slackware's vim package now includes a $VIM/vimrc file (in this case, /usr/share/vim/vimrc) for vim's default configuration. This default should provide a suitable start for most and your ~/.vimrc will override it if not, but if you had previously not explicitly set, e.g., 'backup', because vim's compiled-in default resulted in no backups and that suited you, the $VIM/vimrc includes 'set backup' and you will suddenly be keeping backups. These settings can be overridden individually (in this case with 'set nobackup') but one of several ways to avoid having $VIM/vimrc affecting your configuration at all is to put this at the top of your ~/.vimrc, overriding everything in $VIM/vimrc:
 set all&amp; " reset all options to compiled in defaults (thanks to deryni in #vim)
 unmap Q " remove mapping to gq
 syntax off " turn syntax off
 filetype plugin indent off " turn filetype detection off
 augroup! vimrcEx " delete the autocommand group that wraps text, etc.
* If you have an ati radeon card and are experiencing problems with it locking up, there is a patched set of ati modules at /extra/x11-radeon-patched/ - if you are not experiencing problems, then don't install this, as it does tend to cause problems if you weren't already having them...
* The ttf-indic-fonts package supports Bengali, Devanagari, Gujarati, Kannada, Malayalam, Oriya, Punjabi, Tamil, and Telugu.  For information about fully enabling Indic support (including input), see: /usr/doc/Linux-HOWTOs/Indic-Fonts-HOWTO.
* As part of the upgrade to nfs-utils and portmap, the /etc/rc.d/rc.portmap script has been replaced by /etc/rc.d/rc.rpc.  The rc.rpc script does not have to be executable unless you plan on mounting nfs shares &lt;b&gt;manually&lt;/b&gt;, as it will be run by other init scripts if any nfs shares or mounts are detected.
* php5 and lvm2 are available in /extra if you would like to use them
* cairo-1.2.4, flex-2.5.33, fontconfig-2.4.1, gutenprint-5.0.0, hplip-1.6.9, iptables-1.3.6, and wpa_supplicant-0.4.9 are available in /testing if you need/want them

[http://www.slackforum.de/wiki/Aenderungen102110 german version]</text>
    <sha1>13e19ada68315b7579510342fd63c10e6eb83701</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Changing Window Managers</title>
  <ns>0</ns>
  <id>59</id>
  <revision>
    <id>80</id>
    <timestamp>2009-06-02T03:21:59Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="992" xml:space="preserve">Well I'm sure you all want to change you window manager at some point
in time:), well this tutorial is going to show you how in
Slackware. First as a user run the following command:

 xwmconfig

This will bring up an ncurses based menu to select the window manager
you want. What this does for the user is copy the xinitrc from
/etc/X11/xinit/. For instance, Say I want KDE to startup, all the
tool would do is run:

 cp /etc/X11/xinit/xinitrc.kde $HOME/.xinitrc

That is basicly what it does, Now say you want to start a program from 
when starting your window manager? Well thats easy, we shall open up the
~/.xinitrc: (I am going to use the fluxbox one)

 exec /usr/X11R6/bin/fluxbox

That is what you see, so say you want to start a program before
fluxbox, like a program that changes your background? Well here is an
example:

 background-program &amp;
 exec /usr/X11R6/bin/fluxbox

You see you MUST have the &amp; or fluxbox wont startup. 

I hope you learned from this.

[[Category:Tutorials]]</text>
    <sha1>c9cbfa99b44c8d08d97606b46be63cc891e97ba6</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Common Commands</title>
  <ns>0</ns>
  <id>60</id>
  <revision>
    <id>81</id>
    <timestamp>2009-06-02T03:22:38Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4980" xml:space="preserve">Here is a list of common commands and some descriptions:

  cd 
: Changes the directory. Example: &lt;code&gt;cd /&lt;/code&gt;
  rm &lt;i&gt;options filename&lt;/i&gt;
: Removes Files. Example: &lt;code&gt;rm &lt;i&gt;filename&lt;/i&gt;&lt;/code&gt;
::Options: -R - Removes all files and subdirectories (very dangerous). Example: &lt;code&gt;rm -R /home/bill/public_html/&lt;/code&gt;
  rmdir &lt;i&gt;directory&lt;/i&gt;
: Removes an Empty Directory. Example: &lt;code&gt;rmdir /home/bill/emptydir&lt;/code&gt;
  mount 
: Mounts filesystems and partitions, etc
::Example: &lt;code&gt;mount /mnt/cdrom&lt;/code&gt; &lt;--Only useable if &lt;code&gt;/mnt/cdrom&lt;/code&gt; is listed in [[Fstab|/etc/fstab]]
::Example: &lt;code&gt;mount -t iso9660 /dev/hdc /mnt/cdrom&lt;/code&gt;
  ls &lt;i&gt;options optional_directory_path&lt;/i&gt; (if no directory path is given, the current directory is listed)
: Lists files and directories. Example: &lt;code&gt;ls&lt;/code&gt;
::Options:
:::-a - Lists ALL files and directories, even hidden ones. Example: &lt;code&gt;ls -a&lt;/code&gt;
:::-l - Lists files and directories with details (e.g. permissions) Example: &lt;code&gt;ls -l /home/bill/&lt;/code&gt;
:::-la - Lists ALL files and directories, even hidden ones with details. Example: &lt;code&gt;ls -la &lt;/code&gt;
  gunzip &lt;i&gt;filename&lt;/i&gt;
: Uncompresses gzip'd files.  Example: &lt;code&gt;gunzip somefile.tar.gz&lt;/code&gt;
  tar &lt;i&gt;options filename&lt;/i&gt;
: Extracts files from .tar files.
::Options
::: -xvf - extract file.tar &lt;code&gt;tar -xvf file.tar&lt;/code&gt;
::: -zxvf - uncompress and extract from a gzip'd tar archive (*.tar.gz or *.tgz) &lt;code&gt;tar -zxvf kernel-2.6.7.tar.gz&lt;/code&gt;
::: -jxvf - uncompress and extract from a bzip2'd tar archive (*.tar.bz2) &lt;code&gt;tar jxvf kernel-2.6.7.tar.bz2&lt;/code&gt;
  mc
: Console File manager
  pico 
: Easy console text editor.  NOTE: Pico is in the PINE package.  If you didn't install Pine, you won't have pico.  (You CAN install pico as a stand-alone binary). An alternative to Pico is [http://www.nano-editor.org/ GNU Nano]. It has many features, including syntax highlighting.
  vi, vim, elvis
: Console text editors - depending on your setup, one of these is accessed as 'vi'. Vim &amp; Elvis are Vi clones (with a few more features). Between Vim and Elvis, Vim is more featureful, but elvis is in /a and installed by default. You can install vim (or xvim/gvim, gui-enabled versions) instead of, or in addition to elvis.
  find
: Program to find files. Example: &lt;code&gt;find / -name lilo.conf&lt;/code&gt;
  cat
: Shows what is currently in a text file. Example: &lt;code&gt;cat /proc/cpuinfo&lt;/code&gt;
  grep
: Searches for strings. Example: &lt;code&gt;grep "model name" /proc/cpuinfo&lt;/code&gt;  Add the option '-i' if you don't want your search to be case-insensitive
  less
: You can control using arrow keys what is displayed in a text file. Example: &lt;code&gt;less /etc/lilo.conf&lt;/code&gt;
  man
: Manual pages for commands. Example: &lt;code&gt;man bash&lt;/code&gt;
  apropos
: Searches a whatis type database. Example: &lt;code&gt;apropos ftp&lt;/code&gt;
  which
: Shows the first match of a program in your path. Example: &lt;code&gt;which bash&lt;/code&gt;
  whereis
: Shows man pages, binaries, etc of a program. Example: &lt;code&gt;whereis bash&lt;/code&gt;
  file
: Determines the file type. Example: &lt;code&gt;file /usr/bin/bash&lt;/code&gt;
  dmesg
: Displays the kernel ring buffer information
  route
: Configures the IP routing (used for setting the default gateway, etc.).
  ifconfig
: Network interface configuration tool (used to bring the NIC up and down and set the IP).
  ssh
: Secure SHell, allows you to login to remote machines.
  startx
: A simple script to start X-Windows
  iwconfig
: This is for configuring wireless cards
  chmod
: Edits permissions on a file or directory (see [[Permissions and Umasks]])
  netconfig
: A tool to help you configure a network card on Slackware
  df
: Shows the free space on your partitions. Example: &lt;code&gt;df -h&lt;/code&gt;
  du
: Calculates disk usage. Example: &lt;code&gt;du -hc&lt;/code&gt;
  bunzip2
: Uncompresses .bz2 files. Example: &lt;code&gt;bunzip2 file.bz2&lt;/code&gt;
  sort
: Sorts data.  A very useful option is '-f', which makes the sort case-insensitive (i.e. AaBbCc rather than ABCabc).  Another useful option is '-n', which sorts by numbers.  Try &lt;code&gt;du | sort&lt;/code&gt; and then &lt;code&gt;du | sort -n&lt;/code&gt; to see the difference.

&lt;h1&gt;Piping&lt;/h1&gt;

You can mix commands to do certain things. 

  dmesg | grep hd

That will search dmesg and try to find the string "hd". Now piping is extremely useful. Another example of a pipe:

  dmesg | less

Now this command you can see the dmesg fully and is easier to read. 

Redirection:

This will save the dmesg information in your home directory in the file log.txt

  dmesg &gt; ~/log.txt

You can also redirect only the [[standard output|stdout]] by using '1&gt;' or only the [[error messages|stderr]] by using '2&gt;'.

For instance, if you want to run a command that gives a lot of junk as output, and you just want to see any errors, you can redirect the output to the null device (&lt;code&gt;/dev/null&lt;/code&gt;):

  mplayer /path/to/movie.avi 1&gt; /dev/null


&lt;hr&gt;
&lt;i&gt;Section on piping moved to [[Piping]]. --sinope&lt;/i&gt;

[[Category:Tips]]</text>
    <sha1>96272c3db843da5c8f1c152b81825a7a625dead5</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Conexant Crypto F200 ADSL</title>
  <ns>0</ns>
  <id>61</id>
  <revision>
    <id>82</id>
    <timestamp>2009-06-02T03:23:25Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6040" xml:space="preserve">[[Category:Tutorials]]
'''
'''Installation Guide for Crypto F200 0572:cb00 Conexant Systems (Rockwell), Inc. E-Tech ADSL Modem v2'''
'''


This is a simple guide-howto for the installation of Crypto F200 ADSL modem (the one that comes with various ForthNet ADSL kits in Greece) on Slackware Linux.
The following procedure was done on a Slackware 10.2 system (full installation) with kernel 2.6.17.1.
The main guide that helped me setup my DSL connection is found in http://accessrunner.sourceforge.net .Excellent site - lots of usefull information . 
The reason for writting this guide is that some of the stuff on that site and a some howtos found on the net is out of date and a bit confusing.
A lot of steps are not necessary when you use a new kernel like 2.6.17.1 .
Having not set up a dsl modem on linux before I spent quite some time to figure out the new stuff from the old stuff - the things i had to do with 2.6.17.1 from the things i would have to do with an older kernel. 
In this guide I will just share with you what I figured out.


So there are 5 simple steps you have to follow.

'''1.'''Set up your new kernel so that it is capable of dealing with your Crypto Modem

'''2.'''Make sure hotplug is up to date (only if you have an old distro)

'''3.'''Grab your modem's windows drivers (tricky part you may have to use alternative drivers from other similar modems), locate CnxEtU.sys
and by using the appropriate utility extract the modem´s firmware from it.

'''4.'''Setup your pppd by editing /etc/ppp/peers/adsl , /etc/ppp/pap-secrets and /etc/ppp/chap-secrets

'''5.'''Run pppd call adsl - You are on the net. Killall pppd to stop the internet connection.


'''1.Kernel configuration:(this was done in 2.6.17.1)'''

Networking -&gt; Networking Options -&gt; Asynchronus Transfer Mode (ATM) (EXPERIMENTAL) (ATM)

Device Drivers -&gt; USB Support -&gt; Support for Host-side USB (USB)

Device Drivers -&gt; USB Support -&gt; USB DSL modem support (USB_ATM)

Device Drivers -&gt; USB Support -&gt; USB DSL modem support -&gt; Conexant AccessRunner USB suppport (USB_CXACRU)


'''2.Hotplug with firmware loader support utility must be available'''

In Slackware 10.2 hotplug is ready. /etc/rc.d/rc.hotplug is by default exexutable.


'''3.Extract the firmware from the files contained in the windows driver files.'''


All conexant access runner based adsl modems (crypto f200 is one of them) work like this: When you plug it in (usb) , your pc sends it its firmware without which the modem does not work (it is the state when the led is permanently off). After it gets the firmware the led starts blinking. It is now that it tries to synchronize with the adsl line. If it succeeds then the led stops blinking and everything works.

So the first thing we do is find the firmware for the modem.

Downlaod cxacru-fw tool (this is the program that extracts the firmware from the file found in windows driver) 
You can find it in http://accessrunner.sourceforge.net/firmware.shtml -&gt; Obtaining firmware (cxacru-fw.bin)
Build cxacru-fw.c by typing gcc cxacru-fw.c -o cxacru-fw

Extracting the firmware from the driver is easy:
Locate CnxEtU.sys in windows driver files.
Use cxacru-fw tool to extract the firmware: name it cxacru-fw.bin 
Place cxacru-fw.bin in /lib/firmware/ (/etc/rc.d/rc.hotplug grubs the firmware from there)

Check if your modem works:
Check the LED on top of the modem (On not blinking) 
Check /var/log/messages (up)
Check /proc/net/atm/cxacru:0 (Line Up)

If this works and the Led on top of the ADSL modem stops blinking a little after you plug it in then (you are lucky) go to step 4.


The Hardest part is to find the appropriate windows driver (the appropriate CnxEtU.sys file) as the cd that came with
my Crypto F200 (with CnxEtU.sys 9/12/03) had a firmware that would not let the adsl modem synchronize.
This is what happens when the modem does not synchronize:(look at /var/log/messages)
Attempt to synchronize
Fail
Second attempt 
Nothing else

and the led on top of the adsl modem keeps blinking for ever.

What I did was to search for drivers for other adsl usb modems with the same chip as Crypto F200 had (conexant) and
the same Vendor and Product ID (which you can get with lsusb (0572:cb00))

Here is a list (posted in http://accessrunner.sourceforge.net)

Conexant ADSL modem (Hasbani project)
*AusLinx AL-2006
ACORP Sprinter@ADSL USB
*Amigo HMX-CA85UR-K8
*Digicom Michelangelo Usb C
*Origo ASU 8000
Atlantis Pocket USB ADSL Modem (A01-AU2)

*These are known to work

I was lucky . AusLinx AL-2006 Driver V099.061 had CnxEtU.sys with working firmware !!!
(look at /var/log/messages)

Jun 25 00:16:27 Itmy kernel: usb 2-2: configuration #1 chosen from 1 choice
Jun 25 00:16:29 Itmy kernel: cxacru 2-2:1.0: found firmware cxacru-fw.bin
Jun 25 00:17:27 Itmy kernel: ATM dev 0: ADSL line: attempting to activate
Jun 25 00:17:52 Itmy kernel: ATM dev 0: ADSL line: training
Jun 25 00:17:57 Itmy kernel: ATM dev 0: ADSL line: channel analysis
Jun 25 00:18:02 Itmy kernel: ATM dev 0: ADSL line: up (512 kb/s down | 128 kb/s up)


'''4.Final step: Setup pppd in order to connect to the internet.'''

-Load pppoatm module:
Slackware:add pppoatm in /etc/modules.conf
in other distros it may be in /etc/modules

-Set pppd options:
Create /etc/ppp/peers/adsl
Edit /etc/ppp/peers/adsl:

	# General configuration options for PPPD:

	lock

	kdebug 1

	defaultroute

	noipdefault

	holdoff 4

	persist

	maxfail 25

	usepeerdns

	passive

	asyncmap 0

	lcp-echo-interval 2

	lcp-echo-failure 7

	user put.your.username.here

	plugin /usr/lib/pppd/2.4.4b1/pppoatm.so

	8.35

	
Edit /etc/ppp/pap-secrets

	"put.your.username.here" * "putyourpasswordhere" *
	
Edit /etc/ppp/chap-secrets

	"put.your.username.here" * "putyourpasswordhere" *


'''5.Connect to the internet !!!'''

Start the connection 
pppd call adsl

If everything goes well you will see something like this:
Plugin /usr/lib/pppd/2.4.4b1/pppoatm.so loaded.
PPPoATM plugin_init
PPPoATM setdevname_pppoatm - SUCCESS:8.35

Stop the connection
killall pppd
[[Link title]]</text>
    <sha1>5b2a2037b683be73b2dca95cc15f3a0adc35a420</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Customising the install disk</title>
  <ns>0</ns>
  <id>63</id>
  <revision>
    <id>84</id>
    <timestamp>2009-06-02T03:24:31Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1057" xml:space="preserve">[[Category:Tips]] [[Category:Slamd64]]

This is from my experience working with [http://www.slamd64.com Slamd64], and will probably grow
as people ask more things.

==Adding a new kernel to the disk==
Firstly, copy the kernels/bare.i/config to .config in your kernel source directory. You then need
to configure your kernel as appropriate, and build it. Once you've done this, go to the kernels/ subdirectory of the tree, and make a new directory for your kernel, then run these commands:

 cd /usr/src/linux
 cp .config /path/to/slackware/tree/kernels/$KERNELNAME/config
 cp arch/x86_64/boot/bzImage /path/to/slackware/tree/kernels/$KERNELNAME/bzImage
 gzip -9 System.map
 cp System.map.gz /path/to/slackware/tree/kernels/$KERNELNAME/System.map.gz

You then need to add a new section to the isolinux/isolinux.cfg file for the kernel,
for example, if $KERNELNAME = 3ware.s (from Slamd64):
 
 label 3ware.s
  kernel /kernels/3ware.s/bzImage
  append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=11719 rw root=/dev/ram SLACK_KERNEL=3ware.s11</text>
    <sha1>690ed08b049b5efec526bdd275902a8f76278995</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>ACPI Modules</title>
  <ns>0</ns>
  <id>64</id>
  <revision>
    <id>85</id>
    <timestamp>2009-06-02T03:25:02Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="582" xml:space="preserve">[[Category:Tips]]

These are the kernel modules that need to be loaded in order to use some of the features of ACPI.

* ac - AC adapter information
* battery - Battery information
* fan
* button - Enables accesing info about ACPI-controlled buttons (like the Power button and the LID button)
* video
* thermal - Driver for the Thermal Zone (/proc/acpi/thermal_zone)
* processor - Loads the ACPI processor driver (/proc/acpi/processor)
* container - Loads the ACPI container driver
* vendor-specific drivers (eg acer_acpi, [http://www.thinkwiki.org/wiki/Thinkpad-acpi thinkpad-acpi])</text>
    <sha1>a1f62a5b9a0a02eca3d6d924c4076b0ae8077c45</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>ACX100 Wireless</title>
  <ns>0</ns>
  <id>65</id>
  <revision>
    <id>86</id>
    <timestamp>2009-06-02T03:26:43Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Hardware</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5904" xml:space="preserve">[[Category:Hardware]]
== Introduction ==
This is a Howto on how I was able to get the ACX100 open source driver to work with my card and Slackware.  There are several other good resources for this driver on the 'net, but I thought it would be good to create one more that included the specific steps I took in Slackware to get my wireless internet running.

For the time being, this is mostly just a placeholder, I will update this when I can find some spare time.  Check out http://acx100.sourceforge.net for more info.


== ACX100 Readme ==
 This tarball is targeted at 2.6 inclusion only.
 Not designed to work or even compile with 2.4.

 Contact:
 netdev@vger.kernel.org
 acx100-devel@lists.sourceforge.net
 acx100-users@lists.sourceforge.net

 Bug reports:

 Visit http://www.catb.org/~esr/faqs/smart-questions.html

 Please describe your wireless setup, manufacturer and type
 (acx100/acx100usb/acx111?) of your hardware. Which firmware image(s)
 are you using? If problem is reproducible, #define ACX_DEBUG 2
 in acx_config.h and modprobe driver with debug=0xffff.
 Post resulting kernel log (bzipped). It is large but very useful
 for bug hunting. Try older versions of the driver.

 Firmware images:

 You should not supply firmware_dir= parameter anymore. Driver will try
 to load the following images via hotplug (not from /usr/share/acx
 directory as older driver did, hotplug firmware directory location
 varies for different distros, try /lib/firmware or
 /usr/lib/hotplug/firmware):

 PCI driver:
 'tiacxNNNcMM' (NNN=100/111, MM=radio module ID (in uppercase hex)):
 combined firmware for specified chipset and radio.
 Failing that, it will try to load images named 'tiacxNNN'
 (main firmware for specified chipset) and 'tiacxNNNrMM' (corresponding
 radio module). For example, my firmware is in file named 'tiacx111c16'.
 Alternatively, I may remove it and use pair of files 'tiacx111' and
 'tiacx111r16' instead.
 USB driver:
 image is named 'tiacxNNNusbcMM'

 Build instructions:

 * Create drivers/net/wireless/acx subdirectory inside
  your kernel tree.
 * BTW, if your kernel has drivers/net/wireless/tiacx directory,
  you already may have acx driver (some different version).
  Decide which one do you want.
 * Unpack tarball into drivers/net/wireless/acx directory.
 * Add a line to drivers/net/wireless/Makefile:
      obj-m += acx/
 * Build your modules as usual (perhaps "make modules modules_install").

 This will create acx module.

 Remove "acx-obj-y += usb.o" line in Makefile
 and "#define CONFIG_ACX_USB 1" line in acx_config.h
 if you want PCI-only driver. Ditto for USB-only one.

 USB snooping:

 If you are an USB driver developer and need to see USB traffic,
 http://benoit.papillault.free.fr/usbsnoop/ may be useful.
 Another very good way to snoop the USB frames is under Linux if your
 driver happens to run under ndiswrapper (which is often the case),
 either by savage printk's, or by using the USB snooping facilities from
 Pete Zaitcev.


 From: Per Bjornsson &lt;perbj@stanford.edu&gt;
 To: ACX100 user mailing list &lt;acx100-users@lists.sourceforge.net&gt;
 Date: Fri, 08 Jul 2005 13:44:26 -0700

 Hi,

 Just a note for those who, like me, prefer not to bother recompiling
 their whole kernel: It's not at all difficult to compile Denis's
 snapshots out of tree, despite what the readme file says! At least in
 somewhat recent 2.6.x kernels, there's a special syntax for compiling
 modules in a particular directory (as noted in the kernel docs in
 Documentation/kbuild/modules.txt):

      * Unpack Denis's tarball in a new directory (note that the
        tarballs currently don't contain a root directory, just the
        files, so you want to do the untarring in an empty directory)
      * If you're building for the currently running kernel, build the
        modules with the command
        make -C /lib/modules/`uname -r`/build M=`pwd`
      * Install the modules (must be root for this step, so use
        'su' if that's your preferred method of doing root stuff) with
        make -C /lib/modules/`uname -r`/build M=`pwd` modules_install

 I figured that the snapshots might get more testing if more people know
 that they don't have to muck around with the whole kernel source in
 order to build this. I tested this on Fedora Core 4; sane distributions
 should be using this setup for accessing the kernel build files (if they
 listened to Linus's suggestions anyways). The one trick is that you
 might need a special "kernel development files" package; on Fedora Core,
 the files are included in the regular kernel package for FC2 and 3 but
 you need the 'kernel-devel' package for FC4.

 And finally, the kernel won't figure out that the module has been
 installed until you run 'depmod -ae' as root. You can check that
 something useful got picked up with 'modinfo'. (Both of these commands
 are likely installed in /sbin so you might need the full path unless
 you're fully logged in as root.)

 The latest snapshot (acx-20050708.tar.bz2) generally seems to work well
 for me, except that it's somewhat noisy and reports a lot of DUPs in the
 system log. However, it appears to associate more consistently with my
 access point that the old versions (when I had those modprobed on boot
 and brought up by the system network scripts, the card would often just
 sit and scan around and never actually associate until I manually
 restarted the connection) - admittedly I've only tried a couple of times
 yet so I don't know just how consistent this is. My hardware is a
 Netgear WG311v2, using the firmware from the latest Netgear Windows
 driver. (Can't check the details right now since I'm not at that
 computer, sorry - it got too late when I was mucking with this and other
 stuff yesterday for me to get a message sent...)

 Cheers,
 Per
 --
 Per Bjornsson &lt;perbj@stanford.edu&gt;
 Ph.D. Candidate, Department of Applied Physics, Stanford University</text>
    <sha1>cb763581eddb7ff55006518a528e5c6cd5dc6fec</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>AllixD Firewall Script</title>
  <ns>0</ns>
  <id>66</id>
  <revision>
    <id>87</id>
    <timestamp>2009-06-02T03:28:07Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2150" xml:space="preserve">I use this. It does not allow any incoming data, so it's no good for NFS servers.

 #!/bin/sh
 
 IPT="/usr/sbin/iptables"
 
 # Let's make sure forwarding is DISABLED:
 echo "0" &gt; /proc/sys/net/ipv4/ip_forward
 
 # Let's enable SYN cookies (to protect against SYN floods):
 echo "1" &gt; /proc/sys/net/ipv4/tcp_syncookies
 
 # Let's disable TCP timestamps to reduce the TCP stack workload:
 echo "0" &gt; /proc/sys/net/ipv4/tcp_timestamps
 
 # Let's enable reverse path filtering for anti-spoofing:
 echo "1" &gt; /proc/sys/net/ipv4/conf/all/rp_filter
 
 # Let's ignore PINGs which have been BROADCAST:
 echo "1" &gt; /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
 
 # Let's disable source routed packets as they are ridiculous:
 echo "0" &gt; /proc/sys/net/ipv4/conf/all/accept_source_route
 
 # Let's allow redirects from trusted gateways only:
 echo "1" &gt; /proc/sys/net/ipv4/conf/all/secure_redirects
 
 # Let's log any UFOs which are spotted:
 echo "1" &gt; /proc/sys/net/ipv4/conf/all/log_martians
 
 # Let's flush-out all the chains in our tables:
 $IPT -F
 $IPT -F -t nat
 $IPT -F -t mangle
 
 # Let's delete every non-builtin chains in our tables:
 $IPT -X
 $IPT -X -t nat
 $IPT -X -t mangle
 
 # Let's set our INPUT policy to DROP:
 $IPT -P INPUT DROP
 
 # Let's set our OUTPUT policy to ACCEPT, because we can
 # appreciate this kinda flexibility on a Home PC:
 $IPT -P OUTPUT ACCEPT
 
 # Let's accept incoming packets which belong to connections
 # that have ALREADY been initiated:
 $IPT -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
 
 # Let's allow all packets initiating new connections LOCALLY:
 $IPT -A INPUT -i lo -m state --state NEW -j ACCEPT
 
 # Let's log every packet that reaches this rule, right before
 # it hits our INPUT policy and gets a DROP:
 $IPT -A INPUT -j LOG --log-prefix "INPUT DROP: "
 
 # Let's load the module allowing Connection Tracking for FTP:
 /sbin/modprobe ip_conntrack_ftp
 
 # Let's load the module allowing Connection Tracking for IRC:
 /sbin/modprobe ip_conntrack_irc
 
 # No rc.firewall script is complete without the ubiquitous echo:
 echo "So let it be written. So let it be done."

[[Category:Security]]</text>
    <sha1>bab170863061646b57bacd635f02d2b78a6837b5</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Apache</title>
  <ns>0</ns>
  <id>67</id>
  <revision>
    <id>88</id>
    <timestamp>2009-06-02T03:30:00Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1994" xml:space="preserve">[[Category:Tips]]
==Tuning logs==

I'm sure all of you have gotten x90's and other worm hits flooding your apache logs. Well its an easy fix, just edit a few things. First find and edit your log entries:

: &lt;code&gt;CustomLog /var/log/apache/access_log common env=good&lt;/code&gt;
: &lt;code&gt;CustomLog /dev/null common env=!good&lt;/code&gt;

You can use an actual file to log errors, instead of dumping them to &lt;tt&gt;/dev/null&lt;/tt&gt;

Now we find a section that looks similiar below

Now lets tell it what to log :) Notice WHAT TO LOG

 &lt;IfModule mod_setenvif.c&gt;
 SetEnvIf Request_Method "HEAD" good
 SetEnvIf Request_Method "GET" good
 SetEnvIf Request_Method "POST" good
 SetEnvIf Request_URL "^/script" !good
 SetEnvIf Request_URL "^/default.ida" !good
 SetEnvIf Request_URI (.*)default\.ida !good
 SetEnvIf Request_URI (.*)cmd\.exe !good
 SetEnvIf Request_URI (.*)scripts !good
 SetEnvIf Request_URI (.*)root\.exe !good
 &lt;/IfModule&gt;

Notice how there are 2 goods, One is with the ! and one without. The first one without the ! is what apache will log. The second !good, that tells apache what you dont want to log. In the above example i have SetEnvIf Request_URI (.*)default\.ida !good. This would actually find anything with default.ida and not log it. This would stop the default.ida?XXXXXXX in the logs. That will match anything with default.ida. This next example would block the IP address you set:

: &lt;code&gt;SetEnvIf Remote_Addr "192\.168\.0\.1" !good&lt;/code&gt;

Again you notice that it wont log anything coming from that IP.

==Enabling PHP in Apache==
Enabling PHP in slackware is fairly easy, all you have to do is open /etc/apache/httpd.conf - as SU - and edit 1 line!. Find the line below - it is near the bottom:

 #Include /etc/apache/mod_php.conf

Then you just make it look like this:
 
 Include /etc/apache/mod_php.conf

When you restart apache you might want to put a small php script in your htdocs directory and test it. To restart apache:
 
 apachectl graceful

==CGI-BIN==
See [[Apache-cgi]]</text>
    <sha1>62103ff09d31ed909ea056b1557ea9028978c06d</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Basic Security Fixes</title>
  <ns>0</ns>
  <id>69</id>
  <revision>
    <id>90</id>
    <timestamp>2009-06-02T03:31:08Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3802" xml:space="preserve">Small tips to increase the security of your Slackware box:

* Use strong passwords! The most common way Linux systems get hacked is through weak user passwords and SSH.
* Use a firewall! [http://www.freshmeat.net Freshmeat.net] has lots of automatic tools to help with configuration, and we have some example scripts posted [[Iptables_Scripts|here]].
* Tell X not to listen for TCP connections:
** KDM: Add "ServerArgsLocal=-nolisten tcp" under section [X-:*-Core] to /opt/kde/share/config/kdm/kdmrc
** XDM: Add "-nolisten tcp" to the line calling X in /etc/X11/xdm/Xservers.
** Console: Use 'startx -- -nolisten tcp' rather than 'startx', possibly with the aid of an alias.
***: You can also edit startx and, at line 168 (where it calls xinit), append '-nolisten tcp' at the end, but this is a dirty hack.
* Close any services you do not require, especially since most run as root. Think about what you will use them for. For instance, would you really want to run an sshd 24/7 when you will only perhaps access it remotely once in a blue moon, of which you will most likely know about in advance at which point you can run the required deamon prior too accessing remotely.
** To disable startup services in /etc/rc.d, unset the executable bit of the rc script. You can still start and stop services by executing the rc script later using 'sh'.
** You can also edit /etc/rc.d/rc.M directly and comment out lines that calls the other rc scripts.
* Disable the "time" service, by commenting out lines 22 and 23 in /etc/inetd.conf - you will need to restart inetd after making the changes. (If you need to run inetd at all!)
* Look for any services/daemons that you don't know about by running "netstat -luntp".
* Run 'ps -e u' several times and become familiar with your usual processes to establish a "baseline". Then keep monitoring regularly to spot when something doesn't seem right.
* If you suspect intrusion or have suspicious files, scan your system for rootkits with 'chkrootkit'. You can also scan for win32 "malware" with 'clamav' for instance if you're using your system as a mail/ftp server.
* Add the following line to hosts.deny to disallow access by any host to your system... 'ALL: ALL' - note that this only affects services built with libwrap (tcpwrappers), but it's one layer of security.  A further layer would be to add the following to /etc/hosts.allow... 'ALL: ALL: DENY'
* Fine tune logrotate by editing /etc/logrotate.conf and add more log rotations in /etc/logrotate.d/

* If you want to restrict who is able to use the su command to switch to certain users, you can use /etc/suauth. The basic format for /etc/suauth is "to-id:from-id:ACTION"

:Example:

    root:foobar:DENY 

:would stop the user foobar from using su to become root.

:Another example:

    root:ALL EXCEPT GROUP wheel:DENY

:would only allow users in the wheel group to su to root. 

:You can also allow users to su with no password required (why you would do this is beyond me), and can require that a user enter their OWN password before switching users. For more information, please consult the man page for /etc/suauth. 

:(Thanks to cubicool for informing me of the existence of /etc/suauth)

:A similar, though perhaps not as fine-grained, way to control who can use su is to change ownership and permissions of /bin/su.  First, add the user(s) that you want to be able to use su to the wheel group in /etc/passwd.  Next, change the ownership of /bin/su to group wheel, and change its permissions to 4750.
 chown root:wheel /bin/su
 chmod 4750 /bin/su
:This makes /bin/su executable *only* by members of the wheel group.

* Another way to restrict the users who can become root is to edit the file /etc/login.defs and change the value of SU_WHEEL_ONLY to yes.

[[Category:Tips]]
[[Category:Security]]</text>
    <sha1>5f3827f2c6a6dd53eb27b78e16058b0b0ebb469e</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Bluetooth</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>91</id>
    <timestamp>2009-06-02T03:31:37Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13813" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
This tutorial is meant to simplify the process of configuring a GNU/Linux Distribution, specifically Slackware, to use Bluetooth wireless technology.  I will show you step by step how I setup my system and got Bluetooth functioning.  Since it is unlikely that you have the exact same hardware that I do, you may need to modify a few steps to fit your needs.

== Example System Information ==
This is a list of my specific hardware that applies to this topic.  Do not worry if your's is not exactly the same because you can still use this information to guide you through the process.

;Motherboard (USB Ports)
:[http://www.msicomputer.com/product/p_spec.asp?model=K8N_Neo4_Platinum/SLI MSI Neo4 Platinum/SLI]
;Bluetooth USB Dongle
:[http://www.amazon.com/gp/product/B0001Q5SZ0/103-7636612-6018206?v=glance&amp;n=172282 Kensington Bluetooth USB Adapter (33085)]
;Cell Phone
:[http://www.motorola.com/motoinfo/product/details.jsp?globalObjectId=72 Motorola V551]
;[http://www.slackware.org Slackware-Current (as of 5/31/06)]
;[http://www.kernel.org Kernel 2.6.16.16] (worked on 2.6.15.6 also)

== Kernel Configuration ==
The first step is enabling the drivers for USB and Bluetooth in your kernel.  I'm not sure exactly which kernel version began including Bluez Bluetooth drivers, but my 2.6.15.6 kernel had them.  [http://www.westmaster.com/zidek/p900/bluetooth/ From this page], it looks like 2.6.5 did not have Bluetooth drivers and needed to be patched.  If you are running an older kernel, follow the directions on that page to apply the Bluez patch.  If you are unfamiliar with the kernel configuration/compilation sequence, then check out the [[Kernel26Compilation]] tutorial before proceeding.

=== USB support ===
For the less-advanced user (like myself), it is safe to go through and answer `M` to everything that you can, and `Y` to everything that can not take `M`.  You should not enable any of the "debug" options, I'm not 100% sure why, but I'm pretty sure that these options will give you verbose output that is only needed for kernel hackers.  Below, you can see the options I have set in my .config file for my kernel.  The options listed are just those that I thought pertained to getting my USB ports working and able to recognize my USB dongle.
 #
 # USB support
 #
 CONFIG_USB_ARCH_HAS_HCD=y
 CONFIG_USB_ARCH_HAS_OHCI=y
 CONFIG_USB=y
 # CONFIG_USB_DEBUG is not set
 #
 # Miscellaneous USB options
 #
 CONFIG_USB_DEVICEFS=y
 CONFIG_USB_BANDWIDTH=y
 # CONFIG_USB_DYNAMIC_MINORS is not set
 # CONFIG_USB_SUSPEND is not set
 # CONFIG_USB_OTG is not set
 #
 # USB Host Controller Drivers
 #
 CONFIG_USB_EHCI_HCD=m
 CONFIG_USB_EHCI_SPLIT_ISO=y
 CONFIG_USB_EHCI_ROOT_HUB_TT=y
 CONFIG_USB_ISP116X_HCD=m
 CONFIG_USB_OHCI_HCD=y
 # CONFIG_USB_OHCI_BIG_ENDIAN is not set
 CONFIG_USB_OHCI_LITTLE_ENDIAN=y
 CONFIG_USB_UHCI_HCD=y
 CONFIG_USB_SL811_HCD=m

=== Bluetooth support ===
Again, it is safe to enable everything that says "Bluetooth" as a Module.  Below are the options from my .config file that I thought might be relevant.
 #
 # FIR device drivers
 #
 CONFIG_USB_IRDA=m
 CONFIG_SIGMATEL_FIR=m
 CONFIG_NSC_FIR=m
 CONFIG_WINBOND_FIR=m
 CONFIG_TOSHIBA_FIR=m
 CONFIG_SMC_IRCC_FIR=m
 CONFIG_ALI_FIR=m
 CONFIG_VLSI_FIR=m
 CONFIG_VIA_FIR=m
 CONFIG_BT=m
 CONFIG_BT_L2CAP=m
 CONFIG_BT_SCO=m
 CONFIG_BT_RFCOMM=m
 CONFIG_BT_RFCOMM_TTY=y
 CONFIG_BT_BNEP=m
 CONFIG_BT_BNEP_MC_FILTER=y
 CONFIG_BT_BNEP_PROTO_FILTER=y
 CONFIG_BT_HIDP=m
 #
 # Bluetooth device drivers
 #
 CONFIG_BT_HCIUSB=m
 CONFIG_BT_HCIUSB_SCO=y
 CONFIG_BT_HCIUART=m
 CONFIG_BT_HCIUART_H4=y
 CONFIG_BT_HCIUART_BCSP=y
 CONFIG_BT_HCIBCM203X=m
 CONFIG_BT_HCIBPA10X=m
 CONFIG_BT_HCIBFUSB=m
 CONFIG_BT_HCIVHCI=m
 CONFIG_IEEE80211=m
 # CONFIG_IEEE80211_DEBUG is not set
 CONFIG_IEEE80211_CRYPT_WEP=m
 CONFIG_IEEE80211_CRYPT_CCMP=m
 CONFIG_IEEE80211_CRYPT_TKIP=m

Now, just compile the kernel and reboot in to it.

== Userland ==
At a bare minimum, you need to install bluez-libs and bluez-utils from http://www.bluez.org.  I used the binary package provided by [http://www.develia.org/tarballs.php?p=networking develia.org], but that was before I knew about SlackBuild scripts.  If you can not find a SlackBuild script and you do not want to create your own, you should use [[Checkinstall]] at the very least.

At this time, you might as well install KDE-Bluetooth, also.  I think I grabbed my binary package from [http://www.linuxpackages.net LinuxPackages], but that was also before I knew better.  You can either grab the source code on it's own from [http://sourceforge.net/project/showfiles.php?group_id=89888 SoureForge] or as a part of [ftp://ftp.kde.org/pub/kde/snapshots/kdeextragear-multimedia.tar.bz2 KDE Extra Gear].  Again, use a Slackbuild script or [[Checkinstall]] to install these.

For more information on SlackBuild scripts, you can see the following tutorials: [[SlackBuild Scripts]], [[Writing A SlackBuild_ Script]], [[Slack-desc]], [[Different Approach To Buildscripts]], [[Checkinstall]]

== Configuration ==
Now, should have all of the tools you need to start connecting your computer to your bluetooth devices.  First, check the status of the bluetooth dongle with hciconfig.
 # hciconfig
 hci0:   Type: USB
        BD Address: 00:11:22:33:44:55 ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN 
        RX bytes:385 acl:0 sco:0 events:18 errors:0
        TX bytes:322 acl:0 sco:0 commands:18 errors:0
If yours says "UP RUNNING" then you are good to go.  If not, you need to bring the interface up.
 # hciconfig hci0 up
 # hciconfig hci0
 hci0:   Type: USB
        BD Address: 00:11:22:33:44:55 ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN 
        RX bytes:385 acl:0 sco:0 events:18 errors:0
        TX bytes:322 acl:0 sco:0 commands:18 errors:0
Since the dongle works, it's time to configure the programs that will make the actual connections.  Use your favorite text editor to edit the PIN in /etc/bluetooth/pin:
 # gvim /etc/bluetooth/pin
The PIN needs to be all digits.  I'm not sure if it needs to be exactly four (4) digits, but four (4) works well.  Here is an example:
 PIN:1234
Then you need to edit /etc/bluetooth/hcid.conf
 #
 # HCI daemon configuration file.
 #
 # HCId options
 options {
        autoinit yes;
        #security auto;
        security user;
        pairing multi;
        pin_helper /opt/kde/lib/kdebluetooth/kbluepin;
        #pin_helper /usr/bin/bluepin;
        #pin_helper /usr/bin/pin;
        #dbus_pin_helper;
 }
 device {
        name "BlueZ %h (%d)";
        class 0x3e0100;
        #pkt_type DH1,DM1,HV1;
        iscan enable; pscan enable;
        lm accept;
        lp rswitch,hold,sniff,park;
        # Authentication and Encryption (Security Mode 3)
        #auth enable;
        #encrypt enable;
 }

=== Choosing a PIN Helper ===
From all the other HOWTO's I read, I got the impression that the /usr/bin/bluepin script supplied with the Bluez-utils was junk.  I found a nice, simple replacement script on this page http://orin.meinlschmidt.org/~znouza/doc/r51/.  I will duplicate it here just for ease, but all rights and respect go to whoever made that page.  Use your favorite text editor and  create the new file /usr/bin/pin:
 #!/bin/bash
 # original script from http://orin.meinlschmidt.org/~znouza/doc/r51/
 cat /etc/bluetooth/pin
when you are done editing, save and close the file, then make it executable.  Choose your permissions wisely.
 # chmod 710 /usr/bin/pin
 # ls -la /usr/bin/pin
 -rwx--x--- 1 root root 35 2006-04-09 19:19 /usr/bin/pin
This /usr/bin/pin script will suffice for pretty much any way you want to connect to your phone.  If you want to use kdebluetooth to connect to your phone, then use kbluepin.  The example hcid.conf file above is already setup to use kbluepin.  To use /usr/bin/pin, simply comment out the kbluepin line and remove the comment character(#) from the /usr/bin/pin line.

=== Making the Connection ===
Next, you need to start up the hcid and sdpd daemons.  It is a good idea to add these to /etc/rc.d/rc.local so they start automatically with each reboot.  At the command line type:
 # /usr/sbin/hcid
 # /usr/sbin/sdpd
and add these lines to /etc/rc.d/rc.local
 /usr/sbin/hcid
 /usr/sbin/sdpd
Then, you can set your phone to "discover" mode, allowing other devices to see it is present, and scan for it.  On the Motorola V551 you go to Settings &gt; Connection &gt; Bluetooth Link &gt; Setup &gt; Find Me.
 # hcitool scan
 Scanning ...
        00:12:34:56:78:9A       Motorola Phone
Using the hardware address from the scan above, you can find out a lot of information about your phone.
 # sdptool records 00:12:34:56:78:9A
 Service Name: Dial-up networking Gateway
 Service Description: Dial-up networking Gateway
 Service Provider: Cingular
 Service RecHandle: 0x10001
 Service Class ID List:
   "Dialup Networking" (0x1103)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 1
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "Dialup Networking" (0x1103)
     Version: 0x0100
 
 Service Name: Voice Gateway
 Service Description: Headset Audio Gateway
 Service Provider: Cingular
 Service RecHandle: 0x10003
 Service Class ID List:
   "Headset Audio Gateway" (0x1112)
   "Generic Audio" (0x1203)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 3
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "Headset" (0x1108)
     Version: 0x0100
 
 Service Name: Hands-Free voice gateway
 Service Description: Hands-Free voice gateway
 Service Provider: Cingular
 Service RecHandle: 0x10007
 Service Class ID List:
   "Handfree Audio Gateway" (0x111f)
   "Generic Audio" (0x1203)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 7
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "Handsfree" (0x111e)
     Version: 0x0101
 
 Service Name: OBEX Object Push
 Service Description: OBEX Object Push
 Service Provider: Cingular
 Service RecHandle: 0x10008
 Service Class ID List:
   "OBEX Object Push" (0x1105)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 8
   "OBEX" (0x0008)
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "OBEX Object Push" (0x1105)
     Version: 0x0100
 
 Service Name: OBEX File Transfer
 Service Description: OBEX File Transfer
 Service Provider: Cingular
 Service RecHandle: 0x10009
 Service Class ID List:
   "OBEX File Transfer" (0x1106)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 9
   "OBEX" (0x0008)
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "OBEX File Transfer" (0x1106)
     Version: 0x0100

=== Radio Frequency Communication (RFCOMM) ===
This is one way to use your phone as a modem.  I believe that most Cingular and T-Mobile (GSM/GPRS) in the USA use channel 1 for the Dial-Up Gateway.  One way to take advantage of this is to use rfcomm to connect to your phone.  In order to do that, you will need to edit /etc/bluetooth/rfcomm.conf:
 #
 # RFCOMM configuration file.
 #
 rfcomm0 {
        # Automatically bind the device at startup
        bind yes;
        # Bluetooth address of the device
        device 00:12:34:56:78:9A;
        # RFCOMM channel for the connection
        channel	1;
        # Description of the connection
        comment "Motorola V551";
 }
Then connect to the phone by typing:
 # rfcomm connect 0
I won't go in to any more details because I don't use my phone as a modem.  But, if you want to use your phone that way, there are plenty of resources out there to show you what to do.

=== KDE Bluetooth ===
I don't use KDE as my window manager/desktop, but kdebluetooth should automatically run when you start KDE.  If you don't use KDE, like me, you can start up the taskbar daemon by typing "kbluetoothd" in a terminal.  You can then use the KDE OBEX Push Client to transfer files to your phone.  I haven't figured out how to get files off of my phone (like pictures), but I have seen [http://openobex.triq.net/obexftp/obexftp obexftp] and [http://openobex.triq.net/obexfs obexfs] which look promising.  When I test those out, I will update this accordingly.

== References ==
http://www.linuxquestions.org/hcl/showproduct.php?product=2879&amp;cat=53

http://www.westmaster.com/zidek/p900/bluetooth/

http://www.bluez.org

http://www.develia.org/tarballs.php?p=networking

http://kde-bluetooth.sourceforge.net/

http://extragear.kde.org/

http://www.gentoo.org/doc/en/bluetooth-guide.xml</text>
    <sha1>664ab6dbe9ea7bef43cd9a832c082f991e6071f3</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Buzzedlightyears IPTables</title>
  <ns>0</ns>
  <id>71</id>
  <revision>
    <id>92</id>
    <timestamp>2009-06-02T03:32:51Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1249" xml:space="preserve"> #!/bin/sh
 
 IPTABLES=/usr/sbin/iptables
 
 #Allow incoming returning requests (Port Scans, Pings)
 $IPTABLES -A INPUT -j ACCEPT -m state --state ESTABLISHED -i eth0 -p icmp
 $IPTABLES -A INPUT -j ACCEPT -m state --state ESTABLISHED -i eth0 -p tcp
 $IPTABLES -A INPUT -j ACCEPT -m state --state ESTABLISHED -i eth0 -p udp
 
 #Allow incoming FTP Connections
 $IPTABLES -A INPUT -p tcp --dport 20 -j ACCEPT
 $IPTABLES -A INPUT -p tcp --dport 21 -j ACCEPT
 
 #Allow new incoming SSH connections
 #$IPTABLES -A INPUT -p tcp --dport 22 -m state --state new -j ACCEPT
 
 #Webserver
 #$IPTABLES -A INPUT -p tcp --dport 80 -j ACCEPT
 
 #Allow Pings
 $IPTABLES -A INPUT -p icmp -j ACCEPT
 
 #Allow All Local Host
 $IPTABLES -A INPUT -i lo -j ACCEPT
 
 #Drop all other and LOG to /var/log/firewall
 $IPTABLES -A INPUT -m limit --limit 3/s --limit-burst 5 -i eth0 -j LOG
 #$IPTABLES -A INPUT -i eth0 -j DROP
 
 $IPTABLES -A FORWARD -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -m limit --limit 1/sec -j ACCEPT
 $IPTABLES -A FORWARD -p icmp -m icmp --icmp-type 8 -m limit --limit 1/sec -j ACCEPT
 $IPTABLES -A FORWARD -m state --state NEW,RELATED,ESTABLISHED,UNTRACKED -j DROP
 $IPTABLES -A INPUT -j DROP
 $IPTABLES -A INPUT -p igmp -j DROP

[[Category:Security]]</text>
    <sha1>47eb20f49e871b35b585ed906b8365d8121311c6</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Changes 10.1 10.2</title>
  <ns>0</ns>
  <id>72</id>
  <revision>
    <id>93</id>
    <timestamp>2009-06-02T03:33:26Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="631" xml:space="preserve">= Purpose =
The purpose of this page is to document the new packages (Package Additions) and removed packages (Package Removals) during the release cycle from Slackware 10.1 to Slackware 10.2.

= Package Additions From 10.1 to 10.2 =

* xap/mozilla-firefox
* xap/mozilla-thunderbird
* n/cyrus-sasl
* l/libgtkhtml
* l/librsvg
* l/libwpd
* l/fribidi
* d/subversion

= Package Removals From 10.1 to 10.2 =

* xap/netscape
* l/orbit
* gnome/*
* xap/jre-symlink
* xap/mozilla-plugins

= Other Concerns =

The following packages were moved from ./gnome when it was removed, so make sure they are still installed:
* l/libidl
* l/libmikmod</text>
    <sha1>708e39be8c4d6d059796362cea55226257ada930</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Changes 11.0 current</title>
  <ns>0</ns>
  <id>73</id>
  <revision>
    <id>94</id>
    <timestamp>2009-06-02T03:34:26Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, Well maybe not.. These DO need Categories however.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="263" xml:space="preserve">I've been doing this on SlackWiki previously, but this information is now available at Slackware.com - see the CHANGES_AND_HINTS.TXT file on any official Slackware mirror:
For example, on OSUOSL: http://slackware.osuosl.org/slackware-current/CHANGES_AND_HINTS.TXT</text>
    <sha1>280ec0280f26ff27cd28fe7b3aa47f5809e8a7c0</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>MySQL Configuration</title>
  <ns>0</ns>
  <id>74</id>
  <revision>
    <id>95</id>
    <timestamp>2009-06-02T03:35:46Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6387" xml:space="preserve">[[Category:Tutorials]]
''Have you just installed Slackware and now see a MySQL error at the login prompt?''

This is a VERY quick HowTo and should take maybe 30 seconds to complete at its slowest.  The reason I decided to do a write-up is because of the sheer number of people asking how to fix it.

== Option 1 ==
In a shell or xterm, type (you have to be logged in as superuser to use the mysql login):

 su mysql

This logs you into the 'mysql' user account.

Next, run:

 mysql_install_db

This will create the needed databases and set their permissions properly.

if your not logon as mysql user (root)

Don't forget to chown folder /var/lib/mysql
&lt;pre&gt;
chown -R mysql.mysql /var/lib/mysql
chmod 755 /etc/rc.d/rc.mysql
&lt;/pre&gt;

You're now finished and should not see the typical MySQL errors at the login prompt.

 /etc/rc.d/rc.mysql start

Now you should set a password for MySQL's root password:

 mysqladmin -u root password 'new-password-here'


You can connect to your MySQL server with:
 mysql -u root -p


For security reasons you should delete an empy user for localhost server
&lt;pre&gt;
mysql&gt; SELECT user, host FROM user;
mysql&gt; DELETE FROM user WHERE host='localhost' AND user=''; 
&lt;/pre&gt;
*''This tutorial is currently linked at ''
* ''http://www.unixfool.com/mysql-slack.shtml''

== Option 2 ==
1. log in as &lt;b&gt;root&lt;/b&gt; and install the mysql package

2. &lt;code&gt;killall -9 mysqld mysqld_safe&lt;/code&gt; to kill any running MySQL processes.

3. copy one of the my-size.cnf files in /etc to my.cnf (picking an apporpriate size):&lt;br&gt;
::&lt;code&gt;cp /etc/my-medium.cnf /etc/my.cnf&lt;/code&gt;

4. Install the MySQL database-

::'''Slackware 12.1''' (and later):
::::&lt;code&gt;mysql_install_db --user=mysql&lt;/code&gt;

::'''Slackware 12.0''' (and before):
::::&lt;code&gt;su mysql&lt;/code&gt;
::::&lt;code&gt;mysql_install_db&lt;/code&gt;
:::: &lt;code&gt;exit&lt;/code&gt; (to get out of the mysql login and back to root).

5. &lt;code&gt;mysqld_safe --skip-grant-tables &amp;&lt;/code&gt;

6. &lt;code&gt;mysql -u root mysql&lt;/code&gt;

7. &lt;code&gt;UPDATE user SET Password=PASSWORD('&lt;i&gt;new_password&lt;/i&gt;') WHERE user='root';&lt;/code&gt;

8. &lt;code&gt;FLUSH PRIVILEGES;&lt;/code&gt;

9. &lt;code&gt;exit&lt;/code&gt;

10. &lt;code&gt;killall -9 mysqld mysqld_safe&lt;/code&gt;

11. &lt;code&gt;mysqld_safe &amp;&lt;/code&gt;


to check the new password, (as root) type:&lt;br&gt;
::&lt;code&gt;mysqladmin -u root -p status&lt;/code&gt;&lt;br&gt;
:::::...and enter the new password.


== Option 3 ==

I'm starting from a [http://www.slackwiki.org/Minimal_System very basic install]. 

The only additional package needed is '''mysql''' in the '''AP''' group.

&lt;pre&gt;
# installpkg mysql-5.0.37-i486-1.tgz
# su mysql
$ mysql_install_db
Installing all prepared tables
Fill help tables
...
$ exit
# chmod 755 /etc/rc.d/rc.mysqld 
# /etc/rc.d/rc.mysqld start
Starting mysqld daemon with databases from /var/lib/mysql
&lt;/pre&gt;

MySQL is now installed, but there are no passwords defined yet.

&lt;pre&gt;
# mysql -u root
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.0.37 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
&lt;/pre&gt;

We can now set passwords from within the MySQL console. I know this can be achieved with '''mysqladmin''', but then, several ways lead to Rome. It's a simple matter of habit.

&lt;pre&gt;
mysql&gt; show databases;
 +--------------------+
| Database           |
+--------------------+
| information_schema | 
| mysql              | 
| test               | 
+--------------------+
3 rows in set (0.01 sec)

mysql&gt; use mysql;
Database changed

mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+----------+
| user | host      | password |
+------+-----------+----------+
| root | localhost |          | 
| root | slacktest |          | 
+------+-----------+----------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

As you can see, there are two 'root' users here (and none of them is our system's root user, don't forget): root@localhost... and root@slacktest. We have to set a password for both of them. In theory, these can be different, but why make things more complicated than they already are? ;o)

&lt;pre&gt;
mysql&gt; set password for root@localhost = password('yatahongaga');
Query OK, 0 rows affected (0.00 sec)
&lt;/pre&gt;

Let's repeat our query above to see the actual changes:

&lt;pre&gt;
mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+-------------------------------------------+
| user | host      | password                                  |
+------+-----------+-------------------------------------------+
| root | localhost | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
| root | slacktest |                                           | 
+------+-----------+-------------------------------------------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

You can see that root@localhost's password is displayed as a shadow password. Now let's set the password for root@slacktest (replace ''slacktest'' by your machine's hostname):

&lt;pre&gt;
mysql&gt; set password for root@slacktest = password('yatahongaga');
Query OK, 0 rows affected (0.00 sec)
&lt;/pre&gt;

What do we have now?

&lt;pre&gt;
mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+-------------------------------------------+
| user | host      | password                                  |
+------+-----------+-------------------------------------------+
| root | localhost | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
| root | slacktest | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
+------+-----------+-------------------------------------------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

Now we have some (very) basic security, we can leave the MySQL monitor.

&lt;pre&gt;
mysql&gt; quit;
Bye
&lt;/pre&gt;

To connect to our MySQL database as MySQL's root user (who, remember, is ''not'' the system's root), we can do the following:

&lt;pre&gt;
# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.0.37 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql&gt;
&lt;/pre&gt;

If we have to do this often, we can create a /root/.my.cnf file and edit it as follows:

&lt;pre&gt;
[mysql]
user            =       root
password        =       yatahongaga
&lt;/pre&gt;

Just to be on the safe side:

&lt;pre&gt;
# chmod 0600 /root/.my.cnf
&lt;/pre&gt;

From now on, you can connect directly to the MySQL monitor, without having to type your password every time.</text>
    <sha1>76136fd2d80d3001fe43e10cee3b3a752f9ae325</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Converting From CRLF To LF</title>
  <ns>0</ns>
  <id>75</id>
  <revision>
    <id>96</id>
    <timestamp>2009-06-02T03:37:08Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, moved to Tips</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="483" xml:space="preserve">=Explanation=

There are several ways of converting the CRLF combination to LF and vice-versa. The simplest one under Slackware is to use the tools &lt;code&gt;fromdos&lt;/code&gt; and &lt;code&gt;todos&lt;/code&gt;, which receive the file from the standard input and write the result to the standard output. They are part of the &lt;code&gt;bin&lt;/code&gt; package.

=Examples=

 $ fromdos &lt;input_file &gt;output_file   # Converts CRLF to LF
 $ todos   &lt;input_file &gt;output_file   # Converts LF to CRLF

[[Category:Tips]]</text>
    <sha1>aa0875e66f3a86ace105ffb53e56e0b5af1ac930</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Cron Jobs</title>
  <ns>0</ns>
  <id>76</id>
  <revision>
    <id>97</id>
    <timestamp>2009-06-02T03:38:28Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1879" xml:space="preserve">Based on [[User:Sandman1|Sandman1]]'s tutorial.

Well you are reading this tutorial because you need to schedule a certain task or a script on a certain day. First you need to know a few things about cron before we get started. One of those things is the table below:

 1 = minute past the hour (0 through 59)
 2 = hour (0 through 23)
 3 = day of month (1 through 31)
 4 = month of year (1 through 12)
 5 = day of the week
     0 = Sunday (This can also be 7)
     1 = Monday
     2 = Tuesday
     3 = Wednesday
     4 = Thursday
     5 = Friday
     6 = Saturday

This table will be used later on in this tutorial. Now first part of editing a cron entry is typing in the following command:

: &lt;code&gt;crontab -e&lt;/code&gt;

(I usually do this as root if the command needed to run requires root)

Well this brings up the regular vi(elvis in slackware) screen. Most people don't use VI. There is a variable you can set to change the default cron editor.

: &lt;code&gt;export VISUAL=pico&lt;/code&gt;

That will change the default editor for the session to pico. It's a little friendlier when it comes to editing for some people out there. There is also a GNU editor like pico called nano. Now we need to schedule a command for running.

: &lt;code&gt;6 10 * * * /root/scripts/example&lt;/code&gt;

The example above here will run the command /root/scripts/example at 10:06 every day. The numbers above (on the table) symbolize the mark of where it belongs. So the 6 would be number 1 on the table and the 10 will be the hour.

: &lt;code&gt;*/30 * * * * /root/scripts/example&lt;/code&gt;

The entry above will run the /root/scripts/example every 30 minutes of every day. Now save your entries and they will run when you tell them to. You also want to add 1&gt; /dev/null on the end of your command so you send the output to /dev/null instead of roots email (this is default on slackware). Good luck!

[[Category:Tutorials]]</text>
    <sha1>964d9af1342aaa9167daceac5a8b71af7b4084c6</sha1>
  </revision>
  <revision>
    <id>98</id>
    <parentid>97</parentid>
    <timestamp>2009-06-02T03:38:57Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1830" xml:space="preserve">Well you are reading this tutorial because you need to schedule a certain task or a script on a certain day. First you need to know a few things about cron before we get started. One of those things is the table below:

 1 = minute past the hour (0 through 59)
 2 = hour (0 through 23)
 3 = day of month (1 through 31)
 4 = month of year (1 through 12)
 5 = day of the week
     0 = Sunday (This can also be 7)
     1 = Monday
     2 = Tuesday
     3 = Wednesday
     4 = Thursday
     5 = Friday
     6 = Saturday

This table will be used later on in this tutorial. Now first part of editing a cron entry is typing in the following command:

: &lt;code&gt;crontab -e&lt;/code&gt;

(I usually do this as root if the command needed to run requires root)

Well this brings up the regular vi(elvis in slackware) screen. Most people don't use VI. There is a variable you can set to change the default cron editor.

: &lt;code&gt;export VISUAL=pico&lt;/code&gt;

That will change the default editor for the session to pico. It's a little friendlier when it comes to editing for some people out there. There is also a GNU editor like pico called nano. Now we need to schedule a command for running.

: &lt;code&gt;6 10 * * * /root/scripts/example&lt;/code&gt;

The example above here will run the command /root/scripts/example at 10:06 every day. The numbers above (on the table) symbolize the mark of where it belongs. So the 6 would be number 1 on the table and the 10 will be the hour.

: &lt;code&gt;*/30 * * * * /root/scripts/example&lt;/code&gt;

The entry above will run the /root/scripts/example every 30 minutes of every day. Now save your entries and they will run when you tell them to. You also want to add 1&gt; /dev/null on the end of your command so you send the output to /dev/null instead of roots email (this is default on slackware). Good luck!

[[Category:Tutorials]]</text>
    <sha1>e9425299551c7282495e0c56635cef849758f81b</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Customizing Bash Prompt</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>99</id>
    <timestamp>2009-06-02T03:39:24Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4804" xml:space="preserve">[[Category:Tips]]
There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying, or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one, or just want some more in it.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@yahoo.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[su_pyrow@yahoo.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finaly, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes. Try it out, and see if it grows on you!</text>
    <sha1>843af697c807be5f0b951ebda67d819501a6d04f</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>DHCP Hostname Entry in DNS</title>
  <ns>0</ns>
  <id>78</id>
  <revision>
    <id>100</id>
    <timestamp>2009-06-03T02:04:13Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="814" xml:space="preserve">[[Category:Tips]]

I have a Windows server that runs both the DNS server and DHCP server for my network.  When I added a Slackware box, I needed the Windows server to update DNS when the slack box obtained a DHCP lease.  Windows was already setup to do this, but the default slack install didn't send the correct information for the Windows DHCP server to setup the DNS A record.  Here is what I did to get slack to work:

First, slack uses ''dhcpcd'' for a dhcp client.  Looking through the options and testing revealed that all I needed to do was send a:

&lt;pre&gt;-h [hostname]&lt;/pre&gt;

with the dhcpcd command.  In order to get slack to do this, I had to edit:

&lt;pre&gt;/etc/rc.d/rc.inet1.conf&lt;/pre&gt;

and set:

&lt;pre&gt;DHCP_HOSTNAME[0]=[hostname]&lt;/pre&gt;

then:

&lt;pre&gt;/etc/rc.d/rc.inet1 restart&lt;/pre&gt;

and everything worked!</text>
    <sha1>ee1a613175808459ce24acdbcf57e86fc4557dac</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>PPPoE</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>101</id>
    <timestamp>2009-06-03T02:04:54Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="527" xml:space="preserve">[[Category:Tutorials]]

== Setting Up PPPoE ==

As root, run '''pppoe-setup'''. Answer the questions.

'''GOTCHA:''' on the last question, answer ''1 STAND ALONE''.


== Connecting With PPPoE ==

As root, run '''pppoe-start'''.


You should now be connected.


PROBLEM: It reports connected but, I can't get to the internet.

FIX: It's probably screwed up your routing table.
::route del default
::route ppp0  &lt;---make note of the Destination IP
::route add default gw ''destination ip''
Your connection should be working now.</text>
    <sha1>a275add12a59e1e33e2a180e0b8bf36ee7f4ef1c</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>PPPoE - Multiple Connections</title>
  <ns>0</ns>
  <id>80</id>
  <revision>
    <id>102</id>
    <timestamp>2009-06-03T02:05:29Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1614" xml:space="preserve">[[Category:Tutorials]]
== How to setup multiple PPPoE connections ==

1) Install multiple network devices (ethernet cards).
: (you can probably do this with one and use eth0:0, eth0:1, etcetera but, it's a bad idea).

2) Make note of each device's MAC address.

3) Make sure the correct interface is assigned to the correct network card.
: Edit &lt;code&gt;/etc/udev/rules.d/70-persistent-net.rules&lt;/code&gt; file so that the MAC address of each card matches the interface you want.  You must do this so the correct pppoe connection connects to the correct modem.

4) Run &lt;code&gt;pppoe-setup&lt;/code&gt; and set up the connection for connection #1.

5) &lt;code&gt;mv /etc/ppp/pppoe.conf /etc/pppoe-connection1.conf&lt;/code&gt;

6) Run &lt;code&gt;pppoe-setup&lt;/code&gt; and set up the connection for connection #2.

7) &lt;code&gt;mv /etc/ppp/pppoe.conf /etc/pppoe-connection2.conf&lt;/code&gt;

8) Repeat steps 6 &amp; 7 for each of the remaining DSL connections.

-setup is complete-


== How to start the connections ==

1) Run &lt;code&gt;pppoe-start /etc/ppp/pppoe-connection1.conf&lt;/code&gt;

2) Run &lt;code&gt;pppoe-start /etc/ppp/pppoe-connection2.conf&lt;/code&gt;

3) Repeat step 2 for all remaining connections.

At this point, you should have ppp0, ppp1 and etc. ppp connections.  Your routing table ''may'' be trashed at this point, you can clear it and use one as the default route by:
:: route del default
:: route add default gw ''ip_address_of_one_of_your_pppoe_connections''

NOTE: The above will set ONE connection as the default, you must adjust your routing to suit your needs from this point on.

== How to setup routing and/or weighted routing ==

Too be added...</text>
    <sha1>0576f2bc742939ee6e6bc7ee9ccaa506733fe130</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>DVB</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>103</id>
    <timestamp>2009-06-03T02:05:59Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9973" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps
Eventually, my SlackBuild will be hosted here http://slackbuilds.rlworkman.net/CONTRIB/linuxtv-dvb-apps/ (thanks to robw810).

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>32696d3ab7ed73d7fdcadd5931d45019269522af</sha1>
  </revision>
</page>
<page arvcontinue="20090529002128|51">
  <title>Dadexter iptables</title>
  <ns>0</ns>
  <id>82</id>
  <revision>
    <id>104</id>
    <timestamp>2009-06-03T02:07:25Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2628" xml:space="preserve">* Script is based on another one I got here
* allows connections to port 443 for web services
* allows connections to port 8080 for ssh access
* allows connections to port 8000 and 2323 for misc services (usually off anyway)


    #!/bin/sh
    
    # This is a very basic LAN NAT script, allowing only SSH to the firewall from
    # the external interface, allowing all outbound LAN traffic, and allowing only
    # established/related traffic back into the LAN.
    #
    # eth1 = external NIC (ISP)
    # eth0 = internal NIC (LAN)
    #
    # allows connections to port 443 for web services
    # allows connections to port 8080 for ssh access
    # allows connections to port 2323 and 8000 for internal forwarding, and shoutcast
    
    ipt=/usr/sbin/iptables
    extip=66.130.x.x # replace with your EXTERNAL IP - eth1
    lan=192.168.100.0/25 # your LAN CIDR range - eth0
    
    # start firewall
    start_firewall() {
    
      echo "Enabling IP forwarding."
      echo 1 &gt; /proc/sys/net/ipv4/ip_forward
    
      echo "Enabling iptables firewall."
      # default policies
      $ipt -P INPUT DROP
      $ipt -P FORWARD DROP
    
      # NAT
      $ipt -t nat -A POSTROUTING -o eth1 -j SNAT --to-source $extip
    
      # INPUT chain
      $ipt -A INPUT -i lo -j ACCEPT
      $ipt -A INPUT -i eth0 -s $lan -j ACCEPT
      $ipt -A INPUT -i eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT
      $ipt -A INPUT -p tcp --destination-port 8080 -j ACCEPT
      $ipt -A INPUT -p tcp --destination-port 443 -j ACCEPT
      $ipt -A INPUT -p tcp --destination-port 8000 -j ACCEPT
      $ipt -A INPUT -p tcp --destination-port 2323 -j ACCEPT
    
      # FORWARD chain
      $ipt -A FORWARD -i eth0 -s $lan -j ACCEPT
      $ipt -A FORWARD -i eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT
    
    }
    
    # stop firewall
    stop_firewall() {
    
      $ipt -P INPUT DROP
      $ipt -P OUTPUT DROP
      $ipt -P FORWARD DROP
      # allow internal traffic
      $ipt -A INPUT -i eth0 -j ACCEPT
      $ipt -A OUTPUT -o eth0 -j ACCEPT
    
    }
    
    # flushing, removing and zeroing tables
    reset_firewall() {
    
      chains=`cat /proc/net/ip_tables_names`
      for i in $chains; do
        $debug $ipt -t $i -F
        $debug $ipt -t $i -X
        $debug $ipt -t $i -Z
      done
    
    }
    
    case "$1" in
    
      start|restart|reload)
        reset_firewall
        start_firewall
        ;;
      stop)
        reset_firewall
        stop_firewall
        ;;
      *)
        echo "Usage: $0 {start|stop|restart|reload}";
        exit 1
        ;;
    
    esac
    

[[Category:Security]]</text>
    <sha1>b31f9e4925b7f6353e11aeeebbfbf114bbe381b0</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Directory Permissions Defaults</title>
  <ns>0</ns>
  <id>83</id>
  <revision>
    <id>105</id>
    <timestamp>2009-06-03T02:10:00Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3057" xml:space="preserve">[[Category:Tutorials]]
= Problem: Sharing Directories =

My wife and I keep our pictures of our kids under a shared directory
called /home/shared.  We download them with Digikam and sometimes edit 
them to send out to relatives.  The problem was this: if I download the
pictures off the camera, then Megan can't edit them or read them.  We
also had problems with shared files (e.g., our accounting spreadsheets)
that I would create and she would modify, or vice versa.

= Solution: ACL =

To set, in effect, default file-creation masks, you can use [[ACL]] (access
control lists).  The user commands you need to set up [[ACL]] are
getfacl(1) and setfacl(1).

== Edit /etc/fstab ==

Edit the fourth field of the fstab entry of the partition you want
to use ACL on.  In this case, it was /dev/sda6  on /home:

&lt;pre&gt;
/dev/sda6  /home  ext3	   defaults,acl 1   1
&lt;/pre&gt;

adding "acl" to the list of permissions.  Without doing this, you'll
get

&lt;pre&gt;
setfacl: /mnt/backup Operation not supported
&lt;/pre&gt;

Then remount the partition: since I was doing this on /home, I
rebooted (mount -a did not work).

== ACL Commands ==

getfacl(1) shows you the current ACL status of a file:

&lt;pre&gt;
 
/media/multimedia: Zshell&gt; getfacl /home                                       
getfacl: Removing leading '/' from absolute path names
# file: home
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
&lt;/pre&gt;

Once the partitions are properly set up (that was the easy part),
enter the setfacl(1) commands:

&lt;pre&gt;
sudo setfacl --recursive -dm g:users:rwx /home/shared
&lt;/pre&gt;

--recursive was important so that each directory beneath /home/shared
inherits the default mask.

Now getfacl(1) gives me this:

&lt;pre&gt;
/media/multimedia: Zshell&gt; getfacl /home/shared
getfacl: Removing leading '/' from absolute path names
# file: home/shared
# owner: joel
# group: users
user::rwx
group::rwx
other::r-x
default:user::rwx
default:group::rwx
default:group:users:rwx
default:mask::rwx
default:other::r-x
&lt;/pre&gt;

And when creating a file:

&lt;pre&gt;
/media/multimedia: Zshell&gt; cd /home/shared
/home/shared: Zshell&gt; touch my_self
/home/shared: Zshell&gt; ls -l my_self
-rw-rw-r--+ 1 joel users 0 2008-04-06 14:36 my_self
&lt;/pre&gt;

The desired outcome!

Note: this did what I wanted, but it's just a beginning.  Read the
setfacl(1) and getfacl(1) man pages for the full story.

= Official Package Data =
&lt;pre&gt;
PACKAGE NAME:     acl-2.2.39_1-i486-2
COMPRESSED PACKAGE SIZE:     139 K
UNCOMPRESSED PACKAGE SIZE:     350 K
PACKAGE LOCATION: ./acl-2.2.39_1-i486-2.tgz
PACKAGE DESCRIPTION:
acl: acl (tools for using POSIX Access Control Lists)
acl:
acl: This package contains a set of tools and libraries for manipulating
acl: POSIX Access Control Lists.  POSIX Access Control Lists (defined in
acl: POSIX 1003.1e draft standard 17) are used to define more fine-grained
acl: discretionary access rights for files and directories.
acl:
acl:
acl:
acl:
acl:
&lt;/pre&gt;
in slackware/a[http://packages.slackware.it/search.php?v=12.0&amp;t=1&amp;q=acl]
[[User:Trashbird1240|Trashbird1240]] 14:49, 6 April 2008 (EDT)</text>
    <sha1>afd8f8e143128e4fb28df169b200853700888389</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Disable dmix for alsa</title>
  <ns>0</ns>
  <id>84</id>
  <revision>
    <id>106</id>
    <timestamp>2009-06-03T02:10:47Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="351" xml:space="preserve">[[Category:Tips]]

Open your favourite text editor and create the file "~/.asoundrc" for custom user configuration or "/etc/asound.conf" for global system configuration and write the following in it:&lt;br&gt;

&lt;font face=courier&gt;pcm.!default {&lt;br&gt;
type plug&lt;br&gt;
slave.pcm hw&lt;br&gt;
}&lt;br&gt;
&lt;/font&gt;

taken from: http://www.pegasos.org/index.php?name=FAQ&amp;id_cat=5</text>
    <sha1>8074646868237faeee3fccd80f3ddfa701233d6b</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Editors</title>
  <ns>0</ns>
  <id>85</id>
  <revision>
    <id>107</id>
    <timestamp>2009-06-03T02:12:08Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="698" xml:space="preserve">[[Category:Information]]

One late night, it came to our attention (a bunch of slackers) that Slackware comes with a long list of text editors... After discussing it, a list was made... so.

The following editors are included in Slackware:

Command Line/Text

* Joe
* Vi (elvis)
* Vim
* Emacs
* Jove
* Jed
* Pico (from pine)
* Ed
* Nano

X11
* Kwrite
* xedit (xorg)
* gvim
* Emacs
* kedit
* kate.

Other editors that may be useful to Slackware users, such as programmers, are:

Command Line
* RHIDE (with SETedit for dual-display debugging)
* SETedit

X11
* RHIDE
* SETedit
* TexMacs (such as for mathematics writing.)
* Xemacs

If you know more that we have forgotten, please add them to the list.</text>
    <sha1>7d1383d88a2883d3174d6cd77b1504e1b3742e4d</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>EeePC</title>
  <ns>0</ns>
  <id>86</id>
  <revision>
    <id>108</id>
    <timestamp>2009-06-03T02:12:44Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4865" xml:space="preserve">[[Category:Hardware]]
== Kernel ==
=== 2.6.24.4 ===
This is the default kernel that comes with Xandros. It is patched to work with a few things. It's ugly and some of the modules don't work correctly when the kernel is transplanted into Slackware.

The source is available from Asus.

=== 2.6.26.3 ===
As of writing, 2.6.26.3 is the latest stable kernel.

The acpi functionality has been merged into the kernel. but the ethernet and wireless require patching / external code to work

=== 2.6.27rc5 ===
As of writing this is still in testing.

The ethernet patch is now in-kernel, not requiring a patch.  The wireless still requires external code.

== 701 ==
===Wireless===
The 701 uses the Atheros chipset.  Use madwifi-hal-0.10.5.6.

*http://madwifi.org/ticket/1192
*http://wiki.eeeuser.com/ubuntu?s=madwifi#wireless_internet_using_native_madwifi_drivers

== 901 ==
===Network===
The network card uses the atl1e module, which requires a patch for the 2.6.26.3 kernel.  as of writing it is slated to be merged into the 2.6.27 kernel.

http://chopp.homelinux.com/EeePC/0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch

&lt;pre&gt;cd /usr/src/linux-2.6.26.3/
patch -p1 &lt; 0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch&lt;/pre&gt;

The following instructions have been tested (and work) on a fresh installation of Slackware 12.1 on the EEE 901 running the generic kernel 2.26.24-5-smp:

http://www.patch-village.com/2008/oct/23/installing-ubuntu-804-server-asus-p5q/

The kernel source code was installed from the second installation disk (in directory 'k').

===Wireless===
The wireless uses the rt2860sta module, an open source module from ralink.com. The source code can be downloaded from here:

http://www.ralinktech.com/ralink/Home/Support/Linux.html

Compiling is straightforward in Slackware 12.1  (see instructions below).    It does however require patching to work with the 2.6.26.3 kernel.

http://chopp.homelinux.com/EeePC/rt2860sta-patched.tar.gz

There are some patches which need to be applied to this source both to get it to work, and to modify the code to the 2.6.26 way of using network devices, namely dev_nd-&gt;net is now dev_net(dev).

The source above has the patches applied and the code fixed to work with 2.6.26.3

It should work with WPA, but I haven't tested it.

&lt;pre&gt;
tar -xzf rt2860sta-patched.tar.gz
cd 2008_0708_RT2860_Linux_STA_v1.7.0.0
make
make install
modprobe rt2860sta
&lt;/pre&gt;

===Sound===
Front Mic does not work out of the box with Slackware 12.1.  Compiling Alsa driver 1.0.18 solves this problem.  However, doing this seems to remove the USB sound driver (copying back snd-usb-audio.ko resolves it).  Be warned that other sound modules are missing after this procedure.    This is a useful link:

http://wiki.debian.org/DebianEeePC/HowTo/Sound

===ACPI===
The acpi extras require the eeepc_laptop module, kernel config is CONFIG_EEEPC_LAPTOP.
In make menuconfig, it is under device drivers -&gt; misc devices, near the bottom.

You need to configure /etc/acpi to make acpi act on events. By default nothing happens.

/etc/acpi/events/hotkey
&lt;pre&gt;
event=hotkey ATKD .*
action=/etc/acpi/hotkey.sh %e
&lt;/pre&gt;
/etc/acpi/hotkey.sh
&lt;pre&gt;
#!/bin/sh

case $3 in
    #Fn+F2
        #Wireless/Bluetooth button
    #Fn+F7
    00000013)
        #Mute button
        amixer set Master toggle
    ;;
    #Fn+F8
    00000014)
        #Volume Down
        amixer set Master 10%-
    ;;
    #Fn+F9
    00000015)
        #Volume Up
        amixer set Master 10%+
    ;;
esac
&lt;/pre&gt;

===Camera===
The camera uses uvcvideo module:
http://www.slackware.com/~alien/slackbuilds/linux-uvc/
{| border="1"
|-
! module
! used by
|-
| uvcvideo
|
|-
| compat_ioctl32
| uvcvideo
|-
| videodev
| uvcvideo
|-
| v4l1_compat
| uvcvideo,videodev
|-
| usbcore
| uvcvideo
|}

===X===
Slack 12.1 uses the same xorg version as the xandros that comes with the 901 linux eee currently.

====xorg.conf====
For the 901, for basic functionality, no configuration of X is required (no xorg.conf).  The intel video driver from the 'x' directory of disc 1 is needed.

This xorg.conf is a copy of the xandros one with a few changes.  It allows you to scroll using two fingers and dragging, and middle click by tapping with two fingers.

[[EeePC/xorg.conf|xorg.conf]]

====Touchpad====
http://rlworkman.net/pkgs/
Grab the xf86-input-synaptics package.

Need synaptics for the touchpad.

====Battery Display====
gkrellm is a nice little program that can be made to show battery life. It comes with slack 12.1

====Wireless Configuration====
Wicd works nicely to make connecting to wireless networks easy.

http://rlworkman.net/pkgs/
Grab the Wicd package.

==Files==
*http://chopp.homelinux.com/EeePC/
*http://www.ksandro.info/
*http://www.ksandro.info/rt2860sta-patched.tar.gz
*http://www.ksandro.info/0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch
*http://rlworkman.net/pkgs/</text>
    <sha1>245c2d44ff96d26b654512186ca1e2e1092364f1</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>EeePC/xorg.conf</title>
  <ns>0</ns>
  <id>87</id>
  <revision>
    <id>109</id>
    <timestamp>2009-06-03T02:13:20Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3430" xml:space="preserve">[[Category:Hardware]]
[[EeePC|Back to Main Article]]
&lt;pre&gt;Section "ServerLayout"
	Identifier     "Slackware"
	Screen      0  "Screen1"
	InputDevice    "keyboard"
	InputDevice    "mouse"
	InputDevice    "synaptics" # make sure to have the synaptics driver
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules" # these paths had to be fixed
	FontPath     "/usr/share/fonts/misc"
	FontPath     "/usr/share/fonts/Type1"
	FontPath     "/usr/share/fonts/75dpi"
	FontPath     "/usr/X11R6/lib/X11/fonts/Type1"
EndSection

Section "Module"
	Load  "glx"
	Load  "dri"
	Load  "extmod"
	Load  "synaptics"
EndSection

Section "ServerFlags"
	Option		"AllowMouseOpenFail"
	Option		"BlankTime" "1"            # power saving, but kinda annoying, minutes.
	Option		"DontVTSwitch"	"false"    # turn this off.
	Option		"AIGLX"   "false"
EndSection

Section "InputDevice"
	Identifier  "keyboard"
	Driver      "kbd"
	Option	    "CoreKeyboard"
	Option	    "XkbRules" "xorg"
	Option      "XkbModel" "pc105"
	Option      "XkbLayout" "us"
	Option      "XkbVariant" "basic"
EndSection

Section "InputDevice"
	Identifier  "mouse"
	Driver      "mouse"
	Option	    "Device" "/dev/input/mice"
	Option	    "Protocol" "IMPS/2"
	Option	    "Emulate3Buttons" "yes"         
	Option	    "ZAxisMapping" "4 5"
	Option	    "CorePointer"
EndSection

Section "InputDevice"
	Identifier  "synaptics"
	Driver      "synaptics"
	Option      "Device"           "/dev/psaux"
	Option      "Protocol"         "auto-dev"
	Option      "LeftEdge"         "1400"
	Option      "RightEdge"        "5900"
	Option      "TopEdge"          "1400"
	Option      "BottomEdge"       "4500"
	Option      "PalmDetect"       "0"
	Option      "SHMConfig"        "true"
	Option      "SendCoreEvents"   "yes"
	Option      "HorizScrollDelta" "0"
	Option      "VertScrollDelta"  "155"
	Option      "RBCornerButton"   "0"
	Option      "RTCornerButton"   "0"
	Option      "TapButton2"          "0"
	Option      "MinSpeed"         "0.095"
	Option      "MaxSpeed"         "0.38"
	Option      "VertTwoFingerScroll" "1"
	Option      "VertEdgeScroll"      "0"
	Option      "HorizEdgeScroll"     "0"
EndSection

Section "Monitor"
	Identifier   "Monitor1"
	VendorName   "ASUS"
	ModelName    "eeePC P701"
	Modeline     "800x480"  29.58  800 816 896 992  480 481 484 497  -HSync +Vsync # 60 Hz
	Modeline     "1024x600"  48.96  1024 1064 1168 1312  600 601 604 622  -HSync +Vsync
EndSection

Section "Monitor"
	Identifier   "TV"
	VendorName   "ASUS"
	ModelName    "eeePC P701"
	Option       "Ignore" "true"
EndSection

Section "Device"
	Identifier  "Device1"
	Driver      "intel"
	VendorName  "Intel Corporation"
	BoardName   "Mobile 915GM/GMS/910GML Express Graphics Controller"
	BusID       "PCI:0:2:0"
	Option      "Monitor-VGA"  "Monitor1"
	Option      "Monitor-LVDS" "Monitor1"
	Option      "Monitor-TV"   "TV"
	Option      "XAANoOffScreenPixmaps" "true"
	Option      "AccelMethod" "XAA"
EndSection

Section "Screen"
	Identifier "Screen1"
	Device     "Device1"
	DefaultDepth     16
	SubSection "Display"
		Depth     8
		Virtual  1024 768
	EndSubSection
	SubSection "Display"
		Depth     15
		Virtual  1024 768
	EndSubSection
	SubSection "Display"
		Depth     16
		Virtual  1024 768
	EndSubSection
	SubSection "Display"
		Depth     24
		Virtual  1024 768
	EndSubSection
EndSection

Section "DRI"
	Mode         0666
EndSection

Section "Extensions"
	Option	    "Composite" "Disable"
EndSection
&lt;/pre&gt;</text>
    <sha1>dfecaa24092417cfe759a8aebece58ad4e3120a2</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Emacs from CVS</title>
  <ns>0</ns>
  <id>88</id>
  <revision>
    <id>110</id>
    <timestamp>2009-06-03T02:14:17Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1210" xml:space="preserve">[[Category:Tutorials]]
The development version of GNU Emacs offers several features over the official Slackware release (Emacs 22), for example Unicode support, multi-TTY, multiple X client frames and font rendering with Xft.  [http://www.unc.edu/~adamsonj/software/emacs-cvs/ Here] is a  SlackBuild that creates a package for Emacs 23.  

Note that the SlackBuild pulls from the CVS server on Savannah, so you do not need to pull the repository first.  If you do, put it in the indicated local cvs directory so that the script will do a "cvs update".

== Installation ==
You should 

&lt;code&gt;
removepkg emacs
&lt;/code&gt;

before installing the Emacs 23 package, which will be installed as package emacs-cvs.

== Automatic Updates ==
I put the following script into /etc/cron.weekly and each Monday I get a newly-updated version of Emacs.  I always keep the old package in case there is any problem with the new version.

&lt;pre&gt;
#! /bin/sh
cd &lt;full path to parent directory&gt;
tar zxvf emacs-cvs.tar.gz
cd emacs-cvs
./emacs-cvs.SlackBuild |mail &lt;yourself&gt;
&lt;/pre&gt;

== Problems? Comments? ==

I have had no problems with the current script.  If you notice anything, please let me know.[[User:Trashbird1240|Trashbird1240]]</text>
    <sha1>98f5435d0c3e90bf9d7a47f3a93f3b7c902dbbef</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Embedded perl</title>
  <ns>0</ns>
  <id>89</id>
  <revision>
    <id>111</id>
    <timestamp>2009-06-03T02:15:10Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2204" xml:space="preserve">[[Category:Tutorials]]
==How to Install Embedded Perl on Slackware 12.0==

First, I installed mod_perl: [[mod_perl|Installing Mod_Perl]].

Then, I used [[cpan|cpan]] to install Embed Perl.  I ran "perl -MCPAN -e shell" and at the prompt typed "install Embperl".  This prompted me for some dependencies, I had to do "install LWP" and then try "install Embperl" again.  Eventually it worked.

I added these lines to the section for my virtual host in /etc/httpd/extra/httpd-vhost.conf (they could also be added in the main httpd.conf to apply to the whole server if desired):
&lt;pre&gt;
#    PerlModule HTML::Embperl
    PerlModule Embperl
    &lt;Directory /home/rgr/public_html/embperl&gt;
        SetHandler perl-script
        Options ExecCGI
#       PerlHandler HTML::Embperl::handler
        PerlHandler Embperl::handler
    &lt;/Directory&gt;
&lt;/pre&gt;

Note the parts that are commented out -- whose were in an online example I found, but they resulted in the "500 internal server error" message.  I could see the detailed message in the apache error log, and perl was looking for HTML/Embperl.pm when it should have been looking for Embperl.pm.

After that I set up an example file (see the tutorial below) and successfully tested it.

==Tutorial on Use==

http://perl.apache.org/embperl/pod/intro/Intro.-page-3-.htm

Here is an example file I created in /home/rgr/public_html/embperl/test.pl (it actually should be in which ever directory you set to be handled via embperl in the httpd.conf file or httpd-vhosts.conf file):

&lt;pre&gt;
&lt;html&gt;
&lt;body&gt;
First line.&lt;br&gt;
[- $a = 5 -] Some stuff! [- $b = 6 if ($a == 5) -]&lt;br&gt;
Now for some output:&lt;br&gt;
[+ $a +]  [+ $array[$b] +] [+ "A is $a" +]
&lt;/body&gt;
&lt;html&gt;
&lt;/pre&gt;

And here is the output of http://localhost/embperl/test.html:

&lt;pre&gt;
First line.
Some stuff!
Now for some output:
5 A is 5
&lt;/pre&gt;

Note that the code with [-  -] is just run.  The code with [+  +] is run, and the results are used to replace that part of the html file.  You can also use [!  !] which is for code that should only be run once, such as function definitions.  The perldoc documentation or the apache page linked above has more complete explanations and tutorials: 
http://perl.apache.org/embperl/</text>
    <sha1>fb19c4a907c951405b51f550da04d2a12d062393</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Faster Console</title>
  <ns>0</ns>
  <id>90</id>
  <revision>
    <id>112</id>
    <timestamp>2009-06-03T02:15:49Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="788" xml:space="preserve">[[Category:Tips]]

With the Frame Buffer enabled, scrolling large amounts of text (e.g. dmesg) and other drawing can be very slow. Give these options to your kernel at boot and scrolling will be much faster.

 video=vesafb:ywrap,mtrr:3

Brief explanation of options:

 vesafb   use the VESA Frame Buffer
 ywrap    enable display panning using the VESA protected mode interface 
 mtrr:3   use Memory Type Range Registers in write-combining mode

You may have to use &lt;code&gt;ypan&lt;/code&gt; or another number with &lt;code&gt;mtrr:&lt;/code&gt; depending on your video hardware. See &lt;code&gt;/usr/src/linux/Documentation/fb/vesafb.txt&lt;/code&gt; for more details.

If it works well, this can be added to your lilo.conf in the append line:

 append = "video=vesafb:ywrap,mtrr:3"

Run &lt;code&gt;lilo -v&lt;/code&gt; and reboot.</text>
    <sha1>10bc668ea0e092ef5429bb5d141121ca3685914e</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Firewall-rworkman</title>
  <ns>0</ns>
  <id>91</id>
  <revision>
    <id>113</id>
    <timestamp>2009-06-03T02:16:25Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="156" xml:space="preserve">Rather than having to update this at two different places, my firewall scripts are housed here:
http://rlworkman.net/conf/firewall/


[[Category:Security]]</text>
    <sha1>019f16de9e293319ff623610a772c88dcfbf8bb4</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Forced Fsck</title>
  <ns>0</ns>
  <id>92</id>
  <revision>
    <id>114</id>
    <timestamp>2009-06-03T02:16:58Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2912" xml:space="preserve">[[Category:Tips]]

A Forced Fsck (forced file check) happens on boot up due to one of three things:

:1) The system was not cleanly shutdown previously (you just turned off the power) and the file system was not cleanly un-mounted.

:2) The maximum number of sucessive re-boots (re-mounts ([[Mount Count|mount count]])) between fsck checks has been reached (you have reached [[Maximum Mount Count]]).

:3) A period of time has passed between fscks that exceed the filesystem's last checked criteria.

==Manually Forcing a Forced Fsck==

To force a check on the next boot, simply create the file '/etc/forcefsck' and reboot:
:&lt;code&gt;touch /etc/forcefsck&lt;/code&gt;


==Bypassing A Forced Fsck==

&lt;b&gt;METHOD 1: Increase the Mount Count/Last-checked time span-&lt;/b&gt;&lt;br&gt;
The only way to bypass a Forced Fsck is to boot the machine from another boot medium (e.g. a boot CD) and use &lt;code&gt;tune2fs&lt;/code&gt; to increase the Maximum Mount Count or the Last-checked Time span.

To increase the Maximum Mount Count: &lt;code&gt;tune2fs -c &lt;i&gt;new_mount_count filesystem&lt;/i&gt;&lt;/code&gt;&lt;br&gt;
EXAMPLE: &lt;code&gt;tune2fs -c 50 /dev/hda1&lt;/code&gt; - This will cause a fsck after 50 re-mounts.

To increase the Last-checked Time span: &lt;code&gt;tune2fs -i &lt;i&gt;new_time_span filesystem&lt;/i&gt;&lt;/code&gt;&lt;br&gt;
EXAMPLE: &lt;code&gt;tune2fs -i 3m /dev/hda1&lt;/code&gt; - This will cause a fsck after 3 months.

&lt;b&gt;GOTCHA:&lt;/b&gt; If you are running a RAID Array, make sure you load a kernel image that supports RAID when booting! See the RAID Array tips.


&lt;b&gt;METHOD 2: Manually run fsck-&lt;/b&gt;&lt;br&gt;
See &lt;i&gt;Bypassing A Hung Forced Fsck&lt;/i&gt; instructions below.


==Bypassing A Hung Forced Fsck==
Sometimes, a forced fsck will occur and may not complete.  It may hang or just keep starting over.  To (down and dirty) fix this, boot the machine from a bootable disk (3.5" or CD), DO NOT mount the unchecked filesystem and manually run fsck.  You may have to run any one of three modes to complete the check:&lt;br&gt;
::&lt;code&gt;fsck -f &lt;i&gt;filesystem&lt;/i&gt;&lt;/code&gt; - Force checking even if the file system seems clean.&lt;br&gt;
::&lt;code&gt;fsck -c &lt;i&gt;filesystem&lt;/i&gt;&lt;/code&gt; - This option causes e2fsck to run the badblocks program to find any blocks which are bad on the filesystem, and then marks them as bad by adding them to the bad block inode. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test.&lt;br&gt;
::&lt;code&gt;fsck -p &lt;i&gt;filesystem&lt;/i&gt;&lt;/code&gt; - Automatically repair ("preen") the file system without any questions.&lt;br&gt;
:::&lt;b&gt;NOTE: &lt;code&gt;&lt;i&gt;filesystem&lt;/i&gt;&lt;/code&gt; = boot partition (e.g. &lt;code&gt;/dev/hda1&lt;/code&gt;)&lt;/b&gt;

&lt;b&gt;GOTCHA:&lt;/b&gt; If you are running a RAID Array, make sure you load a kernel image that supports RAID when booting! See the [[RAID_Array_%28Hardware%29|RAID Array tips]].

After a successful completion of anyone of the above, your filesystem's [[Mount Count|mount count]] will be reset to zero and you should be able to boot normally again.</text>
    <sha1>de9986cd2e124d181576f2c796b8df71435d0bfb</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Fred87's Script</title>
  <ns>0</ns>
  <id>93</id>
  <revision>
    <id>115</id>
    <timestamp>2009-06-03T02:17:36Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1671" xml:space="preserve">* Allows incoming SSH
* Detects and blocks syn floods
* Detects spoofed local packets
* Makes sure "NEW" tcp packets have the syn flag set
* Drops packets with both syn and fin set
* Generated with [http://www.fredemmott.co.uk/index.php?page=kitg KIptablesGenerator]

 #!/bin/sh
 # Generated by KIptablesGenerator
 # Copyright (c) 2004 Fred Emmott &lt;mail@fredemmott.co.uk&gt;
 # See KIptablesGenerator for license information.
 # You probably want to make this a startup script, eg on
 # slackware you probably want to save this as /etc/rc.d/rc.firewall
 IPTABLES=/usr/sbin/iptables
 $IPTABLES -P INPUT DROP
 $IPTABLES -A INPUT -i lo -j ACCEPT
 $IPTABLES -A INPUT ! -i lo -d 127.0.0.0/8 -j DROP
 $IPTABLES -N Flood-Scan
 $IPTABLES -A INPUT -p tcp -m tcp --syn -j Flood-Scan
 $IPTABLES -A Flood-Scan -m limit --limit 1/s --limit-burst 20 -j RETURN
 $IPTABLES -A Flood-Scan -j LOG --log-prefix "OVER-LIMIT: "
 $IPTABLES -A Flood-Scan -j DROP
 $IPTABLES -A INPUT -p tcp -m tcp ! --syn -m conntrack --ctstate NEW -j DROP
 $IPTABLES -A INPUT -p tcp -m tcp --tcp-flags SYN,FIN SYN,FIN -j DROP
 $IPTABLES -A INPUT -p tcp -m conntrack --ctstate ESTABLISHED -j ACCEPT
 $IPTABLES -A INPUT -p tcp -m conntrack --ctstate RELATED -j ACCEPT
 $IPTABLES -A INPUT -p udp -m conntrack --ctstate ESTABLISHED -j ACCEPT
 $IPTABLES -A INPUT -p icmp -m icmp --icmp-type parameter-problem -j ACCEPT
 $IPTABLES -A INPUT -p icmp -m icmp --icmp-type time-exceeded -j ACCEPT
 $IPTABLES -A INPUT -p icmp -m icmp --icmp-type echo-reply -j ACCEPT
 $IPTABLES -A INPUT -p icmp -m icmp --icmp-type destination-unreachable -j ACCEPT
 $IPTABLES -A INPUT -p tcp -m tcp --dport 22 -j ACCEPT

[[Category:Security]]</text>
    <sha1>b2c891127d0c6c2f3d85d5c993e0b9fdbbe222b6</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Fstab</title>
  <ns>0</ns>
  <id>94</id>
  <revision>
    <id>116</id>
    <timestamp>2009-06-03T02:18:32Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3734" xml:space="preserve">The /etc/fstab file tells the system how and where to mount filesystems by default.

==Syntax==
The syntax of the file is this:

&lt;table cellspacing="10"&gt;
&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;MAN PAGE-ese:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;FS_SPEC&lt;/td&gt;
&lt;td align="center"&gt;FS_FILE&lt;/td&gt;
&lt;td align="center"&gt;FS_VFSTYPE&lt;/td&gt;
&lt;td align="center"&gt;FS_MNTOPS&lt;/td&gt;
&lt;td align="center"&gt;FS_FREQ&lt;/td&gt;
&lt;td align="center"&gt;FS_PASSNO&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;IN ENGLISH:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;DEVICE&lt;/td&gt;
&lt;td align="center"&gt;MOUNT_POINT&lt;/td&gt;
&lt;td align="center"&gt;FILESYSTEM&lt;/td&gt;
&lt;td align="center"&gt;OPTIONS&lt;/td&gt;
&lt;td align="center"&gt;DUMP&lt;/td&gt;
&lt;td align="center"&gt;FSCK_ORDER&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;EXAMPLE:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;/dev/hdb1&lt;/td&gt;
&lt;td align="center"&gt;/mnt/windows&lt;/td&gt;
&lt;td align="center"&gt;vfat&lt;/td&gt;
&lt;td align="center"&gt;default&lt;/td&gt;
&lt;td align="center"&gt;0&lt;/td&gt;
&lt;td align="center"&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;

==Field Descriptions==
FS_SPEC (DEVICE) - the device or remote filesystem to be mounted.

FS_FILE (MOUNT_POINT) - the mount point for the filesystem. &lt;i&gt;NOTE: For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces these can be escaped as `\040'.&lt;/i&gt;

FS_VFSTYPE (FILESYSTEM)-  the type of the filesystem. As of Slackware 10.2, the FILE_SYSTEM choices are:
:auto, adfs, affs, autofs, coda, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xfs, xiafs and possibly others.
&lt;i&gt;NOTE: for swap-able and portable devices (e.g. memory sticks and CDROMs), &lt;code&gt;auto&lt;/code&gt; is the best choice because it allows the computer to determine the correct filesystem.&lt;/i&gt;

FS_MNTOPS (OPTION) - the (comma seperated) mount options. See the MOUNT command's MAN PAGE for the options because there are MANY!
The most commonly used options are:&lt;br&gt;
:noauto - do not mount this device/partition automatically on boot-up.
:ro - mount this device/partition READ-ONLY (e.g. CDROM).
:owner - Only allow the owner to mount and un-mount this device/partition.
:users - Allow any user to mount or unmount this device/partition.


FS_FREQ (DUMP) - used for these filesystems by the dump command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. For the most part, this should be "0" (zero).

FS_PASSNO (FSCK_ORDER) - used by the fsck program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

==Benefits Of fstab Entries==
Once you have a device in the fstab, mounting become VERY easy.  Instead of having to:
:&lt;code&gt;mount -t iso9660 /dev/hdb1 /mnt/cdrom&lt;/code&gt;
every time you want to use the CDROM, you can just type:
:&lt;code&gt;mount /mnt/cdrom&lt;/code&gt;
IF you have the entry in your fstab.


==Useful Examples==
CDROM:&lt;br&gt;
:/dev/hdc1 /mnt/cdrom auto noauto,ro,owner,users 0 0

[[USB Memory Stick]]:&lt;br&gt;
:/dev/sda1 /mnt/memstick auto noauto,owner,users 0 0&lt;br&gt;
(make sure to &lt;code&gt;mkdir /mnt/memstick&lt;/code&gt; after changing your /etc/fstab).


Note: For changing who can access the filesystem on NON-Native linux formats see [[Permissions and Umasks]] and [[Windows Partitions]]

[[Category:Tutorials]]</text>
    <sha1>868aa5c1f3711b7a2d7f50761ab86e19ad68d641</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>GNOME</title>
  <ns>0</ns>
  <id>95</id>
  <revision>
    <id>117</id>
    <timestamp>2009-06-03T02:19:24Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2412" xml:space="preserve">As this questions seems to be popping up again and again. The question being either: “''Why was Gnome removed from Slackware''” or “''Why doesn’t Slackware ship with Gnome''”.

In the development cycle of Slackware-10.1 -&gt; 10.2 Patrick Announced that Slackware would drop support for GNOME:

= Announcement in the ChangeLog =

On Sat Mar 26 23:04:41 PST 2005 Patrick Volkerding announced that Gnome gets removed:

&lt;tt&gt;gnome/*: Removed from -current, and turned over to community support and distribution. I'm not going to rehash all the reasons behind this, but it's been under consideration for more than four years. There are already good projects in place to provide Slackware GNOME for those who want it, and these are more complete than what Slackware has shipped in the past. So, if you're looking for GNOME for Slackware -current, I would recommend looking at these two projects for well-built packages that follow a policy of minimal
interference with the base Slackware system:

    http://gware.sf.net

    http://gsb.sf.net

There is also Dropline, of course, which is quite popular. However, due to their policy of adding PAM and replacing large system packages (like the entire X11 system) with their own versions, I can’t give quite the same sort of nod to Dropline. Nevertheless, it remains another choice, and it’s your system, so I will also mention their project:

    http://www.dropline.net/gnome/

Please do not incorrectly interpret any of this as a slight against GNOME itself, which (although it does usually need to be fixed and polished beyond the way it ships from upstream more so than, say, KDE or XFce) is a decent desktop choice. So are a lot of others, but Slackware does not need to ship every choice. GNOME is and always has been a moving target (even the “stable” releases usually aren’t quite ready yet) that really does demand a team to keep up on all the changes (many of which are not always well documented). I fully expect that this move will improve the quality of both Slackware itself, and the quality (and quantity) of the GNOME options available for it.

Folks, this is how open source is supposed to work. Enjoy.&lt;/tt&gt;

= Links =

* http://www.gware.org/ -- GWARE (GNOME for Slackware)
* http://gsb.freerock.org/ -- Freerock GNOME
* http://www.droplinegnome.org/ -- Dropline GNOME
* http://www.slacky.eu/ -- Gnome Slacky

[[Category:Information]]</text>
    <sha1>02ed9f08a1a5bc526aba39b10543c02e27a83591</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Google Earth</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>118</id>
    <timestamp>2009-06-03T02:19:53Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1739" xml:space="preserve">[[Category:Tips]]

You can download Google Earth from http://earth.google.com/

You have to set the .bin file that you download to be executatable, and then run it, to install.

&lt;pre&gt;
chmod a+x GoogleEarthLinux.bin
./GoogleEarthLinux.bin
&lt;/pre&gt;

By default it installs itself in /opt/google-earth/ .  It offers to make a link from /usr/local/bin/googleearth to the right executable, I recommend allowing it to do this.

Once it is done, to run it you just type "googleearth" in an xterm (X must be running).  You can make the appropriate desktop icon or menu item depending on what window manager you are using.

If the splash screen shows up for some amount of time, and then all of X (the entire graphical environment) crashes (if you have graphical login set up, it will give you a login screen again, otherwise you will go back to the console), some people have found this to be solved by downloading the libGL.so library.  It should be put in the /opt/google-earth/ directory:

(as root)
&lt;pre&gt;
cd /opt/google-earth/
wget http://librarian.launchpad.net/7037027/libGL.so.1 -O libGL.so.1
&lt;/pre&gt;

Some places on the web also refer to downloading it from http://www.ground-impact.com/libGL.so.1.2 .  Here are links to a few discussions of the issue:

http://www.linuxquestions.org/questions/slackware-14/google-earth-crashes-x-598569/?s=3ff14bc2cdec277267c5547b7dee84d9
http://forum.mandriva.com/viewtopic.php?t=71691&amp;highlight=googleearth

'''Performance Issue with Google Earth:'''
&lt;pre&gt;
if google earth is slow in slackware Linux, check whether DRI is enabled or not, if Direct Rendering is enabled then
disable "Atmosphere" effect from View menu -&gt; [x] Atmosphere for smoother functioning of the graphics in Google Earth window.
&lt;/pre&gt;</text>
    <sha1>b2ad930a00343e4563141b3261b42c4da4d45198</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>HAL in Slackware 12</title>
  <ns>0</ns>
  <id>97</id>
  <revision>
    <id>119</id>
    <timestamp>2009-06-03T02:20:24Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2470" xml:space="preserve">[[Category:Tutorials]]
== Preface ==
This page was started to provide documentation and examples of the "new" HAL feature in Slackware 12.  Before reading or implementing anything that you've read here, be sure to first read the following two paragraphs from [http://ftp.slackware.pl/pub/slackware/slackware-12.0/CHANGES_AND_HINTS.TXT the CHANGES_AND_HINTS text file]:
 The /dev/cdrom line in /etc/fstab is commented out by default, as it interferes with HAL.
 HAL defaults to on, so if you do not wish to use it, you will need to
 chmod -x /etc/rc.d/rc.hald and uncomment the /dev/cdrom line in /etc/fstab
 
 Note that HAL will honor settings in /etc/fstab if a device is present there, so you could
 technically have removable devices defined in /etc/fstab, but if the fstab settings do not
 allow normal users to mount them (with the "user" or "users" option), then HAL/dbus will
 not allow them to be mounted either. Also note that you will need to run
 "/etc/rc.d/rc.messagebus reload" after adding any users to plugdev, power, or video groups
 so that it re-reads the /etc/group file.

== Enabling HAL for Your Users ==

 First, add your users to the secondary groups: cdrom, plugdev, power
 Second, restart the HAL and messagebus services with the following two commands (as root):
  # /etc/rc.d/rc.messagebus restart
  # /etc/rc.d/rc.hald restart

=== About the /etc/fstab Entry ===
The line that typically mounts the CDROM drive in /etc/fstab is commented out by default. Also, only root can give the command to mount /dev/cdrom by default.  The original line looks something like
 #/dev/cdrom       /mnt/cdrom     auto        noauto,owner,ro     0   0

CHANGES_AND_HINTS suggests that you leave this line commented out in order for HAL to work.  It may be necessary, however, to uncomment this line for certain programs which expect the cdrom device to be mounted to a specific place (games running via WINE come to mind).  To allow this, change the cdrom entry in /etc/fstab to look like
 /dev/cdrom       /mnt/cdrom     auto        noauto,user,owner,ro     0   0

== Using HAL ==
Your users should now be able to take advantage of [[Autofs]], KDE's Storage Media settings and [http://ivman.sourceforge.net/ programs like ivman] in order to mount removable media to the appropriate places.

== Other Reading ==

See rworkman's thread on LinuxQuestions.org about 12.0 and HAL:
http://www.linuxquestions.org/questions/slackware-14/12.0-and-hal-read-this-566862/</text>
    <sha1>034d1b1458b67363ff12721141868cbdc0302438</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>International Language Support</title>
  <ns>0</ns>
  <id>98</id>
  <revision>
    <id>120</id>
    <timestamp>2009-06-03T02:23:26Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4079" xml:space="preserve">[[Category:Tutorials]]
'''This tutorial is not finished yet.  Come back at a later time.'''

Last updated: --[[User:Apeitheo|apeitheo]] 21:58, 10 Apr 2005 (BST)

The aim of this tutorial is to allow you to use Linux with the language of your choice.  I often need to type German characters (ßüöä€„“) on my keyboard, but it took some time to copy the chosen character and paste it where needed.  I could have changed the layout, but I prefer to use the English layout due to programming a lot, and I'm just generally more adapted to this layout. 

With the use of "compose" and "dead" keys you will be able to type foreign characters of your choice, while still preserving your current layout.  The only requirement, which provides definitions for foreign characters, is the glibc-i18n package, which can be obtained from [http://slackware.com/pb/searchpkg.php?v=current&amp;string=glibc-i18n The Slackware package browser] or on your Slackware cd in slackware/l.

== Keyboard Support ==
This section will provide you with information on how to setup your keyboard for foreign characters.  If you wish to use it both outside &amp; inside of X, follow both sections.
=== X11 ===
''-- Speak about xmodmap/xkb, rewrite parts reflecting "compose" keys''

In order to type foreign characters without modifying your current keyboard layout, we will make use of xmodmap and a "dead key" of your choice.  To start, you should locate the corresponding xmodmap.* file that is for your current keyboard layout.  Since I use an English keyboard, mine was found at "/usr/share/xmodmap/xmodmap.us".  Once you've located it, copy it to your user directory and make it hidden, like this:

  cp /usr/share/xmodmap/xmodmap.us-101 /home/joe/.xmodmap

Open this file up for editing with your favorite text editor:

 gedit /home/joe/.xmodmap

Now is a good time to take a look at the long list of "keysyms" which are supported by xmodmap.  This can be found [http://wiki.linuxquestions.org/wiki/List_of_Keysyms_Recognised_by_Xmodmap here].  Locate the special characters that you are missing on your current keyboard layout.  In the .xmodmap file find the keys which you want to be used with the "dead keys."  For example, so that I can use the 'u' key for ü and Ü, I would change:

 keycode 30 = u U udiaeresis Udiaeresis

The first 'u' is what is usually pressed.  The second character, "U" is what is typed when I push the shift key and the 'u'.  The same thing goes for the second part, 'udiaeresis' is typed when I push my right alt key and 'u'.  As you can expect, 'Udiaeresis' is typed when I push the right alt key, the shift key, and the 'u'.  It's that simple.

You may need to assign a key to be the Mode_switch key (which in my case, was the right alt key), or change it if you don't like the current one.  This can be done by changing the specified keycode line to point to "Mode_switch," such as this:

(Before Editing)
 keycode 113 = Alt_R Meta_R
(After Editing)
 keycode 113 = Mode_switch

'''NOTE:''' If you use Gnome or KDE, this next step will not be necessarily unless you manually load them up through ~/.xinitrc.

Once you've finished modifying your custom .xmodmap file, save it, and then open up your ~/.xinitrc file and add the line:

 exec xmodmap ~/.xmodmap

as well as appending an ampersand (&amp;) to the line previous to the last.

For example:

(Before Editing)
 #!/bin/bash
 exec enlightenment
(After Editing)
 #!/bin/bash
 exec enlightenment &amp;
 exec xmodmap ~/.xmodmap

Save this file, type startx, and you're ready to go.

'''NOT FINISHED YET - elaborate on .xmodmap file (Mode_Switch), xev, and xmodmap -pke'''
 
=== Console ===

=== Additional Notes ===

== Application Support ==
This section will provide you with information on how to setup your computer to display applications in the language of your choosing.

''-- Speak about LANG settings''
=== Additional Notes ===

== Conclusion ==

== External Links ==
[http://slackware.com/pb/ The Slackware package browser]

[http://wiki.linuxquestions.org/wiki/List_of_Keysyms_Recognised_by_Xmodmap List of Keysyms]</text>
    <sha1>cd4d59d25607f7896e6a8d06bd5bc051f3e34de7</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Irssi</title>
  <ns>0</ns>
  <id>99</id>
  <revision>
    <id>121</id>
    <timestamp>2009-06-03T02:25:03Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2386" xml:space="preserve">Irssi Quick tutorial - Based on http://www.irssi.org/documentation

== Installation ==
If you did a full install of Slackware, you may already have irssi, and you can skip to the next section of this guide. However, if typing 'irssi' at the command line returns nothing, you will need to install the program. Irssi is located in the 'n' folder of Slackware mirrors - and once you have downloaded it, you only need to run 'installpkg irssi[tab]' as root to install it.

== Usage ==
To start the client, "irssi" is entered from either the console or any xterm.

Connecting is done by the /server command
/server irc.freenode.net , would connect to the freenode server
/connect does the same thing but is used to open a new connection in a new window
/disconnect is to leave that server.

If the nick or handle is already chosen, just issue /nick somenewhandle , this will change to a new name.

Names that are registered on NickServ must be identified by /msg NickServ IDENTIFY &lt;password&gt;
Or you can select window #2 by the alt key and number 2 and enter IDENTIFY &lt;password&gt;.
N.B alt key 0-10 is for  windows 0-10, Alt-q through Alt-o is for 11-19.

To join a channel, issue /j #slackware, that will bring you to the wonderful people on Slackware's official channel on the Freenode IRC network.

Ctrl-X is used to switch between network connections, if you are connected to multiple servers, e.g. irc.freenode.net and another server.

/query and /q are used to initiate private convesationa with people. eg. /query linus would open a private chat window with the user 'linus'.

/set in the first window, shows all the settings, where by help is found by issuing the command. e.g. /help dcc would bring up information on the dcc commmand.

Window management

/WINDOW NEW , splits the screen in half
this new window will have a number assigned to it, to access just type alt 4, if the window is number 4.
/WINDOW CLOSE   , this closes the current window.
/WINDOW BALANCE , this i am constantly using to keep the windows the same size.
/window name hilight, whenever someone types your name in the channel, the line is highlighted in another colour.

Don't forget to run the /save command, so that next time irssi loads, all the windows will be there.

SET term_force_colors ON, is a very useful command, as certain xterms need this to display the colours correctly.


[[Category:Tutorials]]</text>
    <sha1>7742a32bc1484f8443e43b7be996352c254b67b2</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Kernel26Compilation</title>
  <ns>0</ns>
  <id>100</id>
  <revision>
    <id>122</id>
    <timestamp>2009-06-03T02:25:55Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3606" xml:space="preserve">How to build a 2.6.x Kernel on Slackware

Note: Maybe this replaces the 2.6 part of the kernel compile tutorial already here.

==Warning!==
If you work on your kernel and do something wrong you may destroy your system in a way you have to reinstall it. All actions on your own risk! Noone assures that all actions described here are 100% right and work in any case. We are not responsible for damages caused by following this tutorial!

==Prerequisites==

* Get the kernel sources you want from ftp://ftp.de.kernel.org or from a mirror (http://www.kernel.org/mirrors/).
* Make sure you are able to boot your Slackware original kernel after kernel update (You have to install 2.6.13 from "testing" to do this-slack12 uses 2.6.21.5 by default, no need to install it)

image = /boot/vmlinuz-generic-2.6.13&lt;br&gt;
root = /dev/ #Your root partition. Get this from another kernel entry or from original /etc/lilo.conf
label = Backup
read-only

Now run "lilo" once as root
* If you want to play safe you may now reboot and try if the kernel boots without errors.
* Uncompress your kernel sources below /usr/src
* The symlink /usr/src/linux has to point to the directory of the new kernel. For example: /usr/src/linux -&gt; /usr/src/linux-2.6.14.4

==Configure the kernel==

* Change to the kernel directory.
cd /usr/src/linux

* Configure your kernel:
** From scratch, then you may choose from

make config (You get prompted for all possible options)
make menuconfig (You get a nice menu where you may navigate with cursor keys. Needs curses-5.x)
make xconfig (You may configure in X, of course needs working X installation)
make gconfig
make qtconfig

:* From old configuration:
Copy the config file of the old kernel to ./.config. If you want to come from orignal Slackware kernel, then:

cp /boot/config .config

After that "make oldconfig" to configure new features (you may acceppt all questions with "Enter" to use the default values) and use "make menuconfig" (or any other of the above list) to change things if you like.

Important! Be sure to compile the alsa modules (or you won't have sound). You have also to do this if you used "make oldconfig" (for example using "make menuconfig") as the original kernel is compiled without alsa.

==Compile and install kernel==

* The real compiling can start:

make (Now, depending on your computer, you may go drinking some coffee, watch a movie or go on your balcony to smoke one ;-) )

If this finished without errors (we assume this) then your kernel and your kernel modules should be compiled.

* Remove symlinks. If you still run your original slackware kernel, then "vmlinuz" and "System.map" are Symlinks to the kernel files. To get sure that we don't override this files, we delete the symlinks

rm /boot/vmlinuz /boot/System.map

* Install the kernel

Install the kernel modules with:&lt;br&gt;
make modules_install

and the kernel with:&lt;br&gt;
make install

* If all steps have been done successful you may now use your new (self-made) kernel.

==Troubleshooting==

* Help, the kernel doesn't work!

Choose your backup kernel on lilo, check your kernel configuration and recompile.

* Choose your backup kernel sounds easy, but...

Now you know why you should keep a running kernel before you install a new one. Either your system is as usable as you are able to check the kernel configuration or you may boot from your slackware setup CD, mount your root partition to /mnt, chroot /mnt and recompile your kernel from there or install slackware packages of a running kernel.

[http://www.slackforum.de/wiki/Kernel26Kompilieren german version]

[[Category:Tutorials]]</text>
    <sha1>fc9ff4331ec429c4ad75c9cd1fb6a859a3a7abb6</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Kernel Checklist</title>
  <ns>0</ns>
  <id>101</id>
  <revision>
    <id>123</id>
    <timestamp>2009-06-03T02:26:27Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1985" xml:space="preserve"># [&amp;radic;] Make sure the filesystem type of your root partition is compiled into the kernel. To check what your root filesystem is type "mount".
# [&amp;radic;] Check that your networking card is compiled as a module or compiled into the kernel.
# [&amp;radic;] If you are using NVIDIA video card make sure you compile the AGP as a module
# [&amp;radic;] The sound card is important for listening to music; module it, or compile it in.
# [&amp;radic;] Another important thing that people miss out is the IDE chipset. This is important becuase you want to enable DMA on drives, and other important speed inhancements.
# [&amp;radic;] If you are going to use a camera that requires usb mass storage compile in SCSI Generic and USB-Mass storage.
# [&amp;radic;] Compile the sysfs feature in the kernel as that is an important for /sys. It is important for the 2.6 kernel.
# [&amp;radic;] If you must have framebuffer make sure you compile it in with the appropriate things. If you get a black screen set lilo.conf to vga = normal, then mess with it later. Also for nvidia users the rivafb is broken on many cards, so do not compile it in becuase it effects the nvidia driver for X. So use the vesafb instead.
# [&amp;radic;] Another usefull tool that i use is the .config in /proc (A must have I think)
# [&amp;radic;] ATA/ATAPI settings are also usefull for people, might want to make sure your kernel has that.
# [&amp;radic;] SATA/SCSI Make SURE YOU COMPILE it into the kernel and make sure you actually compile it in. If you have a SATA or SCSI hardware.
# [&amp;radic;] Iptables modules if you are going to use iptables or make a firewall. I use modules:)
# [&amp;radic;] I always recommend that in ALSA you compile or module OSS Emulation API
# [&amp;radic;] APM or ACPI is always somthing you might want to enable. This is not a feature needed by the kernel but, some people might need its features.

Just a reminder that the root filesystem (SCSI/SATA/etc) should be compiled into the kernel for obvious reasons.

[[Category:Tips]]</text>
    <sha1>4238ea2c7a9cbaff0c3adc59223853f234ee987b</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Kernel Compilation</title>
  <ns>0</ns>
  <id>102</id>
  <revision>
    <id>124</id>
    <timestamp>2009-06-03T02:26:59Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6724" xml:space="preserve">Kernel Compilation guide for the 2.4 series.&lt;br&gt;
Written by Thomas York - straterra@hotmail.com [[User:Straterra|Straterra]]&lt;br&gt;
Read over the ENTIRE GUIDE at least twice (2x) before trying to compile your first kernel.&lt;br&gt;
Added 2.6 information -- [[User:erik|erik]]&lt;br&gt;

==Prequisites==

# Download the latest kernel from kernel.org.
# It is HIGHLY recommended that you create a folder just for your new kernel. It can be in your user directory or anywhere else you want it to be.
# You must have the GCC Compiler
# You must have NCurses.
# You must have access as root.
# You must have have a bootloader (grub and lilo, the two most popular, are described below)
# You must be familiar with a text file editor (vi, nano, etc)

==Getting Ready to Compile==

# Extract the tar.bz2 file by using &lt;code&gt;tar jxvf linux-VERSION.tar.bz2&lt;/code&gt;
# Change into the newly created directory by using the &lt;code&gt;cd&lt;/code&gt; command.
# Run the command &lt;code&gt;make menuconfig&lt;/code&gt;. This command will open up a semi-graphical menu where you can pick what you want in your kernel. See [[Kernel Checklist]].
#* NOTE : If you already have a config file, you should instead run the command &lt;code&gt;make oldconfig&lt;/code&gt;. Make sure that you have placed the config file in &lt;code&gt;/usr/src/linux-VERSION&lt;/code&gt;, and that the config file has been named &lt;code&gt;.config&lt;/code&gt;.
#* NOTE : When you navigate through the menus, you use the keys 'M' to make the selection a module and 'Y' to compile it into the kernel. The difference is that if you compile it as a module, you can always unload it later. This is ideal if something causes conflicts. For this reason, I prefer to compile as much as possible as modules. It's your kernel, do what YOU want to do. :)  Bear in mind that some options MUST be compiled into the kernel statically (not modular) - for example, support for your root filesystem type must be static.
#* NOTE : If you are unsure what a certain selection does, you can press the '?' while having the confusing item selected. It is recommended you learn what EVERYTHING does your first time around, whether you will compile it in your not. This allows you to not have to press the '?' key every time..you already learned them! :)
# When you exit out of menuconfig, it will ask if you want to save. Say YES. This is critical. If you do not answer YES you will have to go back and do it all over again.

==Compiling v2.4==

# &lt;code&gt;make dep&lt;/code&gt; - This will organize all module dependencies.
# &lt;code&gt;make bzImage&lt;/code&gt; - This option may take a while, depending on how much content you decided to compile directly into the kernel, processor speed, ram, etc..
# &lt;code&gt;make modules&lt;/code&gt; - Again, if you selected for alot of content to be compiled as modules this may take some time.
# &lt;code&gt;su&lt;/code&gt; - Enter your root password. This allows you to have the access to install the compiled kernel.
# &lt;code&gt;make modules_install&lt;/code&gt; - This command will install all of your modules. 
# &lt;code&gt;cp System.map /boot/System.map&lt;/code&gt; - To replace the old System.map file.
# &lt;code&gt;cp arch/i386/boot/bzImage /boot/bzImage-VERSION&lt;/code&gt; - Replacing the variable VERSION with the version of the 2.4 kernel you compiled.

==Compiling v2.6==

# &lt;code&gt;make&lt;/code&gt; - This will build the kernel (vmlinux), compressed kernel (bzImage), and modules.
# &lt;code&gt;su&lt;/code&gt; - Enter your root password.
# &lt;code&gt;make modules_install&lt;/code&gt; - Installs the modules.
# &lt;code&gt;cp System.map /boot/System.map-VERSON&lt;/code&gt; - Replace VERSION with the kernel version number.
# &lt;code&gt;cp arch/i386/boot/bzImage /boot/bzImage-VERSION&lt;/code&gt; - Replace VERSION with the kernel version number.

==Lilo Configuration==

# Edit /etc/lilo.conf. This will open the lilo configuration file for editing.
# Input the following lines at the end of the file, again replacing the variable VERSION with the kernel version, the variable y for the hard drive device location and the variable z for the Linux partition.
#: image = /boot/bzImage-VERSION
#: root = /dev/hdyz
#: label = Linux-VERSION
#: read-only                   
# Save the file and exit.
# Run the command &lt;code&gt;lilo -v&lt;/code&gt;. This command (re)installed the lilo boot loader using the modified /etc/lilo.conf file.
# Hit &lt;tt&gt;Alt-Ctrl-Del&lt;/tt&gt;, or run the command &lt;code&gt;reboot&lt;/code&gt; or &lt;code&gt;init 6&lt;/code&gt;. This will switch to runlevel 6 and restart your computer.

==Grub Configuration==

# Edit /boot/grub/grub.conf OR /boot/grub/menu.lst
# Replace the variable VERSION with the kernel version
# Using grub a device such as /dev/hda1 is not used. Instead a zero indexed system is used (based on all drives grub can see at boot). /dev/hda1 would become (hd0,0), and /dev/hdb3 would become (hd1,2). Note that the root= line is passed to the kernel itself, and is not used by grub - therefore put in the devfs device (/dev/hda1 perhaps)
# First the relevant lines
#: title Linux-VERSION
#: root (hdx,x)
#: kernel /boot/bzImage-VERSION root=/dev/hdxx
# Now a complete one for reference
#: default 0
#: timeout 30
#: splashimage=(hdx,x)/grub/splash.xpm.gz
#: title Linux-VERSION
#: root (hdx,x)
#: kernel /boot/bzImage-VERSION root=/dev/hdxx
# Hit &lt;tt&gt;Alt-Ctrl-Del&lt;/tt&gt;, or run the command &lt;code&gt;reboot&lt;/code&gt; or &lt;code&gt;init 6&lt;/code&gt;. This will switch to runlevel 6 and restart your computer.

==Post-Compilation==

# When the machine reboots, choose the option 'Linux-2.4.x' or 'Linux-2.6.x', where x is your kernel minor version.
# Recompile any software that created a kernel module for your old kernel (nvidia, etc).

==NOTES==

# If the compilation failed at ANY step, you must run the command 'make clean' while in the directory of the extracted kernel source.
# If you try to boot up your new kernel, and you get errors, you can boot your old kernel using the old option in lilo.
# Make sure to compile in support for your filesystem!
# Historically, the kernel source is extracted to /usr/src/ and a &lt;code&gt;linux&lt;/code&gt; symlink is made. So you have the following:
#* /usr/src/linux-2.6.16
#* /usr/src/linux -&gt; linux-2.6.16
#: This allows you to symlink /boot/System.map and /boot/config right to /usr/src/linux/System.map and /usr/src/linux/.config - this way they are always pointing to the correct file and never have to be replaced.  However, neither of these are necessary; a System.map-VERSION file in /boot will work just fine without a symlink to System.map (see http://www.dirac.org/linux/system.map/ for more information).
#: Due to stupid users and old distributions replacing (symlinking) /usr/include, the merits of building a kernel in /usr/src are now under fire. It is (and always has been) safe to build a kernel as root in /usr/src, but you should NEVER replace /usr/include.

[[Category:Tutorials]]</text>
    <sha1>12f0a5f4c3c946892ee1a49a13532066d134403e</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>LCD Monitor Configuration In X.Org</title>
  <ns>0</ns>
  <id>26</id>
  <revision>
    <id>125</id>
    <parentid>34</parentid>
    <timestamp>2009-06-03T02:29:28Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Added to Hardware Category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15046" xml:space="preserve">[[Category:Tutorials]]
[[Category:Hardware]]
==DISCLAIMER==

If there is nothing wrong with your display, please don't go mucking about with your ~/.fonts.conf file (at least, back it up first). If you do have problems with your LCD display, then this is a good bet to try. If you have any success or failure, please do report this back, and changes, if any, that you made to your .fonts.conf file and any other file (perhaps /etc/X11/xorg.conf?) Comments, corrections and thoughts are always welcome.

This may well also work with XFree86 &gt; 4.3, since they use the same font configuration files as this. Older versions have a non-XML font configuration setup (I don't know when the switch over was made though), and will not be covered.

WARNING - Parts of this article are out of date, and there are a few changes required for modular X. These will be added soon.

==Introduction==

LCD/TFTs display fonts very differently to a CRT. Unfortunately with Slackware's default settings on X.Org/FreeType, the results for fonts on an LCD are painful to say the least. This is further compounded by the fact that all the 'helpful' HOWTOs out there are badly out of date, referring to ancient versions of the now defunct XFree86. Whilst there are a few sites out there with bits of information, putting into a workable solution is quite a challenge.

This exists, therefore, to show the naysayers that they're wrong, and that you _can_ enjoy nice looking fonts in Slackware.

(Please note, this is _not_ an exhaustive HOWTO, and it is _not_ a HOWTO about .fonts.conf (please see the Bibliography for a site detailing the tags available in .fonts.conf). This HOWTO is only about configuring an LCD monitor and what works best for one)

==What You'll Need==

*Your favourite text editor
*X.Org (or a later edition of XFree86 &gt;4.3. This has only been tested on Slackware 10.1 and above).
*An LCD/TFT monitor (most of this may also apply to an LCD monitor on a laptop).

==Physical Setup==

===The Monitor===

(I humbly apologise in advance for this section, but better safe than sorry.)

(Standalone Monitors only) Plug up your LCD. Where possible, use the DVI-D (i.e. The digital, not analogue VGA) connector, if both your monitor and your graphics card have one. If not, use an analogue VGA cable and connection (where possible, avoid using DVI-D to VGA adaptors.) Then, ensure the viewing angle of your LCD is correct. Play around with it until you are happy.

==Settings==

===X===

As far as I know, there is no special configuration of X needed for an LCD monitor. Just create the necessary entry for a monitor in /etc/X11/xorg.conf with the correct refresh rates as normal and enjoy (the monitor itself may even be able to give you these, mine does.) I won't cover this in any more detail, as it's pretty standard and covered better elsewhere.

X will also detect the correct sub-pixel alignment, so you don't need to deal with that either.

===Fonts and FreeType===

The real problems begins with font rendering in X. If you are switching over on your machine from a CRT to an LCD, what is facing you at first sight will be unpleasant to say the least.

Of course, this isn't down to X, as in all modern X servers from X.Org (and the later ones from XFree86) FreeType is responsible for all font rendering (any other modules loaded in your /etc/X11/xorg.conf for font rendering are anachronisms: they are no longer used, and X tells you they don't exist). Something I've seen a lot is that “fonts looked better on 9.0” or earlier versions of Slackware, and there is good reason for this. With the changeover to FreeType2, due to various Apple patents in the US and Japan, the 'bytecode interpreter' is now disabled by default. (Plus, IMHO, the Bitstream fonts that ship with Slackware aren't very good). With a CRT, this isn't much of a problem, but it does make a lot of difference on an LCD and is nearly illegible.

There are two ways round this, either:

#Make alterations to .fonts.conf to try and make the Bitstream fonts render better on an LCD.
#Rebuild FreeType with the bytecode interpreter, and use the properly hinted MS fonts (Arial, et al) to get cleaner, crisper looking fonts on the LCD.

Both of these solutions give different results (though I prefer the second).

====Common====

For both alternatives, there are some common settings that must be made.

If you're using KDE or GNOME, you'll find they have tools for doing some of what I'm going to describe. However, I would recommend _against_ using them. I've found their attempts at generating and editing a .fonts.conf file to be dubious to say the least. It is much more preferable to edit the file yourself, and since it is now done through a well defined XML file, this isn't as bad as it once appeared to be (judging from some of those ancient HOWTOs).

Crank up your editor and load ~/.fonts.conf (or /etc/fonts/local.conf)

If it exists: Just add these sections to it, inside the &lt;fontconfig&gt;&lt;/fontconfig&gt; tags.
If it doesn't exist: Use my ~/.fonts.conf skeleton from Appendix A as your .fonts.conf and edit as necessary.

1. Ensure that the sub pixel order is _not_ specified.

X knows the sub pixel order already, and if this is enabled as well, FreeType produces some very strange results. However, if you do still have problems, consider replacing 'none' with 'rgb' (the standard for LCD monitors), 'bgr' (unusual), 'vrgb' (vertical rgb, if you have a monitor that has been rotated by 90 degrees[1]), 'vgbr' (as vrgb, but very rare).

 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="rgba" &gt;
   &lt;const&gt;none&lt;/const&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

2. Enable sub-pixel hinting

This is what really starts to make the difference. Visit http://grc.com/ctwhat.htm for the technical explanation of why we're doing all of this.

 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="hinting" &gt;
   &lt;bool&gt;true&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

3. Set the hinting amount

Usually, this should be full. Valid options are 'none', 'hintslight', 'hintmedium' and 'hintfull' which should be fairly self explanatory if you've read the article at the link above.

 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="hintstyle" &gt;
   &lt;const&gt;hintfull&lt;/const&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

====Option 1) The 'Easy' Way====

Essentially, we're going to enable FreeType's non-patented autohinter and antialiasing to improve the appeareance of the default Bitstream fonts.

Add the following to ~/.fonts.conf. 

#Enable anti aliasing

This makes the fonts start to look nice, but some of the shapes will be distorted, so we need the FreeType autohinter (see next part). 

 &lt;match target="font" &gt;
  &lt;edit mode="assign" name="antialias" &gt;
   &lt;bool&gt;true&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

Fluxbox only:

You may need to enable anti alias separately on Fluxbox before it takes notice of the changes:

fluxbox menu --&gt; Configure --&gt; AntiAlias

#Enable the FreeType autohinter

The autohinter is not turned on automatically, so we have to do this manually.

Please note that OpenOffice.org binaries from the OOo website are built against the bytecode interpreter, so even if you have compiled FreeType with the bytecode interpreter and override it with the autohinter, OOo will still use the bytecode interpreter.

 &lt;match target="pattern" &gt;
  &lt;edit mode="assign" name="autohint" &gt;
   &lt;bool&gt;true&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

====Option 2) The 'Hard' Way====

This is my ([[User:Cathectic]]) preferred solution, as I believe it gives better results. This involves rebuilding FreeType with the bytecode interpreter enabled, and then using the properly hinted fonts 'Core Fonts For the Web' from Microsoft.

For this, you will need to:

#Get a copy of FreeType that has the bytecode interpreter enabled.
##Download the Freetype sources from your local Slackware mirror (slackware-$VERSION/source/l/freetype)
##In freetype.SlackBuild, uncomment the line to apply the bytecode enabling patch
##Run the SlackBuild
##Replace your old freetype package with the new one you've just built.

'''32bit X Applications (Slamd64 only)''': To enable 32bit applications in Slamd64 to use the bytecode interpreter, you need to install a 32bit bytecode enabled FreeType.

#Download and install the 'Microsoft Core Fonts for the Web' (if you have a Windows installation, you could import the fonts from that instead. This tutorial assumes you do not) from either:
##LinuxPackages (install CabExtract, then CoreFonts)
##Or, From the 'Core Fonts for the Web' at http://prdownloads.sourceforge.net/corefonts/ 
###Get all the *.exe files
###Get the CabExtract source RPM, rpm2tgz it, untar, build and install
###Use CabExtract to extract the *.ttf's from the *.exe's you downloaded, and then move the fonts to /usr/X11/lib/X11/fonts/TTF (/usr/share/fonts/TTF for X.Org 7 or newer).

Now add the following to ~/.fonts.conf

1. Disable the autohinter

This isn't strictly necessary – the autohinter is not enabled by default, and if it's not enabled, the bytecode interpreter is used by default. However, it's better safe than sorry.

 &lt;!-- Disable autohinter - using bytecode interpreter instead --&gt;
 &lt;match target="pattern" &gt;
  &lt;edit mode="assign" name="autohint" &gt;
   &lt;bool&gt;false&lt;/bool&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

2. Set the MS fonts as defaults

 &lt;!-- Set sans-serif as Arial --&gt;
 &lt;match target="pattern" name="family" &gt;
  &lt;test name="family" qual="any" &gt;
   &lt;string&gt;sans-serif&lt;/string&gt;
  &lt;/test&gt;
  &lt;edit mode="assign" name="family" &gt;
   &lt;string&gt;Arial&lt;/string&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

 &lt;!-- Set monospace as Courier New --&gt;
 &lt;match target="pattern" name="family" &gt;
  &lt;test name="family" qual="any" &gt;
   &lt;string&gt;monospace&lt;/string&gt;
  &lt;/test&gt;
  &lt;edit mode="assign" name="family" &gt;
   &lt;string&gt;Courier New&lt;/string&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

 &lt;!-- Set serif to Times New Roman --&gt;
 &lt;match target="pattern" name="family" &gt;
  &lt;test name="family" qual="any" &gt;
   &lt;string&gt;serif&lt;/string&gt;
  &lt;/test&gt;
  &lt;edit mode="assign" name="family" &gt;
   &lt;string&gt;Times New Roman&lt;/string&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

(I would also recommend using the template in Appendix B to replace all the Bitstream and Luxi fonts with the MS equivalents (or set them to use serif, sans-serif, monospace instead)).

====Testing====

Just load any application up (I'd recommend a Gtk one, KDE will probably need a restart for the changes to take affect everywhere), and the changes should be immediately obvious (I used Mozilla Firefox, by opening and closing it after every tweak of ~/.fonts.conf, I was able to see the changes immediately).

====Apply System Wide====

You can apply these changes system wide, using /etc/fonts/local.conf

If it exists, just append the sections you added above to it.
If it doesn't, use your .fonts.conf as /etc/fonts/local.conf, and edit it as necessary

(The order of precedence for processing is /etc/fonts/fonts.conf (automatically generated, don't edit it), /etc/fonts/local.conf then ~/.fonts.conf - meaning your ~/.fonts.conf will always override the system settings).

===Application Specific Settings===

Qt and Gtk settings need to be changed. 

====Gtk====

For gtk, edit .gtkrc-2.0 and set the fonts either to the generic 'serif', 'sans-serif', etc (now aliased to the MS fonts), or specify the MS fonts outright.

====Qt====
For qt, edit .kde/kderc and .qt/qtrc

==Suggestions==

===Non TrueType fonts===

Non TrueType fonts don't render well on LCDs as they don't support hinting. For these fonts (e.g. Helvetica), it is recommended that you specify an alternative TrueType font (that is hopefully similar, but it doesn't have to be!) to use instead (in this case, whatever the default sans-serif font on the system is):

 &lt;match target="pattern" name="family" &gt;
  &lt;test name="family" qual="any" &gt;
   &lt;string&gt;Helvetica&lt;/string&gt;
  &lt;/test&gt;
  &lt;edit mode="assign" name="family" &gt;
   &lt;string&gt;sans-serif&lt;/string&gt;
  &lt;/edit&gt;
 &lt;/match&gt;

You can easily reuse this for other fonts. Just copy and paste, then replace 'Helvetica' with the font to replace, and 'sans-serif' with the font you want to replace it with (or you can use the generic descriptions 'serif', 'sans-serif' or 'monospace').

===Old Gtk/Qt===

Some programs (usually older ones) using these libraries may not always use anti aliased fonts, even if you've specified them in .fonts.conf. This can fixed by:

Gtk: Add the following to /etc/profile: 
export GDK_USE_XFT='1'

qt: In ~/.qt/qtrc, ensure the following entry is present under [General]: 
enableXft=true
useXft=true

Programs coded using Gtk 1.x don't appear to support anti aliasing properly – you may want to consider replacing them with ones that use Gtk 2.x (e.g. Replacing XMMS with its Gtk2 fork, Beep Media Player)

===OpenOffice.org===

OpenOffice.org binaries are built against the bytecode interpreter. If you install a bytecode enabled FreeType, OOo will always use it, regardless of any system settings enabling the autohinter. Also, OpenOffice.org fonts have to be changed manually.

Tools &gt; Options &gt; OpenOffice.org &gt; 'Use system font for user interface' (make sure this is checked).

==Appendix A==

The following is a ~/.fonts.conf / /etc/fonts/local.conf skeleton. Use this to put together a working configuration for your system.

 &lt;?xml version="1.0"?&gt;
 &lt;!DOCTYPE fontconfig SYSTEM "fonts.dtd"&gt;
 &lt;fontconfig&gt;
 
 &lt;!-- Settings go between fontconfig tags --&gt;
 
 &lt;/fontconfig&gt;

==Appendix B==

This section is a recommendation only. Some fonts are not TrueType, which means they don't support anti aliasing and look dreadful on an LCD. The way round this is to tell FreeType to replace any such fonts with a properly hinted TrueType equivalent. All of the Bitstream and Luxi fonts should be aliased in this way (some sites, such as Gnome's home page, use these fonts, and they don't render correctly with the bytecode interpreter).

You can copy, paste and edit the following example for Helvetica for any other fonts you want to replace. (Just replace 'Helvetica' with the font to replace, and 'sans-serif' with the font you want it to be replaced with. Generic font descriptions serif, sans-serif and monospace are valid entries, as well as specific font names.)

 &lt;!-- Replace Helvetica with default sans-serif --&gt;
  &lt;match target="pattern" name="family" &gt;
   &lt;test name="family" qual="any" &gt;
    &lt;string&gt;Helvetica&lt;/string&gt;
   &lt;/test&gt;
   &lt;edit mode="assign" name="family" &gt;
    &lt;string&gt;sans-serif&lt;/string&gt;
   &lt;/edit&gt;
  &lt;/match&gt;
 &lt;alias&gt;

==Footnotes==

[1] Apparently, there are some monitors where the screen can be rotated. If so, perhaps the vrgb/vbgr settings might be better for you (but only when the screen is rotated) If you can test this, please report back the results. 

==Bibliography==

Man Page of fonts.conf - http://www.fontconfig.org/fontconfig-user.html&lt;br /&gt;
XFree86 Font Configuration - http://www.xfree86.org/current/fonts2.html&lt;br /&gt;
Explanation of Sub Pixel Hinting - http://grc.com/ctwhat.htm&lt;br /&gt;
Gentoo Xorg &amp; Fonts (And how to fix Konsole Linux fonts problem) - http://gentoo-wiki.com/HOWTO_Xorg_and_Fonts&lt;br /&gt;
If you're running an old version of XFree http://www.tldp.org/HOWTO/FDU/index.html</text>
    <sha1>4a9b2f174da27df04bdc2c152fd4dbe63c69df02</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Libdvdcss</title>
  <ns>0</ns>
  <id>103</id>
  <revision>
    <id>126</id>
    <timestamp>2009-06-03T02:30:12Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1736" xml:space="preserve">'''libdvdcss''' is a highly portable &lt;b&gt;library&lt;/b&gt; for accessing and unscrambling DVDs encrypted with the Content-Scrambling System (CSS) system. It is part of the VideoLAN project and is used by VLC media player and all other open source DVD players such as Ogle, xine and MPlayer.

libdvdcss is designed to be platform independent, with versions for GNU/Linux, Microsoft Windows, Mac OS X, BeOS, BSD and Solaris. It is released under the GNU General Public License.

libdvdcss is not to be confused with [http://en.wikipedia.org/wiki/DeCSS DeCSS]. While DeCSS uses a cracked DVD player key to perform authentication, libdvdcss uses a generated list of possible player keys. If none of them work (for instance, when the DVD drive enforces region coding) a brute force algorithm is tried so the [[region code]] of a DVD is ignored. Unlike DeCSS, libdvdcss has never been fought over in a courtroom.

In many countries it is forbidden to sell or document programs that provide ways around copy protection systems. CSS is not a copy protection system, but thwarts attempts to play the DVD without proper software.
Despite this fact, many Linux distributions do not contain libdvdcss (for example Debian, SUSE Linux, and Ubuntu) for reasons concerning patents. In most of these cases, the library can be easily downloaded from the Internet.

==External links==
*[http://developers.videolan.org/libdvdcss/ Official site]
*[http://slackbuilds.org/repository/12.0/libraries/libdvdcss/ libdvdcss at Slackbuilds.org ] - SlackBuilds.org has a SlackBuild script for libdvdcss.
*[http://www.linuxpackages.net/search_view.php?by=name&amp;name=libdvdcss LinuxPackages.net]- libdvdcss Slackware packages are usually found here.

[[Category:Information]]</text>
    <sha1>68aa50f2215a95c2bc3cdce65e2c507c31048809</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Life of a Software Package</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>127</id>
    <timestamp>2009-06-03T02:30:42Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17263" xml:space="preserve">From the programmer's keyboard to your (Slackware) Linux system.

= Introduction =

This article explains how a program someone writes in one side of the world ends up being managed in your system. It's meant to be easy to understand for a novice user coming from Windows, and only requires some basic knowledge of Unix systems. Specifically, the reader should know:

* How basic Unix permissions work.
* How to interpret the basic output of the ''ls'' command.
* How a command line interface works.

It only contains general ideas that could help a novice user understand the existing differences when installing software under Windows and under Unix, but no specific information about how to do it. The distribution manual will give you the specific details you need, and may be a good read after you have read this article.

= From source code to machine language =

'''Note''': You do not need to run any of the commands in this section. It's enough to understand the text and part of the output.

When a programmer creates a program, it's very common to write the program in a so-called high level language. In other words, he doesn't create the program executable directly specifying the intructions for the computer to run. He writes the program in a language that allows him to represent the program structure and logic, and then that logic is translated to a language the bare machine can understand. Let's suppose someone wants to write a ''Hello, World'' program in the C programming language. This is a program that prints a message to the screen and finishes, in order to check your system can translate the language you have used to machine language and to test the basic stuff works, as well as to give the novice programmer an idea on how the high level language works. This would be a very simple ''Hello, World'' program written in C:

 #include &lt;stdio.h&gt;
 
 int main()
 {
 	printf("Hello, World!\n");
 	return 0;
 }

You do not need to understand that program. The above text is what is commonly known as the '''source code''' of the program. The source code of a program in C is usually spread over one or more source files, so this program could very well be stored in a plain text file called ''hello.c''. You could view this file using a plain text editor like the Windows notepad.

This file cannot be executed directly because it's not a real program. First off, it doesn't have execution permissions, and if we tried to give it execution permissions and run it, we would get an error message:

 $ ls -l hello.c
 -rw------- 1 rg3 users 74 2007-10-15 19:27 hello.c
 $ chmod +x hello.c
 $ ./hello.c
 ./hello.c: line 3: syntax error near unexpected token `('
 ./hello.c: line 3: `int main()'

We need to use a program called ''compiler'' to get a binary and executable file. A file in a specific format that the operating system (Linux in our case) can understand. When you run it, the operating system reads the file, copies the different program components to the computer's memory and starts the program execution. If our machine has everything ready to compile C programs and we want to use the GNU C Compiler (''gcc''), we could do something as simple as:

 $ gcc -o hello hello.c

And we would get a file named ''hello'' which is our program ready to be run. As you see, our program is simply called ''hello'' and not ''hello.exe'', which would be a common name if we were working under Windows. In Unix systems, the convention is that programs do not have any file extension in their name (like EXE). We could then run the program and see that it does what we wanted.

 $ ./hello
 Hello, World!
 $

= Complex programs use libraries =

Most programs do a more sophisticated task than printing a message on the screen and finishing. The source code of the program above has 7 lines. It is not uncommon for a simple program to have thousands of lines, and there are a good amount of complex programs out there that have millions of lines of source code. It is also a very common practice to use items called '''libraries''' (usually '''shared''' libraries) to build your program. Libraries are files that contain the machine code to perform several different tasks. For example, let's suppose you were going to create a program that needs to download some data from the Internet, via HTTP (the web) or via FTP or another network service. And also let's suppose you don't have much knowledge on how to create a program that talks to others using the network, or that the focus of your program is on solving some other problem and you don't want to lose time or create a lot of code just because you want it to be able to download a file. Fortunately for you, there is a library called ''libcurl'' that makes retrieving files over the network very easy. The library contains all the code you need, so the source code you are going to create will not contain anything specific to be able to use the network. You simply indicate that you want to use ''libcurl'' and call the library functions everytime you want to download a file. Do you need to learn to sail or fly a plane or a different language if you want to send a letter to a friend in a different continent? No, you put the letter in the mailbox and the postal service does it for you. Libraries work like this.

In the moment you decide to do this, your program starts '''depending''' on ''libcurl''. Some pieces of the library need to be present in your system if you want to compile that program to create an executable, and some other pieces need to be present in the moment you want to ''run'' the program. Else, the program will not compile or will not be able to run. Libraries are convenient because, if managed well, you can install them in your system once and they will be used by every program that needs them. This is why libraries are regarded as a ''good thing'' or a ''good idea'' in the programming world, in most cases.

In Windows, shared libraries are called DLLs, as the library files usually have the DLL extension. In Unix, it's common for them to have the ''.so'' suffix, or some other containing it. For example, I have ''libcurl'' in my system, and the shared library is located in the file ''/usr/lib/libcurl.so.4.0.0''.

= Libraries and programs all over the place need a package manager =

So your system is going to be populated by a lot of programs, many of them using many different libraries for different tasks, some of them having some libraries in common, others having nothing in common. As you can guess, this situation can evolve into a pretty chaotic system. Let's describe how Windows did this in the past, and how Unix systems have been trying to handle the situation for a good amount of years now.

In Windows, most people distribute programs already compiled. You get a group of files or a single file that holds your program already prepared to be run. You extract those contents and place them somewhere in your hard drive, usually all of them under a specific directory (folder). You could then create some shortcuts in the ''start'' menu and the program is ready to be run. A installer program usually does all of this for you, asking some questions. What happens when the program uses a library? If the library is not very common and cannot be assumed to exist in a standard Windows installation, the common practice is to include a copy of the library with the program. If it's a relatively uncommon library, the installer usually puts it in the same place as the program, and when it is run and requests the library, the system first looks in the folder holding the program and finds the library there, and starts to use it. If it's not an uncommon library but you need a specific version of it, the installer may try to install it in a common place so all the programs can use it. It was very typical, when you had a system in which you had installed a lot of software as time passed, that the installer would ask you "I am trying to install the following library, but it appears to be present in your system in a newer version. Do you want me to replace the copy of it with my copy or do I leave it as it is?". And, in the same line, when you removed the program it would say "I was going to remove this library from the common place, but other programs may want to use it. Can I remove it or should I keep it there?". This chaos was called "DLL Hell".

Unix tries to avoid this problem in several ways, and its solutions bring the need of a package manager as we will explain. First off, in Unix the files on your hard drive are not grouped by program, but by their function. All binaries are stored in two or three folders, and the same for libraries or help documents. If all the documentation and help for the different programs is installed in a common location, it's easier to create a help system from which you can browse the documentation of every program installed on the computer, for example. This is generally considered a good idea and it's the tradition, but of course the idea has its detractors. Anyway, a second difference is that in Unix programs are distributed alone. If a program needs a library to be run, it needs to specify that somewhere, but only under special circumstances it's recommended to include the library as part of the program. In most cases, the library is distributed apart. Those two differences avoid the DLL hell. By installing libraries, programs, documentation and other data to common system locations, you avoid duplicating data. If there's a security problem using a library and every program using it could become compromised and make the system vulnerable, you update the library once and all the programs that use it are automatically protected, as each program doesn't include its own copy in its directory. By separating the programs from the libraries they use and distributing them apart, you make sure programs do not overwrite the libraries used by others or remove common libraries when they are removed.

However, the solution itself brings some new problems. For example, if a program installs files all over common system directories and I later want to remove it, how do I know which files need to be removed? And if a program requires a library to run, can I or should I specify that fact somewhere? Package managers are the answer. Under Unix, software is many times distributed as '''packages'''. Packages are groups of files that contain programs, libraries, documentation or simply data. Under Windows, to install a program many times you download an installer file, run it and the program is installed. This installer file that holds inside all the files the program needs and extracts them to the proper location could be considered a form of package, so you get an idea. Packages in Unix are usually managed by a package manager. A package manager is a program that allows you to install packages, check the list of installed packages, remove packages and many more complex tasks depending on how powerful and featureful the package manager itself is.

When you install a program using a package, the package holds the program binary, the program data and the program documentation, typically, along with information on where those files should be installed in the system, all over the place. Fortunately, prior, during or after the installation, after copying the files to your system, the package manager records somewhere the name and version of the package and the files it installed. This is the trick that allows you to later remove the package using the package manager without having to remember which files had been installed where. In addition, the package may hold information about other packages it needs installed for it to run, and this information may be used by the package manager to automatically download and install them too. Hopefully, you now start to understand the practical vision behind packages and package managers.

= Too many package managers =

The problem with package managers is that many Unix systems and even many different Linux distributions use many different package managers. Each one uses different package formats that cannot understand each other. Slackware uses ''pkgtools'', Debian and Ubuntu use ''apt-get'', Red Hat uses ''yum'', Mandriva uses ''urpmi'', Arch uses ''pacman'', etc.

You are a programmer and created the ''Hello, World'' program we saw at the beginning. How do you distribute your program? You have several solutions. If you don't want people to get the source code of your program, you need to distribute the program already compiled and probably packaged. To do that, you could provide your own program to install and uninstall the package cleanly from any system, and distribute it somehow and break some rules to achieve maximum compatibility, so the program will run on many different systems and distributions. Many commercial games are shipped this way. Unreal Tournament 2004 for Linux is distributed this way, for example. You could also provide it as a package for each of a subset of supported systems. Many companies do this. They give you Debian, Red Hat, Suse and Mandriva packages for you to choose, for example, each in the proper format to be used with the package manager from that distribution. If you want to use the software under other system you are out of luck. You can try some tricks but it's not guaranteed to work.

If, on the other hand, your program is open source and you don't mind people reading the source code of your program, the common case is to avoid creating a package for anything. You simply distribute a tarball (similar to a ZIP or RAR file) containing the source code and instructions to compile it. If someone wants a Debian package to install it, someone will have to compile your program under Debian, and make a package with the result. This is a very very very common case. In fact, distributions like Ubuntu or Debian heavily rely on '''package repositories''', network locations from where you can download thousands of packages for your system, created by a myriad of official and unofficial packagers (people that create packages for the system). For example, if you want to install a program under Ubuntu, it's very infrequent for the program not to exist already packaged in a repository, and you can download and install it, together with its dependencies, in a couple of mouse clicks.

= Summing up =

* Many times the programmer creates programs using source code that must be compiled.
* They use libraries to make writing programs easy.
* Distributing the resulting program is easier using a package manager.
* Many programmers only give you the source code due to the diversity of package managers and systems.
* Someone else is responsible for creating a package for a specific system.

= Slackware specifics =

Slackware is, as you may know, a very simple system. Being simple doesn't mean it's simple to use. On the contrary, a system with a simple design and simple tools usually requires the user to do more things to achieve a goal. The advantage of a simple design is that it's easier to understand if you want to know how your system works, and sometimes it's also more stable and has less bugs. As part of its simple design, the package manager in Slackware is also very simple, and its packages are also very simple. Slackware packages are tarballs (again, something like ZIP files) that, if extracted in the right place, will populate the system with the package files, and it also holds some special files with information about the package itself. As they are simple tarballs, Slackware doesn't try to hide this fact, and Slackware packages have the ''tgz'' extension (short for ''tar.gz''), contrary to other systems in which packages have a special extension to make it clear that they are packages, like ''rpm'' or ''deb''.

This is not a problem, but sometimes this confuses novice users. They go to the program webpage and download the program source code in a tarball (usually a file with ''tar.gz'' extension) and think "Hey, if Slackware packages are tarballs and this is a tarball, I'm going to install this file with the package manager". Wrong! Even when the package manager complains that the package name does not end in ''tgz'' but on ''tar.gz'', they many times rename the file and try again. Those are two mistakes in a row. The package manager will try to extact the tarball contents to that special location we mentioned earlier and nothing will happen, as the files inside the tarball are not structured as they need to be, but this is the small problem. The big one is that what you are trying to install is the source code of the program, and not the program itself! Remember, you need to compile it first in the majority of cases.

Under Slackware, you should first check if there is an official package for the program. If there is not, you could try to to download a ready to use package from a place or someone you trust. Else, you could compile the program yourself and create a package for it, and then install the package. The compilation and package creation can be automated sometimes for ease of use, for example using [[SlackBuild Scripts|SlackBuild scripts]].

[[Category:Information]]</text>
    <sha1>c3cd57a0aefddda8629eb96bd5cc25954d4a05d9</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Lilo</title>
  <ns>0</ns>
  <id>105</id>
  <revision>
    <id>128</id>
    <timestamp>2009-06-03T02:31:17Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1020" xml:space="preserve">Once upon a time you try to boot Slackware, something happens and lilo is messed up. You can fix lilo really easily, all you need is CD1 of Slackware. Boot the CD and when it says boot: then you type the following:

: &lt;code&gt;huge.s root=/dev/hda1 noinitrd ro&lt;/code&gt;

Now you change huge.s to the kernel you want to boot, root= should reflect the root partition of your Slackware install. Now when you type this you have Slackware booting up with the bare.i default kernel. Now at the login prompt you login as root and either type:

: &lt;code&gt;liloconfig&lt;/code&gt;

That will setup Lilo from a ncurses based menu. Now you can also edit lilo's config from a file:

: &lt;code&gt;vi /etc/lilo.conf&lt;/code&gt;

Either way it will fix it hopefully, Now remember man lilo has all the hex errors if you need them. When you have all that setup you now can run:

: &lt;code&gt;/sbin/lilo -v&lt;/code&gt;

Now you must run lilo every time you change /etc/lilo.conf to update the changes, Now restart without the CD and it should work.

[[Category:Tutorials]]</text>
    <sha1>faaece4ac572f843d9d0e7c784166e88c5d88950</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Log Correlation</title>
  <ns>0</ns>
  <id>106</id>
  <revision>
    <id>129</id>
    <timestamp>2009-06-03T02:32:14Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9341" xml:space="preserve">[[Category:Tutorials]]

'''Log Correlation'''

I thought I'd talk about the importance of log correlation. For instance, you've found that someone is continually pinging your server. You want to see if your box is responding to the pings. Usually, you'll know right off, since most people know if their firewall was configured to block pings...I'm just using pings as a quick example, though. Log correlation usually consists of checking, for instance, web server logs against firewall logs, or Snort logs against firewall and web server logs. This helps you understand what suspicious activity is actually doing and if your server/workstation responded (and how it responded, if it did).

I run Snort on a server, along with a web server, which is firewalled with IPTables. I have Snort report what it sees to a MySQL database, although it does record captures to a PCAP file locally. I also run Modsecurity, an application firewall that is designed to sniff and possibly block traffic going to/from web servers, mainly Apache. So, I've a ton of logs that I can correlate: Snort, Apache, IPTables, and Modsecurity logs.

We'll pick something easy. In fact, I'll fabricate some logs by generating some false alerts. I'll use 'wget', to visit my website. Keep in mind that what you see below gives you the advantage...you know what you're doing and looking for when we soon check the logs. This won't be the case when some stranger or worm hits your firewall or web server (or any other application server).

    -bash-2.05b$ wget wigglit.ath.cx/root.exe
    --23:24:05-- http://wigglit.ath.cx/root.exe
    =&gt; `root.exe'
    Resolving wigglit.ath.cx... 66.160.141.30
    Connecting to wigglit.ath.cx|66.160.141.30|:80... connected.
    HTTP request sent, awaiting response... 404 Not Found
    23:24:06 ERROR 404: Not Found.

    -bash-2.05b$ 

I used root.exe because there is an old vulnerability was was used to exploit flaws in IIS...the CodeRed worm of old. Now, let's check the web server's logs. I've tail'd my logs:

    root@starchild:/var/log/apache# tail -f -n 100 access_log
    12.123.12.123 - - [15/Sep/2007:23:34:35 -0400] "GET /root.exe HTTP/1.0" 404 202
    12.123.12.123 - - [15/Sep/2007:23:34:35 -0400] "GET /root.exe HTTP/1.0" 404 202 "-" "Wget/1.10.2"

You see that the communcation was accepted.  A 404 code, which means 'page not found', was generated. This is usually a good indication, as the server didn't respond favorably to the attack.

Now, let us check the firewall logs. We already know that the firewall allowed the traffic, since the web server responded with a 404...if the traffic was being blocked, there would be no record of the attack in the logs, because the firewall would have intercepted the traffic before it reached the web server. We're checking the firewall logs just to be sure this guy hasn't done anything else that the web server didn't see:

    Sep 12 17:28:34 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=34557 DF PROTO=TCP SPT=46656 DPT=10083 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:44 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=18168 DF PROTO=TCP SPT=40091 DPT=449 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:44 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=27053 DF PROTO=TCP SPT=36295 DPT=5060 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:54 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=29291 DF PROTO=TCP SPT=47590 DPT=342 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:54 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=11788 DF PROTO=TCP SPT=43604 DPT=1519 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:04 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=17600 DF PROTO=TCP SPT=32783 DPT=577 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:04 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=51338 DF PROTO=TCP SPT=47879 DPT=18187 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:14 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=58520 DF PROTO=TCP SPT=41983 DPT=517 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:14 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=20255 DF PROTO=TCP SPT=53355 DPT=1986 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:24 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=28213 DF PROTO=TCP SPT=38543 DPT=978 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:24 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=10244 DF PROTO=TCP SPT=45624 DPT=11371 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:37 starchild kernel: ICMP-request: IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=28 TOS=0x00 PREC=0x00 TTL=42 ID=53002 PROTO=ICMP TYPE=8 CODE=0 ID=10683 SEQ=16615
    Sep 15 23:21:08 starchild kernel: ICMP-request: IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=84 TOS=0x00 PREC=0x00 TTL=55 ID=40988 PROTO=ICMP TYPE=8 CODE=0 ID=614 SEQ=0

Quite a bit of stuff, huh? This looks to be a port scan! This is something that we didn't see in the Apache logs! Good thing we checked! Looks like this IP needs to be blocked with IPTables (which we won't do in this exercise).

Sadly, nothing shows in the Modsecurity logs, but we've enough information already. What about Snort? Because I've PCAP files, the search becomes a bit more involved. I'll spare the intimate details, but this is what we see:

    [**] [1:1256:9] WEB-IIS CodeRed v2 root.exe access [**]
    [Classification: Web Application Attack] [Priority: 1]
    09/15-23:34:35.708546 0:C:DB:F5:90:0 -&gt; FE:FD:40:3E:E7:DC type:0x800 len:0xB0
    12.123.12.123:52753 -&gt; 66.160.141.30:80 TCP TTL:56 TOS:0x0 ID:51589 IpLen:20 DgmLen:162 DF
    ***AP*** Seq: 0xAF32BB68 Ack: 0x3F319F7A Win: 0xFFFF TcpLen: 32
    TCP Options (3) =&gt; NOP NOP TS: 288652007 1521931210
    [Xref =&gt; http://www.cert.org/advisories/CA-2001-19.html]

    23:34:35.708546 00:0c:db:f5:90:00 &gt; fe:fd:40:3e:e7:dc, ethertype IPv4 (0x0800), length 176: IP (tos 0x0, ttl 56, id 51589, offset 0, flags [DF], length: 162) 12.123.12.123.52753 &gt; 66.160.141.30.80: P [tcp sum ok] 2939337576:2939337686(110) ack 1060216698 win 65535
    0x0000: fefd 403e e7dc 000c dbf5 9000 0800 4500 ..@&gt;..........E.
    0x0010: 00a2 c985 4000 3806 56c0 47b2 0aa0 42a0 ....@.8.V.G...B.
    0x0020: 8d1e ce11 0050 af32 bb68 3f31 9f7a 8018 .....P.2.h?1.z..
    0x0030: ffff e9c5 0000 0101 080a 1134 7ae7 5ab6 ...........4z.Z.
    0x0040: d3ca 4745 5420 2f72 6f6f 742e 6578 6520 ..GET./root.exe.
    0x0050: 4854 5450 2f31 2e30 0d0a 5573 6572 2d41 HTTP/1.0..User-A
    0x0060: 6765 6e74 3a20 5767 6574 2f31 2e31 302e gent:.Wget/1.10.
    0x0070: 320d 0a41 6363 6570 743a 202a 2f2a 0d0a 2..Accept:.*/*..
    0x0080: 486f 7374 3a20 7769 6767 6c69 742e 6174 Host:.wigglit.at
    0x0090: 682e 6378 0d0a 436f 6e6e 6563 7469 6f6e h.cx..Connection
    0x00a0: 3a20 4b65 6570 2d41 6c69 7665 0d0a 0d0a :.Keep-Alive....

The first is the Snort alert file...this is a fast alert, with minimal detail (no packet capture). The second section is the full alert, including packet capture. It is also garbled (due to the hex code and the fact that this blog has issues with formatting) Note that my logs show no response. Apparently, my Snort install doesn't have a 404 signature. Again, the fact that we can correlate helps me when my Snort install lacks the data that I may have needed. I was able to look at the Apache logs to see the 404 when my Snort logs didn't show the return traffic.

Well, this concludes our chat about correlating existing logs. Note that any log files can be correlated. Correlation can also assist in tracking down network issues or issues with, for instance, a faulty Snort install (ahem). Although this discussion focused more on security, hopefully this helps someone understand their network or software architecture also.

This page is also linked at [http://slackfiles.blogspot.com/2007/09/log-correlation.html my blog]

--[[User:Unixfool|Ron]] 00:35, 16 September 2007 (EDT)</text>
    <sha1>375bd6c95bb9e07c9a07b79854abb8e7ca10554d</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Login Shell</title>
  <ns>0</ns>
  <id>107</id>
  <revision>
    <id>130</id>
    <timestamp>2009-06-03T02:32:43Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4042" xml:space="preserve">[[Category:Tips]]
__TOC__
==Introduction==
Seeing people give bad advice regarding colored ls output, I figured I better address this problem at the source. If you open a terminal and ls does not give colored output, or the prompt is similar to &lt;code&gt;bash-2.04$&lt;/code&gt; then you are in a non-login shell. This means none of the default profile scripts were sourced.

From the BASH man page:

 When  bash  is  invoked  as  an  interactive login shell, or as a non-interactive shell with the
 --login option, it first reads and executes commands from the file /etc/profile,  if  that  file
 exists.   After  reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile,
 in that order, and reads and executes commands from the first one that exists and  is  readable.
 The --noprofile option may be used when the shell is started to inhibit this behavior.

 When  a  login shell exits, bash reads and executes commands from the file ~/.bash_logout, if it
 exists.

 When an interactive shell that is not a login shell is started, bash reads and executes commands
 from  ~/.bashrc,  if  that  file exists.  This may be inhibited by using the --norc option.  The
 --rcfile file option will force  bash  to  read  and  execute  commands  from  file  instead  of
 ~/.bashrc.

 When  bash  is  started  non-interactively, to run a shell script, for example, it looks for the
 variable BASH_ENV in the environment, expands its value  if  it  appears  there,  and  uses  the
 expanded value as the name of a file to read and execute.

You need to configure your terminal to give you an interactive "login shell". A login shell is the same as a login at the console. The default profile and user profile scripts will be sourced. Below are some ways to change how your terminal emulator behaves.

==Eterm==
Chances are if you are using Eterm you know what you're doing and not looking at this page. But just for reference, you can envoke a login shell by passing -l or --login-shell at the command prompt. The preferred method is to edit your .cfg file (the default is $PREFIX/share/Eterm/themes/Eterm/theme.cfg) and add &lt;code&gt;login_shell true&lt;/code&gt; in the toggles section.
 Eterm -l

==Gnome-Terminal==
Edit -&gt; Profiles&lt;br&gt;
Select the profile (Default) and click Edit&lt;br&gt;
Select the Title and Command Tab&lt;br&gt;
Check the box next to Run command as a login shell

==Konsole==
There should be a way to do this from some configuration dialog, but I don't use KDE or Konsole, so all I can recommand at this time is the following:
 konsole --ls

==xterm / rxvt / aterm==
 xterm -ls
 rxvt -ls
 aterm -ls

==XFCE 4.4 Terminal==
Open the XFCE terminal.&lt;br&gt;
Open Edit -&gt; Preferences&lt;br&gt;
Select the "General" icon at the left.&lt;br&gt;
Under "Command", check the box next to "Run command as a login shell"

==screen==
If you launch ''screen'' directly in a X11 terminal emulator, you will notice that using the ''-ls'' or equivalent terminal emulator option is not enough to get colored ''ls'' output. This is because the terminal emulator is not calling the shell directly, and it's ''screen'' who does. ''screen'' has a configuration file option to use a login shell and another one to modify the system logs as if you had logged in (read the ''screen'' manpage for more details). However, this doesn't seem to be enough to get colored ''ls'' output.

Some people avoid these login shell confusions and problems by trying to get the same ''bash'' environment no matter how ''bash'' ends up being called as an interactive shell. This implies setting the bash prompt (controlled by the environment variable PS1) from the ''.bashrc'' user file and either sourcing ''.bashrc'' from ''.bash_profile'' or making ''.bash_profile'' a link to ''.bashrc''. Additionally, you can include the following lines in your ''.bashrc'' script to '''always''' get colored ''ls'' output:

 if [ -z "$LS_COLORS" ]; then
     source /etc/profile.d/coreutils-dircolors.sh
 fi

These recommendations are the "bad advice" the original author mentioned in the first paragraph.</text>
    <sha1>884cb7f41656b7fd7e8d58e4119ab34d6c2df586</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Logitech Marble FX mouse</title>
  <ns>0</ns>
  <id>108</id>
  <revision>
    <id>131</id>
    <timestamp>2009-06-03T02:33:11Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5265" xml:space="preserve">[[Category:Hardware]] 

'''Logitech TrackMan (R) Marble FX Mouse Basic Setup &amp; Tweak Guide'''

This is a simple guide for using this marble mouse on my Slackware 12.0 setup.  

Since this is a plug and play mouse you will find that the 'auto' protocol of xorg.conf for the mouse works quite well on Slackware for this mouse.  There is very little that we need to do to actually use our mouse. 

However one of the advantages to a marble mouse, and the reason I decided to write this how-to is a feature commonly referred to as 'drag lock' which is not activated by default using the auto protocol.  To me this is a must have feature for me when using a marble mouse and only requires a slight addition to our xorg.conf file.

This guide will demonstrate the following:
1. Setup xorg.conf to allow item (2) and (3) below.
2. Enable the drag lock in our xorg.conf file.
3. Optional: Get drag lock to work in web pages in Mozilla Firefox so we can use our track ball to vertically &amp; horizontally scroll.

I will assume that you are already quite familiar with Slackware's xorg.conf.

'''Item 1 &amp; 2 Setup for xorg.conf &amp; Enable drag lock.'''

Below is my xorg.conf for this mouse:

&lt;code&gt;&lt;pre&gt; 
Section "InputDevice"
      Identifier "Mouse1"
      Driver "mouse"
      Option "Device" "/dev/mouse"
      Option "Protocol" "auto"
      Option "EmulateWheel" "true"
#   This is for future use as  button 8 is not supported on Slackware 12 see below.
#   Option "EmulateWheelButton" "8"
      Option "DragLockButtons" "2 1"
EndSection
&lt;/pre&gt;&lt;/code&gt;

For me the important item above is the "DragLockButtons" option above.  

What this does is: 

- makes the white button up top on the mouse above your thumb (which is seen by Xorg as button 2) activate drag lock on the the lower thumb button (which is seen by Xorg as button 1).  

Usage:

Now we can simply press button 2 with our thumb then use our thumb to roll the marble and scroll scroll scroll away while in the background we are in essence, pressing and holding the one key.

In simpler terms, you can press button 2 of your mouse (the white button above your thumb) with your thumb on the title bar of a program and now use your thumb to roll the marble, allowing you to move the application window.  This also works for horizontal scroll bars, vertical scroll bars, or even for selecting text in a web page, word processor, or even moving an icon on your desktop.

As a side note: 

There are other options available for this mouse.  Personally I am happy with the defaults that Xorg yields on entering my xsession.  The following is some of the information presented to us at the bottom of /var/log/Xorg.0.log which re-iterates our settings above *and* also let's us know what defaults it is using for some items that we did not address, that would could tweak further if we like.

&lt;code&gt;&lt;pre&gt; 
(==) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "DragLockButtons" "2 1"
(**) DragLock: button 2 is drag lock for button 1
(**) Mouse1: ZAxisMapping: buttons 4 and 5
(**) Option "EmulateWheel" "true"
(**) Option "EmulateWheelButton" "8"
(==) Mouse1: YAxisMapping: buttons 4 and 5
(**) Mouse1: EmulateWheel, EmulateWheelButton: 8, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
&lt;/pre&gt;&lt;/code&gt;

You also see that Option "EmulateWheelButton" "8" in the xorg.conf &amp; our Xorg.0.log?  Xorg will allow us to uncomment that line in our xorg.conf file.  That *is* what the printout above is for, an xorg.conf file with that line un-commented.  However, for some reason it simply won't do anything on Slackware 12.0.  It will in Slackware 11.0 and I haven't tested it on Slackware 12.1 rc's yet.  It also does work on Debian Lenny, which has the same version of X that Slackware 12.0 does.  Which is totally blowing my mind.  I have played with all the numerous protocol's, xmodmaps to no avail.  Therefore I have left the option in xorg.conf for you above so that you have it for future use, or reference purposes.  The number 8 button is the little red button on the mouse on the thumb side of the mouse.

'''Item 3: How to get the mouse to work in Mozilla Firefox'''

This is totally optional and not required.  There are other ways to achieve this functionality, I simply find this the easiest way.

As stated you can simply use the scroll bar with the draglock feature above.  However, since my mouse is not always near the side or bottom of the page, it's nice to activate scrolling of a page from where ever our mouse may be positioned at the present moment while surfing.

To achieve this I use an extension called "Grab And Drag" by Ian Weiner.  It is available at the firefox add-ons site.

After installing the extension, and restarting Firefox.  Edit Grab and Drag's preferences, click on the "General Tab", under section "Behavior" there is a drop down for "Use the XXX mouse button to grab and drag" .  Where "XXX" is a drop-down selection box.  I use left for that option.

Usage:

Now when I'm surfing the web, regardless of where I have my mouse cursor on the page, I can simply click on my button 2 of my mouse, then roll the marble and I have full vertical and horizontal scrolling with my marble.

I have tested this extension with Firefox 2.0.0.14 and Firefox 3.0 beta 5.

Hope This Helps.</text>
    <sha1>796382a923fbaf547f8797f46745f02ada15b09c</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Madwifi</title>
  <ns>0</ns>
  <id>109</id>
  <revision>
    <id>132</id>
    <timestamp>2009-06-04T05:17:41Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8491" xml:space="preserve">[[Category:Networking]]
[[Category:Wireless]]
[[Category:Driver]]

Latest CVS is 09-Jul-2005 02:35

__TOC__
== Instalsi ==
== Konfigurasi ==

&lt;pre&gt;
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/madwifi \
co madwifi
&lt;/pre&gt;
== iwconfig Options ==
&lt;pre&gt;
iwconfig --help
Usage: iwconfig interface [essid {NN|on|off}]
                          [nwid {NN|on|off}]
                          [mode {managed|ad-hoc|...}
                          [freq N.NNNN[k|M|G]]
                          [channel N]
                          [sens N]
                          [nick N]
                          [rate {N|auto|fixed}]
                          [rts {N|auto|fixed|off}]
                          [frag {N|auto|fixed|off}]
                          [enc {NNNN-NNNN|off}]
                          [power {period N|timeout N}]
                          [txpower N {mW|dBm}]
                          [commit]
&lt;/pre&gt;
&lt;pre&gt;
iwconfig ath0 essid ''avalon''
iwconfig ath0 key ''1234567890''
iwconfig ath0 channel ''13''
iwconfig ath0 rate ''10MB''
iwconfig ath0 ap ''11:22:33:44:55:66''
&lt;/pre&gt;

== iwlist Options ==
&lt;pre&gt;
iwlist --help
Usage: iwlist [interface] frequency
              [interface] channel
              [interface] ap
              [interface] accesspoints
              [interface] peers
              [interface] bitrate
              [interface] rate
              [interface] encryption
              [interface] key
              [interface] power
              [interface] txpower
              [interface] retry
              [interface] scanning
&lt;/pre&gt;
== iwpriv Options ==
&lt;pre&gt;
iwpriv ath0
ath0      Available private ioctl :
          setoptie         (8BE8) : set 256 byte  &amp; get   0      
          getoptie         (8BE9) : set   0       &amp; get 256 byte 
          setkey           (8BE2) : set  60 byte  &amp; get   0      
          delkey           (8BE4) : set   7 byte  &amp; get   0      
          setmlme          (8BE6) : set  10 byte  &amp; get   0      
          addmac           (8BEA) : set   1 addr  &amp; get   0      
          delmac           (8BEC) : set   1 addr  &amp; get   0      
          chanlist         (8BEE) : set  32 byte  &amp; get   0      
          setparam         (8BE0) : set   2 int   &amp; get   0      
          getparam         (8BE1) : set   1 int   &amp; get   1 int  
          turbo            (0001) : set   1 int   &amp; get   0      
          get_turbo        (0001) : set   0       &amp; get   1 int  
          mode             (0002) : set   1 int   &amp; get   0      
          get_mode         (0002) : set   0       &amp; get   1 int  
          authmode         (0003) : set   1 int   &amp; get   0      
          get_authmode     (0003) : set   0       &amp; get   1 int  
          protmode         (0004) : set   1 int   &amp; get   0
          get_protmode     (0004) : set   0       &amp; get   1 int  
          mcastcipher      (0005) : set   1 int   &amp; get   0      
          get_mcastcipher  (0005) : set   0       &amp; get   1 int  
          mcastkeylen      (0006) : set   1 int   &amp; get   0      
          get_mcastkeylen  (0006) : set   0       &amp; get   1 int  
          ucastciphers     (0007) : set   1 int   &amp; get   0      
          get_uciphers     (0007) : set   0       &amp; get   1 int  
          ucastcipher      (0008) : set   1 int   &amp; get   0      
          get_ucastcipher  (0008) : set   0       &amp; get   1 int  
          ucastkeylen      (0009) : set   1 int   &amp; get   0      
          get_ucastkeylen  (0009) : set   0       &amp; get   1 int  
          keymgtalgs       (0015) : set   1 int   &amp; get   0      
          get_keymgtalgs   (0015) : set   0       &amp; get   1 int  
          rsncaps          (0016) : set   1 int   &amp; get   0      
          get_rsncaps      (0016) : set   0       &amp; get   1 int  
          roaming          (000C) : set   1 int   &amp; get   0      
          get_roaming      (000C) : set   0       &amp; get   1 int  
          privacy          (000D) : set   1 int   &amp; get   0      
          get_privacy      (000D) : set   0       &amp; get   1 int  
          countermeasures  (000E) : set   1 int   &amp; get   0      
          get_countermeas  (000E) : set   0       &amp; get   1 int  
          dropunencrypted  (000F) : set   1 int   &amp; get   0      
          get_dropunencry  (000F) : set   0       &amp; get   1 int  
          wpa              (000A) : set   1 int   &amp; get   0      
          get_wpa          (000A) : set   0       &amp; get   1 int  
          driver_caps      (0010) : set   1 int   &amp; get   0      
          get_driver_caps  (0010) : set   0       &amp; get   1 int  
          maccmd           (0011) : set   1 int   &amp; get   0      
          wme              (0012) : set   1 int   &amp; get   0      
          get_wme          (0012) : set   0       &amp; get   1 int  
          hide_ssid        (0013) : set   1 int   &amp; get   0      
          get_hide_ssid    (0013) : set   0       &amp; get   1 int  
          ap_bridge        (0014) : set   1 int   &amp; get   0      
          get_ap_bridge    (0014) : set   0       &amp; get   1 int  
          inact            (0017) : set   1 int   &amp; get   0      
          get_inact        (0017) : set   0       &amp; get   1 int  
          inact_auth       (0018) : set   1 int   &amp; get   0      
          get_inact_auth   (0018) : set   0       &amp; get   1 int  
          inact_init       (0019) : set   1 int   &amp; get   0      
          get_inact_init   (0019) : set   0       &amp; get   1 int
&lt;/pre&gt;

== Locking to a Specific Mode ==
&lt;pre&gt;
    * iwpriv ath0 mode 1 To lock to 11a only.
    * iwpriv ath0 mode 2 To lock to 11b only.
    * iwpriv ath0 mode 3 To lock to 11g only.
    * iwpriv ath0 mode 0 (default) autoselect mode.
&lt;/pre&gt;

== Changing Authentication Mode. ==
&lt;pre&gt;
    * iwpriv ath0 authmode 1 To use open authentication.
    * iwpriv ath0 authmode 2 To use shared key authentication.
    * iwpriv ath0 authmode 3 To use 802.1x authentication.
&lt;/pre&gt;
== Manipulating the MAC white/black list ==
&lt;pre&gt;
    * iwpriv ath0 maccmd 3 To clear the MAC list.
    * iwpriv ath0 maccmd 1 To make the list a whitelist.
    * iwpriv ath0 maccmd 2 To make the list a blacklist.
    * iwpriv ath0 addmac 00:11:22:33:44:55 To add a mac address to the list.
    * iwpriv ath0 delmac 00:11:22:33:44:55 To delete a mac from the list.
&lt;/pre&gt;
== Changing ESSID Visible Mode ==
&lt;pre&gt;
    * iwpriv ath0 hide_ssid 0      &lt;&lt; ======   To make ESSID visible
    * iwpriv ath0 hide_ssid 1      &lt;&lt; ======   To hide ESSID
&lt;/pre&gt;
== iwspy Options ==
&lt;pre&gt;
iwspy --help
Usage: iwspy interface [+] [MAC address] [IP address]
&lt;/pre&gt;
== Contoh ==

== Installing Madwifi on Slackware ==
Pre Install Steps:
   cd /usr/src/sourcepkg
   wget http://
   cd ..
   tar jxvf sourcepkg/madwifi-current.tar.bz2
   cd madwifi
   make
   make install
   modprobe ath_pci
   lspci | grep ath

Post Install Steps:

   1. After the module is loaded and your ath0 interface is up, run ifconfig and get the MAC address of ath0.
   2. Edit /etc/rc.d/rc.wireless.conf and comment out the section beginnning with “*)”
   3. Below the lines you commented in /etc/rc.d/rc.wireless.conf add something like this:
&lt;pre&gt;
 00:0F:3D:A9:97:90)
        INFO="D-LINK DWL-G650"
        ESSID="avalon"
        KEY="6281321313252"
        ;;
&lt;/pre&gt;
Your MAC address, ESSID, KEY and info comment are obviously going to be different.

   1. Run “/etc/rc.d/rc.wireless” and then “dhcpcd ath0” which should be enough to get you up and running.
   2. Check your settings if you want “ifconfig” and “iwconfig.”

There are relatively easy ways to get slackware to bring up your interface:

   1. Put an “ifconfig ath0” statement at the bottom of /etc/rc.d/rc.local
   2. update your slackware to slackware-current, our pat has understand what whee need :-)
      upgrade your packages to lates n/tcpip and n/wireless-tools
   3. If you’re using hotplug, you can have it automatically bring up the interface by editing
      /etc/hotplug/net.agent and inserting the following lines in the “case add|register)” branch:

&lt;pre&gt;
   ath*)
     dhcpcd -n $INTERFACE % If you use dhcp for the interface
     % or if you prefer to just hardcode your interface, put your ifconfig statement here.
     % ifconfig ath0 192.168.1.1 netmask 255.255.255.0 ...
     ;;
&lt;/pre&gt;

In the remove|unregister branch it will automatically bring down dhcpcd if running.

== External Links ==

* http://www.madwifi.net/
* http://madwifi.otaku42.de/
* http://madwifi.sourceforge.net/
* http://madwifi.sourceforge.net/dokuwiki/doku.php</text>
    <sha1>9a2c92220f69300a373b319ce1bfa0231642bdfb</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Masquerade</title>
  <ns>0</ns>
  <id>110</id>
  <revision>
    <id>133</id>
    <timestamp>2009-06-04T05:18:06Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="996" xml:space="preserve">Masquerading is what Windows calls "Internet Connection Sharing", although you can use it for sharing any network connection.

This is just a basic script to give you the general idea, and to refine upon for yourself.

 #!/bin/sh
 # Define as appropriate for your setup
 # external interface (connected to the internet)
 EXT_IF=eth0
 # internal interface (connected to your local network)
 INT_IF=eth3
 # path to your iptables binary - leave this alone on slack
 IPTABLES=/usr/sbin/iptables
 # We don't want to just forward anything to anyone, or let everything
 # into our local network
 $IPTABLES -F FORWARD
 $IPTABLES -P FORWARD DROP
 $IPTABLES -A FORWARD -i $INT_IF -o $EXT_IF -j ACCEPT
 $IPTABLES -A FORWARD -i $EXT_IF -o $INT_IF -m state --state ESTABLISHED,RELATED -j ACCEPT
 # Do the actual masquerading
 $IPTABLES -t nat -F POSTROUTING
 $IPTABLES -t nat -A POSTROUTING -o $EXT_IF -j MASQUERADE
 # Enable IP packet forwarding
 echo 1 &gt; /proc/sys/net/ipv4/ip_forward

[[Category:Security]]</text>
    <sha1>9d4896be6daa25e168d1b4b2637140d44d9da276</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Mediawiki E-Mail</title>
  <ns>0</ns>
  <id>111</id>
  <revision>
    <id>134</id>
    <timestamp>2009-06-04T05:19:19Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1402" xml:space="preserve">[[Category:Tips]]

==Can't Send Out Confirmation E-mails (using SMTP)==
(confirmed on Slackware 10.2 &amp; Mediawiki 1.7.x)&lt;br&gt;
To use SMTP on Mediawiki 1.5+ you must add:&lt;br&gt;
 $wgSMTP = array(
          'host'     =&gt; "&lt;i&gt;your.smtp.server&lt;/i&gt;",
          'IDHost'   =&gt; "&lt;i&gt;your domain or blank&lt;/i&gt;",
          'port'     =&gt; 25,
          'auth'     =&gt; true &lt;i&gt;(or false)&lt;/i&gt;, 
          'username' =&gt; "&lt;i&gt;username (if auth=true)&lt;/i&gt;",
          'password' =&gt; "&lt;i&gt;password (if auth=true)&lt;/i&gt;"
          );&lt;br&gt;

:::...somewhere into LocalSettings.php (found in the Mediawiki's root directory).


After adding the above to your LocalSettings.php file, the SMTP service still &lt;i&gt;probably&lt;/i&gt; will &lt;b&gt;not&lt;/b&gt; work. If you examine your &lt;code&gt;/var/log/apache/error_log&lt;/code&gt; file, it probably will have this error:&lt;br&gt;

&lt;code&gt;[error] PHP Warning:  usermailer(Mail.php): failed to open stream: No such file or directory in /home/joebleau/public_html/wiki/includes/UserMailer.php on line 82&lt;/code&gt;


For some reason, the Wiki's config script screws up the path to the PHP's PEAR extensions.  To fix this, edit the LocalSettings.php line that says:&lt;br&gt;
::&lt;code&gt;$path = array( $IP, "$IP/includes", "$IP/languages");&lt;/code&gt;

to say:

::&lt;code&gt;$path = array( $IP, "$IP/includes", "$IP/languages"&lt;b&gt;, "/usr/lib/php"&lt;/b&gt; );&lt;/code&gt;

After that, your smtp outgoing mail &lt;i&gt;should&lt;/i&gt; work for your Mediawiki installation.</text>
    <sha1>92e956e54a657a4f62d25e07e97528b31297d794</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Mod perl</title>
  <ns>0</ns>
  <id>112</id>
  <revision>
    <id>135</id>
    <timestamp>2009-06-04T05:20:46Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2692" xml:space="preserve">[[Category:Tutorials]]
This is an example of installing mod_perl on SlackWare 12.0 using the SlackBuild system.  I put everything in /root/SlackBuild_mod_perl and I did all the following commands as root.  I figured it out from this page: http://slackbuilds.org/howto/

First, I downloaded everything.  I went to http://slackbuilds.org/repository/12.0/development/mod_perl/ and I downloaded the "slackbuild" file, mod_perl.tgz, and the source, mod_perl-2.0.3.tar.gz, into /root/SlackBuild_mod_perl

I unpacked the SlackBuild package:
&lt;pre&gt;
root@pecan:~# cd ~/SlackBuild_mod_perl/
root@pecan:~/SlackBuild_mod_perl# tar xzvf mod_perl.tgz 
mod_perl/
mod_perl/README
mod_perl/doinst.sh
mod_perl/mod_perl.SlackBuild
mod_perl/mod_perl.conf
mod_perl/mod_perl.info
mod_perl/slack-desc
root@pecan:~/SlackBuild_mod_perl# 
&lt;/pre&gt;

I moved the mod_perl source into the mod_perl SlackBuild directory, and editted the SlackBuild script:
&lt;pre&gt;
mv mod_perl-2.0.3.tar.gz mod_perl
cd mod_perl
emacs mod_perl.SlackBuild
&lt;/pre&gt;

When editting, I just checked that the VERSION= line matched the actual version of the source (2.0.3).

Then I executed the SlackBuild script:
&lt;pre&gt;
./mod_perl.SlackBuild
&lt;/pre&gt;

That command ran for quite a while and produced a lot of compiling output.

When it was done, there was a package left in /tmp.  I moved it to /root so it would not be deleted later.

I installed it with installpkg:
&lt;pre&gt;
root@pecan:~# installpkg mod_perl-2.0.3-i486-1_SBo.tgz 
Installing package mod_perl-2.0.3-i486-1_SBo... 
PACKAGE DESCRIPTION:
mod_perl: mod_perl (Perl Interpreter for Apache)
mod_perl:
mod_perl: Mod_perl incorporates a Perl interpreter into the Apache web server
mod_perl: so that the Apache web server can directly execute Perl code.
mod_perl: Mod_perl links the Perl runtime library into the Apache web server 
mod_perl: and provides an object-oriented Perl interface for Apache's C
mod_perl: language API. The end result is a quicker CGI script turnaround 
mod_perl: process, since no external Perl interpreter has to be started.
mod_perl:
mod_perl: Homepage: http://perl.apache.org/
mod_perl:
Executing install script for mod_perl-2.0.3-i486-1_SBo...
root@pecan:~# 
&lt;/pre&gt;

At this point I checked that the file /usr/lib/httpd/modules/mod_perl.so existed, and it did.  I editted /etc/httpd/httpd.conf and uncommented the line that included /etc/httpd/mod_perl.conf, and then ran httpd -t to make sure there were no syntax errors.
I ran "/etc/rc.d/rc.httpd restart" to restart the apache server, and it appeared to work.  The web page still worked, and perl scripts still ran. 

How can I tell if mod_perl or perl cgi is being used ?  I'm not sure, please add that info you know.</text>
    <sha1>a5b0b48d68877b7f8ebbbf69d522af61e35becb2</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Modules</title>
  <ns>0</ns>
  <id>113</id>
  <revision>
    <id>136</id>
    <timestamp>2009-06-04T05:21:23Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2503" xml:space="preserve">When you are compiling a kernel for the first time asking the question
to yourself should I module this or compile this in the kernel? Well
the answer to this question is not an exact science. Meaning that it
depends on what you believe in yourself. The following are a few
things that I like to follow when I compile a kernel:

1. Always compile the root file system in the kernel because without the root file system mounted, How can the kernel load the module:)

2. I like to compile my networking card into the kernel. The reason being is what happens if the modules screw up, I would like to be able to SSH into the box and fix it.

3. Iptables and networking OPTIONS I like to compile as modules, because sometimes I may not need them loaded.

4. IDE chipsets (or SCSI chipsets (if you boot from a SCSI disk)) should NOT be compiled as a module because the devices are needed to boot the system and is required to be loaded BEFORE modules are loaded.

::MEANING: If you boot from an IDE hard-drive but make the IDE drivers a module, your system will never boot! Your boot device driver(s) MUST be compiled into the kernel so the system can start up so that it can later load modules.&lt;/b&gt;


Now remember that Linux is a monolithic kernel so when you load
modules the modules go into the kernel space. This would make it so
modules run at the SAME speed as if you were to compile the modules
into the kernel. My philosophy is that if you REALLY need to load
something on startup ( like root file system, or IDE/ATAPI support)
then you should compile it into the kernel. The other stuff like ALSA/
Networking Options/USB/I2C/Etc and stuff like that can be unloaded and reloaded
which would make sense if you put them as modules. 


This is just some advice and it is not 100% correct because some
people follow their own strategy when compiling kernels. This is more
like a recommendation:)

==Listing Loaded Modules==
&lt;code&gt;lsmod&lt;/code&gt; will produce a list of modules that the kernel has loaded.


==Manually Loading a Module==
&lt;code&gt;modprobe &lt;i&gt;module&lt;/i&gt;&lt;/code&gt; will manually load a module (if the module exists).

EXAMPLE: &lt;code&gt;modprobe 8139too&lt;/code&gt; will load the 8139too ethernet driver.


==Checking To See If A Module Exists==

EASY WAY: &lt;code&gt;modprobe &lt;i&gt;module&lt;/i&gt;&lt;/code&gt; - if the modules doesn't exist (or has a problem), you will get an error message.

HARDER WAY: &lt;code&gt;cd&lt;/code&gt; into the &lt;code&gt;/lib/modules/2.X.X/&lt;/code&gt; directories and start poking around for it.


[[Category:Tips]]</text>
    <sha1>53af1a02fe14f273e0e905f5f9002f84077f5614</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>More MySQL</title>
  <ns>0</ns>
  <id>114</id>
  <revision>
    <id>137</id>
    <timestamp>2009-06-04T05:22:07Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tips</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2396" xml:space="preserve">[[Category:Tips]]
::...in no particular order.


&lt;B&gt;NOTE: All actions on this page assume you are already logged into the MySQL console and have the proper permissions.&lt;/B&gt;

==How do I select which database to work on?==
You &lt;code&gt;use&lt;/code&gt; it.

::&lt;code&gt;USE &lt;i&gt;database_name&lt;/i&gt;;


==How do I create a table in a database?==
::1) make sure you are &lt;code&gt;USE&lt;/code&gt;-ing the correct database!
::2) &lt;code&gt;CREATE TABLE &lt;i&gt;table_name&lt;/i&gt;(&lt;i&gt;column1 type&lt;/i&gt;(&lt;i&gt;size&lt;/i&gt;), &lt;i&gt;column2 type&lt;/i&gt;(&lt;i&gt;size&lt;/i&gt;), &lt;i&gt;...etc.&lt;/i&gt; );&lt;/code&gt;


:::&lt;B&gt;EXAMPLE:&lt;/B&gt;
::::&lt;code&gt;CREATE TABLE products(part_num char(6), description char(25), price decimal(5));&lt;/code&gt;


==How do I see what the 'columns' are in a table?==
::1) make sure you are &lt;code&gt;USE&lt;/code&gt;-ing the correct database!
::2) &lt;code&gt;DESCRIBE &lt;i&gt;table_name&lt;/i&gt;&lt;/code&gt;

This will show you the column information including the data type and length.


==How do I show the records in a table?==
'''Make sure''' you are &lt;code&gt;USE&lt;/code&gt;-ing the correct database!

1) Create a temporary table from a SELECT statement-
:: &lt;code&gt;SELECT CREATE TABLE &lt;i&gt;table_name&lt;/i&gt;;&lt;/code&gt;

2) Show ENTIRE contents of a database including record names:
::&lt;code&gt;SELECT * FROM &lt;i&gt;table_name&lt;/i&gt;;&lt;/code&gt;
::&lt;b&gt;WARNING: Don't use on a large table!!&lt;/b&gt;

3) Show selected contents from a table:
::&lt;code&gt;SELECT * FROM &lt;i&gt;table_name&lt;/i&gt; WHERE &lt;i&gt;condition&lt;/i&gt;;&lt;/code&gt;


==How do I clear the primary key on a table?==
::1) make sure you are &lt;code&gt;USE&lt;/code&gt;-ing the correct database!
::2) &lt;code&gt;ALTER TABLE &lt;i&gt;table_name&lt;/i&gt; DROP PRIMARY KEY;&lt;/code&gt;


==How do I add a primary key to a table?==
::1) make sure you are &lt;code&gt;USE&lt;/code&gt;-ing the correct database!
::2) &lt;code&gt;ALTER TABLE &lt;i&gt;table_name&lt;/i&gt; ADD PRIMARY KEY (&lt;i&gt;column_name&lt;/i&gt;);&lt;/code&gt;


==There's a blank space in a column name and now I can't fix it==

::To get MySQL to recognize a column name with a blank space in it, you must put the column name in back-ticks (`) NOT apostrophes (').
::::EXAMPLE: &lt;code&gt;ALTER TABLE inventory ADD PRIMARY KEY (`Part Number`);&lt;/code&gt;


==How do I list all the users?==
::A) To list all the users (regardless of database or table):
::::&lt;code&gt;SELECT User,Host FROM mysql.user;&lt;/code&gt;

::B) To list all the users on a database.table:
::::Don't know this one...  working on it.

::C) To list all the databases &amp; tables granted to a user:
::::&lt;code&gt;SHOW GRANTS FOR &lt;i&gt;user@host&lt;/i&gt;;&lt;/code&gt;</text>
    <sha1>4ca5e8a5d7d2e3324576e1caf7a36f38e1d6f876</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Mount Count</title>
  <ns>0</ns>
  <id>115</id>
  <revision>
    <id>138</id>
    <timestamp>2009-06-04T05:22:58Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Information</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="336" xml:space="preserve">[[Category:Information]]
A count of how many times a filesystem has been mounted.  Used to determine whether a [[Forced Fsck]] should be executed.

After a successful fsck (filesystem check), the mount count is reset to zero.  When the mount count reaches (or exceeds) the [[Maximum Mount Count]], a Forced Fsck is executed during boot.</text>
    <sha1>c1016fca1d75994c5e6b497417bdb52c0f774c4a</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Mount with hal from command line</title>
  <ns>0</ns>
  <id>116</id>
  <revision>
    <id>139</id>
    <timestamp>2009-06-04T05:23:35Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1736" xml:space="preserve">= Manually mounting a device using HAL from the command line =


If you're like me, you probably live in the command line and prefer it way over those nasty and uncomfortable file managers. But you also live in a world were people lends you their USB sticks / Portable HDs to copy something. Then, you've probably also felt that there must be a better way to mount than the typical "dmesg|tail ; mount -t vfat,ntfs-3g what where" (and "what" tipically is /dev/sda1 and "where" might be /mnt/hd or something).

The obvious solution to make that more streamlined is to use HAL. But part of HAL's ugliness is that there are only graphical tools to work with.

Well, fortunatelly for us, XFCE comes with a little handy tool called "exo-mount" (and "exo-unmount") which does the dirty job of figuring out the HAL weird device name (another piece of HAL's ugliness), use the appropiate /usr/libexec/hal-* command (maybe via a DBUS message, I don't know) to create the mount point and mount the device as well as unmount the device and delete the mount point.

The only problem is that you must still have lots of X/Gtk/Pango/... libraries installed (so it may not be a viable choice for an X-less system, but then you're probably not running a desktop but a server and shouldn't have HAL running).

The usage is relatively simple:

  exo-mount -d /dev/sda1 # The usual "what" is /dev/sda1

and ''voila'' (if you have HAL running, that is). It should be mounted under /media/&lt;Volume name&gt;.

To umount:

  exo-'''un'''mount -d /dev/sda1

And that's it... You still don't have console automounting (but there are many tutorials covering that, and personally I don't like it), but you're now using HAL to do your mount/unmount.

[[Category:Tips]]</text>
    <sha1>1ad5b0b8fcfd0d62bc68cb90712230dd876327de</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Mutt</title>
  <ns>0</ns>
  <id>117</id>
  <revision>
    <id>140</id>
    <timestamp>2009-06-04T05:24:05Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5910" xml:space="preserve">[[Category:Tutorials]]
= Mutt =

Mutt is a text-based mail client renowned for its powerful features and the fact that it is almost totally customizable. This article will cover the installation and configuration of mutt in order to use it as your daily email client. Please note that I use GMail as my primary email address, so the examples are designed for GMail users. Not much differs though other than the fact that GMail uses SSL.


== Installation ==

Slackware comes with a package for mutt v1.4. If you did a full install, you already have it installed. If not, it can be located on the 'n' series on your Slackware install CD or favourite mirror. This tutorial also uses getmail, procmail and msmtp. procmail and getmail are available as Slackware packages, and can be installed in the same manner...

If you have the CD, follow these steps as root to install it:

  mount /mnt/cdrom
  installpkg /mnt/cdrom/slackware/n/mutt-1.4.2.1i-i486-2.tgz
  installpkg /mnt/cdrom/slackware/n/getmail-4.4.4-noarch-1.tgz
  installpkg /mnt/cdrom/slackware/n/procmail-3.22-i486-1.tgz

If you would rather install it from a mirror:

  wget http://www.slackware.at/data/slackware-current/slackware/n/mutt-1.4.2.1i-i486-2.tgz
  wget http://www.slackware.at/data/slackware-current/slackware/n/getmail-4.4.4-noarch-1.tgz
  wget http://www.slackware.at/data/slackware-current/slackware/n/procmail-3.22-i486-1.tgz
  installpkg mutt-1.4.2.1i-i486-2.tgz getmail-4.4.4-noarch-1.tgz procmail-3.22-i486-1.tgz

Be sure to replace 'slackware-current' with the actual version of Slackware you are using.

msmtp is not part of Slackware, and will need to be installed separately. It can be downloaded from [http://msmtp.sourceforge.net/ here]. If you need information on building Slackware packages, click [[Building_A_Package]] for an excellent tutorial.

== Configuration ==

=== Mutt ===
First, let start with mutt, and a very simple ''~/.muttrc'':
 # Name
 set realname='Slackware User'
 
 # Where we store our emails
 set folder=~/mail
 set mbox=+mbox
 set spoolfile=+inbox
 set record=+sent
 set postponed=+drafts
 set mbox_type=Maildir 
 mailboxes +inbox
 
 # my favourite editor is 'joe'
 set editor=joe
 
 ignore *	# this means "ignore all headers by default"
 # I still want to see some basic details
 unignore	date from subject to cc
 
 # Mutt options
 set edit_headers=yes
 set hdrs # Allows us to create our own headers
 my_hdr From: Slackware User &lt;user@slackware.com&gt;
 my_hdr X-Mailer: `mutt -v| head -n 1`

So far, it's simple, and cannot do much. We can almost read emails stored in ~/mail, compose and save drafts.

In order for us to read emails, first, we need to create our mail folders. We are using the Maildir format, so we need to create them using:

 mkdir -p ~/mail/inbox/{,cur,tmp,new}
 mkdir -p ~/mail/sent/{,cur,tmp,new}
 mkdir -p ~/mail/drafts/{,cur,tmp,new}

Now, when we have an email in ~/mail/inbox, we will be able to read it. Postponed messages will also be saved in ~/mail/drafts. But want to be able to send emails too, right? That's where msmtp comes into play.

For this part, we will assume that msmtp is installed. msmtp is basically a SMTP client that will be called by mutt when sending an email. So we need to have added to the mutt config like this:

 set sendmail="/usr/bin/msmtp"

Now, that's useless by itself. We need to setup msmtp to send emails...
Open up ~/.msmtprc with your favourite editor. This is a copy of mine, setup to use GMail's smtp server:

 account default
 host smtp.gmail.com
 port 587
 protocol smtp
 auth on
 from username@gmail.com
 user username@gmail.com
 password mypassword
 tls on
 tls_starttls on


So, after going through this and identifying what we need for our SMTP server, we are ready to send emails... Let's test it:

Launch mutt by running:
 mutt -y

Running mutt without '-y' will ignore our mailboxes statement, so we won't see any emails...

You can see in mutt the key shortcuts at the top of the screen: 'm' for composing a new message.
After we save the message, we see a new shortcut at the top: 'y' to send the message.

We now have mutt that can read emails from ~/mail/inbox, and send emails!!! 
The next step is to get the emails in ~/mail, and that's getmail's job.

=== Getmail ===

Getmail is a Python application that's included with Slackware. Similar to fetchmail, many people prefer it, saying it's easier to configure. Just like mutt, getmail is in the 'n' series, and should already be installed if you chose to do a full install. If not, just check out the mutt section above to install what's needed for this tutorial.

Once we have it all installed, let's create a basic getmail configuration. This configuration sits in ''~/.getmail/getmailrc'':

 [retriever]
 type = SimplePOP3SSLRetriever
 server = pop.gmail.com
 username = username@gmail.com
 port = 995
 password = password
 
 [destination]
 type = Maildir
 path = ~/mail/inbox

If you use a standard POP3 account that doesn't use SSL, use something like:

 [retriever]
 type = SimplePOP3Retriever
 server = pop.isp.net
 username = username
 port = 110
 password = password
 
 [destination]
 type = Maildir
 path = ~/mail/inbox

As simple as that. Now, it will connect to your email account, and download all your emails to ~/mail/inbox. Please note that if you want to fetch mail for multiple accounts, unlike fetchmail, getmail works with a single account per config file. So if you have two email accounts, you can have each account configured in their own config file like ''~/.getmail/getmailrc'' and ''~/.getmail/getmailrc-isp''

If you want automatic check, just add the following lines to your crontab by running ''crontab -e'' for each one of your email accounts:

 /5 * * * * /usr/bin/getmail
 /30 * * * * /usr/bin/getmail -r ~/.getmail/getmailrc-isp

=== Procmail ===

Procmail is an advanced mail filtering solution. More to come

== Todo ==
The rest...</text>
    <sha1>c57ce5f562f0609faad6a0a117180cc108fbc049</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>MySQL</title>
  <ns>0</ns>
  <id>118</id>
  <revision>
    <id>141</id>
    <timestamp>2009-06-04T05:24:41Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4325" xml:space="preserve">[[Category:Tips]]

==I installed the MySQL package, now what?==
See [[Configuring MySQL]] for how to get [[mysqld]] running.


==How do I start mysqld?==
As &lt;b&gt;root&lt;/b&gt; type: &lt;code&gt;mysqld_safe &amp;&lt;/code&gt;


==How do I check that mysqld is running?==
&lt;code&gt;ps aux&lt;/code&gt;

If it's running, you should see several lines of something like this:&lt;br&gt;
:&lt;code&gt;mysql    14429  0.0  6.4  58056 15544 ?        S    18:44   0:00 /usr/libexec/mysqld --basedi... blah blah&lt;/code&gt;&lt;br&gt;
:&lt;code&gt;mysql    14430  0.0  6.4  58056 15544 ?        S    18:44   0:00 /usr/libexec/mysqld --bas... blah blah&lt;/code&gt;&lt;br&gt;

==How do I login to the MySQL console client?==
:&lt;code&gt;mysql -u root -p&lt;/code&gt;&lt;br&gt;
:you will be prompted for root's password after which you will get the &lt;code&gt;mysql&gt;&lt;/code&gt; prompt.


==How do I exit the MySQL console client?==
:&lt;code&gt;exit;&lt;/code&gt;


==How do I see what databases already exist?==
:FROM SHELL: &lt;code&gt;echo "show databases;" | mysql -u root -p&lt;/code&gt;&lt;br&gt;
:FROM A MYSQL CLIENT: &lt;code&gt;show databases;&lt;/code&gt;


==How do I  make a database?==
:FROM SHELL: &lt;code&gt;mysqladmin -u root -p create database &lt;i&gt;databasename&lt;/i&gt;&lt;/code&gt;&lt;br&gt;
:FROM A MYSQL CLIENT: &lt;code&gt;CREATE DATABASE &lt;i&gt;databasename&lt;/i&gt;;&lt;/code&gt;

It will ask you for the root password and then it will create the database.

==How do I delete a database?==
:FROM SHELL: &lt;code&gt;mysqladmin -u root -p drop database &lt;i&gt;databasename&lt;/i&gt;&lt;/code&gt;&lt;br&gt;
:FROM A MYSQL CLIENT: &lt;code&gt;DROP DATABASE &lt;i&gt;databasename&lt;/i&gt;;&lt;/code&gt;


==How do I create a table in a database?==
Now you are starting to get complex, see [[More MySQL]].


==How do I connect to it?==
You must add users to the database.

:1) Log into mysqld as root: &lt;code&gt;mysql -u root -p&lt;/code&gt;&lt;br&gt;
:: It will ask you for root's password, enter it. You will then get the &lt;code&gt;mysql&gt;&lt;/code&gt; prompt&lt;br&gt;

:2) Add the user at localhost: &lt;code&gt;GRANT &lt;i&gt;privileges (usually &lt;/i&gt;ALL&lt;i&gt;)&lt;/i&gt; PRIVILEGES ON &lt;i&gt;database&lt;/i&gt;.* TO '&lt;i&gt;username&lt;/i&gt;'@'localhost' IDENTIFIED BY '&lt;i&gt;password&lt;/i&gt;';&lt;/code&gt;&lt;br&gt;
::&lt;b&gt;NOTES:&lt;/b&gt;&lt;br&gt;
:::: a) Even if you only want pople to connect from remote machines, &lt;b&gt;you must first&lt;/b&gt; give them privileges as localhost. This seems to be a MySQL quirk.&lt;br&gt;
:::: b) To grant permissions on ALL databases, use &lt;code&gt;*.*&lt;/code&gt; as the database name.&lt;br&gt;
::At this point, users should be able to connect and manipulate databases from localhost.&lt;br&gt;

&lt;b&gt;FROM REMOTE MACHINES:&lt;/B&gt;
:3) Add permissions from remote machines: &lt;code&gt;GRANT &lt;i&gt;privileges (usually &lt;/i&gt;ALL&lt;i&gt;)&lt;/i&gt; PRIVILEGES ON &lt;i&gt;database&lt;/i&gt;.* TO '&lt;i&gt;username&lt;/i&gt;'@'&lt;i&gt;IP address or machine name&lt;/i&gt;' IDENTIFIED BY '&lt;i&gt;password&lt;/i&gt;';&lt;/code&gt;&lt;br&gt;

:&lt;b&gt;EXAMPLE:&lt;/b&gt;
:::&lt;code&gt;mysql -u root -p&lt;/code&gt;&lt;br&gt;
:::&lt;i&gt;enter password&lt;/i&gt;&lt;br&gt;
:::&lt;code&gt;GRANT ALL PRIVILEGES ON mydatabase.* TO 'joebleau'@'localhost' IDENTIFIED BY 'mypassword';&lt;/code&gt;&lt;br&gt;
:::&lt;code&gt;GRANT ALL PRIVILEGES ON mydatabase.* TO 'joebleau'@'192.168.1.2' IDENTIFIED BY 'mypassword';&lt;/code&gt;


:&lt;b&gt;--&gt;GOTCHA&lt;--&lt;/b&gt; Sometimes domain name resolution can screw up your connections, if your machine has a name in the &lt;code&gt;/etc/hosts&lt;/code&gt; file or the DNS system, you may encounter a problem. Watch for connection errors and note if they say something like &lt;code&gt;Connection for 'root'@'www.hawtsecks.com' is not allowed&lt;/code&gt;. Even though the machine is really localhost, you may need to grant permissions to "root@www.hawtsecks.com" or even "root@192.168.2.42" depending on your situation.


&lt;b&gt;CAN'T CONNECT FROM A REMOTE MACHINE&lt;/b&gt;
:If you are using programs to connect to your databases (e.g. Navicat, MySQLadmin, or web scripts) &lt;b&gt;from&lt;/b&gt; a remote machine and you cannot get them to connect correctly, you should check:

::- Make sure that mysqld is running.
::- Make sure that your firewall isn't blocking the port (3306).
::- Make sure you have been GRANT'd on to the database &lt;i&gt;and from the correct machine address&lt;/i&gt;(see above).
::- Make sure mysqld has networking on &lt;b&gt;--&gt;SLACKWARE 10+ GOTCHA&lt;--&lt;/b&gt;
::::As of about Slackware 10.0, Patrick has set the &lt;code&gt;/etc/rc.d/rc.mysqld&lt;/code&gt; script to start MySQL daemon with external connections ignored. To fix this, find the &lt;code&gt;/etc/rc.d/rc.mysqld&lt;/code&gt; line that says &lt;code&gt;SKIP="--skip-networking"&lt;/code&gt; and comment it out (put a "#" in front of it).

==How do I ________?==
For more helpful MySQL tips, see [[More MySQL]].</text>
    <sha1>432eec569607c3da5450c5f5f258c8aae02ba71a</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>NAT Script</title>
  <ns>0</ns>
  <id>119</id>
  <revision>
    <id>142</id>
    <timestamp>2009-06-04T05:25:20Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1648" xml:space="preserve">&lt;pre&gt;
#!/bin/sh

# This is a very basic LAN NAT script, allowing only SSH to the firewall from
# the external interface, allowing all outbound LAN traffic, and allowing only
# established/related traffic back into the LAN.

ipt=/usr/sbin/iptables
extip=192.168.1.41 # replace with your EXTERNAL IP - eth0
lan=10.5.3.0/25 # your LAN CIDR range - eth1

# start firewall
start_firewall() {

  echo "Enabling IP forwarding."
  echo 1 &gt; /proc/sys/net/ipv4/ip_forward

  echo "Enabling iptables firewall."
  # default policies
  $ipt -P INPUT DROP
  $ipt -P FORWARD DROP

  # NAT
  $ipt -t nat -A POSTROUTING -o eth0 -j SNAT --to-source $extip

  # INPUT chain
  $ipt -A INPUT -i lo -j ACCEPT
  $ipt -A INPUT -i eth1 -s $lan -j ACCEPT
  $ipt -A INPUT -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
  $ipt -A INPUT -p tcp --destination-port 22 -j ACCEPT

  # FORWARD chain
  $ipt -A FORWARD -i eth1 -s $lan -j ACCEPT
  $ipt -A FORWARD -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT

}

# stop firewall
stop_firewall() {

  $ipt -P INPUT DROP
  $ipt -P OUTPUT DROP
  $ipt -P FORWARD DROP
  # allow internal traffic
  $ipt -A INPUT -i eth1 -j ACCEPT
  $ipt -A OUTPUT -o eth1 -j ACCEPT

}

# flushing, removing and zeroing tables
reset_firewall() {

  chains=`cat /proc/net/ip_tables_names`
  for i in $chains; do
    $debug $ipt -t $i -F
    $debug $ipt -t $i -X
    $debug $ipt -t $i -Z
  done

}

case "$1" in

  start|restart|reload)
    reset_firewall
    start_firewall
    ;;
  stop)
    reset_firewall
    stop_firewall
    ;;
  *)
    echo "Usage: $0 {start|stop|restart|reload}"
    exit 1
    ;;

esac
&lt;/pre&gt;

[[Category:Security]]</text>
    <sha1>fcceeb6d2d9a7dea4b35450decd71bf3a3ca5bdc</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>NESSUS</title>
  <ns>0</ns>
  <id>120</id>
  <revision>
    <id>143</id>
    <timestamp>2009-06-04T05:25:51Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1450" xml:space="preserve">[[Category:Tutorials]]

A simple guide on how to install Nessus on slackware 11.0

As you may know "Tenable" doesn't provide native packages for slackware, so we must do some tricks in order to run it.

First go and grab the package for fedora core 4 (that's what I'll be using for this example).When you are done you have to convert this package to tgz , this is done by simply using the "rpm2tgz" utility, so you do something like:
"'''rpm2tgz packagename.rpm'''". Then you should wait for a while ... after everything is done you must install the package:
"'''installpkg packagename.tgz'''"

After the package is installed, it places its files in /opt/nessus dir.Now you should do the following things:
1.Then you must copy all files from /opt/nessus/lib to /usr/local/lib and run the '''ldconfig''' utility in order to update the library list.(Only the files, not the "nessus" subfolder)
2.Now it's time for some symbol linking:
2.1 Go into /usr/lib dir and execute the following commands:
'''ln -s libcrypto.so.0 libcrypto.so.5
ln -s libssl.so.0 libssl.so.5
ln -s libdb4-4.so libdb-4.3.so'''

After you've done this you may try and run '''nessus-add-first-user''', then '''nessus-mkcrt''', and finally '''nessus -D'''

I wish you luck.And I do not take any responsibility if you crash your system or something (Most probably it won't happen)

Author: LordDoskias with a little help from iddqd
You can contact me on irc.freenode.net @ ##slackware</text>
    <sha1>3f450baa66cfcbe6a8a46f5c8b4298f4c47f827c</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>NFS and Firewall</title>
  <ns>0</ns>
  <id>121</id>
  <revision>
    <id>144</id>
    <timestamp>2009-06-04T05:26:18Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3145" xml:space="preserve">The most recent version of this document can always be found at:
http://rlworkman.net/howtos/NFS_Firewall_HOWTO
--rworkman


This document is intended to give you detailed steps for making NFS bind to
user-specified ports instead of random ports assigned by the portmapper.
This makes it *much* easier to run a firewall on the NFS server, as you don't
have to kludge something to find the NFS ports at each boot to open them with 
iptables.

First, you'll want (it's not necessary, but handy to have for later) to make
sure all of this is in /etc/services.  I made sure "NFS" is in all of what I
added or modified so that I can easily remove them (or just find them) if I 
need them later.

 bash-3.00# grep NFS /etc/services 
 sunrpc          111/tcp    rpcbind      # SUN Remote Procedure Call
 sunrpc          111/udp    rpcbind      # SUN Remote Procedure Call 
 mountd          861/udp                 # NFS mountd
 mountd          861/udp                 # NFS mountd
 rquotad         863/udp                 # NFS rquotad
 rquotad         863/tcp                 # NFS rquotad
 status          865/udp                 # NFS status (listen)
 status          865/tcp                 # NFS status (listen)
 status          866/udp                 # NFS status (send)
 status          866/tcp                 # NFS status (send)
 nfsd            2049/tcp                # NFS server daemon
 nfsd            2049/udp                # NFS server daemon
 lockd           4045/udp                # NFS lock daemon/manager
 lockd		4045/tcp		# NFS lock daemon/manager

Next, you'll need to modify your /etc/rc.d/rc.nfsd script accordingly:
For other linux distributions, find the script that starts these
daemons and add the needed flags.
* Make the quota daemon listen on port 863
  if [ -x /usr/sbin/rpc.rquotad ]; then
    echo "  /usr/sbin/rpc.rquotad -p 863"
    /usr/sbin/rpc.rquotad -p 863
  fi
* Make the mount daemon listen on port 861
  if [ -x /usr/sbin/rpc.mountd ]; then
    echo "  /usr/sbin/rpc.mountd -p 861"
    /usr/sbin/rpc.mountd -p 861
  fi
Now modify the /etc/rc.d/rc.rpc script (again, for other linux distros,
find the script that starts this daemon and add the needed flags).
On older versions (less than 11.0) of Slackware, rpc.statd is started
in rc.nfsd, so look there instead.
*Make the status daemon listen on port 865 and talk on port 866 - note that you'll have to open port 866 on the NFS clients
  if ! ps axc | grep -q rpc.statd ; then
    echo "Starting RPC NSM (Network Status Monitor):  /sbin/rpc.statd -p 865 -o 866"
    /sbin/rpc.statd -p 865 -o 866
  fi
Finally, make the lock daemon listen on port 4045 only - note that this requires 
setting module loading parameters in /etc/modules.conf (for 2.4 kernels) 
or /etc/modprobe.conf (for 2.6 kernels) or /etc/modprobe.d/options (for 
newer 2.6 kernels with module-init-tools &gt;=3.2.2; create this file if it doesn't 
already exist) - it won't hurt to set it in all of them.
You'll need to add this line to the files referenced above.
  options lockd nlm_udpport=4045 nlm_tcpport=4045

Good luck - talk to me on IRC if you have trouble.

[[Category:Tutorials]]</text>
    <sha1>60259f70c4ee2162fa3830297f5914ddbd43be8e</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>NTFS-3G</title>
  <ns>0</ns>
  <id>122</id>
  <revision>
    <id>145</id>
    <timestamp>2009-06-04T05:26:59Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8968" xml:space="preserve">[[Category:Tutorials]]

[http://www.ntfs-3g.org/ NTFS-3G] is a fully functional NTFS writer/reader built as a userspace filesystem, thanks to the magic of [http://fuse.sourceforge.net/ FUSE]. For another way to get read/write support of NTFS filesystem, see [[Captive NTFS]].

Please note that the following instructions are made in such a way that it should be easy to [[SlackBuild Scripts|create a SlackBuild script]] or [[Building A Package|make a package]].


== Installing FUSE ==
Since [http://www.ntfs-3g.org/ NTFS-3G] is not implemented as a kernel module, it has to find ways to communicate with the kernel and make its services as a filesytem available to any other process.
To do this, it uses a library called [http://fuse.sourceforge.net/ FUSE] (which stands for Filesystem in Userspace).

Slackware 11.0's 2.6.17.13 kernel already has FUSE support compiled, but the version which comes with this kernel lacks a few features (such as proper block devices handling) and that seems to annoy NTFS-3G, so we'll begin by installing a newer FUSE.

If you have FUSE already installed, please check that it is at least 2.6.0 with 
this command:


   $ sudo /sbin/modprobe fuse
   $ dmesg | grep fuse
   kernel: fuse init (API version 7.8)
   kernel: fuse distribution version: '''2.6.0'''

If it doesn't print the ''distribution version'' line then you have a version older than 2.6.

=== Getting FUSE to work ===
You have to make sure that the version of FUSE you're downloading is &amp;ge; 2.6.0 and &amp;ne; 2.6.2, unless you like annoying warnings and malfunctioning filesystems.

I prefer to do my building in a /tmp folder, so I'll start with this:

   mkdir  /tmp/fusebuild
   cd /tmp/fusebuild

First, you have to get the most recent version (at the time of writing, 2.6.3):

   wget http://superb-west.dl.sourceforge.net/sourceforge/fuse/fuse-2.6.3.tar.gz

(There are several other mirrors. You can go to [http://sourceforge.net/project/showfiles.php?group_id=121684&amp;package_id=132802 SF.net's download page] to find another mirror.)

Then you can extract the source.

   tar zxf fuse-2.6.3.tar.gz
   cd fuse-2.6.3

Before compiling, you have to make sure that your kernel sources and .config matches your running kernel. If you've build your own kernel (and haven't touched the source since then) then you should be fine. Otherwise, if you're running Slack's binary kernels, you'll have to install [http://packages.slackware.it/search.php?v=11.0&amp;t=1&amp;q=%22kernel-source%22 the kernel source]. Usually, that's enough. Should you have some other kernel-related trouble, check out the [http://fuse.sourceforge.net/ FUSE homepage].

Now, you can compile your fuse library/tools/module

   # You might want to change the CFLAGS or the --with-kernel path
   # Also, take note of the --exec-prefix=/ this allows you to have
   # /usr mounted later (or even as an NTFS partition, but why would
   # you want that?) and still mount NTFS drives. You may as well
   # remove it, and everything will get in /usr/*
   CFLAGS="-O2 -march=i486 -mtune=i686" ./configure \
   --enable-kernel-module \
   --with-kernel=/lib/modules/$(uname -r)/build \
   --enable-lib \
   --enable-util \
   --enable-example \
   --localstatedir=/var \
   --sysconfdir=/etc \
   --prefix=/usr \
   --exec-prefix=/ \
   --program-prefix= \
   --profram-suffix= \
   i486-slackware-linux
   
   make
   
   # Do the following steps as root:
   make install
   
   # This is only necesary if you didn't change/remove
   # the --exec-prefix option at configure time.
   mv /lib/pkgconfig/* /usr/lib/pkgconfig/
   rmdir /lib/pkgconfig
   
   cat &gt; /etc/udev/rules.d/99-fuse.rules &lt;&lt;_EOF_
   KERNEL=="fuse", MODE="0666"
   _EOF_
   
   # Note that fuse will also put some stuff in /etc/init.d, let's
   # put it where it belongs.
   mv /etc/init.d/fuse /etc/rc.d/rc.fuse
   rmdir /etc/init.d
   
   # You might also want to add this at the bottom of
   # /etc/rc.d/rc.modules:
   # [ -x /etc/rc.d/rc.fuse ] &amp;&amp; /etc/rc.d/rc.fuse start


If you're making a slackbuild or building a package, instead issue:
   
   mkdir -p /tmp/tmproot
   make install DESTDIR=/tmp/tmproot
   
   # Also prepend /tmp/tmproot to the paths references which come after
   # that. You may have to actually create some of those paths.
   

To make sure that everything is working so far, let's run a simple test (as root):

   cd example
   mkdir /tmp/mntpoint
   
   # Run this as root.
   ./hello /tmp/mntpoint &amp; #you can add a "-d" flag if you want to see what's goinng on.
   
   ls -l /tmp/mntpoint
   # You should see something like this:
   # total 0
   # -r--r--r--   1 root root 13 Jan  1 1970 hello
   
   cat /tmp/mntpoint/hello
   # It should print the famous "Hello, World!".
   # If it did, then FUSE is working as it  should.
   
   # Run this also as root.
   fusermount -u /tmp/mntpoint
   
   rmdir /tmp/mntpoint
   cd ..

If everything is fine so-far, you can  delete the cruft left behind:

   cd
   rm -rf /tmp/fusebuild


== Installing NTFS-3G ==
Now you should be ready to install NTFS-3G.
Again, let's begin by making a build directory:

   mkdir /tmp/ntfs-3gbuild
   cd /tmp/ntfs-3gbuild

=== Getting the greatest &amp; latest ===
Then we can get the latest NTFS-3G. Note that there are usually two or three releases per month, so make sure to check [http://www.ntfs-3g.org/ the homepage] to get the latest version.

   wget http://www.ntfs-3g.org/ntfs-3g-0.20070207-RC1.tgz

=== Configuring and compiling ===
Compiling NTFS-3G is actually quite easy, it is one of those programs were compiling "just works".

First, you have to untar the source:

  tar zxf ntfs-3g-0.20070207-RC1.tgz
  cd ntfs-3g-0.20070207-RC1

Next, let's configure the sources:

  CFLAGS="-O2 -march=i486 -mtune=i686" ./configure \
  --prefix=/usr \
  --exec-prefix= \
  --program-prefix= \
  --program-suffix= \
  i486-slackware-linux

That usually works without problems, unless you are missing libfuse. If so, you  must see the above steps on configuring FUSE.

Now compile and install.

  make
  
  make install
  
  # If you're making a package or a slackbuild, you will have to issue the next trick to avoid some st*pid error:
  #
  # make install LDCONFIG=/bin/true DESTDIR=$YOUR_ROOT_DIR
  #
  # also, you'll have to make sure that the mount.ntfs-3g.8 symlink points to the right (maybe gzipped) ntfs-3g.8 file.

And that's pretty much it.

== Mounting with NTFS-3G ==
So, how to mount something? NTFS makes mounting NTFS filesystems as easy as with other filesystems:

  root@damned-02# mount -t ntfs-3g /dev/sda1 /mnt/pendrive

If you fail to see some files which you know are there, you should try using
the locale option, specially if that partition is used by a non-english
Windos.

For example:
:For some reason I don't know, My WinXP in Spanish uses en_US for character encoding (not even en_US.utf8),  to see my files with "special" chars (mostly &amp;aacute;, &amp;eacute;, &amp;iacute;, &amp;oacute;, &amp;uacute; and &amp;ntilde;) I have to use:

  root@damned-02# mount -t ntfs-3g -o '''locale=en_US''' /dev/sda1 /mnt/pendrive

The only way I know to find the right locale is to do some trial and error.
If when you mount without locale, it shows all your files, then your correct
locale is the one printed by

  echo $LANG

To see which locales you have support for (there are 342 in Slack 11.0), type

  locale -a | less

=== Using /etc/fstab ===
You can use /etc/fstab to mount ntfs partitions at boot time. For example,
my laptop's fstab looks like this:

    /dev/hda1        swap             swap        defaults         0   0
    /dev/hda3        /                jfs         defaults         1   1
    /dev/hda4        /home            jfs         noatime          1   2
    /dev/hda2        /mnt/win         ntfs-3g     dmask=0007,fmask=0117,gid=6,locale=en_US  1   0
    /dev/cdrom       /mnt/cdrom       auto        noauto,group,ro  0   0
    devpts           /dev/pts         devpts      gid=5,mode=620   0   0
    proc             /proc            proc        defaults         0   0

This gives read/write access to anyone in the disk group (gid=6) to the
NTFS partition at hda2 mounted in /mnt/win.

Note, though, that "mount" reports the filesystem as "fuseblk" (unless you have
a version of fuse &amp;lt; 2.6 which won't allow you to mount block devices anyway).

=== Allowing users ===
NTFS-3G can let users other than root mount NTFS filesystems, but you'll have to
set the suid flag in /bin/ntfs-3g. This applies &lt;b&gt;even when using fstab&lt;/b&gt; with the ''users'' option.

So for this to work:

   /dev/sda1        /mnt/pendrive   ntfs-3g     noauto,users       0   0

You have to do (as root):

   # chmod 4755 /bin/ntfs-3g

== RTFMs ==
If you have any problems or doubts:

*http://www.ntfs-3g.org/
*:spec. http://www.ntfs-3g.org/support.html
*http://www.linux-ntfs.org
*http://fuse.sourceforge.net

If you find any error in this tutorial, don't forget this is a wiki and don't hesitate fixing or updating or improving or ...</text>
    <sha1>bb7236739d73d332f6dbd515eb46cf5ba20484a2</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>NVIDIA Graphics</title>
  <ns>0</ns>
  <id>123</id>
  <revision>
    <id>146</id>
    <timestamp>2009-06-04T05:27:35Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2077" xml:space="preserve">[[Category:Hardware]]

= Introduction =

There are three main drivers for nvidia graphics card on linux, one of which is shipped with slackware:

* nv (shipped with slackware) - this provides basic 2d acceleration, not 3d
* nvidia (NVidia's proprietary driver) - this is the generally recommended driver, providing good 2d and 3d performance
* nouveau - an attempt to reverse-engineer the nvidia driver; not particular usable or stable

This article assumes you want the 'nvidia' driver; if you do not, generic (IE not slackware-specific) documentation available.

= Obtaining the driver =

The driver can be found at [http://www.nvidia.com/object/unix.html].

= Installing the driver =

The driver must not be installed while X is running; if X is running, stop X, install the driver, then start X again how you normally would (eg "telinit 4", or "startx").

Download the driver, then "sh FILENAME.run" in the directory you downloaded it do, replacing "FILENAME" with the name of the file you downloaded.

== XOrg config ==

There are two options:

=== nvidia-xconfig ===

This is an automated tool, that the above installer offers to run for you. It attempts to modify your XOrg.conf automatically to use the nvidia driver.

=== Manual Editing ===

Find the section relating to your graphics card in /etc/X11/xorg.conf, and change the driver to "nvidia". If you want to change the default settings, for example, add dual-head support, see the readme installed into /usr/doc/NVIDIA_GLX-1.0/.

= Checking It's Working =

* Check "nvidia-settings" runs in X
* Check "glxinfo | grep direct" returns "direct rendering: Yes"
* Check "glxgears" gives a reasonable result (google for comparisons)

Pay close attention to specific model of graphics card when checking for suitable glxgears results; keep in mind that glxgears isn't really a good 'benchmark', but should indicate if DRI is working properly or not. For example:

* On an Intel X3100, a good result is somewhere around 1000 FPS
* On an NVidia 7800GTX, a good result is somewhere above 12000 (though 15k is fairly normal)</text>
    <sha1>c285d7d7e02d6b2a7668b15fac70e0131ddabf81</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>NVIDIA-Prompted-Kernel-Compile</title>
  <ns>0</ns>
  <id>124</id>
  <revision>
    <id>147</id>
    <timestamp>2009-06-04T05:28:04Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9403" xml:space="preserve">[[Category:Tutorials]]

=== nVidia Graphics Driver Installation &amp; Kernel Recompile in Slackware 12.0  ===

====Warning!====
----

:Please do all this at your own risk.  If you change your kernel and cause any damage to your system, you and only you are responsible for it.  By providing this tutorial I do not take any responsibility for any damages or losses to your system.  This is a disclaimer!

==== Background Info &amp; Rationale for Kernel Recompile ====
----
:I recently bought a used ''Geforce N6200'' video card (nvidia chipset) to replace the ''ATI Radeon 9200SE'' that suddenly died on me.  I ran Xorg configuration utility ''xorgconfig'' to set the new card up.  Slackware 12.0 ships with a generic ''nv'' driver for nvidia cards, but it does not support graphics acceleration and/or direct rendering.  That means no games and no graphic heavy websites.  Fortunately, nvidia provides a Linux binary driver for your video card that will do direct rendering and 3D acceleration just fine, although the driver is closed-source.  But hey, at least it works.

:Assuming that you're running Slackware 12.0 and using huge generic kernel 2.6.21.5 or newer or the smp version of it, you are going to face some problems compiling the nvidia driver against that kernel.  The nvidia installer utility compiles the binary driver to suit your kernel.  In Slackware 12.0 the support for Riva framebuffer is enabled by default in the huge-2.6.21.5 and huge-2.6.21.5-smp kernels and it is a problem for the nvidia installer utility.  As soon as it notes the riva support enabled in the kernel header files, it quits and the driver module compilation fails.  Most people will experience this problem in Slackware 12.0.  The solution is to disable riva framebuffer support from the kernel and recompile it.

:At the end of this tutorial you will have a fresh kernel compiled for your system, the nvidia driver compiled against this kernel and installed as kernel module and 3D graphics acceleration as well as direct rendering enabled.  So let's begin taking one thing at a time.


==== Back Up Current Kernel &amp; Kernel Modules ====
----

:It is important that you have a backup of your currently working kernel modules so if the new kernel fails, you would still be able to use the old kernel to boot the system.  Let's play safe.  Important: All steps in this tutorials are done as superuser.

 cd /lib/modules
 ls
 2.6.21.5  2.6.21.5-smp

:Above currently installed kernels on your system are listed.  Rename the kernel you're using to something like ''kernel-name''.backup.  If you do not know which kernel you're using, do the following.  The output of it should list the kernel you're using.  Once you find it out, rename it as follows.

 uname -a
 Linux 2.6.21.5 #1 Sun Mar 16 14:46:57 CDT 2008 i686 AMD Athlon(tm) AuthenticAMD GNU/Linux

 mv 2.6.21.5 2.6.21.5-backup
 ls
 2.6.21.5-smp 2.6.21.5-backup

==== Kernel Configuration and Recompile ====
----

:Now that we have a backup of our current kernel and its modules, its time to proceed with configuration and recompiling the kernel.  Change to the kernel source directory and copy the current kernel config file to the kernel source directory

 cd /usr/src/linux
 cp /boot/config .config  #Note that config in /boot has no dot before it, but when we copy it, we include a dot prefix.

This step will copy your current configuration so we can use it as a reference for further steps.  Now let's begin kernel configuration

 make menuconfig

This should give you a nice ''ncurses'' style detailed graphical menu of kernel configuration. 

 Select Device Drivers &gt; Graphics Support &gt; 

:Scroll down to ''Riva Framebuffer Support'' (not ''nvidia Riva Support'') and press space bar twice.  First space bar press will change the &lt;M&gt; to &lt;*&gt; and second will change &lt;*&gt; to &lt; &gt; (blank).  Now press ''exit'' three times.  The menuconfig will ask you if you want to save the changes.  Select ''Yes'' and quit.  We have now removed Riva Framebuffer Support from kernel configuration, the culprit for failing nvidia driver module compilation.

:It's time to compile the kernel.  Do the following:
 
 make bzImage

:This is a good time to take a break for any of these:  Coffee / Tea / Cigarette / Quick run to the grocery store.  In short, depending upon how fast your procesor is, this step will take anywhere between 15 minutes to an hour.  If everything goes fine, it will compile a new kernel and install newly compiled modules in /lib/modules/.  If you get errors, something went wrong and you'll need to get some help from kernel documentation or ask in ##slackware on IRC host ''freenode.net''

:Now that we have a kernel compiled, its time to compile and install kernel modules

 make modules &amp;&amp; make modules_install

:Again, this step will take some time.  But it will be worth the wait.  In the basic kernel, there is close to 1000 modules that need to be compiled.  Once this step is finished and you did not get any errors, its time to make sure the kernel bzImage was created and the modules were installed to the appropriate location.

 pwd
 /usr/src/linux
 cd arch/i386/boot
 pwd
 /usr/src/linux/arch/i386/boot
 ls
 Makefile  bootsect.S  '''bzImage'''     edd.S  mtools.conf.in  setup.S  tools    vmlinux.bin
 bootsect  bootsect.o  compressed  install.sh  setup  setup.o  video.S

:bzImage is your newly compiled kernel without Riva framebuffer support.

 cd /lib/modules
 ls
 2.6.21.5  2.6.21.5-smp  2.6.21.5-backup

The first entry above is the location of your newly installed kernel modules.

==== Install New Kernel And Update lilo.conf ====
----

:Time to install the new kernel and notify your boot loader of its existence.

 cd /usr/src/linux/arch/i386/boot
 cp bzImage /boot
 
:Open your favorite text editor and add following lines to your boot loader (typically /etc/lilo.conf)

 cd /etc
 emacs -nw lilo.conf

 #Linux bootable partition config begins
  image = /boot/bzImage
  root = /dev/hda2 #or whatever partition your / is located on 
  label = New-Kernel #You can name it whatever you want. Just don't name it the same as the old kernel
 #Linux bootable partition config ends

:Save file, close it and run lilo so the new changes take effect.

 lilo
 Added *Linux
 Added *New-Kernel

:Excellent!  It's time to test the new kernel.  When you reboot, lilo will now present you with two choices for kernel, use the New-Kernel and boot.  If somehow it fails, you can always go back to the old kernel.  Just rename the /lib/modules/2.6.21.5-backup as 2.6.21.5 and rename the new kernel modules as something else.  You see how important it was for us to backup the kernel as well as kernel modules in the beginning?

:Assuming that your new kernel booted just fine and you had a fully functional system back up, its time to get the nVidia graphics driver from nvidia.com and install it.  The current incarnation of nVidia driver is version # 169.12.  Either use your favorite browser to download the driver from http://www.nvidia.com/Download/index.aspx?lang=en-us  or do the following:

 cd /tmp
 wget http://us.download.nvidia.com/XFree86/Linux-x86/169.12/NVIDIA-Linux-x86-169.12-pkg1.run

Make the installer utility executable and execute it

 chmod 755 NVIDIA-Linux-x86-169.12-pkg1.run
 ls -la
 -rwxr-xr-x  1 user groupname 17636559 2008-03-17 13:06 NVIDIA-Linux-x86-169.12-pkg1.run

Before we execute it, we need to exit the X server.  

 telinit 3    #This changes runlevel to 3, shuts down the X server and drops you off at the terminal 
 sh ./NVIDIA-Linux-x86-169.12-pkg1.run

:This installer utility first tries to find a pre-compiled driver for your kernel which it would not find, then it tries to download it via ftp from nvidia servers which fails too, and finally it proceeds to compile the driver kernel module against your newly installed bzImage kernel.  This time, there is no riva framebuffer in the kernel header files and so this step should not fail.  Should it fail, ask for help in your local LUG or the highly knowledgeable folks at ##slackware in irc channel freenode.net

==== Updating X.Org Configuration File ====
----

:After the installer utility finishes compiling and installing kernel module for the nvidia driver, it will ask you if you want it to make appropriate changes to your /etc/X11/xorg.conf.  I personally chose not to, because I did not want my already customized xorg.conf to be messed with by a third party software.  I simply changed the driver name from '''nv''' to '''nvidia''' in the &lt;device&gt; section of /etc/X11/xorg.conf

:That's it folks.  You now have a new kernel, new kernel modules and nvidia driver with 3D acceleration and direct rendering.  Check direct rendering as follows:

 glxinfo | grep dri

:Third line of the output should tell you that Direct Rendering has been enabled.  Now its time to fire up X server and check your new driver.

 telinit 4

:This should launch X server, you should be seeing a flash of nvidia screen and then back to your favorite window manager.  If everything went fine, you should go ahead and check video performance with some game, or a graphics intensive website or such.

==== Acknowledgements ====
----

:This article benefited substantially by input from ##slackware (irc.freenode.net) user  '''InspectorCluseau'''

:If you have any questions or if you find a mistake in this tutorial, please contact me at [mailto:crypticlineage@gmail.com]</text>
    <sha1>b215dfaa343899f8728191f252eb1737761e044b</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Networking 101</title>
  <ns>0</ns>
  <id>125</id>
  <revision>
    <id>148</id>
    <timestamp>2009-06-04T05:28:45Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="116" xml:space="preserve">This link is Alan Hicks' "Networking 101" class.  http://www.lizella.net/networking_101.txt


[[Category:Tutorials]]</text>
    <sha1>ca3d24cd3965a14cdc64a5939a9ad5867eea4228</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>NTPD</title>
  <ns>0</ns>
  <id>126</id>
  <revision>
    <id>149</id>
    <timestamp>2009-06-04T05:29:28Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2388" xml:space="preserve">'''ntpd (Network Time Protocol Daemon)'''&lt;br&gt;
The ntpd program is an operating system daemon which sets and maintains the system time of day in synchronism with Internet standard time servers. It is a complete implementation of the Network Time Protocol (NTP) version 4, but also retains compatibility with version 3, as defined by RFC-1305, and version 1 and 2, as defined by RFC-1059 and RFC-1119, respectively.


'''Automating the time synchronization'''&lt;br&gt;
You have two choices for automatic time updating, you can run ntpd all the time as a background process or you can have it run once in awhile (if you are tight on system resources).

Running ntpd all the time-&lt;br&gt;
::Just enable rc.ntpd script:
::::&lt;code&gt;chmod +x /etc/rc.d/rc.ntpd&lt;/code&gt;
::After the script is enabled you probably will want ntpd to start immediately so, can either restart the system or manually start ntpd with:
::::&lt;code&gt;/etc/rc.d/rc.ntpd start&lt;/code&gt;

Running ntpd once in awhile-&lt;br&gt;
::You have many choices but the two best ones are:
:::1) Set up a cron job
:::2) Set up a /etc/rc.d/rc.local entry and update the time on start-up only.
::Either way, you need to add the following commands into your cron job or rc.local script:
::::&lt;code&gt;ntpdate -o 4 pool.ntp.org&lt;/code&gt; &lt;---(updates the time)
::::&lt;code&gt;hwclock --systohc&lt;/code&gt; &lt;-----------------(saves the time to the hardware clock)


'''Manually updating the time'''&lt;br&gt;
Issue the following commands:
::::&lt;code&gt;ntpdate -o 4 pool.ntp.org&lt;/code&gt;
::::&lt;code&gt;hwclock --systohc&lt;/code&gt;


'''Choosing the right time server'''&lt;br&gt;
On ntp.org you will find a complete list with the right time server for you.
Let's say you live in germany, then you will choose &lt;code&gt;de.pool.ntp.org&lt;/code&gt;. A complete List is available at http://support.ntp.org/bin/view/Servers/NTPPoolServers


'''DST changes'''&lt;br&gt;
If your time is off due to DST changes, you must update the &lt;code&gt;/etc/localtime&lt;/code&gt; file.  You should be able to find a correct file on the internet and just replace the old &lt;code&gt;/etc/localtime&lt;/code&gt; file.

NOTE: Slackware 11 is immune to the 2007 DST changes.


'''Possible Errors &amp; Fixes'''&lt;br&gt;
ERROR: "Unable to contact time server:" error with KDE time Control Module.&lt;br&gt;
FIX: Make sure ntpd is NOT running.  If ntpd is running, manual ntp and KDE ntp updates will return errors due to ntpd having control of the ntp port.


[[Category:Tutorials]]</text>
    <sha1>9e7d314e29cb984ea5d205b6d027e7a0b4274e3f</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>OpenVPN</title>
  <ns>0</ns>
  <id>127</id>
  <revision>
    <id>150</id>
    <timestamp>2009-06-04T05:29:57Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14136" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.

__TOC__
== Instalasi ==

Download source dari [http://openvpn.net openvpn.net]

download versi 2.0

instalasi Lzo
&lt;pre&gt;
tar zxvf lzo-1.08.tar.gz
cd lzo-1-08.tar.gz
./configure --prefix=/usr
make ; make install-strip
&lt;/pre&gt;
insalasi OpenVPN
&lt;pre&gt;
tar zxvf openvpn-2.0.tar.gz
cd openvpn-2.0
./configure --prefix=/usr \
--sysconfdir=/etc/openvpn \
--enable-pthread \
--enable-iproute2 \
--with-ssl \
--with-lzo-header=/usr/include \
--with-lzo-lib=/usr/lib \
--with-ifconfig \
--with-route \
--with-mem-check=dmalloc 
make ; make install-strip
&lt;/pre&gt;
== Konfigurasi ==

==Konfigurasi Sertifikat==

Simpan seluruh sertifikat di '''''/etc/openvpn/certs'''''
&lt;pre&gt;
This is a small RSA key management package,
based on the openssl command line tool, that
can be found in the easy-rsa subdirectory
of the OpenVPN distribution.

These are reference notes.  For step
by step instructions, see the HOWTO:

http://openvpn.net/howto.html

INSTALL

1. Edit vars.
2. Set KEY_CONFIG to point to the openssl.cnf file
   included in this distribution.
3. Set KEY_DIR to point to a directory which will
   contain all keys, certificates, etc.  This
   directory need not exist, and if it does,
   it will be deleted with rm -rf, so BE
   CAREFUL how you set KEY_DIR.
4. (Optional) Edit other fields in vars
   per your site data.  You may want to
   increase KEY_SIZE to 2048 if you are
   paranoid and don't mind slower key
   processing, but certainly 1024 is
   fine for testing purposes.  KEY_SIZE
   must be compatible across both peers
   participating in a secure SSL/TLS
   connection.
5  . vars
6. ./clean-all
7. As you create certificates, keys, and
   certificate signing requests, understand that
   only .key files should be kept confidential.
   .crt and .csr files can be sent over insecure
   channels such as plaintext email.
8. You should never need to copy a .key file
   between computers.  Normally each computer
   will have its own certificate/key pair.

BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY

1. ./build-ca
2. ca.crt and ca.key will be built in your KEY_DIR
   directory

BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)

1. ./build-inter inter
2. inter.crt and inter.key will be built in your KEY_DIR
   directory and signed with your root certificate.

BUILD DIFFIE-HELLMAN PARAMETERS (necessary for
the server end of a SSL/TLS connection).

1. ./build-dh

BUILD A CERTIFICATE SIGNING REQUEST (If
you want to sign your certificate with a root
certificate controlled by another individual
or organization, or residing on a different machine).

1. Get ca.crt (the root certificate) from your
   certificate authority.  Though this
   transfer can be over an insecure channel, to prevent
   man-in-the-middle attacks you must confirm that
   ca.crt was not tampered with.  Large CAs solve this
   problem by hardwiring their root certificates into
   popular web browsers.  A simple way to verify a root
   CA is to call the issuer on the telephone and confirm
   that the md5sum or sha1sum signatures on the ca.crt
   files match (such as with the command: "md5sum ca.crt").
2. Choose a name for your certificate such as your computer
   name.  In our example we will use "mycert".
3. ./build-req mycert
4. You can ignore most of the fields, but set
   "Common Name" to something unique such as your
   computer's host name.  Leave all password
   fields blank, unless you want your private key
   to be protected by password.  Using a password
   is not required -- it will make your key more secure
   but also more inconvenient to use, because you will
   need to supply your password anytime the key is used.
   NOTE: if you are using a password, use ./build-req-pass
   instead of ./build-req
5. Your key will be written to $KEY_DIR/mycert.key
6. Your certificate signing request will be written to
   to $KEY_DIR/mycert.csr
7. Email mycert.csr to the individual or organization
   which controls the root certificate.  This can be
   done over an insecure channel.
8. After the .csr file is signed by the root certificate
   authority, you will receive a file mycert.crt
   (your certificate).  Place mycert.crt in your
   KEY_DIR directory.
9. The combined files of mycert.crt, mycert.key,
   and ca.crt can now be used to secure one end of
   an SSL/TLS connection.

SIGN A CERTIFICATE SIGNING REQUEST

1. ./sign-req mycert
2. mycert.crt will be built in your KEY_DIR
   directory using mycert.csr and your root CA
   file as input.

BUILD AND SIGN A CERTIFICATE SIGNING REQUEST
USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY -- this
script generates and signs a certificate in one step,
but it requires that the generated certificate and private
key files be copied to the destination host over a
secure channel.

1. ./build-key mycert (no password protection)
2. OR ./build-key-pass mycert (with password protection)
3. OR ./build-key-pkcs12 mycert (PKCS #12 format)
4. OR ./build-key-server mycert (with nsCertType=server)
5. mycert.crt and mycert.key will be built in your
   KEY_DIR directory, and mycert.crt will be signed
   by your root CA. If ./build-key-pkcs12 was used a
   mycert.p12 file will also be created including the
   private key, certificate and the ca certificate.

IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.
IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.

(4) Sign server certificates with one CA and client certificates
    with a different CA.  The client config "ca" directive should
    reference the server-signing CA while the server config "ca"
    directive should reference the client-signing CA.

NOTES

Show certificate fields:
  openssl x509 -in cert.crt -text
&lt;/pre&gt;
&lt;pre&gt;
# cd easy-rsa
# vi vars
. vars
./clean-all

## BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY
./build.ca

## BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)
./build-inter inter

## BUILD DIFFIE-HELLMAN PARAMETERS (necessary for the server end of a SSL/TLS connection).
./build.dh

## BUILD A CERTIFICATE SIGNING REQUEST 
## (If you want to sign your certificate with a root certificate controlled by another individual 
## or organization, or residing on a different machine)

./build-req mycert
## SIGN A CERTIFICATE SIGNING REQUEST
./sign-req mycert

## BUILD AND SIGN A CERTIFICATE SIGNING REQUEST USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY
./build-key mycert (no password protection)
OR 
./build-key-pass mycert (with password protection)
OR 
./build-key-pkcs12 mycert (PKCS #12 format)
OR 
./build-key-server mycert (with nsCertType=server)
&lt;/pre&gt;

==Konfigurasi Server==

edit server.conf '''''vi /etc/openvpn/server.conf'''''
&lt;pre&gt;
## Mode Server
mode server

## Local Host Name/IP Server
;local 127.0.0.1

## Protocol
;proto tcp
proto udp

## Port
; port 1194

## Device Interface
;dev tap
dev tun

## TAP-Win32 adapter name
;dev-node MyTap

## SSL/TLS 
## root certificate (ca)
## certificate (cert)
## private key (key)
ca /etc/openvpn/certs/ca.crt
cert /etc/openvpn/certs/server.crt
key /etc/openvpn/certs/server.key

## Diffie hellman parameters
dh dh1024.pem

## VPN subnet
server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

##ethernet bridging
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

## dhcpcaveats
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

;learn-address ./script

## dhcpcaveats
;push "redirect-gateway"
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

##
;client-to-client

## same "COMMON NAME" certificate/key
;duplicate-cn

## Status Connection
keepalive 10 120

## tls-auth key
;tls-auth ta.key 0 

## Cryptographic cipher
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

## Link Compresion
comp-lzo

## Max Client Connections
;max-clients 100

## daemon privileges (non windows saja)
user nobody
group nobody

persist-key
persist-tun

## Openvpn Log
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

## Output Log
status /var/log/openvpn/openvpn-status.log

## Log Verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## Repeating Messages
;mute 20

## Pid File
writepid /var/run/openvpn.pid
&lt;/pre&gt;

'''Routing'''

&lt;pre&gt;
echo 1 &gt; /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.4.0.2
&lt;/pre&gt;

'''Firewall'''
&lt;pre&gt;
iptables -A INPUT -p udp -s 1.2.3.4 --dport 1194 -j ACCEPT
OR
iptables -A INPUT -p udp --dport 1194 -j ACCEPT

## Tun Device
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT

## Tap Device
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
&lt;/pre&gt;

==Konfigurasi client==

edit file client.conf '''''vi /etc/openvpn/client.conf'''''
&lt;pre&gt;
## Config
client

## Device Interface
;dev tap
dev tun

## Tap adapter name (Win only)
;dev-node MyTap

## Conectivity
;proto tcp
proto udp

## Server [hostname/ip] [port]
remote my-server-1 1194
;remote my-server-2 1194

## load-balancing
;remote-random

## resolve host name OpenVPN server
resolv-retry infinite

# local port
nobind

## privileges (non windows saja)
user nobody
group nobody

## preserve
persist-key
persist-tun

## HTTP proxy
;http-proxy-retry 
;http-proxy [proxy server] [proxy port]

## duplicate packet warnings
;mute-replay-warnings

## SSL/TLS parms
/etc/openvpn/certs/ca ca.crt
/etc/openvpn/certs/cert client.crt
/etc/openvpn/certs/key client.key

## nsCertType key
;ns-cert-type server

## tls-auth key
;tls-auth /etc/openvpn/certs/ta.key 1

## Cryptographic cipher
;cipher x

## Link compression
comp-lzo

## verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## repeating messages
;mute 20
&lt;/pre&gt;
'''Routing'''
&lt;pre&gt;
route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.4.0.1 
&lt;/pre&gt;


==Example==

'''Example 1:''' A simple tunnel without security&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 --verb 9
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 --verb 9 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 2:''' A tunnel with static-key security (i.e. using a pre-shared secret)&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--verb 5 --secret key
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--verb 5 --secret key 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 3:''' A tunnel with full TLS-based security &lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--tls-client --ca tmp-ca.crt --cert client.crt --key client.key \
--reneg-sec 60 --verb 5 
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--tls-server --ca tmp-ca.crt --cert server.crt --key server.key \
--reneg-sec 60 --verb 5 --dh dh1024.pem
&lt;/pre&gt;

On May:

    ping 10.4.0.2 

On Jun:

    ping 10.4.0.1

== External Links ==

* http://dmalloc.com/
* http://valgrind.org/
* http://www.oberhumer.com/opensource/lzo/
* http://openvpn.net/
* http://openvpn.net/howto.html
* http://openvpn.net/1xhowto.html (Old-v1.06)
* http://openvpn.net/man.html</text>
    <sha1>a1601b7ee4db3b7301b533a706c6829931779591</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>151</id>
    <parentid>40</parentid>
    <timestamp>2009-06-06T21:14:42Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Updating the Notice with a new link and completion progress</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3493" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==NOTICE==
After a long time and numerous upgrades, the DB finally caved in on itself. This is a fresh start. [http://slackwiki.org/old/index.php?title=Special:AllPages The old Wiki can be found here.] The data is still there, any help copying the old pages over here to the new Wiki would be greatly appreciated. UPDATE: Pages beginning with letters A through O have been copied.

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>26a20c5fecca7229dab9f0df98029cbb2f9219b6</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Perl</title>
  <ns>0</ns>
  <id>128</id>
  <revision>
    <id>152</id>
    <timestamp>2009-06-06T21:16:12Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="624" xml:space="preserve">[[Category:Tips]]

==mod_perl and Apache==

Here is a guide to installing mod_perl on Apache (out of the box, Slackware 12.0 runs perl as a cgi script): [[mod_perl|Mod_perl on Slackware 12.0]]

==Embedded Perl==

Embedded Perl is a way you can put a chunk of perl code in the middle of an html file, and apache will run the perl code and put it's results at that point in the html before it sends the page to the remote browser.  It's older and a bit arcane, most people would use mod_perl or cgi perl these days.  [[embedded_perl|Embedded Perl on Slackware 12.0]]

==Modules==
[[Perl_Modules|How to deal with Perl Modules]]</text>
    <sha1>02f2783b3798ed2a7b6491f9319cffd3dd728ae8</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>Perl Modules</title>
  <ns>0</ns>
  <id>129</id>
  <revision>
    <id>153</id>
    <timestamp>2009-06-06T21:17:50Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1873" xml:space="preserve">[[Category::Tutorials]]
==Getting To The CPAN Prompt==
To administer your Perl modules you must use the CPAN prompt. To get to the CPAN prompt, &lt;b&gt;as root&lt;/b&gt; type:

::&lt;code&gt;perl -MCPAN -e shell&lt;/code&gt;

If this is the first time that you have entered the CPAN shell, you will be asked some set-up questions that will allow the shell to access CPAN's servers to get modules.  Just read the questions and answer them.

If you ever need to re-run the set-up again, enter the CPAN shell and then type:

::&lt;code&gt;o conf init&lt;/code&gt;


==Listing The Installed Modules==
As of Slackware 10.2 and Perl 5.8.7- you can look the &lt;code&gt;perllocal.pod&lt;/code&gt; file and see the modules.

::&lt;code&gt;cat /usr/lib/perl5/5.8.7/i486-linux/perllocal.pod&lt;/code&gt;


A much cleaner way is by using this Perl program:

::&lt;code&gt;#!/usr/bin/perl&lt;/code&gt;
::&lt;code&gt;use ExtUtils::Installed;&lt;/code&gt;
::&lt;code&gt;my $instmod = ExtUtils::Installed-&gt;new();&lt;/code&gt;
::&lt;code&gt;foreach my $module ($instmod-&gt;modules())&lt;/code&gt;
:::&lt;code&gt;{&lt;/code&gt;
:::&lt;code&gt;my $version = $instmod-&gt;version($module) || "???";&lt;/code&gt;
:::&lt;code&gt;print "$module -- $version\n";&lt;/code&gt;
:::&lt;code&gt;}&lt;/code&gt;

==Installing New Modules==
From the CPAN shell prompt, type:

::&lt;code&gt;install &amp;lt;Some::Module&amp;gt;&lt;/code&gt;


==Removing Modules==

A clean way is by using this Perl program:

::&lt;code&gt;#!/usr/bin/perl -w&lt;/code&gt;
::&lt;code&gt;use ExtUtils::Packlist;&lt;/code&gt;
::&lt;code&gt;use ExtUtils::Installed;&lt;/code&gt;
::&lt;code&gt;$ARGV[0] or die "Usage: $0 Module::Name\n";&lt;/code&gt;
::&lt;code&gt;my $mod = $ARGV[0];&lt;/code&gt;
::&lt;code&gt;my $inst = ExtUtils::Installed-&gt;new();&lt;/code&gt;
::&lt;code&gt;foreach my $item (sort($inst-&gt;files($mod)))&lt;/code&gt;
:::&lt;code&gt;{&lt;/code&gt;
:::&lt;code&gt;print "removing $item\n";&lt;/code&gt;
:::&lt;code&gt;unlink $item;&lt;/code&gt;
:::&lt;code&gt;}&lt;/code&gt;
::&lt;code&gt;my $packfile = $inst-&gt;packlist($mod)-&gt;packlist_file();&lt;/code&gt;
::&lt;code&gt;print "removing $packfile\n";&lt;/code&gt;
::&lt;code&gt;unlink $packfile;&lt;/code&gt;</text>
    <sha1>b779469519919769a118b9e2c2cd1da10a9a4255</sha1>
  </revision>
</page>
<page arvcontinue="20090603021000|105">
  <title>PaRisc CrossCompile</title>
  <ns>0</ns>
  <id>130</id>
  <revision>
    <id>154</id>
    <timestamp>2009-06-06T21:19:30Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1140" xml:space="preserve">[[Category:Tutorials]]
Cross compiler setup instructions
=================================

Work in progress, a script to build the hppa-linux compiler toolchain on Slackware

#!/bin/bash

export TARGET=hppa-linux
export MACH=i686-linux
export DEST=/usr/local
export SRC=~/pabuild

mkdir -p $DEST $SRC
mkdir -p $DEST/include

cd $SRC
mkdir binutils-build
mkdir gcc-build
mkdir glibc-build
mkdir linux

# Extract binutils
tar -zxvf binutils-&lt;version&gt;.tar.gz
cd binutils-build

../binutils/configure --target=$TARGET --prefix=$DEST/hppa-linux --host=$MACH --disable-nls
make
make install
cd ..

# Extract gcc
tar -zxvf gcc-3.4.6.tar.gz
cd gcc-build
../gcc/configure --target=$TARGET --prefix=$DEST --host=$MACH --disable-shared --disable-nls

make LANGUAGES=c

cd ..


# Extract the kernel source from CVS

cd linux
make oldconfig
make dep

# Extract glibc
cd glibc-build

../glibc/configure --HOST=$TARGET --BUILD=$MACH --PREFIX=$DEST/hppa-linux
--WITH-HEADERS=$DEST/include --disable-profile --without-cvs --enable-add-ons
make
make install
cd $DEST/hppa-linux/include
ln -s ~/source/linux/include/asm .
ln -s ~/source/linux/include/linux .</text>
    <sha1>e477a63e9ed937ac527c4394b7af3fecd2a670ba</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Perl Modules</title>
  <ns>0</ns>
  <id>129</id>
  <revision>
    <id>155</id>
    <parentid>153</parentid>
    <timestamp>2009-06-06T21:20:12Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1872" xml:space="preserve">[[Category:Tutorials]]
==Getting To The CPAN Prompt==
To administer your Perl modules you must use the CPAN prompt. To get to the CPAN prompt, &lt;b&gt;as root&lt;/b&gt; type:

::&lt;code&gt;perl -MCPAN -e shell&lt;/code&gt;

If this is the first time that you have entered the CPAN shell, you will be asked some set-up questions that will allow the shell to access CPAN's servers to get modules.  Just read the questions and answer them.

If you ever need to re-run the set-up again, enter the CPAN shell and then type:

::&lt;code&gt;o conf init&lt;/code&gt;


==Listing The Installed Modules==
As of Slackware 10.2 and Perl 5.8.7- you can look the &lt;code&gt;perllocal.pod&lt;/code&gt; file and see the modules.

::&lt;code&gt;cat /usr/lib/perl5/5.8.7/i486-linux/perllocal.pod&lt;/code&gt;


A much cleaner way is by using this Perl program:

::&lt;code&gt;#!/usr/bin/perl&lt;/code&gt;
::&lt;code&gt;use ExtUtils::Installed;&lt;/code&gt;
::&lt;code&gt;my $instmod = ExtUtils::Installed-&gt;new();&lt;/code&gt;
::&lt;code&gt;foreach my $module ($instmod-&gt;modules())&lt;/code&gt;
:::&lt;code&gt;{&lt;/code&gt;
:::&lt;code&gt;my $version = $instmod-&gt;version($module) || "???";&lt;/code&gt;
:::&lt;code&gt;print "$module -- $version\n";&lt;/code&gt;
:::&lt;code&gt;}&lt;/code&gt;

==Installing New Modules==
From the CPAN shell prompt, type:

::&lt;code&gt;install &amp;lt;Some::Module&amp;gt;&lt;/code&gt;


==Removing Modules==

A clean way is by using this Perl program:

::&lt;code&gt;#!/usr/bin/perl -w&lt;/code&gt;
::&lt;code&gt;use ExtUtils::Packlist;&lt;/code&gt;
::&lt;code&gt;use ExtUtils::Installed;&lt;/code&gt;
::&lt;code&gt;$ARGV[0] or die "Usage: $0 Module::Name\n";&lt;/code&gt;
::&lt;code&gt;my $mod = $ARGV[0];&lt;/code&gt;
::&lt;code&gt;my $inst = ExtUtils::Installed-&gt;new();&lt;/code&gt;
::&lt;code&gt;foreach my $item (sort($inst-&gt;files($mod)))&lt;/code&gt;
:::&lt;code&gt;{&lt;/code&gt;
:::&lt;code&gt;print "removing $item\n";&lt;/code&gt;
:::&lt;code&gt;unlink $item;&lt;/code&gt;
:::&lt;code&gt;}&lt;/code&gt;
::&lt;code&gt;my $packfile = $inst-&gt;packlist($mod)-&gt;packlist_file();&lt;/code&gt;
::&lt;code&gt;print "removing $packfile\n";&lt;/code&gt;
::&lt;code&gt;unlink $packfile;&lt;/code&gt;</text>
    <sha1>64e6c8bff1ade1ebe338a06b5761145dd962c29f</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>PhpMyAdmin</title>
  <ns>0</ns>
  <id>131</id>
  <revision>
    <id>156</id>
    <timestamp>2009-06-06T21:21:37Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2143" xml:space="preserve">= phpMyAdmin =

== Install ==
Download ''phpMyAdmin'' from [http://www.phpmyadmin.net phpMyAdmin.net] and put it in ''/usr/src/sourcepkg''.
Extract and add a symbolic link for later use in our config.

&lt;pre&gt;
cd /var/www
tar jxvf /usr/src/source/phpMyAdmin-XXX.tar.bz2
ln -sf phpMyAdmin-XXX phpMyAdmin
&lt;/pre&gt;

=== apache1 running under Slackware &lt;12 ===
Make a directory for the config files and create the phpMyAdmin config file for apache.

&lt;pre&gt;
mkdir /etc/apache/conf.d
touch /etc/apache/conf.d/phpMyAdmin.conf
vi /etc/apache/conf.d/phpMyAdmin.conf
&lt;/pre&gt;

Add alias to apache (like at apache-2) and add these lines to phpMyAdmin.conf

&lt;pre&gt;
Alias /phpMyAdmin /var/www/phpMyAdmin

&lt;Location /phpMyAdmin&gt;
#    Order deny,allow
#    Deny from all
#    Allow from 127.0.0.1
#    Allow from ::1
#    Allow from .example.com
&lt;/Location&gt;
&lt;/pre&gt;

and append to the httpd.conf 

&lt;pre&gt;
echo 'Include /etc/apache/conf.d/phpMyAdmin.conf' &gt;&gt; /etc/apache/httpd.conf
&lt;/pre&gt;

=== httpd (apache2) under Slackware 12 ===
Create the phpMyAdmin config file and edit it.

&lt;pre&gt;
touch /etc/httpd/phpMyAdmin.conf
jed /etc/httpd/phpMyAdmin.conf
&lt;/pre&gt;

Add an alias to httpd (since the phpMyAdmin directory isn't in ''var/www/htdocs'') and change the ''Directory'' rules. 

&lt;pre&gt;
#
# phpMyAdmin - MySQL Database Administration Tool
#

Alias /phpMyAdmin /var/www/phpMyAdmin

&lt;Directory /var/www/phpMyAdmin&gt;
#  AllowOverride None
#  Options None
  Order allow,deny
  Allow from all
&lt;/Directory&gt;
&lt;/pre&gt;

Edit ''httpd.conf'' to use our new config and append at the end. 

&lt;pre&gt;
# Uncomment the following line to enable phpMyAdmin support:
#
Include /etc/httpd/phpMyAdmin.conf
&lt;/pre&gt;

== Configuration ==
Restart apache
&lt;pre&gt;
/etc/apache/rc.httpd restart
&lt;/pre&gt;

Go to your browser and open http://localhost/phpMyAdmin 

If you have set a password for your MySQL root user, you will have an error

Edit /var/www/phpMyAdmin/config.inc.php:

Change to something unique: 
 $cfg['blowfish_secret'] = '';

Change:
 $cfg['Servers'][$i]['auth_type']     = 'config';
To:
 $cfg['Servers'][$i]['auth_type']     = 'cookie';

refresh the browser

Finished.

[[Category:Tutorials]]</text>
    <sha1>b9767267f6ad74e610f203ccb4b4b8cd556f2baa</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Piping</title>
  <ns>0</ns>
  <id>132</id>
  <revision>
    <id>157</id>
    <timestamp>2009-06-06T21:24:00Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1798" xml:space="preserve">You can mix [[Common Commands|commands]] to do certain things. 

  dmesg | grep hd

That will search dmesg and try to find the string "hd". Now piping is extremely useful. Another example of a pipe:

  dmesg | less

Now this command you can see the dmesg fully and is easier to read. 

You can also make longer 'pipelines' by using a pipe of several commands.  For instance, to browse the last fifty lines of &lt;code&gt;dmesg&lt;/code&gt;:

  dmseg | tail -50 | less

&lt;b&gt;Redirection:&lt;/b&gt;

This will save the dmesg information in your home directory in the file log.txt

  dmesg &gt; ~/log.txt

You can also redirect only the [[standard output|stdout]] by using '1&gt;' or only the [[error messages|stderr]] by using '2&gt;'.

For instance, if you want to run a command that gives a lot of junk as output, and you just want to see any errors, you can redirect the output to the null device (&lt;code&gt;/dev/null&lt;/code&gt;):

  mplayer /path/to/movie.avi 1&gt; /dev/null

You can also use the &gt; and &gt;&gt; to cat stdin into a new or existing file:

  bash-3.1$ cat &gt; newFile
  This is a new file            
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits

* Warning 
* cat &gt; fileThatAlreadExists WILL OVERWRITE THE FILE! be careful :-)

You can use cat to check the text you just added:

  bash-3.1$ cat newFile 
  This is a new file 
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits
  
Now that a file is created you can add to it with the &gt;&gt; operator
 
  bash-3.1$cat &gt;&gt; newFile
  This is a new line to add to newFile

And if you use cat again to read the file 

  bash-3.1$cat newFile
  This is a new file 
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits
  This is a new line to add to newFile


[[Category:Tutorials]]</text>
    <sha1>0c88be229e86591eb46af05c311019a8614eee42</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Compiling Postfix</title>
  <ns>0</ns>
  <id>133</id>
  <revision>
    <id>158</id>
    <timestamp>2009-06-06T21:25:00Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tips</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="814" xml:space="preserve">[[Category:Tips]]
==Errors When Compiling From Source==

''(from a Slackware 11 perspective)''

'''Problem:''' Make dies complaining about a missing db.h file and/or &lt;code&gt;dbx-devel&lt;/code&gt;.

'''Solution:'''
::1) Make sure you have the db4 library (found on the Slackware install CD).
::2) If you have the db library installed, Postfix's makefile is dumb so,
:::: &lt;code&gt;ln -s /usr/include/db42/db.h /usr/include&lt;/code&gt;
:::This makes a link to the &lt;code&gt;db.h&lt;/code&gt; file from where the postfix makefile is looking for it.


'''Problem:''' Make dies complaining about &lt;code&gt;ld: cannot find -ldb&lt;/code&gt;.

'''Solution:'''
::The &lt;code&gt;libdb.so&lt;/code&gt; file cannot be found.  Make a link pointing to &lt;code&gt;/lib/libdb-4.2.20&lt;/code&gt; from &lt;code&gt;/lib/libdb.so&lt;/code&gt; file:
:::&lt;code&gt;ln -s /lib/libdb-4.2.20 /lib/libdb.so&lt;/code&gt;</text>
    <sha1>55aa8afb8baf4a8b9ad67e8cb2a9dbbcbd30eb21</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Power Management in Xorg</title>
  <ns>0</ns>
  <id>134</id>
  <revision>
    <id>159</id>
    <timestamp>2009-06-06T21:25:43Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1547" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
If you let your pc turned on for long periods of time, you should take in consideration the use of the Power Management Features of Xorg, (DPMS) to prevent your LCD or CRT monitor to burn the screen. 

== How to do it ==
To enable DPMS, you need to open your favorite editor and go to:

 /etc/X11/xorg.conf

find the Monitor Section and add Option "DPMS" so, it may look something like this:

 Section "Monitor"
      Identifier  "My Monitor"
      HorizSync   31.5 - 57.0
      VertRefresh 50-90
      Option "DPMS"
 EndSection

After that you can restart your X server, to do that, just end you current X server session and if kdm is active just restart it pressing Ctrl+Alt+Backspace, after that log in again.

Now you can test the changes with this command:

 xset dpms force off

Your screen should go totally off, that means the backlight should go off as well (for LCD monitors).

Next thing is to tell xorg when to turn the screen off, for that you need to edit the same file again, and go to the ServerLayout section and add:

 Option "OffTime" "20"

For me, that section looks like this:

 Section "ServerLayout"
    Identifier  "Simple Layout"
    Screen "Screen 1"
    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
    Option "OffTime" "20"
 EndSection


Now you are done, after that you can set up your screen saver on kde control center, remember to check the "Make aware of power management" box

== Related reading ==
[[LCD_Monitor_Configuration_In_X.Org]]</text>
    <sha1>ee30e923f02129a8119241f914c96ffbe2b1e4e7</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Qmail</title>
  <ns>0</ns>
  <id>135</id>
  <revision>
    <id>160</id>
    <timestamp>2009-06-06T21:26:23Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="987" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]

P2 - Pre-Installation Checklist

Installation steps

Part 01 - Download All the Needed Items for the Qmail installation

Part 02 - Installing Qmail itself

Part 03 - Installing EZmlm and EZmlm-idx

Part 04 - Installing Autoresponder

Part 05 - Installing Vpopmail

Part 06 - Installing VQadmin

Part 07 - Installing maildrop

Part 08 - Installing QmailAdmin

Part 09 - Finalizing the qmail installation

Part 10 - Uninstalling Sendmail

Part 11 - Starting up qmail

Part 12 - Installing Courier-imap/imaps with Courierpassd

Part 13 - Installation of the Squirrelmail web mail program

Part 14 - Clam Anti Virus &amp; SpamAssassin

Part 15 - Installing qmail-scanner w/qms-analog

Part 16 - Installing Qmailanalog &amp; Qlogtools

Part 17 - Installing Qtrap

Part 18 - Maintaining your qmail server

Part 19 - Mail client configuration

Part 20 - Feedback


== External Links ==

* http://qmailrocks.org/
* http://qmail.org
etc</text>
    <sha1>ef9d44ea5e68e7ba7136025d9cf99748533ca924</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>161</id>
    <parentid>151</parentid>
    <timestamp>2009-06-06T21:26:47Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3493" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==NOTICE==
After a long time and numerous upgrades, the DB finally caved in on itself. This is a fresh start. [http://slackwiki.org/old/index.php?title=Special:AllPages The old Wiki can be found here.] The data is still there, any help copying the old pages over here to the new Wiki would be greatly appreciated. UPDATE: Pages beginning with letters A through Q have been copied.

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>afce2dc81dc1aaaebb216325ddfb13cf1c469c2c</sha1>
  </revision>
  <revision>
    <id>170</id>
    <parentid>161</parentid>
    <timestamp>2009-06-06T21:38:09Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3493" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==NOTICE==
After a long time and numerous upgrades, the DB finally caved in on itself. This is a fresh start. [http://slackwiki.org/old/index.php?title=Special:AllPages The old Wiki can be found here.] The data is still there, any help copying the old pages over here to the new Wiki would be greatly appreciated. UPDATE: Pages beginning with letters A through S have been copied.

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>b9c8f971693aae4b9243a5ff89af29366ad84801</sha1>
  </revision>
  <revision>
    <id>171</id>
    <parentid>170</parentid>
    <timestamp>2009-06-06T21:38:54Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3493" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==NOTICE==
After a long time and numerous upgrades, the DB finally caved in on itself. This is a fresh start. [http://slackwiki.org/old/index.php?title=Special:AllPages The old Wiki can be found here.] The data is still there, any help copying the old pages over here to the new Wiki would be greatly appreciated. UPDATE: Pages beginning with letters A through R have been copied.

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>d2a49993ac6abe74a529cde40b4e337462c58890</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>RAID Array (Software)</title>
  <ns>0</ns>
  <id>136</id>
  <revision>
    <id>162</id>
    <timestamp>2009-06-06T21:31:22Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2087" xml:space="preserve">[[Category:Tips]]


== Raid1 Root ==
I was looking for a way to install a Slackware 12 as described in README_LVM.TXT but on top of a Software Raid1 array.
The installation is really straight forward :

Assuming we have two disk 
RAID_DSK[0]=/dev/sda and 
RAID_DSK[1]=/dev/sdb

First partion both disk using the type fd  Linux raid auto
You need at least two partions as descibed in README_LVM.TXT,
a small one that will be mounted on /boot and a big one that will support LVM.

create the raid array :
 # boot                                                                                                                              
 mdadm -q --create /dev/md0 --level=1 --raid-devices=2 ${RAID_DSK[0]}1 ${RAID_DSK[1]}1
 # lvm                                                                                                                               
 mdadm -q --create /dev/md1 --level=1 --raid-devices=2 ${RAID_DSK[0]}2 ${RAID_DSK[1]}2

Follow the instruction find in README_LVM.TXT to install LVM, 
just use /dev/md0 for the boot partition and 
/dev/md1 for the Physical Volume (PV) 
 pvcreate /dev/md1 ...

Complete the initrd installation as described in README_LVM.TXT to support LVM, but don't exit the chroot when it's done!
You need to apply more modification.

== Initrd Raid1 ==
You are still in the chroot ? fine.
copy the mdadm utility in /boot/initrd-tree/
 cp /sbin/mdadm /boot/initrd-tree/sbin/
save the configuration of your raid array in the initrd-tree
 /sbin/mdadm -D --scan &gt; /boot/initrd-tree/etc/mdadm.conf

modify /boot/initrd-tree/init to add the following
 # rebuild RAID ARRAY
 /sbin/mdadm --assemble --scan 2&gt; /dev/null

Just before
 # Initialize LVM:

That it! just rebuild the initrd image without resiting the tree (do not use the -c option!).

Just for info your lilo Global section should look like that :

 # Start LILO global section
 raid-extra-boot=mbr-only
 lba32 # Allow booting past 1024th cylinder with a recent BIOS
 boot = /dev/md0
 #message = /boot/boot_message.txt
 prompt
 timeout = 3

restart lilo, exit the chroot, reboot and
Enjoy!</text>
    <sha1>55b2b7f51a10667e2d6398bc9ca88ef51ac7b04c</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>RAID Array (Hardware)</title>
  <ns>0</ns>
  <id>137</id>
  <revision>
    <id>163</id>
    <timestamp>2009-06-06T21:31:50Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5990" xml:space="preserve">[[Category:Tips]]
[[Category:Tutorials]]
[[Category:Hardware]]

==My Card Is In, Now What?==

1) SET UP THE ARRAY- If you are using a hardware RAID card (like ones made by 3ware), on boot you must enter the card's BIOS and set up your array.  This is done by hitting a hotkey (ALT-3 for 3ware cards).  Read your card's instructions for details on how to configure your array.

2) BOOT WITH THE CORRECT KERNEL- After you have set up your array, boot the computer with the Slackware Install CD (CD1) like normal. &lt;b&gt;At the &lt;code&gt;boot:&lt;/code&gt; prompt, choose a RAID supporting image (e.g. &lt;code&gt;raid.s&lt;/code&gt;).&lt;/b&gt;  YOU CAN NOT USE THE DEFAULT KERNEL (bare.i) to boot into set-up, you have to use a boot kernel that supports RAID arrays.

:EXAMPLE: &lt;code&gt;boot: raid.s&lt;/code&gt;

3) PROCEED NORMALLY- Once you boot the RAID kernel, everything else proceeds normally except the hard-drive is (usually) &lt;code&gt;/dev/sda&lt;/code&gt;. Go ahead set up your partitions (&lt;code&gt;fdisk /dev/sda&lt;/code&gt;) and continue the normal Slackware install.


==FAQs==

Q: What device is my RAID array?&lt;br&gt;
A: You are most likely running RAID.S kernel so therefore it is probably &lt;code&gt;/dev/sda&lt;/code&gt;

Q: It's not &lt;code&gt;/dev/sda&lt;/code&gt; where is it really?&lt;br&gt;
A: I don't know. Reboot your machine and watch the messages scroll by.  If you don't see the info, you don't have RAID support compiled into your kernel or as a module and you need to fix that.

Q: My system has a [[forced fsck]] and it starts but after awhile, it resets and re-boots.  How do I fix this?&lt;br&gt;
A: Re-boot the system using a Slackware install CD (make sure you boot with a RAID kernel) then get to a command line prompt and manually run &lt;code&gt;fsck&lt;/code&gt;.
: EXAMPLE: &lt;code&gt;fsck -p /dev/sda1&lt;/code&gt;

Q: I'm trying to run &lt;code&gt;fsck&lt;/code&gt; manually but I get an "&lt;code&gt;The superblock cannot be read...&lt;/code&gt;" error.  How do I fix this?&lt;br&gt;
A: MOST LIKELY, you're not running a RAID supporting kernel.  Re-boot and choose a RAID kernel like &lt;code&gt;raid.s&lt;/code&gt;.

Q: I'm running &lt;code&gt;fsck&lt;/code&gt; manually and I am getting a "&lt;code&gt;error allocating inode bitmap (2)&lt;/code&gt;".  How do I fix this?&lt;br&gt;
A: No clue. I haven't been able to find out what that means.  If you do, let us know please.

==Hardware RAID Specific Help==

[[3ware 3DM2]] - Help with 3ware's 3DM2 program.

==Hardware RAID Specific Help==

[[3ware 3ware 8006-2LP Installation]] - 

Installed slackware 12.2 with the 3ware 8006-2LP card today. I chose this hardware due to the fanfare I found on the net. It is supported with RedHat and Suse (presumably because they have a preinstall driver installation dialog) 

Installing with slack was not as easy as was hoped. Lilo choked twice, first by installing to the MBR which the 3ware bios simply didn't see, and second after installing to the root partition, lilo complained with error 99 which is apparently a BIOS disk address mismatch of some sort. 

What worked was this: 

1. Install the card, or receive the machine with the card already installed. 

2. Double check that all your cable connections are tight. mine were loose when the chassis arrived from the vendor. I am sincerely glad I found this now rather than later. 

3. Slackware 12.2 has the 3ware driver in it, so it should boot from CD and see the disk as: 

   /dev/sda  

4. fdisk /dev/sda and create some partitions, mine are as follows: 

   /dev/sda1 50G (/ this is the root partition) set bootable
   /dev/sda2 2G  (for /boot)  
   /dev/sda3 2G  ( for swap) toggle to type 82
   /dev/sda4 (extended) 
   /dev/sda5 25G (for /var) 
   /dev/sda6 25G (for /home) 
   /dev/sda7 50G (for the webserver) 
   /dev/sda8 50G (for the database) 
   /dev/sda9 10G (for source code) 

You will note seperate /boot and /home partitions. Configuring the disk this way adds some security, which we will discuss in a moment. 

5. Run setup and select your packages. 

6. Do the configuration dialog: Generally I believe all network enabled devices should be on UTC so I set both system and hardware clocks accordingly.  ignore gpm, ignore fancy fonts, and number the network interface... Then make sure the network interface _isn't_ connected.  

7. Let the lilo configurator screw up lilo by select "Guess my lilo config" or whatever. 

8. exit setup, DO NOT REBOOT! 

9. chroot /mnt 

10. vi /etc/lilo and make it point at your root partition. My lilo.conf is as follows: 

   lba32 # any modern drive should be able to do this. 
   boot = /dev/sda1
   append = " vt.default_utf8=0"
   vga = normal
   image = /boot/vmlinuz
   root = /dev/sda1
   Label = Linux
   read-only # for fscking during bootup. 

11. Note above that /dev/sda1 is the root partition, or "/" if you stick it somewhere else, change as appropriate. 

12. obliterate the master boot record: (prevents lilo from getting confused for some reason): 
    lilo -z -M /dev/sda

13. run lilo and listen to it complain: 
   lilo 

14. If you don't get any fatals errors (warnings are ok), remove the cd then: 
    exit 
    reboot

15. Do your little chair dance, and irritate your coworkers. 

16. vi /etc/fstab and adjust the following partitions:
 
   /dev/sda2         /boot            ext2        defaults,ro         1   2
   /dev/sda6         /home            ext2        defaults,nosuid         1   2

Leave your partitions ext3 if they are configured that way, but note the addition of "ro" to /boot and "nosuid" to /home. This makes the kernel secure from modification until the next reboot, and prevents root privileged code from being executed from /home. Generally good and fairly unintrusive security policy. 

Now proceed onward oh great progenitors of slack. Your next steps should probably be using "find" to locate and disable most of what has a suid bit set, and then installing and configuring tripwire or some equivilant, then making a brutal set of access controls with iptables, and _then_.... _maybe_ you can connect the box to a public network. 

But don't take my word for it.  

Good Luck!</text>
    <sha1>5214be1411b980d4630f8b471f2b6088a57e2d96</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Region Set (program)</title>
  <ns>0</ns>
  <id>138</id>
  <revision>
    <id>164</id>
    <timestamp>2009-06-06T21:32:49Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Hardware</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="775" xml:space="preserve">[[Category:Hardware]] [[Category:Tips]]
== Description ==
A small stand-alone console progran to set/change a DVD drive's region code.

&lt;b&gt;WARNING:&lt;/b&gt; As of this writing (9/2006) almost all DVD drives can only have their region codes set/changed four times.  Some hacked firmware patches can bypass this.

Region set can be obtained from: [http://prdownloads.sourceforge.net/dvd/regionset.tar.gz http://prdownloads.sourceforge.net/dvd/regionset.tar.gz]

== Useage ==

To use this file:
::1) un-compress/archive the files-
::::&lt;code&gt; gunzip regionset.tar.gz&lt;/code&gt;
::::&lt;code&gt;tar -xvf regionset.tar&lt;/code&gt;

::2) CD into the directory-
::::&lt;code&gt;cd regionset&lt;/code&gt;

::3) Make the program-
::::&lt;code&gt;make&lt;/code&gt;

::4) Execute the program (as root)-
::::&lt;code&gt;./regionset&lt;/code&gt;</text>
    <sha1>8792a45eb418c802760abe3212eed2b17df9ce3f</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Recompile php with mcrypt</title>
  <ns>0</ns>
  <id>139</id>
  <revision>
    <id>165</id>
    <timestamp>2009-06-06T21:33:35Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2695" xml:space="preserve">[[Category:Tutorials]]
PhpMyAdmin (available at [http://www.SlackBuilds.org/ SlackBuilds.org]) works well when you compile PHP with the mcrypt extension.  After installing PhpMyAdmin, you may see a warning that it cannot find the mcrypt extension.    Unfortunately the official Slackware package does not include this extension.  Recompiling PHP is necessary, as is enabling the mcrypt.so extension in /etc/httpd/php.ini.  The first step is a little tricky, since compiling PHP requires a little trick: you must compile alpine during the PHP build.  It is fairly simple once you have things in place, but this tripped me up when I first tried to recompile PHP.

== Install mcrypt and libmcrypt ==

mcrypt is available from [http://www.SlackBuilds.org SlackBuilds.org].  First build and install mcrypt and libmcrypt before compiling PHP.

== Recompile PHP ==

Go to a Slackware mirror and download Pat's Slackbuild directory for php from the source/n directory.  I used 

&lt;code&gt;wget --mirror &lt;mirror&gt;/n/php&lt;/code&gt;

to download the whole directory.  You will also need to download the alpine/ directory into the parent of the newly-created php/.  In other words, you should have a parent directory with both php and alpine.  For example, mine is ~/SlackBuilds/n, where I have two subdirectories: one for alpine/ and one for php/.

'''
Be sure to chmod +x both the alpine and php SlackBuilds before attempting to build.'''  If you don't, things may go for quite a while depending on the speed of the machine you're building on before you get an error (and you ''will'' get an error).

=== Edit php.SlackBuild ===

You will need to add a "--with-mcrypt=" flag to the configure command in php.SlackBuild. Since you already have mcrypt installed, you can use 

&lt;code&gt;--with-mcrypt=`which mcrypt`&lt;/code&gt;

Remember to add the slash at the end of the line.  I positioned this flag second to the bottom.  The position of the flag only matters for your ability to find it next time, order will not affect the build process.  SlackBuilds customarily have the "--build=" flag at the bottom, so I left it where it was.

=== Upgrade PHP ===
Install the new package with upgradepkg.  Keep in mind that you will need to repeat this process whenever there is a security alert for php.  In that case, download the new source, update the VERSION variable, recompile and upgrade.  For this reason, I've kept ~/SlackBuilds/n the way it is with alpine and php subdirectories.

== Configure PHP ==

Configuring PHP to use mcrypt is easy: add the line

&lt;code&gt;extension=mcrypt.so&lt;/code&gt;

to /etc/httpd/php.ini and then restart apache.  Now when you log in to PhpMyAdmin, you should no longer see the warning about mcrypt.</text>
    <sha1>895d4100b9586f0651a1fef79befea937b61bca2</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Reinstalling Lilo</title>
  <ns>0</ns>
  <id>140</id>
  <revision>
    <id>166</id>
    <timestamp>2009-06-06T21:34:49Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1020" xml:space="preserve">Once upon a time you try to boot Slackware, something happens and lilo is messed up. You can fix lilo really easily, all you need is CD1 of Slackware. Boot the CD and when it says boot: then you type the following:

: &lt;code&gt;huge.s root=/dev/hda1 noinitrd ro&lt;/code&gt;

Now you change huge.s to the kernel you want to boot, root= should reflect the root partition of your Slackware install. Now when you type this you have Slackware booting up with the bare.i default kernel. Now at the login prompt you login as root and either type:

: &lt;code&gt;liloconfig&lt;/code&gt;

That will setup Lilo from a ncurses based menu. Now you can also edit lilo's config from a file:

: &lt;code&gt;vi /etc/lilo.conf&lt;/code&gt;

Either way it will fix it hopefully, Now remember man lilo has all the hex errors if you need them. When you have all that setup you now can run:

: &lt;code&gt;/sbin/lilo -v&lt;/code&gt;

Now you must run lilo every time you change /etc/lilo.conf to update the changes, Now restart without the CD and it should work.

[[Category:Tutorials]]</text>
    <sha1>faaece4ac572f843d9d0e7c784166e88c5d88950</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Release Changes</title>
  <ns>0</ns>
  <id>141</id>
  <revision>
    <id>167</id>
    <timestamp>2009-06-06T21:35:23Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="708" xml:space="preserve">The purpose of this page is to provide links to documentation of the changes occurring from one release of Slackware to the next.  We do not make any guarantees that the information provided is complete, but every effort is made to ensure accuracy and completeness.


[[Changes_9.1_10.0 | Changes From 9.1 to 10.0]]

[[Changes_10.0_10.1 | Changes From 10.0 to 10.1]]

[[Changes_10.1_10.2 | Changes From 10.1 to 10.2]]

[[Changes_10.2_11.0 | Changes From 10.2 to 11.0]]

[[Changes_11.0_current | Changes From 11.0 to -current]]

If anyone is so inclined, we certainly welcome page additions for changes between older versions - please do them in the same format as the existing ones.

[[Category:Information]]</text>
    <sha1>36220e4a69837662c9b6c5b2dcee5bad0271b6fc</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Relocatable packages</title>
  <ns>0</ns>
  <id>142</id>
  <revision>
    <id>168</id>
    <timestamp>2009-06-06T21:36:40Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Information</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1323" xml:space="preserve">[[Category:Information]]
Relocatable packages are created such that the user can choose to install the package in a different installation location than the default (usually '''/''').

All Slackware packages are technically relocatable, since [[pkgtools]] can install packages in a different installation root directory if the ROOT environment variable is set to another directory, regardless of whether the package was specifically designed to be relocatable. 

In practice, however, few packages are built with relocatability in mind, and installing them in any other installation root directory other than '''/''' will probably cause path related problems.

==Why Relocate?==

Installing into a different installation location other than '''/''' is useful in such cases as:

* Installing multiple versions of a program
* Installation by a normal (non-root) user in a user, non-system directory
* Trying out new software
** Installing a new version of a package without removing  (or overwriting) the older version of the package at any time
** Testing the new package
*** Possible approach: install as a normal user, test, and then install as root into system-wide areas.

Relocatable packages allow for more flexibility, and depending on the program to be packaged, may only require minimal additional effort to create.</text>
    <sha1>a4738fc69f23987b07f22c560936a5274ecf2c94</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Rsync</title>
  <ns>0</ns>
  <id>143</id>
  <revision>
    <id>169</id>
    <timestamp>2009-06-06T21:37:33Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2150" xml:space="preserve">[[Category:Tutorials]]
Rysnc is a great tool for backing up things, downloading things and
keeping up with Slackware -current. Why? Because say you have a lot of
files in /home/$USER/slackware/ that you want to update, say with the
newest -current. ( These files would be the files off of your
Slackware 10.1 disk, on the folder /slackware on the root of the
Slackware disk) rsync would only download what is new and can also
erase what is no longer there, this could save a lot of bandwidth. So
where do we begin? Lets use a Slackware mirror and actually update
your Slackware 10.1 cd , to -current. So we will use a Slackware
mirror:

 rsync inferno.bioinformatics.vt.edu::

The above command would list the modules on the rsync server. Well
what is a module? A module is something that people export their files
and directories to in a module format. So someone running a rsync
server could make a module called "slackware" and export
"/home/slackware/".  Then the user could download all or some of the
files in that module. Now lets list the files and directories of the
module we need:

 rsync inferno.bioinformatics.vt.edu::slackware

See from the above you can see the slackware versions we could all
download. Since we have our slackware 10.1 in /home/$USER/slackware
and we want to upgrade to -current, we could use this command:

 rsync -rvz --delete inferno.bioinformatics.vt.edu::slackware/slackware-current/slackware/ /home/$USER/slackware/

Now this command looks weird at first, but lets examine. First the -r
means recursive ( Meaning it goes through all the sub directories and
downloads ). Next we see -v which means verbose, so we can see what is
going on, next the -z. This means compress, it will compress the
things so it will shorten the bandwidth requirement. The --delete
means that it will delete anything that the server doesn't have, this
would make an exact mirror copy:)! That pretty much sums that command
up.

So since this was a simple rsync tutorial and pretty much told you how
to download Slackware -current an efficient way, read UPGRADE.txt to
find out how to fully upgrade your box:)

Thanks for reading, Sandy</text>
    <sha1>dc881a3571e22dd9c24db1c4548a730f2d0df592</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>SSL</title>
  <ns>0</ns>
  <id>144</id>
  <revision>
    <id>172</id>
    <timestamp>2009-06-06T23:17:15Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12958" xml:space="preserve">[[Category:Tutorials]]
= openSSL 0.9.8e =
'''IMPORTANT: Since this version has a [http://www.mail-archive.com/openssl-users@openssl.org/msg48671.html bug in the blowfish encryption] it is recommended not to use blowfish since it is incompatible with all other openSSL versions!'''

&lt;br&gt;Everything you read here was tested on Slackware 12&lt;br&gt;

; wikipedia says about openSSL:
: ''OpenSSL is an open source implementation of the SSL and TLS protocols. The core library (written in the C programming language) implements the basic cryptographic functions and provides various utility functions. Wrappers allowing the use of the OpenSSL library in a variety of computer languages are available.''

There are many ways to use openSSL. This just covers certificates for use with httpd. You can also use easy-rsa that comes with the openVPN package and can be found in ''/usr/doc/openvpn-2.0.9/easy-rsa/''. For more information read the included ''README'' or look here: [http://openvpn.net/easyrsa.html A Guide to basic RSA Key Management].
Normally you will make a ''Certificate Signing Request (CSR)'' and send this one to a ''Certifying Authority (CA)'' to be signed. But since we don't wanna pay for this and only want to use it for our own special purpose, we don't need to do that and sign everything ourself.

= openSSL + httpd =
Switch to ''/etc/ssl''
&lt;pre&gt;
cd /etc/ssl
&lt;/pre&gt;

In this directory you should see the following listing.  One some non-Slackware linuxes, or if OpenSSL was installed from source, the appropriate directory might be ''/etc/openssl''.
&lt;pre&gt;
root@pecan:/etc/ssl# ls -l
total 24
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 certs/
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 misc/
-rw-r--r-- 1 root root 9374 2007-06-13 12:40 openssl.cnf
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 private/
root@pecan:/etc/ssl# 
&lt;/pre&gt;

We need to generate a private and public RSA key file.
The public key is used to encrypt messages to you and is distributed with your certificate.

== Creating a Self-Signed ''Certificate'' (CRT) ==

=== openssl.cnf + openSSL DB ===
(You should still do this step even if you are buying a commercial certificate.) First things first, so we gotta edit this file, mainly the ''[ CA_default ]'' section.
The 
&lt;pre&gt;
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
...
certificate	= $dir/cacert.pem 	# The CA certificate
...
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
...
&lt;/pre&gt;
to
&lt;pre&gt;
[ CA_default ]

dir		= /etc/ssl		# Where everything is kept
...
certificate	= $dir/certs/ca.crt   	# The CA certificate
...
crl		= $dir/crl/ca.crl	# The current CRL
private_key	= $dir/private/ca.key   # The private key
...
&lt;/pre&gt;
You can even change more options in this file but be aware what you are doing.&lt;br&gt;
openSSL has a database for storing information such as ''Certificate Revocation Lists'' (CRL). Since these files don't exist on startup and we don't use the ''CA.sh'' or ''CA.pl'' scripts we got to create them ourself:
&lt;pre&gt;
mkdir newcerts certs crl private
touch serial index.txt crlnumber crl/ca.crl
echo 01 | tee serial | tee crlnumber
&lt;/pre&gt;
Thanks to ''alienBOB''. Hail to tee king! :p

=== Becoming a ''Certification Authority'' (CA) ===
(Skip this step if you are buying a certificate from a commercial certificate authority such as GoDaddy.) Before you can create and sign your own certificates, you first have to establish yourself as a "Certificate Authority".
To do so, we first create our key file (with a public and a private key) and use it to create our "master certificate" to use when signing other certificates.

; Generate the CA RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/ca.key 4096&lt;/pre&gt;
; Create the CA CRT with the CA RSA Key
: &lt;pre&gt;openssl req -new -x509 -days 3650 -key private/ca.key -out certs/ca.crt&lt;/pre&gt;

=== Create Server CRT ===
A CRT contains your RSA public key, your name, the name of the CA, and is digitally signed by the CA. Browsers that know the CA can verify the signature on that CRT, thereby obtaining your RSA public key. That enables them to send messages which only you can decrypt.
The next step is to create a Server RSA key, generate a ''Certificate Signing Request'' (CSR) out of it and sign it with our CA CRT to get a working SSL CRT for our server.
A CSR is a digital file which contains your public key and your name. Normally you would send the CSR to a CA, who will convert it into a real certificate, by signing it.

; Generate the Server RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/server.key 1024&lt;/pre&gt;
; Create the Server CSR using the Server RSA Key
: '''When asked for the CommonName (CN) enter your domain!'''
: &lt;pre&gt;openssl req -new -key private/server.key -out private/server.csr&lt;/pre&gt;
; Sign the CSR with our CA CRT
: &lt;pre&gt;openssl ca -in private/server.csr -out certs/server.crt&lt;/pre&gt;

You can now delete ''server.csr'' if you want, because it is no longer needed.

(If you are using a commercially signed certificate from a place such as GoDaddy, do the first two commands above but not the last.  Then do ''cat private/server.csr'' to get the text of the certificate request, which you will paste into GoDaddy's web interface to get the certificate.  GoDaddy will then email the email address listed in the ''whois'' information for that domain (Make sure you haven't put in a fake address there to avoid spam!), and after the link in that email is clicked, GoDaddy will email another link to you from which you download a zip file.

The zip file will contain two .crt files, and you should put both of them in /etc/ssl/certs.  Other commerical certificate authorities follow a very similar procedure.)

== Setup httpd ==
=== Edit httpd.conf ===
The whole httpd config is located in ''/etc/httpd''. Fire up your preferred text editor and simply change this at Line 459:
&lt;pre&gt;
# Secure (SSL/TLS) connections
#Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to this
&lt;pre&gt;
# Secure (SSL/TLS) connections
Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to enable SSL support.

You may also have to uncomment the line that starts ''LoadModule ssl_module''.

=== Edit extra/httpd-ssl.conf ===
Now we're going into the guts of the httpd SSL config. Search for ''SSLCertificateFile'' and ''SSLCertificateKeyFile'' change the path to our newly created CRT:
&lt;pre&gt;
...
SSLCertificateFile /etc/ssl/certs/server.crt
...
SSLCertificateKeyFile /etc/ssl/private/server.key
...
SSLCertificateChainFile /etc/ssl/certs/server.crt
...
SSLCACertificatePath /etc/ssl/certs
SSLCACertificateFile /etc/ssl/certs/ca.crt
...
SSLCARevocationPath /etc/ssl/crl
SSLCARevocationFile /etc/ssl/crl/ca.crl
...
&lt;/pre&gt;

(If you have purchased a certificate from a commercial authority, the SSLCertificateFile will be one of the two files you receive from the CA (GoDaddy or VeriSign or whomever), and the SSLCACertificateFile will be the other.  The files will be named such that you can tell which is which -- the SSLCertificateFile will probably be something like ''www.yourdomainname.com.crt'' and the SSLCACertificateFile will be something like ''nameofca-bundle.crt''.)

== Pass-phrase on httpd startup ==
The reason this dialog pops up at startup and every re-start is that the RSA private key inside your ''server.key'' file is stored in encrypted format for security reasons. The pass-phrase is needed decrypt this file, so it can be read and parsed. Removing the pass-phrase removes a layer of security from your server - proceed with caution!
&lt;ol&gt;
&lt;li&gt;
Remove the encryption from the RSA private key (while keeping a backup copy of the original file):
&lt;pre&gt;
cd /etc/ssl
mv private/server.key private/server.key.org
cd private
openssl rsa -in server.key.org -out server.key
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
Make sure the server.key file is only readable by root since it is decrypted:
&lt;pre&gt;
cd /etc/ssl
chmod 0400 private/server.key
&lt;/pre&gt;
&lt;/li&gt;&lt;/ol&gt;
Now server.key contains an unencrypted copy of the key. If you point your server at this file, it will not prompt you for a pass-phrase. HOWEVER, if anyone gets this key they will be able to impersonate you on the net. PLEASE make sure that the permissions on this file are such that only root or the web server user can read it (preferably get your web server to start as root but run as another user, and have the key readable only by root).

As an alternative approach you can use the ''SSLPassPhraseDialog exec:/path/to/program'' facility. Bear in mind that this is neither more nor less secure, of course.

== Verifying and debugging ==
If you simply want to see every information on a CRT:
&lt;pre&gt;openssl x509 -noout -text -in XXX.crt&lt;/pre&gt;

=== Verifying ===
; Verify that a private key matches its Certificate
: Generate a MD5 out of the public key/CRT and compare
: &lt;pre&gt;openssl x509 -noout -modulus -in private/XXX.crt | openssl md5 &amp;&amp; openssl rsa -noout -modulus -in private/XXX.key | openssl md5&lt;/pre&gt;

=== Debugging ===
; s_server - Debugging clients
: &lt;pre&gt;openssl s_server -accept 443 -www&lt;/pre&gt;
; s_client - Debugging servers
: &lt;pre&gt;openssl s_client -connect localhost:443&lt;/pre&gt; or &lt;pre&gt;openssl s_client -connect localhost:443 -state -debug&lt;/pre&gt;

== Security ==
All the files expect the CRTs are only for your eyes, so we change the permissons:
&lt;pre&gt;chmod 0400 private/*.key&lt;/pre&gt;

=== Client Revokation ===
This is only needed if your server certificate is compromised (eg. someone hacked your server and stole your server.key).
&lt;pre&gt;
openssl ca -gencrl -keyfile private/ca.key -cert certs/ca.crt -out crl/ca.crl
&lt;/pre&gt;
That generated us the needed files which we use when we want to revoke a CRT.
&lt;br&gt;&lt;br&gt;
Now that we got a compromised CRT, we got to get rid of it:
&lt;pre&gt;openssl ca -revoke server.crt -keyfile private/ca.key -cert certs/ca.crt&lt;/pre&gt;

== Other ==

=== Change the pass-phrase ===
&lt;pre&gt;
openssl rsa -des3 -in server.key -out server.key.new
mv server.key.new server.key
&lt;/pre&gt;
The first time you're asked for a PEM pass-phrase, you should enter the old pass-phrase. After that, you'll be asked again to enter a pass-phrase - this time, use the new pass-phrase. If you are asked to verify the pass-phrase, you'll need to enter the new pass-phrase a second time.

=== CRT for Clients ===
Ok.. i won't write anything on this, and simply just C/P:
&lt;pre&gt;
openssl genrsa -des3 -out private/client1_priv.key 2048
openssl genrsa -des3 -out private/client2_priv.key 2048
# and so on... depends on how much clients you wanna serv...
openssl req -new -key private/client1_priv.key -out private/client1.csr
openssl req -new -key private/client2_priv.key -out private/client2.csr
# and so on...
openssl ca -in private/client1.csr -out private/client1.crt
openssl ca -in private/client2.csr -out private/client2.crt
cp private/client1.crt private/client1_preconv.crt 
cat private/client1.key &gt;&gt; private/client1_preconv.crt
openssl pkcs12 -export -in private/client1_preconv.crt -out private/client1_postconv.p12 
&lt;/pre&gt;
Install in the clients browser... and change httpd.conf:
&lt;pre&gt;
SSLCACertificateFile PATH/TO/server.crt
SSLVerifyClient require
SSLVerifyDepth 1
&lt;/pre&gt;

=== Convert CRT from PEM to DER format ===
Normally all CRTs are stored in the PEM format.
&lt;pre&gt;openssl x509 -in ca.crt -out ca.crt.der -outform DER&lt;/pre&gt;

== Testing the CRT ==
If you have live web sites, you might wish to test your configuration before restarting apache, to avoid having that panicy few minutes of downtime while you scramble to see what you can do faster, fix the problem or copy back your backup configs.  Test like this:
&lt;pre&gt;httpd -t&lt;/pre&gt;
Look at the error messages it prints out, or the error_log as explained below, if it doesn't work.

Restart your httpd:
&lt;pre&gt;/etc/rc.d/rc.httpd restart&lt;/pre&gt;
Take a look at the httpd ''error_log'' and scroll to the end of the file:
&lt;pre&gt;jed /var/log/httpd/error_log&lt;/pre&gt;
If your getting an error like this:
&lt;pre&gt;[error] Init: Unable to read pass phrase [Hint: key introduced or changed before restart?]&lt;/pre&gt;
... then you should take a look at ''Pass-phrase on httpd startup'' ...

= openSSL + openVPN =
$foo ... maybe next month...

= External Links =
* [http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html SSL/TLS Strong Encryption: FAQ @ httpd.apache.org]
* [http://www.tc.umn.edu/~brams006/selfsign.html Creating a self-signed SSL certificate]
* [http://www.madboa.com/geek/openssl/ OpenSSL Command-Line HOWTO]
* [http://www.5dollarwhitebox.org/wiki/index.php/Howtos_Self_Signed_SSL_Certificates OpenSSL Quick Reference]
* [http://www.opensourcehowto.org/how-to/apache/setup-apache2-with-openssl.html Setup Apache2 with OpenSSL]
* [http://www.marschke.info/admin/ap_opssl_https.html Apache2, OpenSSL und HTTPS: Server- und Client-Authentifizierung mit Zertifikaten über verschlüsselte Internet-Verbindungen]
* [http://www.online-tutorials.net/security/openssl-tutorial/tutorials-t-69-207.html openSSL / openVPN.. comming soon]</text>
    <sha1>ebc5be38291a6dd81f0ef352440df618a80d298d</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Samba</title>
  <ns>0</ns>
  <id>145</id>
  <revision>
    <id>173</id>
    <timestamp>2009-06-06T23:17:56Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19859" xml:space="preserve">[[Category:Tutorials]]
... this is a W.I.P ... will write more the next days, hope this is ok :)

comments, suggestions, etc. are welcome!

== Introduction ==
This Tutorial shows you how to configure Samba 3.0.x on Slackware 12.x.

It should later act as simple and secure as it can be in a heterogen network with Windows systems (a workstation with admin access, guest accounts for the rest [eg. your friends]), a media streaming client (eg. Xbox) and Linux / *nix (Solaris / Mac OS X).

I wanted to have all necessary parameters for home usage in my smb.conf so i can easily change them and have a mostly secure and stable system. Printing is disabled by default in my config, since i have no need to attach my printer to the server (the printer has its own print server: HP P2015). Also i really have no clue how to use a printer with linux. If someone wants to write something on printing then feel free to do so...

== Upgrade / Build Samba ==

If you are here you probably will know what Samba is good for and how it works.
Normally Samba is installed on your system and ready for action and doesn't need to be upgraded.

=== Upgrade Samba ===

All upgrades to Samba should be done via the patches directory on your favorite mirror. You should NOT NOT NOT mix -current packages with a non "-current" Slackware. 

=== Building Samba ===

Hey! Wanna build Samba? Get the source, get the slackbuild, make a package and install it!

I used the latest build from the 3.0.x fork since this comes with Slackware 12.x.

You can also try building Samba 3.2.x. If you want a optimized build with a better performance that suits your system, you should consider installing GCC &gt;4.2.4 since it supports better optimizing functions (''-march=native'' - specifying ''-march=native'' implies ''-mtune=native''. This will enable all instruction subsets supported by the local machine (hence the result might not run on different machines).) and use Samba 3.2.x cause it has a better overall performance. Only do this if you know what you are doing!

* Get the source + SlackBuild, edit it and build the package...
&lt;pre&gt;$ mkdir /tmp/samba
$ cd /tmp/samba
$ wget http://us3.samba.org/samba/ftp/stable/samba-3.0.31.tar.gz
  ...
$ wget -r -nH ftp://slackware.osuosl.org/pub/slackware/slackware-current/source/n/samba
$ jed samba.SlackBuild
  &gt;  VERSION=3.0.30
  &gt;&gt; VERSION=3.0.31

  &gt;  tar xjvf $CWD/samba-$VERSION.tar.bz2
  &gt;&gt; tar xfvz $CWD/samba-$VERSION.tar.gz
$ chmod +x samba.SlackBuild
$ ./samba.SlackBuild
$ upgradepkg /tmp/samba-3.0.31-i486-1.tgz&lt;/pre&gt;

== Configure Samba ==

There are a few requirments i had for this config.
* Guest access from Windows without the need for a password
* Guests are only allowed to read and have no ''home directory'' (eg. /home/guest)
* Guests are only allowed to put new files in a given directory
* Make everything secure as it can get with this config
* Users on the system have access to their ''home directory''
* No Printing at all
* Disable NetBios, we only have Windows XP or higher / *nix
* Maybe more?

=== /etc/samba/smb.conf ===
This is my own ''smb.conf'' as i use it on my system.

The config file itself should be selfexplaining. 

==== '''smb.conf /w comments''' ====
&lt;pre&gt;#smb.conf - v1.1
#
# Samba-3.0.30 - Slackware 12.x
# e.v.o ( e.v.o [A-T] gmx.net )
#
# ; COMMENT
# #PARAMETER ( name = default value )
# Normally every parameter should have its default value.
# If the parameter is commented out then it is the default value,
# otherwise you should have a look at "man smb.conf"
#
# This config is based on the smb.conf manual page
# and "Using Samba, 3rd Edition" from O'Reilly
#

# VARIABLE SUBSTITUTIONS
; %U	session username
; %G	primary group name of %U
; %h	the Internet hostname that Samba is running on
; %m	the NetBIOS name of the client machine (very useful)
; %L	the NetBIOS name of the server
; %M	the Internet name of the client machine
; %R	the selected protocol level after protocol negotiation
; %d	the process id of the current server process
; %a	the architecture of the remote machine
; %I	the IP address of the client machine
; %i	the local IP address to which a client connected
; %T	the current date and time
; %D	name of the domain or workgroup of the current user
; %w	the winbind separator
; %v	Samba version number
;
; The following substitutes apply only to some configuration options
; Only those that are used when a connection has been established
;
; %S	the name of the current service, if any
; %P	the root directory of the current service, if any
; %u	username of the current service, if any
; %g	primary group name of %u
; %H	the home directory of the user given by %u
; %N	the name of your NIS home directory server
; %p	the path of the service's home directory

[global]
; Parameters in this section apply to the server as a whole

; ###  USERSHARES  ### # Capability for non-root users to 
; ==================== # add/modify/delete own share definitions 
;
; Controls if usershares can permit guest access
#usershare allow guests      =
; Maximum number of user defined shares allowed
#usershare max shares        =
; If set only directories owned by the sharing user can be shared
#usershare owner only        =
; Directory containing the user defined share definitions
#usershare path              =
; Comma-separated list restricting what directories can be shared
#usershare prefix allow list =
; Comma-separated list restricting what directories can be shared
#usershare prefix deny list  =
; Pre-existing share used as a template for creating new usershares
#usershare template share    =

; ###  NAME MANGLING  ### # By default, Samba has the same
; ======================= # semantics as a Windows NT server
;
; Filenames are case sensitive
#case sensitive      = auto
; Default case for new filenames
#default case        = lower
; New files are created with the case that the client passes
#preserve case       = yes
; New files which conform to 8.3 syntax are created upper case
#short preserve case = yes

; ###  PRINTING  ###
; ==================
;
; All printers in the printcap will be loaded for browsing by default
load printers           = no
; Only applicable if printing is set to cups.
#cups server            = ""
; Show the "Add Printer Wizard" Dialog
show add printer wizard = no
; Yes = open, write to and submit spool files on the specified directory
printable               = no

; ===============================
; #   -   S E T T I N G S   -   #
; ===============================

; \-= USER SCRIPTS =-/    # These scripts are used on a PDC or stand-alone 
; ====================    # machine to add or delete corresponding unix accounts

; Script that will be run when a new group is requested
#add group script               = /usr/sbin/groupadd %g
; Script that will be run when a machine is added to Samba's domain
#add machine script             = /usr/sbin/adduser -s /bin/false -d /dev/null %u -n -g machines -c Machine 
; Script which will add a new service definition to smb.conf
#add share command              =
; Script which will add a new user
#add user script                = /usr/sbin/useradd -m %u
; Script that will be called when a user is added to a group
#add user to group script       = /usr/sbin/usermod -G %g %u
; Script which will modify an existing service definition in smb.conf
#change share command           =
; Script when a group is requested to be deleted
#delete group script            = /usr/sbin/groupdel %g
; Script when a user is removed from a group using the Windows NT domain administration tools
#delete user from group script  = /usr/sbin/deluser %u %g
; Script that will be run when managing users with remote RPC (NT) tools
#delete user script             = /usr/sbin/userdel -r %u
; Script that will be run under special circumstances
#rename user script             = no
; This script sets the primary group in the unix userdatase when an administrator sets the 
; primary group from the windows user manager or when fetching a SAM with net rpc vampire
#set primary group script       = /usr/sbin/usermod -g '%g' '%u'
; Program that can be used to set UNIX user passwords
#passwd program = /usr/bin/passwd %u
; Controls the "chat" conversation between smbd and the local password changing program
#passwd chat = "*New password:*" %n\r "*New password (again):*" %n\r \ "*Password changed*"

; \-= PERMISSION MASKS =-/
; ========================

#inherit owner                 = no
#inherit permissions           = no

#directory mask                = 0755
#directory security mask       = 0777
#force create mode             = 000
#force directory mode          = 000
#force directory security mode = 0
#force security mode           = 0
#security mask                 = 0777

; \-= USER PARAMETER =-/
; ======================

; List of users who will be granted administrative privileges on the share
admin users     = evo
; This is a list of users that should be allowed to login to this service
valid users     = evo guest
; This is a list of users that should not be allowed to login to this service
invalid users   = root nobody ftp adm apache bin daemon games gdm haldaemon halt lp mail messagebus mysql news operator pop rpc shutdown smmsp sshd sync uucp
; This is a list of users that are given read-only access to a service
read list       = evo guest
; This is a list of users that are given read-write access to a service
write list      = evo

; -= Guest Settings =-
; Username which will be used for access to services which are specified as guest ok
guest account   = guest
; Yes for a service, then no password is required to connect to the service
guest ok        = no
; Yes for a service, then only guest connections to the service are permitted
guest only      = no

; -= Forced User/Group Settings =-
; UNIX user name that will be assigned as the default user for all users
;force user = guest
; UNIX group name that will be assigned as the default primary group for all users
force group = users

; -= Map Settings =-
; Specify a file containing a mapping of usernames from the clients to the server
#username map = 
;
#map acl inherit  = no
#map archive      = yes
#map hidden       = 
#map read only    = yes
#map system       = no
map to guest     = Bad User

; \-= SHARE PARAMETER =-/
; =======================

; Lets you "turn off" a service. If available = no, then ALL attempts to connect to the service will fail
available       = yes
; Controls whether this share is seen in the list of available shares in a net view and in the browse list
browseable      = yes
; Allow or disallow client access to accounts that have null passwords 
#null password  = no
; If this parameter is yes, then users of a service may not create or modify files in the service's directory
read only       = yes
; Setting this parameter to no prevents any file or directory that is a symbolic link from being followed
follow symlinks = no
; This parameter controls whether or not links in the UNIX file system may be followed by the server
wide links      = no

; This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found
#default service = 
; This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty
dont descend     = /bin,/boot,/dev,/etc,/lib,/opt,/proc,/sbin,/srv,/sys,/tmp,/usr,/var

; -= Hide Files =-
; This is a boolean parameter that controls whether files starting with a dot appear as hidden files
#hide dot files         = yes
; This is a list of files or directories that are not visible but are accessible
#hide files             = 
; This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings
#hide special files     = no
; This parameter prevents clients from seeing the existance of files that cannot be read
#hide unreadable        = no
; This parameter prevents clients from seeing the existance of files that cannot be written to
#hide unwriteable files = no

; \-= WINDOWS PARAMETER =-/
; =========================

; Specifies the charset that samba will use to print messages to stdout and stderr
#display charset = "LOCALE" or "ASCII" (depending on the system)
; This option specifies which charset Samba should talk to DOS clients
#dos charset = # No default
; Enabling this parameter allows a user who has write access to the file (by whatever means) to modify the permissions
#dos filemode = no

; \-= NETWORK/CONNECTION PARAMETER =-/
; ====================================

; This controls what workgroup your server will appear to be in when queried by clients
workgroup = KlingKlang
; This controls what string will show up in the printer comment box in print manager and next to the IPC connection in net view
server string = FileDealer
; This sets the NetBIOS name by which a Samba server is known
netbios name = FileDealer
#netbios aliases = 

; -= Interface Settings =-
; This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service
hosts allow = 127.0.0.1 192.168.
hosts deny  = ALL

; -= Connection Options =-
; Represents the number of minutes of inactivity before a connection is considered dead and disconnected
#deadtime        = 0 
; The value of the parameter (an integer) represents the number of seconds between keepalive packets
#keepalive       = 300
; This option allows the number of simultaneous connections to a service
#max connections = 0
; This option allows you to set socket options to be used when talking with the client
socket options   = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536

; \-= OTHER PARAMETER =-/
; =======================

security = user

; Enabling this parameter will disable netbios support in Samba
disable netbios = yes
; Do a lookup with the DNS server
dns proxy = no

; -= SMBpasswd Settings =-
; This option allows the administrator to chose which backend will be used for storing user and possibly group information
#passdb backend = smbpasswd:/etc/samba/private/smbpasswd
; This option sets the path to the encrypted smbpasswd file
#smb passwd file = /etc/samba/private/smbpasswd

; -= Directory Settings =-
; This option specifies the directory where lock files will be placed
#lock directory = /var/lock
; This parameters defines the directory smbd will use for storing such files as smbpasswd and secrets.tdb
#private dir = /etc/samba/private

; -= Logging Settings =-
; This option allows you to override the name of the Samba log file
log file = /var/log/samba/samba.%m
; This option (an integer in kilobytes) specifies the max size the log file should grow to
max log size = 5000
; Parameter maps how Samba debug messages are logged onto the system
#syslog = 1
; Parameter is set then Samba debug messages are logged into the system syslog only
#syslog only = no

; Using the following line enables you to customise your configuration on a per machine
; basis. The %m gets replaced with the netbios name of the machine that is connecting.
; Note: Consider carefully the location in the configuration file of
;       this line.  The included file is read at that point.
#include = /etc/samba/smb.conf.%m

; ===========================
; #   -   S H A R E S   -   #
; ===========================

[homes]
comment    = Eigene Dateien

guest ok   = yes
read only  = no
browseable = no

[printers]
comment    = Drucker
path       = /var/spool/samba

browseable = no
available  = no
guest ok   = no
printable  = yes

[BitHalde]
comment   = 3TB
path      = /mnt/raid

guest ok  = yes
read only = yes
&lt;/pre&gt;

==== smb.conf w/o comments ====
&lt;pre&gt;[global]
        workgroup = KLINGKLANG
        server string = FileDealer
        map to guest = Bad User
        guest account = guest
        log file = /var/log/samba/samba.%m
        disable netbios = Yes
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
        load printers = No
        show add printer wizard = No
        dns proxy = No
        invalid users = root, nobody, ftp, adm, apache, bin, daemon, games, gdm, haldaemon, halt, lp, mail, messagebus, mysql, news, operator, pop, rpc, shutdown, smmsp, sshd, sync, uucp
        valid users = evo, guest
        admin users = evo
        read list = evo, guest
        write list = evo
        force group = users
        hosts allow = 127.0.0.1, 192.168.
        hosts deny = ALL
        wide links = No
        follow symlinks = No
        dont descend = /bin,/boot,/dev,/etc,/lib,/opt,/proc,/sbin,/srv,/sys,/tmp,/usr,/var

[homes]
        comment = Eigene Dateien
        read only = No
        guest ok = Yes
        browseable = No

[printers]
        comment = Drucker
        path = /var/spool/samba
        printable = Yes
        browseable = No
        available = No

[BitHalde]
        comment = 3TB
        path = /mnt/raid
        guest ok = Yes
&lt;/pre&gt;

== Using Samba ==

In this section we will have a look on how to use, start and restart samba

=== Optimizing Samba ===

== Testing and Troubleshooting ==

In this section we will have a look on how we test our configuration and what to do if we ran into problems.

=== Using ''testparm'' ===

&lt;blockquote&gt;testparm — check an smb.conf configuration file for internal correctness&lt;/blockquote&gt;

*: If your done with the setup of your ''smb.conf'' you should run ''testparm''. Do this by simply typing it ;)
&lt;pre&gt;$ testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
NOTE: Service printers is flagged unavailable.
Processing section "[BitHalde]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions&lt;/pre&gt;
:: Normally this is what the output should look like. By pressing enter you will get a list of all used parameters in smb.conf.

*: If you wish to have a complete list of all options and how they are set:
&lt;pre&gt;$ testparm -v&lt;/pre&gt;

==== Using ''smbclient'' ====

&lt;blockquote&gt;smbclient — ftp-like client to access SMB/CIFS resources on servers&lt;/blockquote&gt;

* Connecting as a guest and list all shares
&lt;pre&gt;$ smbclient -L localhost -N
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Sharename       Type      Comment
        ---------       ----      -------
        BitHalde        Disk      3TB
        IPC$            IPC       IPC Service (FileDealer)
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        KLINGKLANG           FILEDEALER&lt;/pre&gt;
&lt;blockquote&gt;-L ''host'' This option allows you to look at what services are available on a server.&lt;br/&gt;
-N Suppresses the normal password prompt. Useful when accessing a service that does not require a password.&lt;/blockquote&gt;

* Connecting with a specified username and list all shares
&lt;pre&gt;$ smbclient -L localhost -U evo
Password:
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Sharename       Type      Comment
        ---------       ----      -------
        BitHalde        Disk      3TB
        IPC$            IPC       IPC Service (FileDealer)
        evo             Disk      Eigene Dateien
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        KLINGKLANG           FILEDEALER&lt;/pre&gt;
&lt;blockquote&gt;-U Sets the SMB username or username and password.&lt;/blockquote&gt;


== To Do ==
* alle user eintragen (cat /etc/passwd | cut -d':' -f1 | sort)
* user scripte vervollständigen
* masken richten + upload beim gast/evo gehört root? warum das?
* was ist mit umlauten?
* --&gt; wie starten? rc.samba
* Testmethoden aus dem samba buch einfügen</text>
    <sha1>b2507605307c2895beae4c84fa5372d47ca90e8d</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Samba As PDC</title>
  <ns>0</ns>
  <id>146</id>
  <revision>
    <id>174</id>
    <timestamp>2009-06-06T23:18:26Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3650" xml:space="preserve">[[Category:Tutorials]]
How to use Samba as a Primary Domain Controller
by dadexter

----


This tutorial will explain how to use Samba as a Primary
Domain Controller using OpenLDAP for authentication.


Why:

A client of mine is migrating to a Linux server farm, and a mix of Linux
and Windows workstations. In order to do that, I set it up at home using
SlackWare.

STEP 1

----

The first step in this exercise is to setup Samba to act as PDC. I did that
with the samba provided by a standard Slackware 10.1 install.

First, we need a config file. Here's a copy of mine:

    ; /etc/samba/smb.conf
    ; Machine: Cirion
    
    [global]
        workgroup = SIGTERM
        netbios name = Cirion
        server string = Domain Controller [Cirion]
        hosts allow = 192.168.100. 127.
    
        security = user
        encrypt passwords = yes
        socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
        interfaces = lo eth0
        bind interfaces only = yes
        password level = 20
    
        local master = yes
        os level = 65
        domain master = yes
        preferred master = yes
        null passwords = no
        hide unreadable = yes
        hide dot files = yes
    
        domain logons = yes
        logon script = login.bat
        logon path = \\%L\profiles\%U
        logon drive = H:
        logon home = \\%L\%U\.9xprofile
        wins support = yes
        name resolve order = wins lmhosts hosts bcast
        dns proxy = no
        time server = yes
        log file = /var/log/samba/log.%m
        max log size = 50
        smb passwd file = /etc/samba/private/smbpasswd
    
        add user script = /usr/sbin/useradd -m %u
        delete user script = /usr/sbin/userdel -r %u
        add group script = /usr/sbin/groupadd %g
        delete group script = /usr/sbin/groupdel %g
        add user to group script = /usr/sbin/usermod -G %g %u
        add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null %u
        passwd program = /usr/bin/passwd %u
        passwd chat = "*New password:*" %n\r "*New password (again):*" %n\r \ "*Password changed*"
    
    [netlogon]
        path = /var/lib/samba/netlogon
        public = no
        writeable = no
        browseable = no
    
    [profiles]
        path = /var/lib/samba/profiles
        browseable = no
        writeable = yes
        default case = lower
        preserve case = no
        short preserve case = no
        case sensitive = no
        hide files = /desktop.ini/ntuser.ini/NTUSER.*/
        write list = @users @root
        create mode = 0600
        directory mode = 0770
        nt acl support = Yes
    
    [homes]
        comment = Home Directories
        browseable = no
        read only = no
        create mode = 0750
        path = /home/%U
        valid users = %S
        guest ok = no
    
    [winstuff]
        comment = Windows Stuff
        path = /usr/local/site/windows
        public = yes
        writeable = no
        browseable = yes
        write list = @users
    

After the config file is created, restart Samba by issuing the following command
as root:

    '''/etc/rc.d/rc.samba stop'''
    '''/etc/rc.d/rc.samba start'''


Next, we need to add our users to Samba. Please note that is temporary for step 1.
We will replace that with LDAP authentication in step 3.

    '''smbpasswd -a root'''
    '''smbpasswd -a &lt;USER&gt;'''

The 1st command is required to be able to add your Windows machines to the Domain.
Run the 2nd one for every user you want to login to this PDC.

----
More to come... I'm not done with the setup.


--[[User:Dadexter|dadexter]] 23:51, 27 Aug 2005 (GMT)</text>
    <sha1>d258027cfc27a73831ee90f20cd21ec2da25a37a</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Screen</title>
  <ns>0</ns>
  <id>147</id>
  <revision>
    <id>175</id>
    <timestamp>2009-06-06T23:19:13Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="737" xml:space="preserve">[[Category:Tutorials]]
The screen tool is most commonly used with irc clients. What it
actually does is makes the program run in the background and then
resume later. For this example im going to use the irssi irc
client. First you need to start a term and type the following:

 screen -S irc

Now the -S means what to call the actual session name. Now we have a
session started, now lets launch irssi:

 irssi

Now we see the normal screen and this is nothing new. Now press
ctrl-a-d. Now your session has now gone away. Now say you want to come
back later on another ssh session? well this is possible!:

 screen -r irc

This now shows the session of irssi. Now isn't that COOL :). This is
useful for all programs as well not just irc.</text>
    <sha1>4f788c3561a1855ab71863abbcf86186ab5e54cd</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Security Assessment using Nmap</title>
  <ns>0</ns>
  <id>148</id>
  <revision>
    <id>176</id>
    <timestamp>2009-06-06T23:19:47Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7136" xml:space="preserve">[[Category:Tutorials]]
This tutorial will be a general guide on how to determine what ports have listening services and how to assess if those ports are available to the world wide web.  We will be using Nmap, netstat, and telnet.

We are concerned with three different things:

    1. Assessing localhost (127.0.0.1) on a given machine.

    2. Assessing the machine's IP from another machine within the LAN.

    3. Assessing the machine from the internet.

Running Nmap against localhost can be deceiving, as the ports that are listening on the machine may not actually be available to another machine, on or off the LAN. Note that 127.0.0.1 only pertains to the local machine. This is the loopback address that every machine uses to communicate to itself. I'll compare a localhost scan against a scan that was conducted from another machine on the LAN.

I'll scan localhost first:

    -su-2.05b# nmap localhost

    Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-09-12 17:20 EDT
    Interesting ports on localhost.home (127.0.0.1):
    Not shown: 1674 closed ports
    PORT STATE SERVICE
    22/tcp open ssh
    25/tcp open smtp
    3306/tcp open mysql
    5801/tcp open vnc-http-1
    5901/tcp open vnc-1
    6001/tcp open X11:1

    Nmap finished: 1 IP address (1 host up) scanned in 10.662 seconds

Now, I'll scan the machine's IP from another machine:

    root@slackbox:~# nmap 10.150.1.103

    Starting Nmap 4.20 ( http://insecure.org ) at 2007-09-12 17:36 EDT
    Interesting ports on delly (10.150.1.103):
    Not shown: 1693 filtered ports
    PORT STATE SERVICE
    22/tcp open ssh
    80/tcp open http
    3306/tcp open mysql
    5900/tcp closed vnc
    MAC Address: 00:C0:4F:61:28:1F (Dell Computer)

    Nmap finished: 1 IP address (1 host up) scanned in 22.277 seconds

Comparing the two scans, some things are readily apparent: port 25/tcp and 5801/tcp, 5901/tcp, and 6001/tcp aren't as exposed as the other services are. Also, note that certain ports are possibly bound to the IP but not the loopback. The more important aspect of these two scans is the services listening on a non-loopback address, because services use IPs to communicate to other machines, not loopback devices.

So, TCP ports 25, 5801, 5901, and 6001 appear to be open. We can test this. Remember, we're concerned about whether these ports can be seen as open to the internet. We'll test this by using telnet. Below, I'm logged into another machine and attempting to telnet on port 25 to the machine we Nmap'd on localhost:

    root@slackbox:~# telnet 10.150.1.103 25
    Trying 10.150.1.103...
    telnet: connect to address 10.150.1.103: Connection timed out

The connection timed out. This is proof that the machine doesn't have services on 10.150.1.103:25

We can also test by running 'netstat -an' on the machine. Whle netstat doesn't connect to the port in question, it does indicate what interface services are using:

    -su-2.05b# netstat -an | grep -i listen
    tcp4 0 0 *.5801 *.* LISTEN
    tcp4 0 0 *.5901 *.* LISTEN
    tcp4 0 0 *.6001 *.* LISTEN
    tcp4 0 0 *.3306 *.* LISTEN
    tcp4 0 0 10.150.1.103.8118 *.* LISTEN
    tcp4 0 0 10.150.1.103.80 *.* LISTEN
    tcp4 0 0 127.0.0.1.25 *.* LISTEN
    tcp4 0 0 *.22 *.* LISTEN
    tcp6 0 0 *.22 *.* LISTEN

See port 25? What IP address is assigned to the service? Loopback! This means that this service isn't exposed to any other machine on the LAN or internet. The other services are listening (for example, *.22) but the '*' usually means that the service is assigned to an interface (which may have a number of IPs assigned to it). Ports 80 and 8118 have an IP assigned to the service, instead of '*'. This means that only IP 10.150.1.103 is assigned to that interface. Ports 80 and 8118 also do not show up when scanning localhost, but yet I can telnet to port 80 and 8118 when using the telnet command (and also browser), using 'telnet localhost 80' or 'telnet localhost 8118'. Port 80 is a web server. Port 8118 is a Privoxy proxy. The reason is probably because my PF install on that machine filters some loopback traffic. If I scan the IP of the machine, port 80 is then detected. The reason is because PF is configured to allow port 80 traffic to/from 'slackbox' from/to 10.150.1.103.

What's curious is the fact that the VNC ports (5801, 5901) are showing as assigned to an interface, but not 127.0.0.1 and they aren't reachable from the outside of the machine (so sayeth nmap).  They may well be assigned to the 'lo' interface or iptables/pf may be filtering this traffic...this is worth checking out at a later time.

All of this is very elaborate. Everything has to be taken into consideration: what the firewall does/doesn't allow; what services run on 127.0.0.x; what services run on interfaces; what services run on IP addresses.

The last thing we'll do is scan the LAN from the internet. The results will be determined by what ports the gateway router/firewall are forwarding to machines within the LAN. For example, I know I've port 22/tcp open to the world because I've told my gateway firewall to forward any traffic on 22/tcp to 10.150.1.103. I also don't allow much else and also allow some traffic to be forwarded to different machines within the LAN. So, when a scan is being conducted from the outside, the whole LAN's security posture is taken into account. Now, let us scan from the internet:

    Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
    Interesting ports on pool-xx-xxx-xx-xx.washdc.fios.verizon.net  xx.xxx.xx.xxx):
    (The 1599 ports scanned but not shown below are in state: filtered)
    Port State Service
    22/tcp open ssh
    3306/tcp open mysql 

NICE! Of all the scans we've conducted thus far, this is the one that is most important. The other scans paint the smaller picture, but this one puts it all together and is THE security assessment that one wants to conduct. So, you can see, ports 22 and 3306 are open to the world. This could be two different machines that need those ports open to the internet, or this could be one machine that has those two ports open to the world wide web. While I can reach those ports, my firewall is configured to allow communication from the machine I scanned from. If a machine, from Google.com or any other IP/domain that is not accounted for within the FW policy, attempted the same thing, those ports wouldn't show as opened, as the firewall would drop the traffic.  So, while the two ports appear to be open to the world in the above results, they actually aren't, as the traffic is being filtered.

I hope all of this has helped some in understanding security and how to assess your LAN gateway and hosts within the LAN. We've used Nmap, telnet, and netstat to determine the security posture of a given machine. There are other tools that I didn't mention for brevity, (such as socklist, tcpdump, snort, for example) but Unix and Linux machines offer much in the way of testing security of a machine.

''This tutorial is mirrored  [http://slackfiles.blogspot.com/2007/09/assessment-of-hardened-box.html here]''

--[[User:Unixfool|Ron]] 00:44, 16 September 2007 (EDT)</text>
    <sha1>c2629de03fead7d8e0c8e98979a155bd663ba05e</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Sdogi's Script</title>
  <ns>0</ns>
  <id>149</id>
  <revision>
    <id>177</id>
    <timestamp>2009-06-06T23:20:26Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2353" xml:space="preserve">[[Category:Security]]
&lt;pre&gt;# Internet + sharing
adsl-start
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -o "ppp0" -j MASQUERADE

iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

# BANNED FROM LOGS
iptables -A INPUT -i "ppp0" -p tcp --dport 445 -j DROP
iptables -A INPUT -i "ppp0" -p tcp --dport 135 -j DROP
iptables -A INPUT -i "ppp0" -p tcp --dport 139 -j DROP
iptables -A INPUT -i "ppp0" -p tcp --dport 113 -j REJECT
iptables -A INPUT -i "ppp0" -p tcp --dport 2449 -j DROP

# Forwarded or accepted
iptables -t nat -PREROUTING -i "ppp0" -p tcp --dport 6002 -j DNAT --to 192.168.0.3
iptables -t nat -A PREROUTING -i "ppp0" -p tcp --dport 1988 -j DNAT --to 192.168.0.2
iptables -t nat -A PREROUTING -i "ppp0" -p udp --dport 1988 -j DNAT --to 192.168.0.2
iptables -t nat -A PREROUTING -i "ppp0" -p tcp --dport 6666 -j DNAT --to 192.168.0.1:8000
iptables -A INPUT -i "ppp0" -p tcp --dport 1984 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 13931 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 8080 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 8001 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 8000 -j ACCEPT
iptables -A INPUT -s 192.168.0.4 -p tcp --dport 6000 -j ACCEPT
iptables -A INPUT -s 192.168.0.4 -p udp --dport 177 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 2086 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 31731 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 2000:2500 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 6881:6889 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 9176 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 2234 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 5534 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 80 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 21 -j ACCEPT
iptables -A INPUT -i "ppp0" -p tcp --dport 22 -j ACCEPT


# Log everything else to messages and drop them(logging is not really good idea because
# /var/log/messages can get full pretty fast. Look above for making them not show up in logs)

iptables -A INPUT -i "ppp0" -p tcp --dport 1:65535 -j LOG
iptables -A INPUT -i "ppp0" -p tcp --dport 1:65535 -j DROP
&lt;/pre&gt;</text>
    <sha1>2a2ef8e7db25076f7eab5cf0804c0e83192bd307</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Selkfoster firewall</title>
  <ns>0</ns>
  <id>150</id>
  <revision>
    <id>178</id>
    <timestamp>2009-06-06T23:21:01Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4857" xml:space="preserve">=== rc.fireball ===
is a simple and powerful firewall script for a Home PC.
The most recent version of this script can be found here: http://selkfoster.com.ar/scripts/rc.fireball.gz

&lt;pre&gt;
#!/bin/sh
# Start/stop/restart/status
#
# Versión: 0.3	Mié Ago 30 16:42:25 ART 2006
#
# Escrito por Matías A. Fonzo &lt;selkfoster@gmail.com&gt;, &lt;http://selkfoster.com.ar&gt;.

IPT=/usr/sbin/iptables

fireball_start() {
  # INTERFACE POR DEFECTO:
  IFACE="ppp0"

  # Flush de reglas:
  $IPT -F; $IPT -X; $IPT -Z

  # Políticas por defecto:
  $IPT -P INPUT   DROP
  $IPT -P FORWARD DROP
  $IPT -P OUTPUT  ACCEPT

  # Bloquea las conexiones nuevas, excepto, si vienen desde adentro:
  $IPT -N block
  $IPT -A block -m state --state ESTABLISHED,RELATED -j ACCEPT
  $IPT -A block -m state --state NEW -i ! $IFACE -j ACCEPT
  $IPT -A block -m state --state NEW,INVALID -i $IFACE -j DROP
  $IPT -A block -p tcp ! --syn -m state --state NEW -i $IFACE -j DROP
  $IPT -A block -j DROP

  # Prevención de ataques SYN flood:
  $IPT -N syn-flood
  $IPT -A INPUT -i $IFACE -p tcp --syn -j syn-flood
  $IPT -A syn-flood -m limit --limit 1/s --limit-burst 4 -j RETURN
  $IPT -A syn-flood -j LOG --log-prefix "SYN flood: "
  $IPT -A syn-flood -j DROP

  # Descartar paquetes fragmentados:
  $IPT -A INPUT -i $IFACE -f -j DROP
  $IPT -A INPUT -i $IFACE -f -j LOG --log-prefix "pkt frag: "

  # Recibir PING's desde el exterior:
  $IPT -A INPUT -i $IFACE -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT

  # Loguear peticiónes de Ping:
  $IPT -A INPUT -i $IFACE -p icmp --icmp-type echo-request -j LOG --log-prefix "ping request: "

  # Activar protección contra IGMP's:
  $IPT -A INPUT -i $IFACE -p igmp -j DROP

  # Evitar Spoofing:
  $IPT -A INPUT -i $IFACE -s 127.0.0.0/8 -j REJECT --reject-with icmp-host-prohibited
  $IPT -A INPUT -i $IFACE -s 192.168.0.1/16 -j REJECT --reject-with icmp-host-prohibited


  ## Saltar a la cadena block desde las cadenas INPUT y FORWARD:
  $IPT -A INPUT   -j block
  $IPT -A FORWARD -j block

  # Evitar técnicas del tipo "OS fingerprint guessing":
  $IPT -A OUTPUT -p icmp -o $IFACE --icmp-type 3/4 -j DROP
  $IPT -A OUTPUT -p icmp -o $IFACE --icmp-type 5   -j DROP
  $IPT -A OUTPUT -p icmp -o $IFACE --icmp-type 13  -j DROP
  $IPT -A OUTPUT -p icmp -o $IFACE --icmp-type 14  -j DROP
  $IPT -A OUTPUT -p icmp -o $IFACE --icmp-type 15  -j DROP
  $IPT -A OUTPUT -p icmp -o $IFACE --icmp-type 16  -j DROP
  $IPT -A OUTPUT -p icmp -o $IFACE --icmp-type 17  -j DROP
  $IPT -A OUTPUT -p icmp -o $IFACE --icmp-type 18  -j DROP

# Verificación de dirección.
for f in /proc/sys/net/ipv4/conf/*/rp_filter ; do
  echo "1" &gt; $f
done

# Envio de mensajes de redireccion.
for f in /proc/sys/net/ipv4/conf/*/send_redirects ; do
    echo "0" &gt; $f
done

# FORWARD entre interfaces (routing).
echo "0" &gt; /proc/sys/net/ipv4/ip_forward

# Redireccion de interfaces.
for f in /proc/sys/net/ipv4/conf/*/accept_redirects ; do
    echo "0" &gt; $f
done

# Para gateway o enrutador.
for f in /proc/sys/net/ipv4/conf/*/accept_source_route ; do
  echo "0" &gt; $f
done

# IP dinámica (SLIP, PPP o DHCP).
echo "1" &gt; /proc/sys/net/ipv4/ip_dynaddr

# Ignorar respuestas extrañas de ICMP.
echo "1" &gt; /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses

# Ignorar broadcasts.
echo "1" &gt; /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts

# Protección TCP SYN Cookie.
echo "1" &gt; /proc/sys/net/ipv4/tcp_syncookies

# Log marciano (paquetes con direcciónes imposibles).
echo "1" &gt; /proc/sys/net/ipv4/conf/all/log_martians

# Timestamps.
echo "0" &gt; /proc/sys/net/ipv4/tcp_timestamps

# Reducir la habilidad de los DoS, reduciendo los timeouts.
# Defaults: 60 - 7200 - 16384
echo "30" &gt; /proc/sys/net/ipv4/tcp_fin_timeout
echo "3600" &gt; /proc/sys/net/ipv4/tcp_keepalive_time
echo "4096" &gt; /proc/sys/net/ipv4/tcp_max_orphans

echo "1" &gt; /proc/sys/net/ipv4/tcp_window_scaling
echo "0" &gt; /proc/sys/net/ipv4/tcp_sack

  echo "fireball start on $IFACE"
}

fireball_stop() {
  # flush de reglas...
  $IPT -F; $IPT -X; $IPT -Z

  # set de políticas...
  $IPT -P INPUT   ACCEPT
  $IPT -P FORWARD ACCEPT
  $IPT -P OUTPUT  ACCEPT

  # remover modulos...
  # para kernel 2.6.16+
  for modules in ipt_REJECT xt_limit ipt_LOG xt_tcpudp xt_state iptable_filter ip_conntrack ip_tables x_tables ; do
    rmmod $modules 2&gt; /dev/null
  done
	
  # anterior a 2.6.16 y de la serie 2.4
  #for modules in ipt_REJECT ipt_limit ipt_LOG ipt_state iptable_filter ip_conntrack ip_tables ; do
  #  rmmod $modules 2&gt; /dev/null
  #done   
	
  echo "fireball stopped"
}

fireball_restart() {
  echo -n "Restarting... "
  fireball_start
}

fireball_status() {
  $IPT -L -n -v
}

case "$1" in
'start')
  fireball_start
  ;;
'stop')
  fireball_stop
  ;;
'restart')
  fireball_restart
  ;;
'status')
  fireball_status
  ;;
  *)
  echo "uso $0 start|stop|restart|status"
esac

&lt;/pre&gt;
[[Category:Security]]</text>
    <sha1>befb4df4f2529bbb9d399b4ea9336839c185a402</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Sendmail: Listen on Loopback Only</title>
  <ns>0</ns>
  <id>151</id>
  <revision>
    <id>179</id>
    <timestamp>2009-06-06T23:21:37Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1779" xml:space="preserve">It is almost always necessary to run the [[sendmail]] daemon, even on systems that don't act as public SMTP servers.  Without sendmail, output from [[cron]] and [[at]] jobs won't be delivered.  However, unnecessarily exposing your SMTP ports to the Internet or even to a large LAN is poor security practice.  This article will explain how to configure sendmail to listen ''only'' on the local [[loopback]] interface (127.0.0.1).

=== Required Packages ===

You must have the '''sendmail-cf''' package installed, which in turn requires the '''m4''' package.  These packages are available as part of the official Slackware distribution.

=== Edit the Configuration File ===

Change into the directory '''/usr/share/sendmail/cf/cf'''.  This directory is installed by the sendmail-cf package and contains a wide variety of sample sendmail configuration files.  The default configuration on Slackware is the '''sendmail-slackware.mc''' file.  Edit this file, and make the following additions:

* Along with the other FEATURE options, add this line:

  &lt;code&gt;FEATURE(`no_default_msa')dnl&lt;/code&gt;

* Right before the MAILER lines, add this line:

  &lt;code&gt;DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1,Name=MTA')dnl&lt;/code&gt;

== Install the Configuration File ==

  &lt;tt&gt;m4 sendmail-slackware.mc &gt;/etc/mail/sendmail.cf&lt;/tt&gt;

'''Warning:''' If you had previously hard-coded any configuration options in sendmail.cf, they will be overwritten.  It is recommended (and generally easier) to make changes only to sendmail-slackware.mc and then rebuild sendmail.cf with the command above.

== Restart Sendmail ==

  &lt;tt&gt;/etc/rc.d/rc.sendmail restart&lt;/tt&gt;

== Sources ==

* http://rg03.wordpress.com/2007/01/20/making-sendmail-listen-on-the-loopback-interface-only-under-slackware/

[[Category:Security]]</text>
    <sha1>9e20fa0bf226075f8a3f32133b1ad2448991e04e</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Sendmail TLS SASL SMTP-AUTH</title>
  <ns>0</ns>
  <id>152</id>
  <revision>
    <id>180</id>
    <timestamp>2009-06-06T23:22:18Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13962" xml:space="preserve">[[Category:Tutorials]] 

= Sendmail TLS SMTP-AUTH - A Quick and Dirty howto =

Reliable, flexible, and configurable enough to solve any mail routing needs, '''sendmail''' has withstood the test of time, but has become no less daunting in its complexity. Even the most experienced system administrators have found it challenging to configure and difficult to understand. We cut through the chase and describe how to setup sendmail with industry standard encryption and discourage spam in less than an hour. Although described as a Slackware specific howto, the actual setup is similar for all UNIX's.

This HOWTO is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. Copyright (C) 2006 Strykar: s_at_hackerzlair_dot_org  

* NOTE: I hate wiki markup and the latest and much more readable version of this howto can always be found at [http://www.hungryhacker.com/articles/misc/sendmail_howto.html]

== Sendmail server configuration achieved by this howto: ==

* SMTP-AUTH based relay for authorized users only.
* Encrypted SMTP-AUTH client/server transaction preventing sniffing of username and passwords.
* Configure and use Cyrus SASL to verify user credentials against the UNIX shadow file.
* Create and use your own SSL certificates. Get them signed at no charge by cacert.org and use their CRL.
* Disable using the old SSLv2 protocol and support SSLv3 and TLSv1.
* Enable/Disable use and verification of client certificates for user identification.
* Throttle the number of connections sendmail will accept and limit the number of child processes it spawns.
* Use features like delay checks to make full use of the versatile access_db.
* Enable blacklisting recipients and use DNSBL for real-time blackisting of known spam hosts.
* Use regular expressions and the MAP_REGEX feature to ease complicated header processing and re-writing. -- '''TBD'''
* The ability to add any missing/desired sendmail feature to itself by mailing the author a postcard with pictures of mountains in your area.

== Prerequisites: ==

* Untouched Slackware 12 or updated to Slackware-current install Sendmailwise.
* Latest version of sendmail - v 8.14.1 at the time of writing. You can check your version by &lt;code&gt;sendmail -d0.1 -bt &lt; /dev/null&lt;/code&gt; 
* Just &lt;code&gt;wget &amp;&amp; upgradepkg&lt;/code&gt; the latest version from your favorite Slackware mirror.
* Make sure the output of the command above at least includes: &lt;blockquote&gt;Compiled with: &lt;code&gt;DNSMAP LOG MAP_REGEX SASLv2 STARTTLS USERDB&lt;/code&gt;&lt;/blockquote&gt;
* Ensure you have the latest version of Cyrus-SASL - v 2.1.22 at the time of writing. See that our required password mechanisms are allowed by doing:
&lt;code&gt;root@john:~# saslauthd -v saslauthd 2.1.22 authentication mechanisms: getpwent rimap shadow&lt;/code&gt;&lt;br/&gt;shadow is what we will use.

* A real hostname that is available when you: &lt;code&gt;host myhost.org&lt;/code&gt;
* Reset any configurations you may have played with for Cyrus-SASL and sendmail. Keep your pack of smokes and mug of coffee handy. Figure out why your system won't play nice if it doesn't meet any of the above prerequisites.
* Call that friend who told you to move to Postfix and ask him to call you back in an hour.


=== Diving right in: ===

''For the purpose of this HOWTO, we will assume the FQDN of the host is &lt;code&gt;john.doe.org.&lt;/code&gt;''

First, start by creating your private key and Certificate Signing Request (CSR) as shown in the much easier than before steps below. The only field in you need to fill is the Common Name (CN). Put your mailserver hostname there when prompted, like &lt;code&gt;mail.doe.org&lt;/code&gt;

&lt;br /&gt;&lt;code&gt;root@john:~# openssl genrsa 1024 &gt; smtp.key.pem &lt;br /&gt;root@john:~# openssl req -new -key smtp.key.pem &gt; newreq.csr&lt;/code&gt;

Get the CSR signed by CAcert.org. That will give you the server certificate, paste it into a file named &lt;code&gt;smtp.cert.pem&lt;/code&gt;


'''1.''' Make sure you have the user &lt;code&gt;smmsp&lt;/code&gt;, sendmail will not start up unless it has it's own userid:

&lt;code&gt;root@john::~# cat /etc/passwd | grep smmsp smmsp:x:25:25:smmsp:/var/spool/clientmqueue:&lt;/code&gt;

&lt;br/&gt;If not, create one:

&lt;code&gt;root@john:~# groupadd -g 25 smmsp &lt;br /&gt;root@john:~# useradd -u 25 -g 25 -c smmsp -d /var/spool/clientmqueue -s /usr/bin/true smmsp &lt;br /&gt;root@john:~# mkdir -p /var/spool/clientmqueue /var/spool/mqueue &lt;br /&gt;root@john:~# chmod 770 /var/spool/clientmqueue &lt;br /&gt;root@john:~# chown smmsp /var/spool/clientmqueue &lt;br /&gt;root@john:~# chgrp smmsp /var/spool/clientmqueue &lt;br /&gt;root@john:~# chmod 700 /var/spool/mqueue &lt;br /&gt;root@john:~# chown root /var/spool/mqueue &lt;br /&gt;root@john:~# chgrp daemon /var/spool/mqueue &lt;/code&gt;


'''2.''' Now edit &lt;code&gt;/etc/mail/access&lt;/code&gt; and make sure your hostname is in there:

&lt;code&gt;root@john:~# cat /etc/mail/access &lt;br/&gt;john.doe.org RELAY &lt;br/&gt;doe.org RELAY&lt;/code&gt;


'''3.''' Now edit &lt;code&gt;/etc/hosts&lt;/code&gt; and make sure 127.0.0.1 points to localhost:

&lt;code&gt;root@john:~# cat /etc/hosts &lt;br/&gt;127.0.0.1 localhost localhost.localdomain &lt;br/&gt;1.2.3.4 john.doe.org john&lt;/code&gt;

Replace 1.2.3.4 with the actual public IP address of your mailserver.


'''4.''' Now edit &lt;code&gt;/etc/resolv.conf&lt;/code&gt; and make sure the DNS settings your ISP provided you are in there:

&lt;code&gt;root@john:~# cat /etc/resolv.conf search doe.org nameserver 1.2.3.4&lt;/code&gt;

Replace 1.2.3.4 with the IP address of your ISP's DNS box.


'''5.''' Create a directory where sendmail will read your certificates for TLS from:
&lt;code&gt;root@john:~# mkdir /etc/mail/certs&lt;/code&gt;

Download the CAcert root certificate and their CRL from http://www.cacert.org/index.php?id=3 and name them &lt;code&gt;CA.cert.pem&lt;/code&gt; and &lt;code&gt;revoke.crl&lt;/code&gt;
Copy all three (including the private key file) into &lt;code&gt;/etc/mail/certs&lt;/code&gt;

These need strict permissions as they shouldn't be world-readable:

&lt;code&gt;root@john:~# chmod -R 700 /etc/mail/certs root@john:~# chown -R root:sys /etc/mail/certs&lt;/code&gt;


'''6.''' Whip up your favorite editor (mine's &lt;code&gt;joe&lt;/code&gt;) and edit &lt;code&gt;/usr/share/sendmail/cf/cf/sendmail-slackware-tls-sasl.mc&lt;/code&gt;

Make sure it includes all the options below. CAREFULLY READ the notes after the end of the configuration, denoted by &lt;code&gt;dnl# EOF&lt;/code&gt; to understand the additions I have made to the default &lt;code&gt;sendmail-slackware-tls-sasl.mc&lt;/code&gt; file. Ensure you know what you're doing if you modify anything.
&lt;code&gt;
root@john:~# cat /usr/share/sendmail/cf/cf/sendmail-slackware-tls-sasl.mc&lt;br /&gt;&lt;br /&gt; dnl# This is the a sendmail .mc file for Slackware with TLS support.&lt;br /&gt; dnl# To generate the sendmail.cf file from this (perhaps after making&lt;br /&gt; dnl# some changes), use the m4 files in /usr/share/sendmail/cf like this:&lt;br /&gt; dnl#&lt;br /&gt; dnl# cp sendmail-slackware-tls.mc /usr/share/sendmail/cf/config.mc&lt;br /&gt; dnl# cd /usr/share/sendmail/cf&lt;br /&gt; dnl# sh Build config.cf&lt;br /&gt; dnl#&lt;br /&gt; dnl# You may then install the resulting .cf file:&lt;br /&gt; dnl# cp config.cf /etc/mail/sendmail.cf&lt;br /&gt; dnl#&lt;br /&gt; include(`../m4/cf.m4')&lt;br /&gt; VERSIONID(`TLS supporting setup for Slackware Linux')dnl&lt;br /&gt; OSTYPE(`linux')dnl&lt;br /&gt; dnl#&lt;br /&gt; dnl# You will need to create the certificates below with OpenSSL first:&lt;br /&gt; define(`confCACERT_PATH', `/etc/mail/certs/')&lt;br /&gt; define(`confCACERT', `/etc/mail/certs/CA.cert.pem')&lt;br /&gt; define(`confSERVER_CERT', `/etc/mail/certs/smtp.cert.pem')&lt;br /&gt; define(`confSERVER_KEY', `/etc/mail/certs/smtp.key.pem')&lt;br /&gt; define(`confCRL', `/etc/mail/certs/revoke.crl')&lt;br /&gt; dnl# These settings help protect against people verifying email addresses&lt;br /&gt; dnl# at your site in order to send you email that you probably don't want:&lt;br /&gt; define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun')dnl&lt;br /&gt; dnl# Uncomment the line below to send outgoing mail through an external server:&lt;br /&gt; dnl define(`SMART_HOST',`mailserver.example.com')&lt;br /&gt; dnl# No timeout for ident:&lt;br /&gt; define(`confTO_IDENT', `0')dnl&lt;br /&gt; dnl# Enable the line below to use smrsh to restrict what sendmail can run:&lt;br /&gt; dnl FEATURE(`smrsh',`/usr/sbin/smrsh')dnl&lt;br /&gt; dnl# LOCAL_CONFIG dnl &lt;br/&gt;dnl#CipherList=ALL:!ADH:!NULL:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:-LOW:+SSLv3:+TLSv1:-SSLv2:+EXP:+eNULLdnl#dnl&lt;br /&gt; See the README in /usr/share/sendmail/cf for a ton of information on&lt;br /&gt; dnl# how these options work:&lt;br /&gt; FEATURE(`delay_checks')dnl&lt;br /&gt; FEATURE(`use_cw_file')dnl&lt;br /&gt; FEATURE(`use_ct_file')dnl&lt;br /&gt; FEATURE(`mailertable',`hash -o /etc/mail/mailertable.db')dnl&lt;br /&gt; FEATURE(`virtusertable',`hash -o /etc/mail/virtusertable.db')dnl&lt;br /&gt; FEATURE(`access_db', `hash -T&lt;TMPF&gt; /etc/mail/access')dnl&lt;br /&gt; FEATURE(`blacklist_recipients')dnl&lt;br /&gt; dnl #FEATURE(`enhdnsbl', `relays.ordb.org', `', `t', `127.0.0.2')&lt;br /&gt; FEATURE(`dnsbl',`dnsbl.sorbs.net',`"554 Rejected spam as" $&amp;{client_addr} " found in dnsbl.sorbs.net"')dnl&lt;br /&gt; FEATURE(`enhdnsbl', `zen.spamhaus.org', `"Spam blocked see: http://www.abuse.net/sbl.phtml?IP="$&amp;{client_addr}', `t')dnl&lt;br /&gt; FEATURE(`enhdnsbl', `bl.spamcop.net', `"Spam blocked see: http://spamcop.net/bl.shtml?"$&amp;{client_addr}', `t')dnl&lt;br /&gt; FEATURE(`enhdnsbl', `list.dsbl.org', `"Spam blocked see: http://dsbl.org"$&amp;{client_addr}', `t')dnl&lt;br /&gt; FEATURE(`local_procmail',`',`procmail -t -Y -a $h -d $u')dnl&lt;br /&gt; FEATURE(`always_add_domain')dnl&lt;br /&gt; FEATURE(`redirect')dnl&lt;br /&gt; FEATURE(`no_default_msa')dnl&lt;br /&gt; dnl# Turn this feature on if you don't always have DNS, or enjoy junk mail:&lt;br /&gt; dnl FEATURE(`accept_unresolvable_domains')dnl&lt;br /&gt; EXPOSED_USER(`root')dnl&lt;br /&gt; dnl# Also accept mail for localhost.localdomain:&lt;br /&gt; LOCAL_DOMAIN(`localhost.localdomain')dnl&lt;br /&gt; MAILER(local)dnl&lt;br /&gt; MAILER(smtp)dnl&lt;br /&gt; MAILER(procmail)dnl&lt;br /&gt; dnl# Allow SASL authentication/relaying:&lt;br /&gt; define(`confAUTH_OPTIONS', `A p y')dnl&lt;br /&gt; define(`confAUTH_MECHANISMS', `LOGIN PLAIN DIGEST-MD5 CRAM-MD5')dnl&lt;br /&gt; TRUST_AUTH_MECH(`LOGIN PLAIN DIGEST-MD5 CRAM-MD5')dnl&lt;br /&gt; DAEMON_OPTIONS(`Port=smtp, Name=MTA')dnl&lt;br /&gt; DAEMON_OPTIONS(`Port=smtps, Name=MSA-SSL, M=E')dnl&lt;br /&gt;dnl# EOF
&lt;/code&gt;


Notice the filenames in &lt;br/&gt;&lt;code&gt;define(`confCACERT', `/etc/mail/certs/CA.cert.pem') &lt;br/&gt;define(`confSERVER_CERT', `/etc/mail/certs/smtp.cert.pem') &lt;br/&gt;define(`confSERVER_KEY', `/etc/mail/certs/smtp.key.pem')&lt;/code&gt; -- make sure your certificates are named exactly the same as in your mc configuration.

I use free certificates signed by [http://www.cacert.org www.cacert.org] and use their CRL - &lt;code&gt;define(`confCRL', `/etc/mail/certs/revoke.crl')&lt;/code&gt; above.

The &lt;code&gt;define(`confAUTH_OPTIONS', `A p y')dnl&lt;/code&gt; configures sendmail to:

* &lt;code&gt;A&lt;/code&gt; is a workaround for broken MTAs that do not implement RFC 2554.
* The &lt;code&gt;p&lt;/code&gt; option tells sendmail: "don't permit mechanisms susceptible to simple passive attack (e.g., &lt;code&gt;LOGIN, PLAIN&lt;/code&gt;), unless a security layer (think TLS tunnel) is active."
* The &lt;code&gt;y&lt;/code&gt; option prohibits anonymous logins.

Take note that this will only allow &lt;code&gt;LOGIN/PLAIN SMTP-AUTH&lt;/code&gt; after encryption has been established in a TLS tunnel. Allowing both TLS and non-TLS &lt;code&gt;PLAIN/LOGIN SMTP-AUTH&lt;/code&gt; is left as an exercise to the reader.

Read: http://www.sendmail.org/~ca/email/doc8.12/op-sh-5.html#sh-5.6 for more information.

The &lt;code&gt;define(`confCONNECTION_RATE_THROTTLE', `100')&lt;/code&gt; and &lt;code&gt;define(`confMAX_DAEMON_CHILDREN',`1000')&lt;/code&gt; are for my configuration and should be set to 50% higher than what your requirements are. If you don't understand what this does (sendmail forks); comment those two lines out with a &lt;code&gt;dnl#&lt;/code&gt; before them like: &lt;code&gt;dnl# define (`confMAX_DAEMON_CHILDREN',`1000')&lt;/code&gt;

None of my user's email clients use certificates; this tells sendmail not to ask for them for one: &lt;code&gt;define(`confTLS_SRV_OPTIONS', V')&lt;/code&gt;

'''SLACKWARE USERS NOTE''' line 37:

&lt;code&gt;LOCAL CONFIG CipherList=ALL:!ADH:!NULL:!EXPORT56:RC4 RSA: HIGH: MEDIUM:-LOW: SSLv3: TLSv1:-SSLv2: EXP: eNULL&lt;/code&gt;

This disables using the older SSLv2 protocol and allows SSLv3 and TLSv1. You'll need some &lt;code&gt;openssl ciphers&lt;/code&gt; and &lt;code&gt;perl&lt;/code&gt;-fu to get this going with Slackware 12 as it's not compiled with &lt;code&gt;_FFR_TLS_1. STARTTLS&lt;/code&gt;

Read [http://sial.org/howto/sendmail/cipherlist this for info] on setting it up in Slackware, it's trivial. Some older clients don't speak TLS and you may want to skip this.


'''7.''' Now:

&lt;code&gt;root@john:~# cd /usr/share/sendmail/cf/cf &lt;br/&gt;root@john:~# m4 sendmail-slackware-tls-sasl.mc &gt; /etc/mail/sendmail.cf&lt;/code&gt;

Also remember that the mc file should always end in a new line. So hit enter at the end of &lt;code&gt;sendmail-slackware-tls-sasl.mc&lt;/code&gt; if m4 crashes with an &lt;code&gt;m4: INTERNAL ERROR: recursive push_string error&lt;/code&gt;.


'''8.''' If the previous command gives no errors, you're done! Simply restart sendmail using &lt;code&gt;/etc/rc.d/rc.sendmail restart&lt;/code&gt;

Now see what sendmail is saying by &lt;code&gt;tail -f /var/log/maillog&lt;/code&gt;

You can increase log verbosity by adding: &lt;code&gt;-O LogLevel=16&lt;/code&gt; to &lt;code&gt;/etc/rc.d/rc.sendmail&lt;/code&gt;


'''9.''' Also: Add hosts for which you receive mail to &lt;code&gt;/etc/mail/local-host-names&lt;/code&gt;

&lt;code&gt;root@john:~# cat /etc/mail/local-host-names&lt;/code&gt;
&lt;code&gt;&lt;br/&gt;# names of hosts for which we receive email &lt;br/&gt;john.doe.org doe.org&lt;/code&gt;


'''10.''' Make sure SASL is with you:

&lt;code&gt;root@john:~# cat /usr/lib/sasl2/Sendmail.conf&lt;/code&gt;
&lt;br/&gt;&lt;code&gt;pwcheck_method:saslauthd mech_list:login plain&lt;/code&gt;

&lt;code&gt;root@john:~# testsaslauthd -u yourusername -p yourpassword&lt;/code&gt;

If you see:

&lt;code&gt;0: OK! Success!&lt;/code&gt;

Congratulations! SASL is now working.

If not, make sure saslauthd is running by: &lt;code&gt;/etc/rc.d/rc.saslauthd start&lt;/code&gt;


'''11.''' Most errors are because of not following this HOWTO to the T.

Go over each step again and confirm you did everything right.</text>
    <sha1>1c686bb774fa50e46559d9f5c22d40e28dc0bf33</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Server firewall</title>
  <ns>0</ns>
  <id>153</id>
  <revision>
    <id>181</id>
    <timestamp>2009-06-06T23:22:58Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="462" xml:space="preserve">An iptables script with ingress/egress filtering, rate-limiting, logging and dynamic IP allow/block listing and more.

Useful as a starting point when making your own server firewall policy.
Does not do NAT and is intended for a standalone public server running some services.

To prevent having to update the script in 2 places, you can find the latest version at http://www.hungryhacker.com/articles/security/rc.firewall.html


- Strykar

[[Category:Security]]</text>
    <sha1>18979e026e1777142bfaef17fc6f66a178a39e0c</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Shoutcast radio</title>
  <ns>0</ns>
  <id>154</id>
  <revision>
    <id>182</id>
    <timestamp>2009-06-06T23:23:25Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7021" xml:space="preserve">= Introduction =

This tutorial is written for people who want to broadcast music to other people but don't know how. This tutorial is dealing with SHOUTCAST client and server, although there are many others. Also this tutorial is going to teach you how to make a "radio" user. So you can give other people this users password and they can broacast music too.

= Getting Started =

First thing to do is make an user account for radio. Let's choose user radio:

&lt;pre&gt;adduser radio&lt;/pre&gt;

Put the home directory wherever you want. 

Firstly, download the [http://www.shoutcast.com/download/files.phtml server] and [http://www.shoutcast.com/download/broadcast.phtml broadcasting tool].

Now comes unpacking part.. first let's unpack server:

&lt;pre&gt;
tar zxvf shoutcast-(your version here).tar.gz
tar zxvf sc_trans_posix_(your version here).tgz
&lt;/pre&gt;

You should rename the server directory to shoutcast:

&lt;pre&gt;mv shoutcast-(your version here).tar.gz shoutcast&lt;/pre&gt;

and broadcasting tools folder to sc_sender:

&lt;pre&gt;mv sc_trans_posix_(your version here).tgz sc_sender&lt;/pre&gt;

This is done to make scripts work, we talk about them later. Now you should configure server and broadcasting tool as you like. There are some things you should definately do though, for the scripts. 

= Configuring the Broadcasting Tool =

First create a playlist file:

&lt;pre&gt;touch sc_sender/playlist&lt;/pre&gt;

Now configure the broadcasting tool. Let's cd to it's directory and delete some files we don't want and rename binary:

&lt;pre&gt;
cd sc_sender
rm sc_trans_freebsd sc_trans_macosx example.lst # unneeded files
mv sc_trans_linux sender # rename for convenience
&lt;/pre&gt;

Now open sc_trans.conf in your favourite editor, and change:
* "PlaylistFile" to "playlist"
* "ServerIP" to "localhost"
* "LogFile" to blank
* Your password
* "Shuffle" to "0"

The logfile is blanked to avoid broadcasting tool crashing. When log file grows too big, the broadcasting tool usually crashes.

There are lots of other things to edit; fortunately this file is well commented.

= Configuring the Shoutcast Server =

&lt;pre&gt;cd ../shoutcast &amp;&amp; pico sc_serv.conf&lt;/pre&gt;

Only thing you need here is setting password to the same password you did set broadcasting tool. Then edit 'MaxUser' to something you can handle. And then disable LogFile again.(same problem as broadcasting tool):

&lt;pre&gt;LogFile=&lt;/pre&gt;

Nothing more is needed. You should edit things like 'TitleFormat' etc for making it look nice on http:/yourhost:8000 and client player.

= Configuration of scripts =

Now create 'bin' directory to your radio user's root dir.

&lt;pre&gt;mkdir bin&lt;/pre&gt;

After that create a file '.profile' to your users root dir.

&lt;pre&gt;pico .profile&lt;/pre&gt;

Add this line to that file:

&lt;pre&gt;export PATH=~/bin:$PATH&lt;/pre&gt;

Character ~ stands for your homefolder, so with my user radio it's like /home/radio/ and ~/bin means /home/radio/bin/. Now if you use program 'screen' alot then you should add the same line to a file .bashrc too. Because 'screen' doesn't use .profile.

Now go to your bin directory and download scripts.

&lt;pre&gt;cd ~/bin/&lt;/pre&gt;
and
&lt;pre&gt;wget http://www.hot.ee/sdogi/scripts.tar.gz&lt;/pre&gt;

then unpack them and delete scripts.tar.gz

&lt;pre&gt;tar zxvf scripts.tar.gz&lt;/pre&gt;
and
&lt;pre&gt;rm scripts.tar.gz&lt;/pre&gt;

These scripts are all simple bash scripts. If you didn't follow my filenaming and playlist creation then you can always change filenames from those scripts. Also you could change them however you like and put a newer and better ones link up here. These are kind a outdated. Now I have created scripts that you can use from remote host. Like you write "next" and ssh connection is made to radio server to change the song with signal. It is actually easy to implement to those scripts if you are familiar with bash. Although it is possible that I will some day add my improved scripts here.

= Add command =

Add command works like this. You go to some folder, find some file you like, and then you write

&lt;pre&gt;add filename.mp3&lt;/pre&gt;

Pretty simple eh? Anyway, if i remember correct it won't support adding multible files, if it does it's great. But what it does support is just writing add, then it adds all files from folder, also the folder name, which could screw up the playing, so you usually do like this

&lt;pre&gt;cd somefolder/&lt;/pre&gt;
and
&lt;pre&gt;add&lt;/pre&gt;

and then you write edit and get rid of the folder name. Edit uses pico so you just press Ctrl+K on the folder line and it removes the whole line.

= Other scripts and using them all together =

Now basic usage of those scripts is like this. You log to system, want to change songs... first you write 'dlist' it deletes your old playlist. Then you go and add some mp3's with add command. If just wrote add in a folder you write 'edit' after adding all the songs and you remove stuff you don't want. These could be the songs you don't want, folder names and maby even pictures or some other crap. After you have done editing you just write 'reload' to load new playlist in. After that you can again delete that playlist, it's known to broadcasting tool already.

For checking what files are in the playlist you write 'list', dohh.. for next song you write 'next' if you want to check what song is playing without going to webinterface(http://localhost:8000) you write 'radio'. Also there is a command 'shuffle' which shuffles, dohh.

= Making it all run 24/7 =

When you are creating a dedicated Shoutcast server, you should make it come up even when program crashes or computer goes rebooting for some reason. For this i have made simple spawn scripts. You can get them here:

&lt;pre&gt;wget http://www.hot.ee/sdogi/spawn.tar.gz&lt;/pre&gt;

Extract it to your users root dir. Like this:

&lt;pre&gt;tar zxvf spawn.tar.gz&lt;/pre&gt;

Delete spawn.tar.gz, and again, if you didn't follow my renamings, sc_trans_linux to sender, etc then you should edit these two files. Spawn is for server and spawn2 is for broadcasting tool. you have to set exec bit on them if they don't have one. You do it like this:

&lt;pre&gt;chmod +x spawn spawn2&lt;/pre&gt;

Also keep in mind that if you let some other guy to broadcast to your radio you should take exec bit off from spawn2, because it will autoconnect and rune your friends broadcast be overbroadcasting it. You do it like this:

&lt;pre&gt;chmod -x spawn2&lt;/pre&gt;

And then kill your broadcasting tool. Do it like this:

&lt;pre&gt;killall sender&lt;/pre&gt;

Now for the crontab part finally. Crontab is for making it to exec spawn and spawn2 every couple of minutes. You can edit crontab by writing

&lt;pre&gt;crontab -e&lt;/pre&gt;

This brings up crontab file in vi. If you don't like vi you can do

&lt;pre&gt;export VISUAL="pico"&lt;/pre&gt;

and use pico. Then type crontab -e. Anyway, to crontab you have to add two lines, these are:

&lt;pre&gt;
*/10 * * * * ~/spawn &amp;&gt; /dev/null
*/10 * * * * ~/spawn2 &amp;&gt; /dev/null
&lt;/pre&gt;

This makes crontab hit spawn and spawn2 after every 10 minutes. You can make this interval larger or smaller if you want. And remember, if spawn and spawn2 don't have exec bit, they aren't ran.

[[Category:Tutorials]]</text>
    <sha1>1382022dee12391b59b36496910e421b4d89efe2</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Showing Slackware Changelog</title>
  <ns>0</ns>
  <id>155</id>
  <revision>
    <id>183</id>
    <timestamp>2009-06-06T23:23:57Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1672" xml:space="preserve">[[Category:Tips]]

Since this is most useful on Login, make sure to comment out /etc/rc.d/rc.S, line 385 (or 334 in Slack 12) so it reads


  # echo "$(/bin/uname -sr)." &gt; /etc/motd


Otherwise, Slackware will keep printing the kernel version you're using.


  root@tachikoma:/tmp# cat /etc/cron.daily/slacklog
  #!/bin/sh
  wget -q ftp://ftp.slackware.com/pub/slackware/slackware-10.2/ChangeLog.txt -O /tmp/slacklog.$$
  diff /tmp/.slack-changelog /tmp/slacklog.$$ &gt; /etc/motd
  mv /tmp/slacklog.$$ /tmp/.slack-changelog


  root@tachikoma:/tmp# cat /etc/motd
  0a1,17
  &gt; Tue Sep 19 14:07:49 CDT 2006
  &gt; patches/packages/gzip-1.3.5-i486-1_slack10.2.tgz:
  &gt;   Upgraded to gzip-1.3.5, and fixed a variety of bugs.
  &gt;   Some of the bugs have possible security implications if gzip or its tools are
  &gt;   fed a carefully constructed malicious archive.  Most of these issues were
  &gt;   recently discovered by Tavis Ormandy and the Google Security Team.  Thanks
  &gt;   to them, and also to the ALT and Owl developers for cleaning up the patch.
  &gt;   For further details about the issues fixed, please see:
  &gt;     http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-0758
  &gt;     http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-0988
  &gt;     http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-1228
  &gt;     http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4334
  &gt;     http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4335
  &gt;     http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4336
  &gt;     http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4337
  &gt;     http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4338
  &gt;   (* Security fix *)</text>
    <sha1>1f9d16373f60c980af859b0b36521e5e77a1894e</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Simple firewall</title>
  <ns>0</ns>
  <id>156</id>
  <revision>
    <id>184</id>
    <timestamp>2009-06-06T23:24:31Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1729" xml:space="preserve">This script should suit most people well - simply edit the EXT_IF variable below and replace it with your network interface that's connected to the net.
--rworkman

 #!/bin/bash
 
 # Define variables
 IPT=/usr/sbin/iptables		# change if needed
 EXT_IF=eth0			# external interface (connected to internet)
 
 # Enable TCP SYN Cookie Protection
 # ** comment the line below if it throws an error;
 # ** TCP_SYN_COOKIES must be enabled in the kernel
 # ** for this to work
 echo 1 &gt; /proc/sys/net/ipv4/tcp_syncookies
 
 # Disable ICMP Redirect Acceptance
 echo 0 &gt; /proc/sys/net/ipv4/conf/all/accept_redirects
 
 # Do not send Redirect Messages
 echo 0 &gt; /proc/sys/net/ipv4/conf/all/send_redirects
 
 # Enable bad error message protection
 echo 1 &gt; /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses
 
 # Enable broadcast echo protection
 echo 1 &gt; /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
 
 # Disable source-routed packets
 echo 0 &gt; /proc/sys/net/ipv4/conf/all/accept_source_route
 
 # Log spoofed packets, source-routed packets, and redirect packets
 echo 1 &gt; /proc/sys/net/ipv4/conf/all/log_martians
 
 # Set default policy to DROP
 $IPT -P INPUT DROP
 $IPT -P OUTPUT ACCEPT
 $IPT -P FORWARD DROP
 
 # Flush old rules
 $IPT -F
 
 # Allow loopback traffic
 $IPT -A INPUT -i lo -j ACCEPT
 $IPT -A OUTPUT -o lo -j ACCEPT
 
 # Allow packets of established connections and those 
 #   which are related to established connections
 $IPT -A INPUT -i $EXT_IF -p all -m state --state ESTABLISHED,RELATED -j ACCEPT
 
 # Allow incoming ssh from internet 
 # ** (uncomment the line below if you want to allow incoming ssh)
 #$IPT -A INPUT -i $EXT_IF -p tcp --destination-port 22 -m state --state NEW -j ACCEPT 
 
[[Category:Security]]</text>
    <sha1>2e131379ce0fd481c1eb0997ac7bdd0b2556463c</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>SlackRoll Tutorial</title>
  <ns>0</ns>
  <id>157</id>
  <revision>
    <id>185</id>
    <timestamp>2009-06-06T23:25:35Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16959" xml:space="preserve">&lt;strong&gt;SlackRoll&lt;/strong&gt; is a package or update manager for Slackware Linux. Part of this tutorial has been taken from its [http://wiki.github.com/rg3/slackroll/ official webpage] and FAQ. SlackRoll's defining points:

* Its internal mechanism based on package states.
* Like &lt;em&gt;slackpkg&lt;/em&gt;, SlackRoll only works with official mirrors, meaning that to keep third party packages up to date you need to perform the task by hand (recommended practice, using SlackBuild scripts) or use a second different tool.
* It does not try to compare package version numbers to decide if a package should be upgraded or not.
* Partly as a consequence of the previous point, it has no known flaws detecting package updates (including reverts), new packages, removed packages, third party packages getting an official version and blacklisted packages (&lt;em&gt;frozen&lt;/em&gt; in its terminology) being removed.
* It has a broad range of operations and features.
* It attempts to be fast. Most internal operations like listing available upgrades usually take less than one second on a modern computer.


= Installation =

== Requirements ==

* Python 2.4 or later (provided by package &lt;em&gt;python&lt;/em&gt; starting with Slackware 10.1).
* GnuPG (provided by package &lt;em&gt;gnupg&lt;/em&gt; or &lt;em&gt;gnupg2&lt;/em&gt;).
* Vim (provided by package &lt;em&gt;vim&lt;/em&gt;).
* A pager which is &lt;em&gt;less&lt;/em&gt; by default (provided by package &lt;em&gt;less&lt;/em&gt;).

== Procedure ==

Download the SlackRoll package from the [http://github.com/rg3/slackroll/downloads project download page] and install it in your system using &lt;tt&gt;installpkg&lt;/tt&gt;.

= Background Information =

The majority of SlackRoll commands that receive a list of packages expect only the package names (&lt;em&gt;foo&lt;/em&gt; as opposed to &lt;em&gt;foo-1.1-i486-3.tgz&lt;/em&gt;). Some of them also allow using a specific version, but they are the exception.

SlackRoll creates a persistent database of packages in your hard drive. Each package is in one of several possible states. Part of the initial configuration consists in deciding which states some of your packages will have. There are two types of states: states to avoid (temporary states) and normal states. When the remote Slackware official tree is updated, SlackRoll may put some packages in temporary states. By upgrading, installing, removing and marking packages your objective is to correct those packages and put them in a normal state.

== States to Avoid ==

=== New ===

New packages are packages present in the remote tree that weren't present before. You should decide if you want to install them or mark them as not installed.

=== Outdated ===

Outdated packages are present in your system, but the version you have does not match any relevant one in the remote tree. You should upgrade these packages.

=== Unavailable ===

Unavailable packages are packages present in your system. Previously, they probably existed in the remote tree, but now they do not seem to be available for downloading and installing. You should decide if you want to remove them or mark them as foreign.

== Normal States ==

=== Installed ===

Installed packages are very common. They are present in your system and in the remote tree, and both versions match.

=== Not Installed ===

Not installed packages are also very common. They are present in the remote tree but not in your system. They can be downloaded and installed if you want.

=== Foreign ===

Foreign packages are packages present in your system but not in the remote tree. However, unlike unavailable packages, they are supposed to be present in your system. No package will enter this state automatically. Only the ones you mark. It's usually reserved for third party packages and packages you build yourself. It's worth noting that if a foreign package ever appears in the remote official tree, it will be marked as installed or, probably, outdated. Thus, SlackRoll will give priority to the new official package over yours. If you still want to use your own build, mark it as frozen.

=== Frozen ===

Frozen packages are present in your system and in the remote tree. Your version may or may not match the ones from the remote tree, but SlackRoll will not tell you they need to be upgraded. No package will enter this state automatically. It's usually reserved for packages that shouldn't be upgraded automatically or ever (&lt;em&gt;aaa_elflibs&lt;/em&gt;, kernels, etc) and sometimes for customized versions of official packages. It's also worth mentioning that a frozen package will be moved to unavailable if it disappears from the remote tree. It that happens and you want to continue using it, you'll need to mark it as foreign.

= Initial Configuration =

Word of warning: it's highly recommended to do the initial configuration from an up-to-date and controlled system. This will avoid confusion and helps preventing mistakes setting the initial package states.

== Preparing Your System ==

Choose a Slackware mirror for your Slackware version. Use the &lt;em&gt;set-mirror&lt;/em&gt; operation to select one mirror. SlackRoll can work with stable trees as well as the &lt;em&gt;current&lt;/em&gt; tree. Example:

  # slackroll set-mirror 'http://slackware.example.org/slackware-current/'

Do not forget to include the trailing slash in the mirror URL. Import, to your keyring, the GnuPG key used to sign the official Slackware packages. This key can be found in Slackware CDs and DVDs as the file GPG-KEY, and you can import the key to your keyring using the command &lt;em&gt;gpg --import&lt;/em&gt;, but SlackRoll is able to download the key from the mirror and importing it automatically, if you trust the mirror.

  # slackroll import-key

Finally, retrieve the mirror information for the first time. This will download a few metadata files, and this is what you need to do when you're going to handle a new round of updates.

  # slackroll update

== Going Over Package States for The First Time ==

When you run SlackRoll for the first times, it will put every remote package not present in your system in the state New. When your system is up to date and under control, you can blindly mark every new package as not installed with the following command:

  # slackroll new-not-installed

Any third party package present in your system will be put in the state Unavailable. When your system is up to date and under control you can blindly mark all unavailable packages as foreign. &lt;em&gt;However&lt;/em&gt;, the number of foreign packages is usually not very high and forgetting to remove from your system a package that was removed from the remote tree is a common mistake. The Book of Best Practices would suggest that you review the list of unavailable packages once and carefully in order to detect packages that should not be present in your system. To print the list run:

  # slackroll list-unavailable

If you locate any package that needs to be removed, you can remove them using &lt;em&gt;removepkg&lt;/em&gt; or the &lt;em&gt;remove&lt;/em&gt; operation. The later has additional functionality so it's recommended:

  # slackroll remove foo bar

Now you can mark the rest as foreign packages.

  # slackroll unavailable-foreign

Finally, you probably want to mark some packages as frozen. It's usually a good idea to do this with &lt;em&gt;aaa_elflibs&lt;/em&gt;, kernel packages and others.

  # slackroll frozen aaa_elflibs foo bar

= Day to Day Usage =

Apart from the operations listed here, you can run the &lt;em&gt;help&lt;/em&gt; operation to get the full list of supported operations, along with a brief description of each one. A more detailed description can be found in the [http://wiki.github.com/rg3/slackroll/operations-guide operations guide].

== New Round of Updates ==

What to do when there is a new round of updates? The Book of Best Practices suggests taking care of different events in a specific order:

* Updates to glibc-solibs, sed and pkgtools need to be handled first, in that order.
* If there are new packages, handle them second.
* Then, it's time to upgrade outdated packages.
* If packages have been deleted from the remote tree, handle them last.

This is the correct order in 99% of the cases. SlackRoll will attempt to warn you and ask for confirmation if it detects you may be breaking this order. However, &lt;strong&gt;you&lt;/strong&gt; have the last word on what to do, so proceed with caution and don't break your system.

First, update the remote mirror information with the &lt;em&gt;update&lt;/em&gt; operation we mentioned before. New changelog entries will be saved to your hard drive. It's recommended that you take a look at the changelog at this point, using the &lt;em&gt;changelog&lt;/em&gt; operation. Then, get an overview of the events using the &lt;em&gt;list-transient&lt;/em&gt; operation, which will list the new, outdated and unavailable packages along with a big fat warning message if activity in key system packages is detected.

The best way to deal with glibc-solibs, sed and pkgtool updates is to use the &lt;em&gt;upgrade-key-packages&lt;/em&gt; operation.

  # slackroll upgrade-key-packages

You could also use the &lt;em&gt;install&lt;/em&gt; operation. Despite its name, it can be used to both install and upgrade individual packages. Let's suppose packages &lt;em&gt;glibc-solibs&lt;/em&gt; and &lt;em&gt;sed&lt;/em&gt; where updated:

  # slackroll install glibc-solibs sed

The &lt;em&gt;install&lt;/em&gt; operation is one of the few operations allowing you to pass specific package versions. It will proceed in the order you indicate, so remember to give the packages in the correct order if you use this method.

Second, you should handle new packages. You can clearly get a list of new packages with the &lt;em&gt;list-new&lt;/em&gt; operation. New packages can be installed with the &lt;em&gt;install&lt;/em&gt; operation as we just showed. When installing a remote package, SlackRoll will give you the opportunity of selecting the version to install if there are several available in the remote tree. Or, if you are not interested in installing a new package, mark it as not installed:

  # slackroll not-installed foo bar

If the package names are not enough for you to decide if you want to install it or not, you can always use the &lt;em&gt;info&lt;/em&gt; operation and SlackRoll will download and display the package info file (small &lt;em&gt;txt&lt;/em&gt; files in the remote tree). And, of course, be carefull with new libraries as they may have been included to extend the functionality of an existing package you may have installed.

The third step is taking care of outdated packages. For that, a few operations are available. &lt;em&gt;list-upgrades&lt;/em&gt; lets you see a summary of the available upgrades. You can download and install them with &lt;em&gt;upgrade&lt;/em&gt; or download them with &lt;em&gt;download-upgrades&lt;/em&gt; or even print their URLs with &lt;em&gt;urls-upgrades&lt;/em&gt;.

And, finally, review the list of unavailable packages. Be careful with unavailable packages. Sometimes you install a foreign package but forget to mark it as such in SlackRoll. To avoid that problem, it's better to install them with the &lt;em&gt;install-foreign&lt;/em&gt; operation. Individual unavailable packages can be removed with the &lt;em&gt;remove&lt;/em&gt; operation as we showed before, and also all of them at the same time with the &lt;em&gt;remove-unavailable&lt;/em&gt; operation.

== Installing and Removing Individual Packages ==

There are a few operations related to installing and getting some information about individual packages. The most common ones are &lt;em&gt;install&lt;/em&gt; to upgrade or install packages, &lt;em&gt;info&lt;/em&gt; to maybe download and display package info files, &lt;em&gt;urls&lt;/em&gt; to get a list of URLs and &lt;em&gt;remove&lt;/em&gt; to remove individual packages.

Operations that install packages let you manage &lt;em&gt;.new&lt;/em&gt; files after the installation is completed, in a similar way to &lt;em&gt;slackpkg&lt;/em&gt;. You can view the differences between the &lt;em&gt;.new&lt;/em&gt; file and its counterparts with &lt;em&gt;vimdiff&lt;/em&gt; (which provides a nice and colorized way of spotting the differences and maybe porting the old configuration to the new file), you can overwrite the old file with the &lt;em&gt;.new&lt;/em&gt; file, delete the &lt;em&gt;.new&lt;/em&gt; file directly, etc.

Additionally, removal operations also track pairs of &lt;em&gt;.new&lt;/em&gt; files and give you the opportunity of deleting configuration files that have been left behind. You are not forced to remove the files left behind, of course.

Upgrade operations will perform both tasks. First, they will let you review the &lt;em&gt;.new&lt;/em&gt; files and then they will give you the opportunity of deleting obsolete configuration files left behind.

While using &lt;em&gt;vimdiff&lt;/em&gt;, turning off syntax highlighting is recommended. &lt;em&gt;Vim&lt;/em&gt; uses colors to highlight file differences and those can interfere with syntax highlighting colors, making text invisible or hard to read. Syntax highlighting can be turned off temporarily by using "&lt;tt&gt;:syntax off&lt;/tt&gt;" in command mode, or you can disable it permanently putting "&lt;tt&gt;syntax off&lt;/tt&gt;" in your &lt;tt&gt;~/.vimrc&lt;/tt&gt; file (noting that usually you run SlackRoll as the superuser).

== Managing Customized Versions of Official Packages ==

There are at least three ways of dealing with customized versions of official packages. These are custom versions or compilations of packages present in the remote official tree. They are normally used to add or remove features, or activate or apply patches that are disabled by default. For example, if you want to activate the &lt;em&gt;freetype&lt;/em&gt; bytecode interpreter, you need to rebuild that package.

The simplest way of dealing with these packages is to give them the same name and version as the official packages. When they are upgraded in the remote tree, however, SlackRoll will want to upgrade them. You can mark them as frozen before upgrading and only unfreeze them after you have rebuilt the new version, if you want to avoid SlackRoll replacing them with the new official version.

Second, you can give them the same name and version as the official package, &lt;strong&gt;but&lt;/strong&gt; keep them frozen all the time. How would you know then if they need to be rebuilt? With the &lt;em&gt;list-outdated-frozen&lt;/em&gt; operation. Take into account the information given by &lt;em&gt;list-outdated-frozen&lt;/em&gt; is not reflected by any other command. Specifically, it's not reflected as part of &lt;em&gt;list-transient&lt;/em&gt; and friends.

Third, you can give them a name or version different to the official package. Typically this means adding a custom build suffix and marking the package as frozen. How would you know if you need to rebuild it? Paying attention to the changelog specifically searching for upgrades in those packages and also using the &lt;em&gt;list-versions&lt;/em&gt; operation, that lets you view the different known versions of a package, including local and remote ones.

== Maintenance ==

SlackRoll barely requires maintenance. It keeps all downloaded packages in its package cache, located in the &lt;em&gt;/var/slackroll/packages&lt;/em&gt; directory. When downloading files, it keeps them in a temporary directory until they're fully downloaded. If you want to remove every downloaded package, you can simply perform &lt;code&gt;slackroll erase-cache&lt;/code&gt;. There is, however, a &lt;em&gt;clean-cache&lt;/em&gt; operation which does &lt;strong&gt;not&lt;/strong&gt; remove every downloaded package, but only those that are no longer present in the remote tree. Running that operation from time to time keeps your package cache sane and controlled. It may also be a good idea to delete the temporary directory contents from time to time, with &lt;code&gt;slackroll erase-tmp&lt;/code&gt;, but it should be empty unless you interrupt SlackRoll while downloading stuff and never attempt to complete the download.

== Other Operations ==

If you run the &lt;em&gt;help&lt;/em&gt; operation you will see SlackRoll has many other operations, including operations to list packages by state, list local packages, list remote packages and list all known packages. It has operations to put packages in specific states and checking the state of packages. You can also download, install, display info or remove new or unavailable packages or packages with a matching path (like &lt;em&gt;/slackware/kde/&lt;/em&gt;). Finally, there are search operations, to search for packages by name or path, search for files in your local system (like running &lt;em&gt;grep&lt;/em&gt; on the contents of &lt;em&gt;/var/log/packages&lt;/em&gt;), query the Slackware Package Browser, and finally a few very slow but sometimes useful operations to search for broken symlinks under a specific hierarchy and the same for orphan files (files not belonging to any package), as well as searching for missing files.

As a general rule, every operation either does not accept arguments or allows a list of them. Operations accepting packages as arguments expect the package name only unless the help text mentions that they also accept specific package versions. Some operations need regular expressions. For the most part they have the same syntax as they have in &lt;em&gt;grep&lt;/em&gt; or &lt;em&gt;Perl&lt;/em&gt;, but you can read the [http://docs.python.org/lib/re-syntax.html Python regular expressions syntax reference] if you want to perform an unusually complex search.

[[Category:Tutorials]]</text>
    <sha1>293de572ee50a5b8ce6c81a72544e87c6ea662d6</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Slackware-Upgrade-HowTo</title>
  <ns>0</ns>
  <id>158</id>
  <revision>
    <id>186</id>
    <timestamp>2009-06-06T23:26:40Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3522" xml:space="preserve">[[Category:Tutorials]]
=== Upgrading to Slackware 12.0: List of things to do beforehand ===

====Get the installation discs &amp; other software ====
----

*Slackware Install Discs I, II &amp; III
*Download /patches directory for 12.0 from one of Slackware's mirrors
*Download nvidia Linux driver installer utility for Geforce FX5200 to /mnt/cruzer
*Download XAMPP package to /mnt/cruzer

====Backup the system ====
----

*Backup the entire $HOME folder to /mnt/freeagent, the external hard drive
*Backup website folder /opt/lampp/htdocs to /mnt/freeagent, the external hard drive
*Backup /etc/X11/xorg.conf to /mnt/cruzer
*Backup entire /etc folder to /mnt/cruzer
*Print current xorg.conf for reference

====Start Installation ====
----

*Place Installation Disc I in cd drive and reboot the system
*Follow Instructions on screen to launch the installer

=====Partitioning =====
----

*Launch cfdisk and delete existing partitions
*Create two new partitions, Swap 2GB &amp; Linux Remaining space (approx 240GB)
*Write partition table to the disc and exit
*Launch setup program and follow the instructions for a complete install
*Make sure not to install php, apache and mysql.  We're going to install that separately using XAMPP later on
*Choose one of the generic "huge" or "huge-smp" kernels at the end of installation process.

====Fresh System ====
----

*Hopefully, I will have a working fresh system after the installation is complete.
*The default runlevel is 3
*Launch xorgconfig, and set up xorg.conf
*Try launching X server to see if it works.  If it works, we're good for next steps.  
*Exit the window manager (KDE by default). This will drop you off at the terminal.

====Compile Kernel ====
----

*Backup /lib/modules/your-kernel to /lib/modules/your-kernel.backup.  This step will make sure that your current kernel is available as backup if the kernel we're going to compile does not work.
*Copy /boot/config to /usr/src/linux/.config
*Become root
*cd /usr/src/linux
*make menuconfig
*Remove Riva Framebuffer Support from the configuration menu, save and exit the configuration menu
*make bzImage.  This will create a new kernel "bzImage" in /usr/src/linux/arch/i386/boot/
*make modules &amp;&amp; make modules_install.  This will compile and install kernel modules in /lib/modules/your-kernel directory.
*cp /usr/src/linux/arch/i386/boot/bzImage /boot #This copies our newly compiled kernel in /boot directory.
*Edit /etc/lilo.conf as follows.  Add this at the end of lilo.conf

 #Bootable partition configuration starts
 image = /boot/bzImage
 root = /dev/your-device-where-root-is-located
 label = Tux (use any label you want for the new kernel)
 #Bootable partition configuration ends

*Run /sbin/lilo to add the new kernel info to the boot loader.

==== Test the new Kernel ====
----

*If everything went fine, reboot the computer.  
*Select new kernel to boot from
*If the kernel boots properly and you get a working system back, we're good for next steps.

==== Install the nVidia Graphics Driver ====
----

*Get the driver from nvidia's website
*Make it executable and launch using sh utility
*This will compile the kernel module for driver and install it.
*If the driver was installed successfully, change xorg.conf to reflect that.  Just change driver name from ''nv'' to ''nvidia''.
*Launch X server with startx and test the system out.
*glxinfo | grep dri   Third line of the output should tell you if you have direct rendering enabled now.
*telinit 4.  Change the runlevel to 4 and enjoy your new graphic powers.</text>
    <sha1>2b5e032aa2bcec12295888039e1098a30d35baca</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>VMware Guest Install</title>
  <ns>0</ns>
  <id>159</id>
  <revision>
    <id>187</id>
    <timestamp>2009-06-06T23:27:17Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11552" xml:space="preserve">[[Category:Tutorials]]
'''HOWTO: Install Slackware 11.0 as a guest on VMWare Workstation for Windows 5.5 with:'''
* a 2.6 kernel;
* the ext3 filesystem;
* the LSI Logic SCSI adapter;
* and tips using XDMCP on the guest.

== Prerequisites ==
* Some previous experience installing any version of Slackware (no experience with 2.6 kernels necessary).
* Some previous experience using VMware Workstation for Windows.
* Experience using console-based editors such as Vi, pico, or Emacs.
* Some degree of comfort using a bash prompt.

== Tips and recommendations ==
* Use the VMWare "snapshot" feature throughout the installation. That way, if you make a mistake, you won't have to start over from the beginning. I take a snapshot during each reboot. You can delete the snapshots after you're sure the installation is successful.
* Make sure to install the Slackware 11.0 patches after successfully completing the installation.
* This is not the only way to install Slackware 11.0 on a VMware guest. For example:
** You don't have to run a 2.6 kernel if you don't want, the 2.4 kernel will work just fine. If you decide to use the 2.4 kernel, just skip the [[#Upgrade_the_kernel_from_2.4_to_2.6|kernel upgrade step]].
** You can use the BusLogic SCSI adapter instead of the LSI Logic adapter, you'll just need to load the appropriate drivers for this adapter instead of the ones listed in the [[#Upgrade_the_kernel_from_2.4_to_2.6|mkinitrd step]].
** You can use something other than ext3 for the filesystem (for example, ext2 or ReiserFS). If you do this, you'll need to load different drivers during the [[#Upgrade_the_kernel_from_2.4_to_2.6|mkinitrd step]].
** Technically, you don't need to install the VMWare guest tools as covered [[#Build.2C_install.2C_and_configure_the_VMware_guest_system_tools|here]], but they are highly recommended as they greatly increase performance and usability (particularly when using X, or when running the guest from a laptop host).

== Use the VMware new guest wizard to create the new guest ==
Use the following settings: 
&lt;ul&gt;
&lt;li&gt;Custom&lt;/li&gt;
&lt;li&gt;New – Workstation 5&lt;/li&gt;
&lt;li&gt;Linux, Other Linux 2.6.x Kernel&lt;/li&gt;
&lt;li&gt;Name your machine&lt;/li&gt;
&lt;li&gt;1 Proc&lt;/li&gt;
&lt;li&gt;set memory not less than 256 MB&lt;/li&gt;
&lt;li&gt;Use either bridged or NAT; I used NAT because bridged gave me problems with the wireless networking adapter on my laptop&lt;/li&gt;
&lt;li&gt;LSI Logic adapter (you can use BusLogic, but you'll have to use different drivers than the ones listed here in the initrd configuration)&lt;/li&gt;
&lt;li&gt;new virt disk&lt;/li&gt;
&lt;li&gt;SCSI&lt;/li&gt;
&lt;li&gt;Not less than 4GB&lt;/li&gt;
&lt;li&gt;Name disk file&lt;/li&gt;
&lt;/ul&gt;

== Install Slackware 11.0 on the guest ==
&lt;ol&gt;
&lt;li&gt;Either insert the Slackware install CD in your CD-ROM drive, or add the Slackware install ISO as a new CD-ROM device in the guest configuration.&lt;/li&gt;
&lt;li&gt;Boot&lt;/li&gt; 
&lt;li&gt;At the boot: prompt from Slackware install CD, type “raid.s”. This will start the installation with the 2.4 kernel &amp; SCSI support for the VMware LSI SCSI adapter.&lt;/li&gt;
&lt;ul&gt;&lt;li&gt;Note: I haven't figured out a way to install Slackware using the 2.6 kernel and/or installing the 2.6 kernel during the installation. The easiest way I can figure out how to do it is to install with the 2.4 kernel and then upgrade to 2.6 after installation is complete.&lt;/li&gt;&lt;/ul&gt;
&lt;li&gt;create your partitions using: &lt;tt&gt;cfdisk /dev/sda&lt;/tt&gt;.&lt;/li&gt;
&lt;ul&gt;&lt;li&gt;You will need to create at least a swap partition and a root partition. My partition table usually looks something like this:&lt;/li&gt;&lt;/ul&gt;
&lt;/ol&gt;
                        cfdisk 2.12r
 
                    Disk Drive: /dev/sda
               Size: 8589934592 bytes, 8589 MB
         Heads: 255   Sectors per Track: 63   Cylinders: 1044 
 
 Name      Flags     Part Type  FS Type        [Label]       Size (MB)
 ---------------------------------------------------------------------
 sda1                Primary    Linux swap                      296.12
 sda2      Boot      Primary    Linux                          8291.09
&lt;ol start="5"&gt;
&lt;li&gt;Start networking (network) if doing a network install from NFS. This will load the pcnet32 network driver.&lt;/li&gt;
&lt;li&gt;Start setup; set up your swap &amp; root partitions, use ext3 for the partition type. Take note of the root partition device name. Set up your install source and package selections, and start the install.&lt;/li&gt;
&lt;li&gt;Things I know for sure you DON'T need to install for a guest to run correctly:&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;Package e (emacs)&lt;/li&gt;
&lt;li&gt;Package f (faqs/howtos)&lt;/li&gt;
&lt;li&gt;Package k (kernel source; this will be replaced anyway when we upgrade to 2.6)&lt;/li&gt;
&lt;li&gt;Package kde and kdei (KDE)&lt;/li&gt;
&lt;li&gt;Package t (TeX)&lt;/li&gt;
&lt;li&gt;Package xap (but if you're using X at all, you'll probably want some of the things in there like a good window manager &amp; desktop environment)&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;Things I know for sure you DO need to install for a guest to run correctly:&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;Package x (X11) (the VMware-tools installation, while console-based, depends on X to complete the installation successfully. I imagine you can uninstall package X after the VMware-tools installation is complete).&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;If you are installing from the ISO mapped to a virtual guest CDROM device, you'll need to switch to the second CD after the first CD is done (you'll receive a message to switch the CDs). To do this, right-click on the CD-ROM device icon in the lower-right corner of the VMWare status bar. Select edit, and change the ISO image location to the second ISO image.&lt;/li&gt;
&lt;li&gt;When configuring the options (after the package install) make sure to:&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;install the “raid.s” kernel to the hard drive.&lt;/li&gt;
&lt;li&gt;Enable hotplug/udev system at boot.&lt;/li&gt;
&lt;li&gt;Simple LILO install: Install LILO automatically&lt;/li&gt;
&lt;li&gt;install LILO to the MBR&lt;/li&gt;
&lt;li&gt;I use the standard Linux console, however some of the framebuffer modes do work.&lt;/li&gt;
&lt;li&gt;ps2 port mouse&lt;/li&gt;
&lt;li&gt;on startup services, make sure rc.pcmcia is unchecked (if this runs it causes a huge amount of kernel error messages and subsequent performance problems)&lt;/li&gt;
&lt;li&gt;hardware clock is set to local time&lt;/li&gt;
&lt;/ul&gt;
&lt;li&gt;Reboot, not from the CD. If everything goes well you should get a regular console login prompt right after the message &lt;tt&gt;Welcome to Linux 2.4.33.3&lt;/tt&gt;.&lt;/li&gt;
&lt;li&gt;If for some reason you didn't get the raid.s kernel installed and instead installed the default 2.4 kernel, you won't be able to boot because the SCSI driver will not load (you will instead get a message about not being able to mount the root device, followed by a kernel panic). Do this:&lt;/li&gt;
&lt;ul&gt;
&lt;li&gt;Boot from the installation CD and enter this at the &lt;tt&gt;boot:&lt;/tt&gt; prompt:&lt;/li&gt;
&lt;li&gt;&lt;tt&gt;raid.s root=/dev/''[your_root_partition]'' noinitrd ro&lt;/tt&gt; (where &lt;tt&gt;''[your_root_partition]''&lt;/tt&gt; is the device name of the root partition (eg: /dev/sda1 or /dev/sda2 etc)).&lt;/li&gt;
&lt;li&gt;Boot and continue at the next [[#Upgrade_the_kernel_from_2.4_to_2.6|section]].&lt;/li&gt;
&lt;/ul&gt;
&lt;/ol&gt;

== Upgrade the kernel from 2.4 to 2.6 ==
# log in as root  
# Install the 2.6 kernel located in the patches or testing installation directory:
#* mount the installation CD or NFS mountpoint containing the Slackware 11.0 testing and/or patches directories (as of this writing, Slackware contains a 2.6 kernel in both testing and patches; the one in testing is a little newer). 
#* Change to the patches/testing directory containing the linux 2.6 kernel installation .tgz files. Take note of the version number of the 2.6 kernel (ie: 2.6.18).
#* &lt;tt&gt;upgradepkg –-install-new kernel-generic*.tgz&lt;/tt&gt;
#* &lt;tt&gt;upgradepkg –-install-new kernel-modules*.tgz&lt;/tt&gt;
#* &lt;tt&gt;upgradepkg –-install-new kernel-source*.tgz&lt;/tt&gt; (only if you want the source)
# &lt;tt&gt;cd /etc/rc.d&lt;/tt&gt;
# &lt;tt&gt;rm rc.modules; ln -s rc.modules-''[X]'' rc.modules&lt;/tt&gt;
#* where &lt;tt&gt;''[X]''&lt;/tt&gt; is the version number of your installed 2.6 kernel.
# Create the initrd filesystem with the ext3 and LSI Logic SCSI drivers: 
#* &lt;tt&gt;mkinitrd -c -k ''[X]'' -m jbd:ext3:scsi_transport_spi:mptbase:mptscsih:mptspi -f ext3 -r /dev/''[Y]'' &lt;/tt&gt;
#** where ''[X]'' is the version of your 2.6 kernel and ''[Y]'' is the name of your root partition device.
#** the order of these modules (the ones separated by colons) is important. 
#** if you're not using ext3, you won't need to load the ext3 or jdb modules (but you'll need to load the modules for your filesystem unless you're using ext2). You need the rest of the modules loaded for SCSI driver support, which you need to mount the VMware LSI scsi hard drive.
#* &lt;tt&gt;cat /boot/initrd-tree/load_kernel_modules&lt;/tt&gt; and inspect to insure that all the modules listed in the mkinitrd command are correctly listed in this file.
# Edit the file /etc/lilo.conf, add the following after the &lt;tt&gt;image =&lt;/tt&gt; line:
#* &lt;tt&gt;initrd = /boot/initrd.gz&lt;/tt&gt;
# &lt;tt&gt;lilo&lt;/tt&gt; 
#* (you should receive the response &lt;tt&gt;Added Linux *&lt;/tt&gt;)
# Reboot. If everything goes well, after bootstrap, you should receive the message &lt;tt&gt;Welcome to Linux ''[X]''&lt;/tt&gt;, where ''[X]'' is the version of your 2.6 kernel, and a login prompt.

== Build, install, and configure the VMware guest system tools ==
# Log in as root. 
# From the VMware Workstation menu bar, choose VM-&gt;Install VMware tools
# From the linux bash prompt: &lt;tt&gt;mount /dev/cdrom /mnt/cdrom&lt;/tt&gt;
# &lt;tt&gt;mkdir /tmp/toolsinstall; cd /tmp/toolsinstall&lt;/tt&gt;
# &lt;tt&gt;tar zxf /mnt/cdrom/VMwareTools*.tar.gz&lt;/tt&gt;
# Create the dummy System V init filesystem for the VMware-tools install program:
#* &lt;tt&gt;mkdir init.d&lt;/tt&gt;
#* &lt;tt&gt;for i in {0,1,2,3,4,5,6}; do mkdir rc$i.d; done&lt;/tt&gt;
#* &lt;tt&gt;touch init.d/network init.d/networking&lt;/tt&gt;
# Bring down the networking so the install program can create the VMware high-performance network driver:
#* &lt;tt&gt;ifconfig eth0 down&lt;/tt&gt;
#* &lt;tt&gt;rmmod pcnet32&lt;/tt&gt;
# &lt;tt&gt;cd vmware-tools-distrib&lt;/tt&gt;
# &lt;tt&gt;./vmware-install.pl&lt;/tt&gt;
#* For the options use the defaults; the only thing I change is the default bin directory from /usr/bin to /usr/local/bin
#* after answering all the configuration questions, vmware-install.pl will build and install all the VMware guest tools and update the dummy System V init filesystem.
# Move the changes in the dummy System V init filesystem into the Slackware BSD init scripts:
#* &lt;tt&gt;cp /tmp/toolsinstall/init.d/vmware-tools /etc/rc.d/rc.vmware-tools&lt;/tt&gt;
#* &lt;tt&gt;sed -i "s/pcnet32/vmxnet/" /etc/rc.d/rc.netdevice&lt;/tt&gt;
#* &lt;tt&gt;echo "/etc/rc.d/rc.vmware-tools start" &gt;&gt;/etc/rc.d/rc.local&lt;/tt&gt;
# Reboot
# Directly before the &lt;tt&gt;Welcome to Linux 2.6.x&lt;/tt&gt; message, you should see messages from the VMware-tools init script:
 Starting VMware Tools services in the virtual machine:
     Switching to guest configuration:                 done
     Guest filesystem driver:                          done
     DMA setup:                                        done
     Guest operating system daemon:                    done
 
 Welcome to Linux 2.6.18 (tty1)
 
 virtslack2 login:

== (Optional) Setting up XDMCP ==
If you want to use XDMP on the guest system, the following caveats apply:
# I recommend the xming X server over Cygwin/X. Cygwin/X doesn't seem to play well with VMware guests for some reason. I had problems with it gradually slowing down until the Cygwin X server would grind to a halt.
# If you're using NAT instead of bridging, make sure you set your &lt;tt&gt;-from&lt;/tt&gt; parameter with the IP address of the VMware network adapter on the host system (on my system, this is 192.168.223.1; you can do an &lt;tt&gt;ipconfig&lt;/tt&gt; on the host system to determine this IP address). If you don't do this step, you'll find performance to be abysmal.</text>
    <sha1>3ef57ae70e56d72452a267579781ef57b51e0e5e</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Slamd64 FAQ</title>
  <ns>0</ns>
  <id>160</id>
  <revision>
    <id>188</id>
    <timestamp>2009-06-06T23:27:57Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4233" xml:space="preserve">[[Category:Slamd64]][[Category:Information]]

__TOC__

==What is Slamd64?==

Slamd64 is an '''unofficial''' port of Slackware to x86_64.

==Is Slamd64 just for AMD64 systems?==

No, Slamd64 is compiled for generic x86_64; this means it should work on both AMD64 and EM64T.

==Do I need all  7 CDs?==

Usually the disc 1 is all you need to download. If you want the packages included on the 2nd, 3rd or 4th discs such as KDE, you can download them after you have installed Slamd64. The 5th, 6th, and 7th discs contain sources and are not needed by most users.

If you have only the first disc, you still don't need to worry when selecting the packages to be installed. If you happen to select packs that are not on the first disc and the installer prompts you for the disc 2, simply press skip. There are no packs on the second or third discs that would be critical for a working system. You can install them later.

You can find out what's on them by looking at the scripts used to create them, which are in extra/scripts/

==Is there SATA support?==

Yes! I've no idea where the misconception that there isn't came from; my development system uses SATA drives. 

==Can I use normal Slackware packages?==

Mostly yes, as long as they don't use Qt/KDE. Libraries can be complicated.

==How do I use these ".jigdo" files?==

Firstly, you need to install [http://atterer.net/jigdo/ jigdo]; a slamd64 package can be found on [http://files.fredemmott.co.uk/jigdo-0.7.2-x86_64-1.tgz files.fredemmott.co.uk]. You will then need to download the tarball of .jigdo, .template, and other files from the "[http://www.slamd64.com/getslamd64.html Get Slamd64]" page. Extract the tarball somewhere, and open a terminal, and 'cd' into the created directory.

If you want to use a mirror other than ftp.heanet.ie, change the following lines in the .jigdo files:
 
 Mirror=ftp://ftp.heanet.ie/pub/slamd64/slamd64-current/
 Mirror=ftp://ftp.heanet.ie/pub/slamd64/slamd64-10.2/tree/

If you keep a copy of the tree locally, you can use a "file:/" url, like the following (assuming you have your tree in /home/ftp/pub/slamd64/):
 Mirror=file://home/ftp/pub/slamd64/slamd64-current/
 Mirror=file://home/ftp/pub/slamd64/slamd64-10.2/tree/

Then simply run "jigdo-lite filename.jigdo" for each disk you want - for example, if you want disks 1 and 2, non-us:
 jigdo-lite slamd64-10.2-disk1.jigdo
 jigdo-lite slamd64-10.2-nonus-disk2.jigdo

==Is there a DVD version?==

Yes.

==Is there flash support?==

Not out-of-the-box, but there's a work-around to get Konqueror to use 32-bit plugins instead of 64-bit; see the [http://forums.gentoo.org/viewtopic.php?t=216959 post on the gentoo forums].

You can also use a 32-bit web-browser, such as Opera, or a version of Firefox from mozilla.org. (The package included in Slamd64 is a 64-bit package)

==Is GNOME included?==

Not out-of-the-box, but [http://gnomeslackbuild.org/ GSB: Gnome SlackBuild] has a [http://gnomeslackbuild.org/download/#quick port] available.

There is also a port of [http://droplinegnome.org Dropline GNOME 2.14.1] desktop available, for download [http://dlg64.droplinegnome.org/dlg-2.14.1-x86_64.iso.torrent a bittorrent link is provided].

Also

==I use the NVidia drivers, I updated/reinstalled 32x11, and now I don't have 3D-acceleration in 32-bit applications. How do I fix this?==

Reinstall the nvidia drivers. 32x11 contains generic 32-bit OpenGL libraries, which overwrite the NVidia drivers.
==I have an ATi card, how do I get the fglrx drivers to build?==

fglrx requires 64bit GCC 3.3 C++ libraries to build (cxxlibs-6.0.3-x86_64-1) and the 32 bit c/ compatibility packages.

Install those libraries, and then get fglrx64 (not fglrx) from ATi's website. You may also need the 32bit compatibility packages in Slamd64, and the driver may require further patching if you want to use it on the latest kernel.

==How can I help?==

Firstly, look at [http://bugs.slamd64.com the bug list], and see if you can provide a fix; also, just using Slamd64 and reporting any bugs you find (after checking that they're not already reported) on that page is useful.

Financial assistance is also always appreciated; please use the PayPal link on [http://www.slamd64.com the Slamd64 website].</text>
    <sha1>38742f7d8e95a8546b99c1f84dd2e8e1dc6ec9aa</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Slapt-get</title>
  <ns>0</ns>
  <id>161</id>
  <revision>
    <id>189</id>
    <timestamp>2009-06-06T23:28:37Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8646" xml:space="preserve">'''slapt-get''' is an [[APT]]-like system for [http://en.wikipedia.org/wiki/Slackware Slackware] [[package management]].

It tries to emulate the features of [[Debian]]'s [[apt-get]] as closely as possible.

==Features==

* uses native [http://en.wikipedia.org/wiki/Slackware Slackware] tools (installpkg, upgradepkg, and removepkg)
* supports multiple package sources (including http://linuxpackages.net)
* cache data concerning packages and updates from package sources
* supports sources from ftp, ftps, http, https, file:/// and more (libcurl)
* resumes broken downloads and will verify package integrity with [http://en.wikipedia.org/wiki/Md5 MD5] checksum
* show packages that are available (from cached data) and installed
* search package listing using [http://en.wikipedia.org/wiki/POSIX POSIX] and extended [http://en.wikipedia.org/wiki/Regular_expressions regular expressions] by package name, location, and description
* retrieve, install, and remove packages by name or by specific version
* retrieve and apply updates
* upgrade from one Slackware release to another in a few simple steps - see [[Upgrade_Using_Slapt-get]]
* show description of packages, including mirror location, version, size, dependencies (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ10 FAQ]), conflicts (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ31 FAQ]), suggestions (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ44 FAQ]), description, and installation status
* exclude (hold) packages from upgrades, by name or by regular expression
* transaction engine for install, remove, and upgrades, reporting concise information on what is to be done, ensuring each step happens correctly
* "compare package version" algorithm to prevent downgrades
* recursive dependency resolution using slack-required meta-data ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ10 see FAQ]) supporting hard, soft, and conditional dependencies
* package conflict resolution using slack-conflicts meta-data ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ31 see FAQ])
* package suggestion support for complimentary packages ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ44 see FAQ])
* Package data download robustness, only writing changes if all sources download successfully as well as only downloading those sources that have changed since the last download
* [http://en.wikipedia.org/wiki/I18n i18n] support via [http://en.wikipedia.org/wiki/GNU GNU] gettext with over 20 language translations
* extremely fast and easy to script with

==Dependencies==

slapt-get does not provide dependency resolution for packages included within the Slackware distribution. It does, however, provide a framework for dependency resolution in Slackware compatible packages similar in fashion to the hand-tuned method [http://en.wikipedia.org/wiki/Advanced_Packaging_Tool Advanced Packaging Tool|APT] utilizes. Several package sources and Slackware based distributions take advantage of this functionality.

Adding dependency information requires no modification to the packages themselves.  Rather, the package listing file, PACKAGES.TXT, is used to specify these relationships.  This file is provided by  [http://en.wikipedia.org/wiki/Patrick_Volkerding Patrick Volkerding] and is similar to the Packages.gz file in use by [http://en.wikipedia.org/wiki/Debian Debian].  Several scripts are available to generate the PACKAGES.TXT file from a group of packages (See [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ17 FAQ #17]).  The file format used by  [http://en.wikipedia.org/wiki/Patrick_Volkerding Patrick Volkerding] is extended by adding a few extra lines per package.  slapt-get then parses this file during source downloads.  Typically, third party packages store the dependency information within the package itself for later extraction into the PACKAGES.TXT ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ19 See FAQ #19]).  The inclusion of this information within the Slackware package format does not inhibit the ability for Slackware pkgtools to install these packages.  This information is silently ignored and discarded after the package is installed.

[http://www.stabellini.net/depslack.html Other methods] exist for adding dependency information for official Slackware packages without altering the packages themselves.

==Package Sources==

slapt-get works with official Slackware mirrors and third party package repositories.  slapt-get looks for support files, PACKAGES.TXT and CHECKSUMS.md5, in the repository for package information.  These files provide package names, versions, sizes (both compressed and uncompressed), checksums, as well as a package description.  These files can be extended, as discussed in the previous section, to add dependency listings, conflict information, and package suggestions.  These files can also proxy for other remote sources by specifying a MIRROR declaration for each package.  

==libslapt==

slapt-get exports a [http://en.wikipedia.org/wiki/C_programming_language C] [http://en.wikipedia.org/wiki/Library_(computer_science) library] that is used by [http://en.wikipedia.org/wiki/gslapt gslapt] to provide similar functionality through a [http://en.wikipedia.org/wiki/GTK+ GTK+] frontend. 

==Distributions==

Besides Slackware, slapt-get may be used with or included by the following distributions:

 * [http://www.vectorlinux.com Vector Linux]
 * [http://www.mutagenix.org Mutagenix]
 * [http://slax.linux-live.org SLAX]
 * [http://www.slamd64.com/ Slamd64]
 * [http://gsb.sourceforge.net/ Freerock GNOME]
 * [http://www.gware.org/ GWARE GNOME]
 * [http://slampp.abangadek.com/ SLAMPP]
 * [http://getopenlab.com/ OpenLab GNU/Linux]
 * [http://ocsid.spaghettilinux.org/ Open Community Slackware Install DVD]
 * [http://floyd-linux.pappapc.com/ Floyd GNU/Linux]
 * [http://www.stibs.cc/stx/ STX GNU/Linux]
 * [http://www.nnlinux.com/ Nonux GNU/Linux]
 * [http://wolvix.org/ Wolvix LiveCD]
 * [http://www.collegelinux.org College Linux]
 * [http://www.zenwalk.org/ Zenwalk Linux]
 * [http://www.truvalinux.org.tr Truva Linux]

==Examples==

  $ slapt-get --update
  Retrieving package data http://www.slackware.at/data/slackware-10.0/ ...Done
  Retrieving patch list http://www.slackware.at/data/slackware-10.0/ ...Done
  Retrieving checksum list http://www.slackware.at/data/slackware-10.0/ ...Done
  Reading Package Lists...Done
  Retrieving package data http://software.jaos.org/slackpacks/10.0/ ...Cached
  Retrieving patch list http://software.jaos.org/slackpacks/10.0/ ...Cached
  Retrieving checksum list http://software.jaos.org/slackpacks/10.0/ ...Cached
  Reading Package Lists...Done

  $ slapt-get --upgrade
  Reading Package Lists... Done
  The following packages have been EXCLUDED:
    devs kernel-headers
  The following packages will be upgraded:
    binutils bash bin bind cdrtools bzip2 kbd cups cxxlibs e2fsprogs etc gawk gcc gdb inetd infozip less links
    logrotate lynx man man-pages openssh openssl openssl-solibs pidentd pkgtools procps sed shadow slocate
    sysklogd sysvinit tar tcpip util-linux vim wget zlib
  39 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  Need to get 36710K of archives.
  After unpacking 17880K of additional disk space will be used.
  Do you want to continue? [y/N]

  $ slapt-get --show slapt-get
  Package Name: slapt-get
  Package Mirror: http://software.jaos.org/slackpacks/10.0/
  Package Location: .
  Package Version: 0.9.9f-i386-1
  Package Size: 147 K
  Package Installed Size: 530 K
  Package Required:   curl &gt;= 7.12.0-i486-1,glibc-solibs &gt;= 2.3.2-i486-7,binutils,openssl &gt;= 0.9.7d-i486-1,pkgtools,zlib
  Package Conflicts:
  Package Suggests:
  Package MD5 Sum:  cb4b44cbb4efee4e993109231b107828
  Package Description:
  slapt-get: slapt-get (APT like system for Slackware)
  slapt-get: slapt-get is an APT like system for Slackware package management.
  slapt-get:
  slapt-get:  * See /usr/doc/slapt-get-0.9.9f/ for complete documentation.
  slapt-get:  * You will also want to customize /etc/slapt-get/slapt-getrc,
  slapt-get:    using a local mirror.  www.slackware.com may be very busy.
  slapt-get:  * Support:
  slapt-get:    http://software.jaos.org/cgi-bin/mailman/listinfo/slapt-get-user
  slapt-get:  * Please translate
  slapt-get:    http://software.jaos.org/BUILD/slapt-get/po/slapt-get.pot
  slapt-get:    then send to slapt-get-devel@software.jaos.org
  slapt-get:
  Package Installed: yes

==External links==
*[http://software.jaos.org/#slapt-get Homepage]

[[Category:Information]]</text>
    <sha1>8d67ca2cb94dcee4f5c9af9af4745e84019c282a</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Soft Reboot</title>
  <ns>0</ns>
  <id>162</id>
  <revision>
    <id>190</id>
    <timestamp>2009-06-06T23:29:00Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="610" xml:space="preserve">[[Category:Tips]]

Avoid the full POST by your BIOS for a slightly faster reboot time, in &lt;code&gt;lilo.conf&lt;/code&gt;:

 append = "reboot=bios,warm"

Brief explanation of options:

 bios   Use the CPU reboot vector for warm reset
 warm   Don't set the cold reboot flag

Using warm reset will be much faster especially on big memory systems because the BIOS will not go through the memory check.
Disadvantage is that not all hardware will be completely reinitialized on reboot so there may be boot problems on some systems.

See &lt;code&gt;/usr/src/linux/Documentation/x86/x86_64/boot-options.txt&lt;/code&gt; for more details.</text>
    <sha1>6df4d7a62c5a599353bdf4af1d101d23e5b37235</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Software Licenses</title>
  <ns>0</ns>
  <id>163</id>
  <revision>
    <id>191</id>
    <timestamp>2009-06-06T23:29:33Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1247" xml:space="preserve">== A ==
{|
!Software
!License
|-
|AbiWord
|GNU GPL
|-
|Apache
|Apache license
|-
|aspell
|GNU LGPL
|}

== B ==
{|
!Software
!License
|-
|bash
|GNU GPL
|-
|BitchX
|BSD license
|}

== C ==
{|
!Software
!License
|-
|CUPS
|GNU GPL &amp; GNU LGPL
|}

== D ==

== E ==

== F ==

== G ==
{|
!Software
!License
|-
|Gaim
|GNU GPL
|-
|gcc
|GNU GPL
|-
|gdb
|GNU GPL
|-
|getmail
|GNU GPL
|-
|GIMP
|GNU GPL
|-
|gFTP
|GNU GPL
|-
|glibc
|GNU LGPL
|-
|GKrellM
|GNU GPL
|-
|gnupg
|GNU GPL
|-
|gnuchess
|GNU GPL
|}

== H ==

== I ==
{|
!Software
!License
|-
|libIDL
|GNU LGPL
|}

== J ==
{|
!Software
!License
|-
|joe
|GNU GPL
|}

== K ==
{|
!Software
!License
|-
|KDE
|GNU GPL, GNU LGPL
|}

== L ==

== M ==
{|
!Software
!License
|-
|mutt
|GNU GPL
|-
|MySQL
|GNU GPL
|}

== N ==
{|
!Software
!License
|-
|nmap
|GNU GPL
|}

== O ==

== P ==
{|
!Software
!License
|-
|Perl
|GPL or Artistic License
|-
|PHP
|PHP License
|}

== Q ==
{|
!Software
!License
|-
|Qt
|GPL, Proprietary, QPL
|}

== R ==
{|
!Software
!License
|-
|rxvt
|GNU GPL
|}

== S ==
{|
!Software
!License
|-
|SDL
|GNU LGPL
|}

== T ==
{|
!Software
!License
|-
|t1lib
|GNU GPL
|}

== U ==

== V ==

== X ==
{|
!Software
!License
|-
|xine-lib
|GNU GPL
|-
|xv
|Shareware
|}

== Z ==


[[Category:Information]]</text>
    <sha1>ce32a5c1c75ddd5afaf11ad0e206eb20c90d813e</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Sony VAIO PCG-C1XD</title>
  <ns>0</ns>
  <id>164</id>
  <revision>
    <id>192</id>
    <timestamp>2009-06-06T23:30:00Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3145" xml:space="preserve">[[Category:Hardware]]
==Slackware on a Sony VAIO PCG-C1XD==

The PCG-C1XD is a very small Pentium II based laptop (I mean, really small). I have had access to one and the opportunity to install Linux on one (it's small enough that with a wireless card I believe I can make a very nice portable wireless access point).

I believe it varies only from other PCG-C1X's in the keyboard layout (the D is a German QWERTZ keyboard - as a non-German QWERTY user I find this very difficult to use!). You can therefore modify these instructions accordingly for your keyboard layout.

(Please note that this is a work in progress and will be updated as I work through setting up the laptop and have more details to hand.)

So far: The laptop boots, I've built a working 2.6 kernel for it, standby appears to work, and I've configured X (and managed to get KDE 3.4 running at a very reasonable speed).

==Hardware==
Output of lspci:&lt;pre&gt;
Coming Soon
&lt;/pre&gt;

===Overview===

* Intel Mobile Pentium II 400MHz processor
* 128mb RAM
* 1024x480 LCD
* NeoMagic Graphics Chip (1.5MB dedicated memory)
* 8GB Hard Drive
* External PCMCIA CD-ROM Drive
* External USB Floppy Drive (untested)
* Yamaha sound chip
* 1 x IR port
* 1 x IEEE-1394 (Firewire) port
* 1 x USB port
* 1 x Sony proprietary port
* 1 x PCMCIA slot
* 1 x Camera (Built into top of laptop)

===Working===

* Video Card: NeoMagic 
* Soundcard
* Nib Mouse (Doesn't need a driver - does make strange sounds though)
* CD-ROM (requires boot parameter)
* Battery Status (See 'Battery' section below).

===Not Tested, but probably works===

* Battery Status (I believe the battery with this laptop is dead)
* Infra Red
* VGA out
* Function/Hot Keys (have not tried all though; extra configuration is probably required)

===Does Not Work===
* Camera (There is a driver in the kernel for this, but I haven't tried it out)

==Kernel Configuration==

You don't need a particularly modern kernel to use this laptop, the default 2.4 series will work fine. For the challenge though, I have successfully built a 2.6 kernel.

As with all Sony VAIO laptops, you will need to select any options that refer to Sony (e.g. the sonypi module). Also, this is an APM  based laptop, so no ACPI here.

==Hardware Package and Software Dependencies==
===CD-Drive===

To use the CD drive that comes with this laptop, you will need to add the following line when installing Slackware, and add it to the append line in LILO.

 hd1=0x180,0x386
===xorg.conf===

Coming Soon - This laptop requires a custom mode line and a few other tweaks due to the very strange resolution of this screen.

===Special Keys===

There is a jogdial on this laptop, but it is untested as of the present.

===Special Keys with X and kde===

To be done.

===Battery info via APM===

To get the battery to display information, you will need to load APM. If you have APM as modules, you will need to load apm and start the APM daemon by hand, or create a startup script to do this for you.

==Troubleshooting==

===Scrolling is too slow in a window manager===
Drop the colours down to 16 bit in /etc/X11/xorg.conf

==External Links/ References==
Coming Soon</text>
    <sha1>7af8d2df16f7efb9edd304e91224ff26b5da92dd</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Ssh-tunneling</title>
  <ns>0</ns>
  <id>165</id>
  <revision>
    <id>193</id>
    <timestamp>2009-06-06T23:30:34Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2960" xml:space="preserve">Sometimes you want to run vnc on a remote machine and do not have the
port forwarded, but you have ssh forwarded. This is a time where ssh
tunneling would work great. It's fast, efficient and its
encrypted. This first example is when you connecting to the server or
client that is running a vnc server:


 ssh -L 5901:localhost:5901 user@server


Now the first -L means that we are going to tunnel from the
localhost to the actual remote host. The first field is ''5901'', the localport to use,
so that when we type '''localhost:5901''' we actually go through the tunnel (on the vnc client).
The next field is ''localhost'' which is resolved on the remote host side. So, localhost in this
example would be the remote host (who said it's confusing ?). The last field ''5901'' is the
port number on the remote host that we want to connect to.
The user@server is the username and host we want to forward to.

Now if we wanted to forward port 631 on the remote host, but it is only binded on the hostname ''server'' the following example would be used:


 ssh -L 9000:server:631 user@server


Port 631 is usually used for CUPS so we can tunnel this as well. So in
order to get that page we would type http://localhost:9000. This would
go through the tunnel and get the cups server remotely. Keep in mind
if you type a password it will be encrypted. 


 ssh -R 9000:localhost:3128 user@server2


Now in this example we are going to forward a remote port to the local
box. For instance the above example we are going to open up port 9000
on server2 and it is going to tunnel to port 3128. This is the same
syntax as the -L option just the other way around for tunneling. The
best explanation between -L and -R is that -R is remotely opening up
the port 9000 while -L is locally opening that port up. 


Now say you are already in an ssh session and want to add ports later
on? Well this is possible through what we call the SSH escape
key. Make sure you are on a new line and type ~C in and you should
see:


 ssh&gt; 


Now you can run the commands -L and -R. These are the same syntax
above just do not put the ssh in front of it.So for instance you could
type:


 -L 8000:localhost:631 server


And if it happened successfully it would say:

Forwarding port 

Now hit enter after it says Forwarding port because sometimes it just
hangs there, but it forwards it fine. There are also more things you
can do with the ~ key. All you have to do is type ~?. (Note do not
type the . after the ?) 

Adding tunneling to ssh is great, but you can also make a socks proxy
out of ssh as well:


 ssh -D 7800 user@server


Then you can use your localhost:7800 as your socks proxy. Now say you
want other computers to be able to connect to your forward ports or
the socks proxy? Thats possible with the -g argument:


 ssh -gD 8700 user@server
 ssh -gL 8000:localhost:3128 user@server


Both of these examples would allow a remote user to connect to
them.

[[Category:Tutorials]]</text>
    <sha1>7399751f61b344923bf7dd6bdc8a4a8190f0f1b2</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Subversion</title>
  <ns>0</ns>
  <id>166</id>
  <revision>
    <id>194</id>
    <timestamp>2009-06-06T23:31:06Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3617" xml:space="preserve">[[Category:Tutorials]]

== Slackware - SVN Howto ==

--[[User:Dadexter|dadexter]] 02:49, 14 Dec 2005 (GMT)

This how to will explain how to setup Subversion, a replacement for CVS.
These instructions were written for use with an apache2 web server. Don't know
if it will actually work with apache1. Thanks to my good old buddy cactus (e.cactuswax.net)
for the original version of this, which I adapted to Slackware :)

1) Install Subversion

Download subversion and compile it using these steps:

# wget http://subversion.tigris.org/downloads/subversion-1.2.3.tar.bz2
# tar -jxvf subversion-1.2.3.tar.bz2
# cd subversion-1.2.3
# ./configure --prefix=/usr --with-apr=/usr/bin/apr-config --with-apr-util=/usr/bin/apu-config --with-zlib
# make
# checkinstall

If you're on Slackware 10.2 and above, subversion should already be installed. If not, grab it
from your nearest friendly slackware mirror :)

2) As root, create the svn root:

# mkdir -p /home/svn/repositories

3) Configure apache-svn support

Add these 2 lines to your httpd.conf (mine is in /etc/apache2):

  LoadModule dav_svn_module       lib/apache/mod_dav_svn.so
  LoadModule authz_svn_module     lib/apache/mod_authz_svn.so

I use SSL for apache, so I need to add

  &lt;Location /svn&gt;
     DAV svn
     SVNParentPath /home/svn/repositories
     AuthzSVNAccessFile /home/svn/.svn-policy-file
     AuthName "Test SVN Repo"
     AuthType Basic
     AuthUserFile /home/svn/.svn-auth-file
     Satisfy Any
     Require valid-user
  &lt;/Location&gt;

to my /etc/apache2/ssl.conf, inside the VirtualHost directive.

Don't forget to restart your httpd at this point

4) Setup the svn root directory:

Create /home/svn/.svn-policy-file

  [/]
  * = r
  
  [test:/]
  dadexter = rw

The * in the / section is matched to anonymous users. Any access above and beyond read only will be prompted for a user/pass by apache AuthType Basic. The /svn/test section inherits permissions from those above, so anon users have read only permission to it. I granted myself read/write permissions to the repo.


Create the svn-auth-file

This is either an htpasswd, or htdigest file. I used htpasswd. Again, because of SSL, I don't worry as much about password sniffing. htdigest would provide even more security vs sniffing, but at this point, I don't have a need for it.

  htpasswd -cs /home/svn/.svn-auth-file dadexter

The above creates the file (-c) and uses sha1 for storing the password (-s). The user cactus is created.
To add additional users, leave off the (-c) flag.

  htpasswd -s /home/svn/.svn-auth-file userX


Create a repository

  svnadmin create --fs-type fsfs /home/svn/repositories/test

I prefer the newer file-system based repository. No database corruption/blocking issues. (--fs-type fsfs)


Set permissions

The apache user needs permissions over the new repository.

  chown -R nobody.nobody /home/svn/repositories/test


4) Client setup

Install the package created above (or the package from the Slackware mirror) on your development machine.
Next, create a directory to hold your development stuff, and create the svn directory structure:

  mkdir -p ~/coding
  cd ~/coding
  mkdir branches tags trunk

Put your source files into the created trunk directory. Here, I copy my development directory for an online
reservation system I'm working on.

  cp -R /home/martin/cal2/* trunk

Finally, import your development project into the svn repository:

  svn import -m "Initial import" https://192.168.100.1/svn/test/


5) Testing the checkout

  cd ~
  rm -rf coding
  svn co https://192.168.100.1/svn/test/

I end up with the same ~/coding I had before :)</text>
    <sha1>c59ec895016c435bbba1e508e678ed9e8687da23</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Sudo</title>
  <ns>0</ns>
  <id>167</id>
  <revision>
    <id>195</id>
    <timestamp>2009-06-06T23:31:33Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2370" xml:space="preserve">Sudo is a program that lets a certain user run a program as root or another user. For instance say you want to let a user run &lt;br&gt;
/usr/sbin/alsactl with root privilege , but not give them your root password? In sudo you can do 
this! First su into root and type:
 
 visudo

You will now see a few example lines, Now first lets make the user "sandman1" be able to run alsactl as root:
 
 sandman1   ALL = /usr/sbin/alsactl

Now of course you change the values of the following above. The first value "sandman1" is of course the username.
the ALL &lt;br&gt; is the hostname, now you can actually put the real host name there , or you can allow a user to be on any host by adding &lt;br&gt; ALL.  Now log into the user and type the following:

 sudo /usr/sbin/alsactl

This command will ask you for a password, type YOURS in and not root
and boom, you now can run /usr/sbin/alsactl as &lt;br&gt; root. With sudo you can
also run programs as a different username besides root:

 sandman1   192.168.0.2 = (test) /usr/sbin/alsactl

Now you noticed that I used an actual IP address in this
example. (That is my local IP anyways) Now you noticed the &lt;br&gt; (test) that
is the username that it will run as if i type the following command:

 sudo -u test /usr/sbin/alsactl

Now the following example makes it so you do not have to type any
password in:

 %wheel   ALL = NOPASSWD: /usr/sbin/alsactl

The % symbolizes that wheel is not a user, but a group. Now if you are
in the group wheel and type "sudo /usr/sbin/alsactl", &lt;br&gt; you will notice
that it did not ask you for the password! Now all of this is great,
but what happens when you have more &lt;br&gt; than 1 user that is not in the
same group, but want to run the same command as root?

 User_Alias GROUPOFUSERS = sandman1, sandy
 GROUPOFUSERS   ALL = NOPASSWD: /usr/sbin/alsactl

Now the 2 users sandman1, and sandy can run /usr/sbin/alsactl as
root! Now see how easy it is to add multiple users? &lt;br&gt; You can also add
multiple Hosts as well:

 Host_Alias SWEETHOST = 192.168.0.2, 192.168.0.3
 sandman1   SWEETHOST = NOPASSWD: /usr/sbin/alsactl

Now you see how easy it is to setup multiple hosts? Now to find out
what commands you can run using sudo just type the &lt;br&gt; following command:

 sudo -l

That will list all the commands you are aloud to run! Now sudo is an
easy tool and I hope you have a great time using it.

[[Category:Tutorials]]</text>
    <sha1>b7772e02c504ef2ca451312605e2aa54db499ea8</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>SysRq</title>
  <ns>0</ns>
  <id>168</id>
  <revision>
    <id>196</id>
    <timestamp>2009-06-06T23:31:58Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2515" xml:space="preserve">[[Category:Tips]]
--[[User:Drijen|Drijen]] 15:06, 22 September 2007 (EDT)

==Recovering from a System Lock==
Sometimes a process can go out to lunch, or the system will simply stop responding to user input. This could be from a process waiting for resources or a zombie, but in any case there is no reason to have to reach for that reset button!

==The Magic SysRq==
The SysRq can be used as a means to save your work, sync the file system(s) and reboot the computer in a clean manner. If you don't know where the SysRq key is, look for the "Prt Scr" (Print Screen) button on your keyboard. SysRq is generally assigned to the same keypress.

===Enabling the SysRq Function===
To enable the SysRq functionality, you must have a 2.6.15 or higher kernel, and it must be compiled directly in.  Not as a Module!

To check that you have it enabled you may run this command:


:&lt;pre&gt;cat /boot/config |grep CONFIG_MAGIC_SYSRQ&lt;/pre&gt;


OR

:&lt;pre&gt;zcat /proc/config.gz |grep SYSRQ&lt;/pre&gt;


if you have /proc/.config support compiled in. (All base slack kernels do)


which should return:


:&lt;pre&gt;CONFIG_MAGIC_SYSRQ=y&lt;/pre&gt;


If you find that you need to compile it in, the option can be found under the heading ''Kernel Hacking'' on your make &lt;(x)(menu)config&gt; screen.


Once you are satisfied that you have the SysRq funtion correctly compiled, ensure that it has not been disabled at boot:


:&lt;pre&gt;cat /proc/sys/kernel/sysrq&lt;/pre&gt;


If the response is &lt;tt&gt;0&lt;/tt&gt; :

:&lt;pre&gt;echo 1 &gt; /proc/sys/kernel/sysrq&lt;/pre&gt;


===Recovering from a Lock Up using SysRq===
If your system has gone out to lunch, you can now use the Magic SysRq key to save your work and reboot. The basic commands are as follows:

   &lt;tt&gt;Alt+SysRq+R&lt;/tt&gt; :Attempts to remove keyboard from Raw mode
   &lt;tt&gt;Alt+SysRq+K&lt;/tt&gt; :Kills all processes (SIGKILL / kill -9)
   &lt;tt&gt;Alt+SysRq+E&lt;/tt&gt; :Terminates all processes (SIGTERM / kill -15)
   &lt;tt&gt;Alt+SysRq+I&lt;/tt&gt; :Interrupts all processes (SIGINT / kill -2)
   &lt;tt&gt;Alt+SysRq+U&lt;/tt&gt; :Force unmount and remount of all filesystems readonly
   &lt;tt&gt;Alt+SysRq+S&lt;/tt&gt; :Syncs all disks
   &lt;tt&gt;Alt+SysRq+B&lt;/tt&gt; :Reboots (INIT 6)


An alternative method is to:

:&lt;pre&gt;Alt+SysRq+R CTRL+ALT+DEL&lt;/pre&gt;

This command will move the keyboard out of raw mode, and attempt to issue a &lt;tt&gt;SHUTDOWN NOW&lt;/tt&gt; command. However, this will not work under some configurations, or if tty1 is defunct.

==Futher Information==
Further instructions and other options can be found in:


&lt;pre&gt;/usr/src/&lt;linux-version&gt;/Documentation/sysrq.txt&lt;/pre&gt;</text>
    <sha1>e77ef928f1ee794eede374fa0587ccaeeae0c9ee</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Tagfile Install</title>
  <ns>0</ns>
  <id>169</id>
  <revision>
    <id>197</id>
    <timestamp>2009-06-06T23:32:41Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2424" xml:space="preserve">==What is a tagfile?==
Tagfiles are text files found in each category directory that Slackware's installer uses to install, not install or ask for each package.


==Where are the tagfiles found?==
There is a single tagfile located in each of the sub-directories under &lt;code&gt;/slackware/&lt;/code&gt; on the Slackware install CD.  Each tagfile lists the packages that are in that sub-directory and tells the Slackware installer to install, not install or ask about each package.

EXAMPLE-&lt;br&gt;

 slackware/
     |-- a
     |   +- blahblah.tgz
     |   +- tagfile
     |   +- u-blahblah.tgz
     |   \- etctera
     |
     |-- ap
     |   +- blahblah.tgz
     |   +- tagfile
     |   +- u-blahblah.tgz
     |   \- etctera
     |
     |-- etcetera


==What are the tagfile options?==
&lt;code&gt;REC&lt;/code&gt; = Required, these packages are automatically installed.&lt;br&gt;
&lt;code&gt;ADD&lt;/code&gt; = Add, these packages are automatically installed.&lt;br&gt;
&lt;code&gt;OPT&lt;/code&gt; = Optional, the installer will stop and ask to install these packages.&lt;br&gt;
&lt;code&gt;SKP&lt;/code&gt; = Skip, these packages will NOT be installed.&lt;br&gt;


==How do I use them?==
You use them to automate an install.  You can either customize the Slackware Install discs with your own tagfiles or you can use custom tagfiles in another director (e.g. a [[floppy]], [[USB_Memory_Stick|memstick]] or whatever).

You need to edit each tagfile and make each package either a &lt;code&gt;ADD&lt;/code&gt; (or &lt;code&gt;REC&lt;/code&gt;) or a &lt;code&gt;SKP&lt;/code&gt;.  REMOVE ALL &lt;code&gt;OPT&lt;/code&gt;s.


'''Customized Slackware install CD-'''&lt;br&gt;
1) Obtain/make an ISO image(s) of the Slackware Install CD(s).&lt;br&gt;
2) Using an ISO Editor program, edit each tagfile as you wish.&lt;br&gt;
3) Burn new Install CDs from your modified ISO images.&lt;br&gt;
4) During Slackware installation, choose "CUSTOM" as your install method.&lt;br&gt;
5) Go get a beer because the install does the rest.&lt;br&gt;

'''Non-customized Install CD method-'''&lt;br&gt;
1) Create the /slackware package directory structure from the install CD(s) on to some media.  Copy each tagfile over but DO NOT COPY THE PACKAGES.&lt;br&gt;
2) Edit the tagfiles as you wish.&lt;br&gt;
3) Before/during the Slackware installation, mount the media so the files are accessible.&lt;br&gt;
4) During Slackware installation, choose "TAG PATH" as your install method and enter to path to your custom tagfiles (where you mounted tor media).&lt;br&gt;
5) Go get a beer because the install does the rest.&lt;br&gt;


[[Category:Tutorials]]</text>
    <sha1>08c6f72547aafbf2fff896547fa78ae40af07cd1</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Third Party Package Managers</title>
  <ns>0</ns>
  <id>170</id>
  <revision>
    <id>198</id>
    <timestamp>2009-06-06T23:33:41Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10354" xml:space="preserve">= Purpose =

The mere mention of third party package managers (such as [http://software.jaos.org/#slapt-get slapt-get] and [http://swaret.sourceforge.net/ swaret]) often results in a quick admonishment from Slackware users, and unfortunately, the only reason given in most cases is something along the lines of "they'll break your system."  This leaves users in a state of confusion, as the respective web sites of these third party tools tout them as an improvement.  The purpose of this page is to explain why and how these tools will often result in system breakage.

= Overview of Slackware's Native Package Tools =

Slackware's native package management utilities (&lt;tt&gt;pkgtool(8)&lt;/tt&gt;, &lt;tt&gt;installpkg(8)&lt;/tt&gt;, &lt;tt&gt;removepkg(8)&lt;/tt&gt;, and &lt;tt&gt;upgradepkg(8)&lt;/tt&gt;) do not support any form of dependency checking.  A Slackware package is essentially a compressed tarball of the files associated with an application, a file containing a short description of the application (&lt;tt&gt;./install/slack-desc&lt;/tt&gt;), and a script that performs some essential post-installation tasks (&lt;tt&gt;./install/doinst.sh&lt;/tt&gt;).  Installing a Slackware package simply copies those files to the filesystem and then executes the post-install script, while removing the package removes the files and reverses the post-install script.  As result, there is no guarantee that libraries and other files needed by a particular package are already present on the system when that particular package is installed.

= Overview of Selected Third Party Tools =

As stated above, Slackware's native package management suite neither has nor supports dependency resolution.  Because the third-party add-ons all use Slackware's native package tools, they are bound by this same limitation, at least to some extent, but some of them try to mitigate this in various ways; the following is an overview.


== swaret ==

=== Overview ===

Swaret makes use of an unofficial file that tries to list all package dependencies based on output of &lt;tt&gt;ldd(1)&lt;/tt&gt;.  The idea is that by running &lt;tt&gt;ldd(1)&lt;/tt&gt; on some binary or shared object, you can see what that file is linked to, and then see what package(s) contain those files, and then install those packages.  

=== Potential Problems ===

Since some library developers don't see the need to update their shared object version strings when making changes that are incompatible with the previous release, it's easy to need a newer release of some package but for swaret to not be able to determine this.
Since swaret is meant for upgrading packages, it will fail to roll back a package's version number if this occurs in the upstream Slackware tree for some reason.


== slapt-get ==

=== Overview ===

Slapt-get makes use of additional files (&lt;tt&gt;slack-required&lt;/tt&gt;, &lt;tt&gt;slack-suggests&lt;/tt&gt;, &lt;tt&gt;slack-conflicts&lt;/tt&gt;) inside a Slackware package.  Essentially, if a package is listed in &lt;tt&gt;slack-required&lt;/tt&gt;, then slapt-get will install or upgrade it first; if a package is listed in &lt;tt&gt;slack-conflicts&lt;/tt&gt;, then slapt-get will remove it first; if a package is listed in &lt;tt&gt;slack-suggests&lt;/tt&gt;, then slapt-get will offer to install it in addition to the packages noted in &lt;tt&gt;slack-required&lt;/tt&gt;.

=== Potential Problems ===

Since official Slackware packages do not have the &lt;tt&gt;slack-required&lt;/tt&gt; and other files needed for slapt-get to determine dependencies, it is not able to resolve dependencies for them.  Therefore, slapt-get's perceived usefulness is in keeping unofficial third-party packages (or at least those which do contain the necessary files) up to date.  See the discussion below for more information on unofficial third-party packages.
Also, slapt-get, like swaret, will not "downgrade" a package to a previous version if it occurs in the upstream Slackware tree.

== sbopkg ==

=== Overview ===

[http://www.sbopkg.org/ SBopkg] is a tool for automating the download, compile and package build for SBo projects hosted in the [http://www.slackbuilds.org SlackBuilds.org ] repository.  SBo packages are reviewed by team members for completeness as well as applicability to each Slackware release.  SBo package documentation includes information regarding dependencies.

= Third Party (Unofficial) Packages =

This subject can elicit opinions just as strong as the topic of third-party package managers, and there are knowledgeable people on both sides of the issue.  Third party packages can obviously present a security risk, as there's no way to know what's really in them, but for the average user, there are (amazingly enough) bigger concerns.  On one hand, the user wants a package of some application that's not included with Slackware, but he doesn't want it to create other problems.  Oftentimes, third party packages are not built on "clean" systems -- that is, the computer on which they're built has quite a few other non-official packages installed -- so the resulting package needs those other things to work properly.  If the packager doesn't make note of all the different packages that this one depends on, the user installs it only to find that it still doesn't work.  Even worse, those other dependencies are often not even necessary if the package is built on a clean system - if the other package had not been present, the new one obviously wouldn't have linked against it.  
Installing third party packages from two different packagers can cause problems.  Package A might depend on Package B, which depends on Package C and optionally Package D.  If the person who built Package B only linked it against Package C (not D), but the Package A expects Package B to have both Package C and Package D dependencies, then Package A may not work, even though you (think you) have everything it needs installed.
Another frequent problem with third party packages is encountered by replacing stock (official) packages with unofficial ones.  In addition to the library version issues mentioned in the swaret discussion, newer package versions often require newer versions of other packages, which might require newer versions of still other packages, and before you know it, you have replaced a sizable portion of the official Slackware packages.  If/when something breaks, you will find it very difficult to find someone willing to help you, as there's no way to know how much effect the unofficial packages are having.


= Slackware -current =

Slackware -current is *not* a stable release of Slackware.  It is intended for advanced users who are familiar with how Slackware works to test (and report success/failure, find and fix bugs, etcetera) the new packages leading to the next stable release of Slackware.  Packages are constantly being added, removed, split up, merged, and otherwise mangled, and third party package managers (swaret/slapt-get/et al) should not be expected to know how to deal with this.  If you use one of those tools while trying to run Slackware -current and you don't understand how they work and their limitations, you *will* break your system and you will *not* have much luck finding someone who is sympathetic.  You have been warned.

You may be wondering why these tools have trouble with -current.  I won't even attempt to detail all of the potential issues, but here are a couple:
1. When upgrading to -current with one of these tools, the package sets are upgraded in alphabetical order (and the packages therein also in alphabetical order).  This means that a/bash will be upgraded before a/glibc-solibs.  If bash has been recompiled against newer glibc, and you upgrade to that new version, it will promptly stop working due to the fact that the needed version of glibc has not been upgraded yet; at that point, you are stuck with a "chicken and egg" problem.
2. Third party package tools will not install *new* packages that have been added in Slackware -current.  This is not a bug - it's a feature; if you purposefully didn't install something, then you don't want your automatic package updater reinstalling it.  However, when a package depends on something else that has been added or split out of an existing package, and your add-on package manager upgrades the existing package but doesn't install the added one, then the (upgraded) existing package will not work any more.


= Solutions and Suggestions =

For upgrading to Slackware -current, there is only *one* supported method: &lt;tt&gt;UPGRADE.TXT&lt;/tt&gt;  --  you can find this file on any Slackware mirror.  Note that this is also the only supported method to upgrade from one stable release of Slackware to another.

For keeping up to date on post-release patches added to a stable release of Slackware, you will *usually* be okay to use one of the third party package managers.  You should still read the &lt;tt&gt;ChangeLog.txt&lt;/tt&gt; before doing any upgrades, though, as new packages are occasionally added in /patches when circumstances require it.

For software not included in official Slackware, consider building it yourself or using a SlackBuild script from one of the projects which provides them.

One of the regular Slackware contributors, PiterPUNK, wrote and maintains a third-party package manager that minimizes all of the risks mentioned above.  [http://slackpkg.org Slackpkg] does not support downloading or installing unofficial packages, and it has provisions to install any added packages and uninstall any removed packages as well as the normal install/upgrade/remove routines.

Another third party package manager that promotes good practices is [http://slackroll.sourceforge.net/ SlackRoll] (see [[SlackRoll Tutorial|tutorial]]). Its philosophy is similar to that of Slackpkg but it is not included as part of Slackware. Programmed in Python, it is faster, has more features and detects more events from Slackware -current. However, the initial setup and workflow are a bit more complex.

= See Also =

* &lt;tt&gt;pkgtool(8)&lt;/tt&gt; -- man 8 pkgtool
* &lt;tt&gt;installpkg(8)&lt;/tt&gt; -- man 8 installpkg
* &lt;tt&gt;removepkg(8)&lt;/tt&gt; -- man 8 removepkg
* &lt;tt&gt;upgradepkg(8)&lt;/tt&gt; -- man 8 upgradepkg
* &lt;tt&gt;makepkg(8)&lt;/tt&gt; -- man 8 makepkg
* &lt;tt&gt;explodepkg(8)&lt;/tt&gt; -- man 8 explodepkg


= TODO =

* Add links to other wiki pages that are related to this topic (add to "See Also" above)
* Add hyperlinks to slapt-get, swaret, and other projects mentioned on this page
* Others?

[[Category:Information]]
[[Category:Tutorials]]</text>
    <sha1>87b633ead33c6105087ad9f9bdb3b153f769897e</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>USB Memory Stick</title>
  <ns>0</ns>
  <id>171</id>
  <revision>
    <id>199</id>
    <timestamp>2009-06-06T23:34:15Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1549" xml:space="preserve">[[Category:Tips]]

==IMPORTANT==

This information primarily applies to Slackware 11.0 and older; if you're using Slackware 12.0 or newer, you probably want to use [[HAL]] instead.

==Prerequisites==
You must have USB support [[Compiling A Kernel|compiled into the kernel]] or [[Modules|loaded as modules]].


==Mounting A USB Memory Stick==
1)Pick/make a mountpoint. (e.g. &lt;code&gt;/mnt/memstick&lt;/code&gt;)

2)Mount the device-

:If you have an [[fstab]] entry for it: &lt;code&gt;mount &lt;i&gt;mountpoint&lt;/i&gt;&lt;/code&gt;&lt;br&gt;
::EXAMPLE: &lt;code&gt;mount /mnt/memstick&lt;/code&gt;

:Otherwise: &lt;code&gt;mount  &lt;i&gt;device  mountpoint&lt;/i&gt;&lt;/code&gt;&lt;br&gt;
::EXAMPLE: &lt;code&gt;mount /dev/sda1 /mnt/memstick&lt;/code&gt;&lt;br&gt;
:: &lt;b&gt;NOTE:&lt;/b&gt; if you have multiple USB devices or Sata/SCSI disks, the device may not be &lt;code&gt;/dev/sda1&lt;/code&gt;, it could be &lt;code&gt;/dev/sdb1&lt;/code&gt;, &lt;code&gt;/dev/sdc1&lt;/code&gt; or any &lt;code&gt;/dev/sd*&lt;/code&gt;.

* you can see which devfile (in /dev/*) some devices get assigned by tracking the /var/log/messages (dmesg) changes.
 $ su 
 # tail -f /var/log/messages

and plug the USB device in the computer. This can be used for any other plug'n'play device.


==Unmounting a USB Memory Stick==
&lt;code&gt;umount &lt;i&gt;mountpoint&lt;/i&gt;&lt;/code&gt;

:EXAMPLE: &lt;code&gt;umount /mnt/memstick&lt;/code&gt;

==Errors and Solutions==
Error: &lt;code&gt;mount: special device /dev/sda&lt;i&gt;x&lt;/i&gt; does not exist&lt;/code&gt;

Solution: Check to see if &lt;code&gt;/dev/sda&lt;i&gt;x&lt;/i&gt;&lt;/code&gt; exists-
::::&lt;code&gt;ls /dev/sda*&lt;/code&gt;
::if &lt;code&gt;/dev/sda&lt;i&gt;x&lt;/i&gt;&lt;/code&gt; does not exist, create it:
::::&lt;code&gt;mknod -m 666 /dev/sda&lt;i&gt;x&lt;/i&gt; b 8 0&lt;/code&gt;</text>
    <sha1>7263c8de9cf0df9d13e2b94f4ba2c55150029a6f</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Udev</title>
  <ns>0</ns>
  <id>172</id>
  <revision>
    <id>200</id>
    <timestamp>2009-06-06T23:34:43Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11965" xml:space="preserve">[[Category:Tutorials]]

This page was originally written by Don Tanner aka [[User:dtanner|dtanner]], but due to the fact that udev has historically been a moving target, most of it is now out of date.  This is an attempt to bring it up to date, but for the most part, you should refer to the official udev documentation.

The information in this page is, to the best of my knowledge, current as of Slackware 11.0 -- the general ideas still apply on later versions, but sysfs keys have different names and such.  See the relevant man pages and udev documentation for information on how to adapt this for later udev (and Slackware) versions.

Users often want to have a device (such as a removable usb flash memory stick) always get assigned the same device node - this makes it easy to specify the node in /etc/fstab for mounting it.  You don't actually want to assign the same device node (in other words, rather than renaming the *real* device node, you want to create a persistent symlink to it - changing the name of the node itself can cause problems later, especially with respect to logging - the kernel logs will show device nodes that no longer exist).  To do this, first plug in the removable memory stick and run &lt;tt&gt;dmesg | tail&lt;/tt&gt; to see what device node is assigned.

 rworkman@tritium:~$ dmesg | tail
 sda: Mode Sense: 03 00 00 00
 sda: assuming drive cache: write through
 SCSI device sda: 2001888 512-byte hdwr sectors (1025 MB)
 sda: Write Protect is off
 sda: Mode Sense: 03 00 00 00
 sda: assuming drive cache: write through
  sda: sda1
 sd 0:0:0:0: Attached scsi removable disk sda
 usb-storage: device scan complete
 sd 0:0:0:0: Attached scsi generic sg0 type 0

As you can see, the device is attached to /dev/sda (and since it has one partition, what I'm actually interested in is /dev/sda1).
Now use &lt;tt&gt;udevinfo(8)&lt;/tt&gt; to find out the sysfs path to the device.

 rworkman@tritium:~$ udevinfo -q path -n /dev/sda1 
 /block/sda/sda1

Now use &lt;tt&gt;udevinfo(8)&lt;/tt&gt; again to show all of the keys exported to sysfs:

 rworkman@tritium:~$ udevinfo -q all -a -p /block/sda/sda1
 
 Udevinfo starts with the device specified by the devpath and then
 walks up the chain of parent devices. It prints for every device
 found, all possible attributes in the udev rules key format.
 A rule to match, can be composed by the attributes of the device
 and the attributes from one single parent device.
 
  looking at device '/block/sda/sda1':
    KERNEL=="sda1"
    SUBSYSTEM=="block"
    DRIVER==""
    SYSFS{stat}=="     131      131        0        0"
    SYSFS{size}=="1999627"
    SYSFS{start}=="245"
    SYSFS{dev}=="8:1"
 
  looking at parent device '/block/sda':
    ID=="sda"
    BUS=="block"
    DRIVER==""
    SYSFS{stat}=="      11      121      139       28        0        0        0        0        0       28       28"
    SYSFS{size}=="2001888"
    SYSFS{removable}=="1"
    SYSFS{range}=="16"
    SYSFS{dev}=="8:0"
 
  looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4/4-6/4-6:1.0/host0/target0:0:0/0:0:0:0':
    ID=="0:0:0:0"
    BUS=="scsi"
    DRIVER=="sd"
    SYSFS{ioerr_cnt}=="0x1"
    SYSFS{iodone_cnt}=="0x15"
    SYSFS{iorequest_cnt}=="0x15"
    SYSFS{iocounterbits}=="32"
    SYSFS{timeout}=="30"
    SYSFS{state}=="running"
    SYSFS{rev}=="0.2 "
    SYSFS{model}=="Cruzer Micro    "
    SYSFS{vendor}=="SanDisk "
    SYSFS{scsi_level}=="3"
    SYSFS{type}=="0"
    SYSFS{queue_type}=="none"
    SYSFS{queue_depth}=="1"
    SYSFS{device_blocked}=="0"
    SYSFS{max_sectors}=="240"
 
  looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4/4-6/4-6:1.0/host0/target0:0:0':
    ID=="target0:0:0"
    BUS==""
    DRIVER==""
 
  looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4/4-6/4-6:1.0/host0':
    ID=="host0"
    BUS==""
    DRIVER==""
 
  looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4/4-6/4-6:1.0':
    ID=="4-6:1.0"
    BUS=="usb"
    DRIVER=="usb-storage"
    SYSFS{modalias}=="usb:v0781p5151d0020dc00dsc00dp00ic08isc06ip50"
    SYSFS{bInterfaceProtocol}=="50"
    SYSFS{bInterfaceSubClass}=="06"
    SYSFS{bInterfaceClass}=="08"
    SYSFS{bNumEndpoints}=="02"
    SYSFS{bAlternateSetting}==" 0"
    SYSFS{bInterfaceNumber}=="00"
 
  looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4/4-6':
    ID=="4-6"
    BUS=="usb"
    DRIVER=="usb"
    SYSFS{configuration}==""
    SYSFS{serial}=="SNDK5D1BF51877607705"
    SYSFS{product}=="Cruzer Micro"
    SYSFS{manufacturer}=="SanDisk Corporation"
    SYSFS{maxchild}=="0"
    SYSFS{version}==" 2.00"
    SYSFS{devnum}=="2"
    SYSFS{speed}=="480"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{bDeviceProtocol}=="00"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bDeviceClass}=="00"
    SYSFS{bcdDevice}=="0020"
    SYSFS{idProduct}=="5151"
    SYSFS{idVendor}=="0781"
    SYSFS{bMaxPower}=="200mA"
    SYSFS{bmAttributes}=="80"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bNumInterfaces}==" 1"
 
  looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4':
    ID=="usb4"
    BUS=="usb"
    DRIVER=="usb"
    SYSFS{configuration}==""
    SYSFS{serial}=="0000:00:1d.7"
    SYSFS{product}=="EHCI Host Controller"
    SYSFS{manufacturer}=="Linux 2.6.17.13 ehci_hcd"
    SYSFS{maxchild}=="6"
    SYSFS{version}==" 2.00"
    SYSFS{devnum}=="1"
    SYSFS{speed}=="480"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{bDeviceProtocol}=="01"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bDeviceClass}=="09"
    SYSFS{bcdDevice}=="0206"
    SYSFS{idProduct}=="0000"
    SYSFS{idVendor}=="0000"
    SYSFS{bMaxPower}=="  0mA"
    SYSFS{bmAttributes}=="e0"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bNumInterfaces}==" 1"
 
  looking at parent device '/devices/pci0000:00/0000:00:1d.7':
    ID=="0000:00:1d.7"
    BUS=="pci"
    DRIVER=="ehci_hcd"
    SYSFS{modalias}=="pci:v00008086d000024CDsv00001028sd00000126bc0Csc03i20"
    SYSFS{local_cpus}=="1"
    SYSFS{irq}=="7"
    SYSFS{class}=="0x0c0320"
    SYSFS{subsystem_device}=="0x0126"
    SYSFS{subsystem_vendor}=="0x1028"
    SYSFS{device}=="0x24cd"
    SYSFS{vendor}=="0x8086"
 
  looking at parent device '/devices/pci0000:00':
    ID=="pci0000:00"
    BUS==""
    DRIVER==""

As you can see, this is a lot of information.  The actual device information exported (the first block that says &lt;tt&gt;looking at device '/block/sda/sda1'&lt;/tt&gt; is not useful to us, as there's no guarantee that it is unique (in other words, some other device could very easily have the same information).  Continue looking down the output (which is actually up the device chain) to parent devices until you find one that has unique information in it.  In this case, the third block (&lt;tt&gt;looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4/4-6/4-6:1.0/host0/target0:0:0/0:0:0:0':&lt;/tt&gt;) might at first appear useful, but it's not -- instead, look at the seventh block (&lt;tt&gt;looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4/4-6'&lt;/tt&gt;) which has the serial number of the device exported.

  looking at parent device '/devices/pci0000:00/0000:00:1d.7/usb4/4-6':
    ID=="4-6"
    BUS=="usb"
    DRIVER=="usb"
    SYSFS{configuration}==""
    SYSFS{serial}=="SNDK5D1BF51877607705"
    SYSFS{product}=="Cruzer Micro"
    SYSFS{manufacturer}=="SanDisk Corporation"
    SYSFS{maxchild}=="0"
    SYSFS{version}==" 2.00"
    SYSFS{devnum}=="2"
    SYSFS{speed}=="480"
    SYSFS{bMaxPacketSize0}=="64"
    SYSFS{bNumConfigurations}=="1"
    SYSFS{bDeviceProtocol}=="00"
    SYSFS{bDeviceSubClass}=="00"
    SYSFS{bDeviceClass}=="00"
    SYSFS{bcdDevice}=="0020"
    SYSFS{idProduct}=="5151"
    SYSFS{idVendor}=="0781"
    SYSFS{bMaxPower}=="200mA"
    SYSFS{bmAttributes}=="80"
    SYSFS{bConfigurationValue}=="1"
    SYSFS{bNumInterfaces}==" 1"

This is the information that we can use to create a custom udev rule for this device.
It's important to remember that all of the information in a single udev rule must come from the same block of information (all from the same device or parent device) or it will not work.  Based on the keys above, we should be able to use this udev rule to always create a custom symlink to &lt;tt&gt;/dev/cruzer&lt;/tt&gt; when the device is plugged in:

 BUS=="usb", SYSFS{manufacturer}=="SanDisk Corporation", SYSFS{product}=="Cruzer Micro", SYSFS{serial}=="SNDK5D1BF51877607705", KERNEL=="sd?1", NAME="%k", SYMLINK+="cruzer"

Note that the "&lt;tt&gt;==&lt;/tt&gt;" string is a test operator and the "&lt;tt&gt;=&lt;/tt&gt;" string is an assignment operator.  In essence, the above rule tests for all the conditions with "&lt;tt&gt;==&lt;/tt&gt;" and makes assignments with "&lt;tt&gt;=&lt;/tt&gt;" - in other words, the rule will assign the default name for the device node (in this case, &lt;tt&gt;/dev/sda1&lt;/tt&gt;), and make a symlink to it at &lt;tt&gt;/dev/cruzer&lt;/tt&gt;.

Now that we've got a rule, where do we put it?  You might think that it would go in the default &lt;tt&gt;/etc/udev/rules.d/udev.rules&lt;/tt&gt; file, but you'd be wrong -- this file should *never* be edited by the system admin unless you are prepared to make the edits after every udev update/upgrade.  The default rules file is *always* overwritten by an upgraded udev package, as these rules *must* remain in sync with the upstream udev rules.  Therefore, the proper place to put our new custom rule is in a custom rules file.  The choice of naming for this file is up to you, but note that it must end with the suffix &lt;tt&gt;.rules&lt;/tt&gt; for &lt;tt&gt;udevd(8)&lt;/tt&gt; to look at it.  A common choice of name is either &lt;tt&gt;10-custom.rules&lt;/tt&gt; or &lt;tt&gt;10-local.rules&lt;/tt&gt;.  Place the rule above into whichever name you choose for the file and unplug the device.  To see if it works properly, the easiest thing to do is run &lt;tt&gt;udevtrigger(8)&lt;/tt&gt; with no arguments:

 root@tritium:/home/rworkman# udevtrigger
 root@tritium:/home/rworkman# ls -l /dev/cruzer 
 lrwxrwxrwx 1 root root 4 2007-05-13 16:25 /dev/cruzer -&gt; sda1

As you can see, the symlink to the device was created correctly, and I can now add this device to /etc/fstab using the /dev/cruzer link.

Note that udev's rule parsing order can influence whether your custom rule works as expected.  That's not to say it will influence whether it works - it just might not work as expected.  For example, your rule in &lt;tt&gt;10-local.rules&lt;/tt&gt; might work properly, but then one of the default rules in &lt;tt&gt;udev.rules&lt;/tt&gt; (this file is named &lt;tt&gt;50-udev.rules&lt;/tt&gt; in Slackware post-11.0) will be evaluated and change the device nodes and such to the defaults.  If you suspect this is happening, either try placing your custom rule in a file that will be evaluated after the default rules, or the ":=" operator (see &lt;tt&gt;udev(7)&lt;/tt&gt;) might help.


See also:
* &lt;tt&gt;udev(7)&lt;/tt&gt; -- type "&lt;tt&gt;man 7 udev&lt;/tt&gt;"
* &lt;tt&gt;udevd(8)&lt;/tt&gt;
* &lt;tt&gt;udevinfo(8)&lt;/tt&gt;
* &lt;tt&gt;udevmonitor(8)&lt;/tt&gt;
* &lt;tt&gt;udevtrigger(8)&lt;/tt&gt;
* &lt;tt&gt;udevsettle(8)&lt;/tt&gt;
* &lt;tt&gt;udevtest(8)&lt;/tt&gt;
* &lt;tt&gt;/usr/doc/udev-$VERSION/&lt;/tt&gt;  -- especially the &lt;tt&gt;./docs/writing_udev_rules/&lt;/tt&gt; directory


OLD INFO - this information is almost certainly out of date, and the sysfs keys are definitely changed, but just in case anyone still needs it, the idea is still basically the same, so I'm leaving it here.  Your mileage may vary...

Cranky Card Readers

Some card readers fail to report the existence of any partitions if they are plugged in before a card is inserted. Thus, if the card reader is assigned &lt;code&gt;/dev/sda&lt;/code&gt; the &lt;code&gt;/dev/cardreader&lt;/code&gt; symlink is created, but &lt;code&gt;/dev/sda1&lt;/code&gt; does not yet exist, and the &lt;code&gt;/dev/cardreader1&lt;/code&gt; symlink is missing. One solution to this problem is to set up a rule that causes all possible device node names to be created when the cardreader is plugged in.

The following rule causes all device nodes to be created for any removable media with a size of zero, i.e., a card reader with no card in it:

: &lt;code&gt;SUBSYSTEM=="block", SYSFS{size}=="0", SYSFS{removable}=="1",  NAME{all_partitions}="cardreader%n"&lt;/code&gt;</text>
    <sha1>29386bee582dcda3ed0d6bf9f72379d94698b8ac</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Upgrading Slackware</title>
  <ns>0</ns>
  <id>173</id>
  <revision>
    <id>201</id>
    <timestamp>2009-06-06T23:35:10Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7417" xml:space="preserve">[[Category:Tutorials]]
= Introduction =
Subject:	Upgrading Slackware&lt;br&gt;
Author:		Chris Clymer  aka:[[User:omal|omal]] / Pat Volkerding&lt;br&gt;
Why:		I've found this all very useful&lt;br&gt;
When:		Fri Aug 26 07:11:53 EDT 2005&lt;br&gt;
Running:	Slackware-current kernel 2.6.11&lt;br&gt;


Rather than waiting to upgrade every 6 months or so when theres a release, I like my Slackware systems to be current.  The way I do this is by mirroring most of the Slackware ftps on my own fileserver with a handy little tool called "rsync".  Rsync downloads only the parts of files that have changed, so by having it run nightly, I always have an up-to-date mirror, with little bandwidth being used up.  You'll want to add a script something like the following to crontab, probably by executing "crontab -e":

 #!/bin/sh
 /usr/bin/rsync -avz rsync://inferno.bioinformatics.vt.edu/slackware/slackware-current/ 
 /mnt/mirror/slackware/

This inferno.bioinformatics server is one i've found to be fairly reliable...they even have -current isos if what one really wants is a fresh install off a CD!  The script just syncs that directory on their server with /mnt/mirror/slackware on the target server...obviously this will probably be different on your server.

Now if you are a SMART person, you will copy all of the files you need over to a local machine before upgrading.  It's what Pat recommends in the guide I've got below...however it's also something I don't personally do ;)  If you like to live on the edge, just mount your shares over SAMBA or NFS, and then proceed, adjusting the guide below accordingly.

Again, this isn't mine but I've always found it useful.  In this case it's the official UPGRADE.txt that Pat always includes with slack.  Any Slackware release is accompanied by this file on the FTPs.  This is my bible for upgrading, and while i deviate in some small ways, it is a very good guide.  Straight from the source himself!


********************************* &lt;br&gt;

= Process =

Slackware 10.0 to 10.1 Upgrade HOWTO  &lt;volkerdi@slackware.com&gt;

This document explains how to upgrade from Slackware 10.0 to Slackware 10.1

-----------------------------------------------------------------------------


Before you begin, I would strongly recommend making a backup of your
system, or, if not the entire system, at least the /etc directory.  You
might find that you need to refer to a few things about the upgrade
process is complete. Back it up, or take your chances.

OK, now that everything is safely backed up, let's proceed. :-)

To do this, you'll need the Slackware 10.1 packages.  If these are on a CD,
create a new directory to mount the CD on so that it doesn't get in the
way during the upgrade:

 mkdir /packages
 mount /dev/cdrom /packages

The packages don't have to be on a CD-ROM, as an alternative you could
copy the slackware directory (the one with the various package
subdirectories in it, basically the "slackware" directory from the install
CD) to someplace like /root/slackware/.  The important thing is that you
know where the slackware packages directory is.  We'll use /root/slackware
in the following examples.


0. Put your machine in single-user mode:
    telinit 1


1. Upgrade your glibc shared libraries.  This is important, or things might go haywire during the first part of the upgrade:

    upgradepkg /root/slackware/a/glibc-solibs-*.tgz


2.  Upgrade your package utilities:

    upgradepkg /root/slackware/a/pkgtools-*.tgz


3.  Install sed.  You should already have this, but since it's used by the package utilities it is best to be sure:

    upgradepkg --install-new /root/slackware/a/sed-*.tgz


4.  Upgrade everything else (and install new packages):

    upgradepkg --install-new /root/slackware/*/*.tgz


5.  Make sure your system will boot.  If you use LILO, make sure the paths in /etc/lilo.conf point to a valid kernel and then type 'lilo' to reinstall LILO.  If you use a bootdisk, you'll need to use makebootdisk to make a new bootdisk using the kernel in /boot.


6.  Fix your config files.  Some of the config files in /etc are going to need your attention.  You'll find the new incoming config files on your system with the ".new" extension.  You may need to fill these in with information from your old config files and then move them over.

Feel brave?  You can use this little script to install all of the .new config files in /etc.  If you've made any local changes you'll need to add them to the newly installed files.  Your old config files will be copied to *.bak.  Anyway, it might be an easier starting point.  Here it is:

     #!/bin/sh
     cd /etc
     find . -name "*.new" | while read configfile ; do
       if [ ! "$configfile" = "./rc.d/rc.inet1.conf.new" \
         -a ! "$configfile" = "./group.new" \
         -a ! "$configfile" = "./passwd.new" \
         -a ! "$configfile" = "./shadow.new" ]; then
         cp -a $(echo $configfile | rev | cut -f 2- -d . | rev) \
           $(echo $configfile | rev | cut -f 2- -d . | rev).bak 2&gt; /dev/null
         mv $configfile $(echo $configfile | rev | cut -f 2- -d . | rev)
       fi
     done

You'll probably also need to edit your /etc/X11/xorg.conf to change the name of the keyboard driver from "Keyboard" to "kbd".  I don't know why this changed, but it did.


7.  Return to multi-user mode:
    telinit 3


8.  Remove obsolete packages.

If you go into /var/log/packages and take a look at the package list:

    ls -lt | less

You may spot some old, obsolete, or discontinued packages.  If so, you can remove these using 'removepkg'.


9.  Remove KDE language bloat.  By upgrading all packages using --install-new you've probably installed all of the KDE language translations from the KDEI series, which will use up about 500MB.  If you need only US English, you may remove the KDE language packs like this:

    cd /var/log/packages
    removepkg kde-i18n* koffice-i18n*

Even if you need one of these, it might be best to start by removing them all, and then go back and install the ones you need with installpkg.    


At this point you should be running Slackware 10.1.  :-)

I wish everyone good luck with this!

---
Patrick Volkerding
volkerdi@slackware.com

********************************* &lt;br&gt;

= Conclusion =

You could of course omit the KDE International packages from your download scripts, or not copy them over for your install.  For most people this is logical.  It's possibly you don't even want all of KDE...I personally install it despite the fact that I don't run it, and reccomend you do the same.  Why?  Because somewhere down the road you may grab a package that depends on one of those KDE libraries, or even find you want a KDE app or two.  Even with KDE slackware is only about 3GB, so unless you are really hardup for drive space, it makes good sense.

Also, I should mention that one way I track slackware-current is through a nice little superkaramba script I wrote(which of course, depends on those KDE libraries!).  There are other ways that may suit you better, like mailing lists and RSS feeds.  I find that for me, this is simplest.  

If you want my script, you can grab it here:  http://kdelook.org/content/show.php?content=23384

The requirements are basically just superkaramba, and whatever KDE libraries it requires.  If you have the latest KDE, superkaramba is already included.

= Related Links =

* [[Release_Changes|Changes in Slackware Release Versions]]</text>
    <sha1>4d3fd16e8bfada17db75e4939d14a25203ffd8fe</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>Upgrade Using Slapt-get</title>
  <ns>0</ns>
  <id>174</id>
  <revision>
    <id>202</id>
    <timestamp>2009-06-06T23:35:42Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10621" xml:space="preserve">[[Category:Tutorials]]
= Introduction =

See the [[Slapt-get]] page for an introduction to slapt-get and its functionality.

Prior to using slapt-get, you should really be familiar with proper usage of the native Slackware package management tools:
 man pkgtool
 man installpkg
 man upgradepkg
 man removepkg
As indicated in the link above, slapt-get is *not* a replacement for those utilities - it *uses* those utilities.  As such, any inherent "limitations" (yes, I use that term loosely) in the pkgtool suite will also apply to slapt-get.

= Installation and Configuration =

Get the [[slapt-get]] package for your version of Slackware.

Once it's installed, configure it to point to your favourite
mirror (edit '''/etc/slapt-get/slaptgetrc''')

    # See /usr/doc/slapt-get-0.10.1/example.slapt-getrc 
    # for example source entries and configuration hints.
    WORKINGDIR=/var/slapt-get
    EXCLUDE=^kernel-.*,^alsa-.*,^glibc.*,.*-[0-9]dl$,^devs$,^udev$,aaa_elflibs,x86_64
    SOURCE=http://slackware.osuosl.org/slackware-12.2/:OFFICIAL
    SOURCE=http://software.jaos.org/slackpacks/12.2/:OFFICIAL

= Usage Hints =

Depending upon your individual goals of using slapt-get, the usage hints will vary.  An individual wishing to upgrade  from one release of Slackware to another will have more issues with which to contend than another individual who simply wants to keep up-to-date with official security/stability patches.

The biggest piece of advice I can give to *anyone* regardless of how/why you're using slapt-get is this: READ THE CHANGELOG!  The pertinent portions of the changelog are also viewable for each package using --show option.  You'll be okay most of the time if you ignore this advice, but don't come crying to ##slackware if you do... :)  

From '''man slapt-get''':
 UPGRADE.TXT and ChangeLog.txt is still required reading, the latter is especially true  when running -current.

By the way, don't even consider trying to follow the Slackware -current development using slapt-get; that's just *asking* for a problem (for reasons which will hopefully be clear later).  
 Official ChangeLog is at ftp://ftp.slackware.com/pub/slackware/slackware-12.2/ChangeLog.txt
 Replace the "12.2" with the release version you're using.
Rather than using the official ChangeLog (and Slackware.com bandwidth), it's better to use one of the official Slackware mirrors (you'll notice faster connections with the mirrors):
 &lt;SlackwareMirror&gt;/slackware-&lt;version&gt;/ChangeLog.txt
See the Slackware site [[http://slackware.com/getslack/]] to find an official mirror site.

== Usage Hint #1: Security and Stability Patches ==

If your only goal is to stay up-to-date with official security and stability patches for your version of Slackware, then the default configuration of slapt-get should work fine for you.  While I'm not the author of slapt-get (Jason, feel free to jump in here), it seems to me that this was the original intent of slapt-get (and it works *extremely* well for that task, might I add).

The only exception of which I can think is kernel upgrades; thankfully, those haven't happened *too* often in official releases in recent memory, but they do occur frequently enough to be worth considering.  The default configuration of slapt-get will ignore kernel upgrades, so the only way you'll know about those is by reading the official ChangeLog.  Anyway, every time you upgrade your kernel, you'll need to make sure the paths in '''/etc/lilo.conf''' point to a valid kernel, and then run '''/sbin/lilo''' to reinstall LILO.  If you use some other boot loader, then I'm going to assume you know enough about its usage to perform the corresponding operation (if required) after upgrading your kernel.

I would recommend that you keep your old kernel around when installing a new one; it's always good to have a known-good kernel lying around just in case the new one doesn't boot.  However, you'll notice that by default, running this command: 
 slapt-get --install kernel-$VERSION
will *upgrade* the kernel; in other words, it will *remove* the old kernel package and *install* the new one.  This is not desirable if you wanted to keep your old kernel, so you can run this command instead:
 slapt-get --install --no-upgrade kernel-$VERSION
From '''man slapt-get''':
  --no-upgrade
         Install the package rather than  attempting  to  detect  if  a  previous  version  is
         installed  and  upgrading  it.   This is useful for installing kernel packages.  This
         option is only valid for --install targets.
You might also find this option useful for installing multiple versions of the alsa-* packages; if you're running both 2.4.x and 2.6.x kernels, you'll need the alsa-driver packages for both kernels, so an *upgrade* of the 2.4.x version to 2.6.x will remove the 2.4.x version.

== Usage Hint #2: Upgrade From One Release To Another ==

Every Slackware release includes a file named UPGRADE.TXT - it was included for a reason, so READ IT!  Once you are familiar with its contents, the rationale behind the information below will make more sense.  

=== Step 1: Edit your /etc/slapt-get/slaptgetrc ===

Edit your '''/etc/slapt-get/slaptgetrc''' file to reflect the new Slackware version

This:
    SOURCE=http://slackware.osuosl.org/slackware-12.1/
    SOURCE=http://software.jaos.org/slackpacks/12.1/
becomes this:
    SOURCE=http://slackware.osuosl.org/slackware-12.2/:OFFICIAL
    SOURCE=http://software.jaos.org/slackpacks/12.2/:OFFICIAL

=== Step 2: Download all updated packages === 

Download all updated packages to slapt-get's working directory; by default, this is '''/var/slapt-get'''
 slapt-get --dist-upgrade --ignore-excludes --download-only

=== Step 3: Put your machine in single-user mode ===

Make sure you have already performed step 2, because the network will not be available in runlevel 1.
 telinit 1

=== Step 4: Upgrade main packages ===

Versions &gt;= 0.9.11 upgrade glibc-solibs, pkgtools, and sed first , and then upgrade the remainder of the packages.  If you have read the UPGRADE.TXT file, you already know why this is needed. (hint, hint)

* '''Step 4a:''' If you are using slapt-get version earlier than 0.9.11, do:
 slapt-get --install kernel --no-upgrade
 slapt-get --install glibc-solibs pkgtools sed
 slapt-get --dist-upgrade

* '''Step 4b:''' If you are using slapt-get version 0.9.11 or later, do:
 slapt-get --install kernel --no-upgrade
 slapt-get --dist-upgrade --ignore-excludes

The '''--dist-upgrade''' option will prompt you to install all *new* packages in the ./a series, and you should say "yes" to ensure that you have a working system after the upgrade.  See step 8 below for more information on installing new packages.

=== Step 5: Update LILO and config files ===
* Make sure the paths in '''/etc/lilo.conf''' point to a valid kernel image, and then run '''/sbin/lilo'''
* Fix your config files in '''/etc'''; the new ones are named with a *.new suffix.  You should be able to use '''diff -u file file.new''' to show the differences between file and file.new.  You'll have to decide whether to completely replace the old files with the new ones or merge your changes into the new ones first, but you *must* use the new files.

=== Step 6: Go back to multi-user mode ===

Sometimes the screen stays blank when you return to runlevel 3, and you might be worried that something went wrong.  Before you panic, type '''clear''' and press Enter - you'll probably get your root prompt back :)
 telinit 3

=== Step 7: Remove obsolete packages ===

There is an option to do this automatically with slapt-get:
 slapt-get [--remove|--dist-upgrade] --remove-obsolete
From '''man slapt-get'''
   --remove-obsolete
         Remove  installed packages that are no longer available.  This works for dist-upgrade
         only.  This removes packages that are no longer available from  any  current  package
         sources,  but  are  currently  installed.  Be careful as this will also remove custom
         built packages.
As you see, this option will be fine ''if you don't have any custom-compiled packages'' installed (such as with [[checkinstall]] or using [[SlackBuild_Scripts]]).  Read through the official ChangeLog to find all packages that were removed from Slackware during the development phase; you might be able use something like this to make the process go a bit more quickly:
 grep -i removed ChangeLog.txt  OR  grep Removed ChangeLog.txt

=== Step 8: Add new packages ===

Similar to removing obsolete packages, there is an option to do this automatically with slapt-get using the '''--install-set''' option:
 slapt-get --upgrade --install-set a ap d f k kde l n t tcl x xap y

From '''man slapt-get''':
   --install-set [disk set(s)]
          Install specified disk set(s).  example: --install-set xap n l

This option will upgrade (or install, if not already installed) every package in every disk set.  For reasons already detailed (kernel/alsa versions), this may not be desirable; additionally, if you don't have a full installation of Slackware for whatever reason, this will not be desirable. 

The safest option is to read through the official ChangeLog.txt, make a note of new packages added during the release cycle, and install them now with this command:
 slapt-get --install &lt;newpackage1&gt; &lt;newpackage2&gt; &lt;...&gt;
You might be able to use something like this to make the process go a bit more quickly, but it will return quite a few extraneous results.
 grep -i added ChangeLog.txt

=== Step 9: Admire the Results :) ===
At this point, you should be running the latest version of Slackware.  

== Usage Hint #3: Keep Up With Slackware -current Development ==

After modifying your &lt;code&gt;/etc/slapt-get/slaptgetrc&lt;/code&gt; file to reflect -current sources, the most important advice you should hear is: &lt;b&gt;READ THE CHANGELOG&lt;/b&gt;

Seriously, always read the ChangeLog.txt file associated with the -current tree; so long as you read it prior to running the &lt;code&gt;slapt-get --upgrade&lt;/code&gt; command, you should be familiar with any issues that might be encountered.

One idea you might consider is to use slapt-get as a "double checking" tool to ensure you haven't accidentally overlooked any packages.  While the concerns detailed earlier in this article apply here (you won't be informed of any new packages added to -current), you can use the following lines to see if you missed anything that needed to be upgraded:

 slapt-get --update
 slapt-get --upgrade --simulate

= Related Links =

* [http://www.slackersbible.org/node/98 Unofficial slapt-get HOWTO]
* [[Release_Changes|Changes in Slackware Release Versions]]</text>
    <sha1>ed5d8d7f93fc48ffb864c3b38a06e4e8c7d26594</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>User Administration</title>
  <ns>0</ns>
  <id>175</id>
  <revision>
    <id>203</id>
    <timestamp>2009-06-06T23:36:15Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1092" xml:space="preserve">[[Category:Tips]]
==Adding Users==
To ADD users:  &lt;code&gt;adduser &lt;i&gt;user&lt;/i&gt;&lt;/code&gt;

==Deleting Users==
To REMOVE users: &lt;code&gt;userdel &lt;i&gt;baduser&lt;/i&gt;&lt;/code&gt;

The above command will remove the entry matching the username &lt;i&gt;baduser&lt;/i&gt; from the &lt;code&gt;/etc/passwd&lt;/code&gt; file and if you're using the Shadow password format (which you should be), also from the &lt;code&gt;/etc/shadow&lt;/code&gt; file.

&lt;b&gt;NOTE: &lt;/b&gt;The &lt;code&gt;/etc/group&lt;/code&gt; file is not modified to avoid removing a group that other users may also belong to. This isn't much of a big deal because you can edit the group file and remove the entry manually.

&lt;b&gt;Should you wish to remove the user's home directory as well&lt;/b&gt;, add the &lt;code&gt;-r&lt;/code&gt; option to the &lt;code&gt;userdel&lt;/code&gt; command.  EXAMPLE: &lt;code&gt;userdel -r &lt;i&gt;baduser&lt;/i&gt;&lt;/code&gt;


==Changing User's Passwords==
To change users password: &lt;code&gt;passwd &lt;i&gt;user&lt;/i&gt;&lt;/code&gt;

==Adding User to Group==
If you want to add your user to other groups in the &lt;code&gt;/etc/group&lt;/code&gt; file,
you can simply use the &lt;code&gt;gpasswd&lt;/code&gt; command like this: &lt;code&gt;gpasswd -a user group&lt;/code&gt;</text>
    <sha1>bb15faa84d503ceb2bc0f769fcb875e3166f938c</sha1>
  </revision>
</page>
<page arvcontinue="20090606212012|155">
  <title>User Limits</title>
  <ns>0</ns>
  <id>176</id>
  <revision>
    <id>204</id>
    <timestamp>2009-06-06T23:36:42Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1218" xml:space="preserve">[[Category:Tips]]

== CPU / Performance Limits ==

To set limits on users (e.g. CPU usage), use &lt;code&gt;ulimit&lt;/code&gt;.

EXAMPLE: &lt;code&gt;ulimit -t;&lt;/code&gt;

From the manpage:
&lt;code&gt;-a&lt;/code&gt; All current limits are reported&lt;br&gt;
&lt;code&gt;-c&lt;/code&gt; The maximum size of core files created&lt;br&gt;
&lt;code&gt;-d&lt;/code&gt; The maximum size of a process's data segment&lt;br&gt;
&lt;code&gt;-f&lt;/code&gt; The maximum size of files created by the shell&lt;br&gt;
&lt;code&gt;-i&lt;/code&gt; The maximum number of pending signals&lt;br&gt;
&lt;code&gt;-l&lt;/code&gt; The maximum size that may be locked into memory&lt;br&gt;
&lt;code&gt;-m&lt;/code&gt; The maximum resident set size&lt;br&gt;
&lt;code&gt;-n&lt;/code&gt; The maximum number of open file descriptors (most systems do not allow this value to be set)&lt;br&gt;
&lt;code&gt;-p&lt;/code&gt; The pipe size in 512-byte blocks (this may not be set)&lt;br&gt;
&lt;code&gt;-q&lt;/code&gt; The maximum number of bytes in POSIX message queues&lt;br&gt;
&lt;code&gt;-s&lt;/code&gt; The maximum stack size&lt;br&gt;
&lt;code&gt;-t&lt;/code&gt; The maximum amount of cpu time in seconds&lt;br&gt;
&lt;code&gt;-u&lt;/code&gt; The maximum number of processes available to a single user&lt;br&gt;
&lt;code&gt;-v&lt;/code&gt; The maximum amount of virtual memory available to the shell&lt;br&gt;
&lt;code&gt;-x&lt;/code&gt; The maximum number of file locks&lt;br&gt;


== Disk Space Limits ==

Use &lt;code&gt;quota&lt;/code&gt;.</text>
    <sha1>e89f1dd55c86ffae9e859b1031dd1455ae8efc43</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Utf-8 linux console</title>
  <ns>0</ns>
  <id>177</id>
  <revision>
    <id>205</id>
    <timestamp>2009-06-06T23:37:38Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old, had no category, placed in Tutorials</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4430" xml:space="preserve">[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two applications - '''unicode_start''' and '''unicode_stop''' - I think these are no longer required and only seem to mess up the screen if they are used together with the kernel parameter, but of course ymmv.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>262752dfe352b31d2ff4e84178fd83af07e8a3ae</sha1>
  </revision>
  <revision>
    <id>223</id>
    <parentid>205</parentid>
    <timestamp>2009-07-27T20:13:53Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Conclusion */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4388" xml:space="preserve">[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two applications - '''unicode_start''' and '''unicode_stop'''. Typing unicode_start &lt;font&gt; will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>ae4b4ef16c82f3186f9c74a9217830f4c35450d6</sha1>
  </revision>
  <revision>
    <id>224</id>
    <parentid>223</parentid>
    <timestamp>2009-07-27T20:14:35Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Conclusion */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4388" xml:space="preserve">[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two applications - '''unicode_start''' and '''unicode_stop'''. Typing unicode_start [font] will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>be79ca8359f41a05b6e25d21067fd639d4e915ed</sha1>
  </revision>
  <revision>
    <id>225</id>
    <parentid>224</parentid>
    <timestamp>2009-07-27T20:15:19Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Conclusion */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4389" xml:space="preserve">[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing unicode_start [font] will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>ca6061f8b31f789e2352af83cfad79bacbf456a7</sha1>
  </revision>
  <revision>
    <id>226</id>
    <parentid>225</parentid>
    <timestamp>2009-07-27T20:15:47Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Conclusion */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4395" xml:space="preserve">[[Category:Tutorials]]
== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>00db55b66cd228e43deb1f75067b54771e88ee39</sha1>
  </revision>
  <revision>
    <id>228</id>
    <parentid>226</parentid>
    <timestamp>2009-08-08T18:33:56Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Quick Look at Using UTF-8 in the Linux Console (without X) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4408" xml:space="preserve">[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://www.tony-franks.co.uk/UTF-8.htm]http://www.tony-franks.co.uk/UTF-8.htm

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>9db6ca8b3e73d9280e294a45f98e9396c442e0bd</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Vi</title>
  <ns>0</ns>
  <id>178</id>
  <revision>
    <id>206</id>
    <timestamp>2009-06-06T23:38:42Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5695" xml:space="preserve">Vi-like editors are a class of editors, some instance of which is on every *nix ever made. So learning to use a vi-like editor is a must! In Slackware, elvis is the default editor, but Slackware also provides a console-only and gui-enabled vim as well. The core command set is the same, though details may vary. (For instance, 'g' and 'gg' are vim commands but not nvi commands, but both recognize 'G' commands.) To find out what you'll be executing, try
 $ ls -l `which vi`

Then open the editor to an example file (as a user)

vi /etc/fstab

Now before we start you must realize that there are two modes. First
is a command mode where you type commands, move the cursor. The other
mode is the Insert Mode and this mode is where you type text. The
basic movement keys are: (sorry for the bad graphic below)


                                ^      
                                k 
                           &lt;h      l&gt;
                                j
                                v

Move around with the keys above and you will find out that you will
get used to it faster then you thought you would. Movement is the key
thing to learn in VI and there are a few things you might need to
know:

 $       Moves to end of the line
 0       Moves to the beginning of the line
 ^       Moves the the end of the white space in the line. 

The above are pretty easy to understand, but I want to explain the ^
key more. Say you have this line:

          Hello Sandman1 is nice

When you are on the line above and you press the ^, You will land on
the H. In VI you can also move forward on words as well:

 w   Goes to the next word including Punctuation
 W   Goes to the next word NOT including Punctuation
 b   Goes back a word including punctuation
 B   Goes back a word NOT including Punctuation

The above commands make your text editing go faster. To explain the no
punctuation look at the follow line:

Hello, My name is Sandman1.

Now imagine your cursor is on the H. If you press the w key you will
land on the comma, but if you press the W key it will land on the M in
My. Now say you are in the insert mode (you will learn how to later in
this tutorial) and you make a mistake? the c command is useful:

 cw  Change the next word
 cb  Change the word behind the cursor
 r   Change Character
 C   Change from the cursor to the end of the line
 c0  Change from the cursor to the beginning of the line
 c^  Change from the cursor to the white space at the begging of the line.

Now these are pretty self explanatory, but I want you to notice how we
used the other commands we learned already such as the B, $ , etc. You
can also use the capital B and the capital W and get the same effect.Now
say you want to erase things as well? We use the d key for that:

 dd  Delete current line
 dw  Delete word
 d$  Delete from the cursor to the end of the line
 d^  Delete from the cursor to the white space at the beginning of the line
 d0  Delete from the cursor to the beginning of the line

These are again pretty basic to understand. 

 i     Insert text before the cursor
 I     Insert text at the beginning of the line
 A     Insert text at the end of the line
 a     Insert text after the cursor
 o     Insert text on a NEW line below the current line
 O     Insert text on a NEW line above the current line

Now these are a lot of memorize, but I only usually use o, A and
i. Now say you are typing and you made a few mistakes the best way to
get rid of the mistakes are getting out of insert mode:

 ESC         &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt; IMPORTANT, learn how to get out of insert mode

Yes you actually press the escape key:). Now you can type the commands
you wish such as delete, or even change a word. Once you start using
VI you will learn these commands and you wont even have to think to do
the tasks. Now say you have an error in a config file and you want to
go to the line type this outside of vi:

 vi +100 /etc/apache/httpd.conf

This will open to line 100. To verify that you're on that line, type
C-g. You can also head to a different line by typing:

 :100
 100G
 G       Goes to the end of File (Special)
 1G      Goes to the beginning of the file (special)

The reason why I marked the 1G and the G special is because they are
REALLY useful and you shouldn't forget them. Since we have used a ctrl
key in here why not just show you how to move up and down a page:

 C-f    Forwards one page
 C-b    Goes back on page

Ok we have a general idea on how we make VI work, but we still don't
know how to close the damn thing. The following are the basic commands
to open and close VI:

 :w      Saves the current buffer to the file you opened with
 :e!     Reloads the current file not saving any changes
 :e      Loads a file
 :q      Quits 
 :wq     Quits and saves

Now the :w and the :e you can also put with a file, for instance:

 :e /etc/lilo.conf

This will open the file /etc/lilo.conf. If you opened a file, but also
had another file opened? Just press C-6 to switch. Now say you have
opened vi and don't want to save, but still quit? Just put a ! in the
command:

 :q!

The ! works with all the commands even :w. Another quick way to save
and exit is just type ZZ in the command mode. That will exit and
save. 

The next thing is out of place, but I think you should know it. Say
you want to move down 5 lines?

 5j

That will move down five lines and you can do this on a lot of
commands.For instance:

 5dj

The follow will erase 5 lines in the down direction! There are more
commands than just listed in this tutorial and perhaps I will write an
advanced tutorial for VI, But for now you know the basic VI. Good
luck:) This is by Sandman1 @ freenode
 
[[Category:Tutorials]]</text>
    <sha1>1fc515610d0305e6896699ee5ec552aae1a17193</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Wifi</title>
  <ns>0</ns>
  <id>179</id>
  <revision>
    <id>207</id>
    <timestamp>2009-06-06T23:39:20Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12239" xml:space="preserve">[[Category:Tutorials]]
Regarding wireless, I promised more info on getting wifi to work with linux. Here it is. I'm still utilizing the Linksys WPC11 wireless PCMCIA network card in Slackware. The methods I'm about to discuss work in Slackware v8.0 through v11 (I've not tested v12 yet, but there shouldn't be an issue). 9.0 and 9.1 seem to use orinoco drivers instead of prism drivers. I COULD fix this by installing prism drivers but the orinoco driver seem to work without problems (so far). When and if problems arise, I'll move to the prism drivers and update this page.

Note: this page goes through the manual steps of gaining internet activity.  I tend to use static IP configurations.  This means that the system won't rely on a DHCP server for connectivty, which is why I cover how to edit the routing table of your system.  Another reason I go through the manual process is so that the new user can know and understand the technical aspects of networking and the internals of Slackware (or any *nix-based system).

Now, my particular laptop accepts a CAT5 connection and will also run PCMCIA wifi (and also USB wifi adapters). I've usually relied upon the PCMCIA method of internet connectivity. Slackware 9.1 (and 9.0) accept PCMCIA cards via the Hotplug function now, which makes things very easy to set up. I usually just insert my wifi card into the PCMCIA slot and hear the computer 'beep'. Follow along by doing what I do. :o) 

After insertion of the card, type 'dmesg' in a shell and you should see something akin to the below:

 orinoco_lock() called with hw_unavailable (dev=ce66f800)
 hermes.c: 4 Dec 2002 David Gibson 
 orinoco.c 0.13d (David Gibson  and others)
 orinoco_cs.c 0.13d (David Gibson  and others)
 eth1: Station identity 001f:0005:0001:0003
 eth1: Looks like an Intersil firmware version 1.3.5
 eth1: Ad-hoc demo mode supported
 eth1: IEEE standard IBSS ad-hoc mode supported
 eth1: WEP supported, 104-bit key
 eth1: MAC address 00:06:25:A8:EA:50
 eth1: Station name "Prism  I"
 eth1: ready
 eth1: index 0x01: Vcc 5.0, irq 3, io 0x0100-0x013f
 eth1: New link status: Connected (0001)
 eth1: New link status: Disconnected (0002)
 eth1: New link status: Connected (0001)

This shows that the wifi card has been recognized and that a device name was assigned to it (eth1, in this case). To use the card, you have to know how you're going to use the card. Most people gain internet access via WAP (wireless access point) and this is what we'll do. I've not net experimented with adhoc (direct computer(s)-to-computer(s) connections) yet, but when I do, this page will be updated. 

A WAP's DHCP server may automatically assign your wifi card an IP.  If that is the case, you won't have much use for this tutorial, other than establishing encryption.  Please be aware that I cover establishing WEP encryption but not WPA/WPA2 (yet).  If you're using static IPs or to establish WEP encryption, continue to read the steps below.

Next, you'll want to assign a WAP for the card to access.  If you type 'iwconfig' (using 'sudo' or as the superuser), you'll see your wifi card's stats:

 ron@toshi:~$ sudo /usr/sbin/iwconfig
 lo        no wireless extensions.
 eth0      no wireless extensions.
 eth1      IEEE 802.11-DS  ESSID:""  Nickname:"Prism  I"
           Mode:Managed  Access Point: 00:00:00:00:00:00  Bit Rate:11Mb/s
           Tx-Power=15 dBm   Sensitivity:1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:0/92  Signal level:-68 dBm  Noise level:-122 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

As you can see, there's no ESSID and the MAC address for the card isn't showing. The wifi card needs to be set up to access the WAP:

 ron@toshi:~$ sudo /usr/sbin/iwconfig eth1 essid applejack
 ron@toshi:~$ sudo /usr/sbin/iwconfig
 lo        no wireless extensions.
 eth0      no wireless extensions.
 eth1      IEEE 802.11-DS  ESSID:"applejack"  Nickname:"Prism  I"
           Mode:Managed  Access Point: 00:00:00:00:00:00  Bit Rate:11Mb/s
           Tx-Power=15 dBm   Sensitivity:1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:0/92  Signal level:-68 dBm  Noise level:-122 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Now, you need to establish an interface. I'm using 'eth1' as an interface so I'd type: "ifconfig eth1 &lt;Static-IP-HERE&gt; up":

 ron@toshi:~# sudo /sbin/ifconfig eth1 10.150.1.171 up

 ron@toshi:~# sudo /sbin/ifconfig eth1
 eth1      Link encap:Ethernet  HWaddr 00:09:5B:05:8E:C7  
           inet addr:10.150.1.171  Bcast:10.255.255.255  Mask:255.0.0.0
           inet6 addr: fe80::209:5bff:fe05:8ec7/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000 
           RX bytes:0 (0.0 b)  TX bytes:468 (468.0 b)
           Interrupt:20 Base address:0xa000 

Next, run 'iwconfig':

 eth1      IEEE 802.11-DS  ESSID:"applejack"  Nickname:"Prism  I"
           Mode:Managed  Frequency:2.437GHz  Access Point: 00:07:23:78:95:80
           Bit Rate:2Mb/s   Tx-Power=15 dBm   Sensitivity:1/3
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:off
           Power Management:off
           Link Quality:90/92  Signal level:5/153  Noise level:117/153
           Rx invalid nwid:0  Rx invalid crypt:51  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

If you're not utilizing encryption on your WAP, then you should be set for online activity (provided your routing table is set up, if you're using static IPs...this is covered below). Some people use WEP/WPA (at the LEAST, use WEP), so we'll establish this now. You'll have to know what bit size your WAP is set to use but I normally use 128-bit. Type 'iwconfig eth1 key (your key here)'. Do this without the parentheses:

 iwconfig eth1 key xxxxxxxxxxxxxxxxxxxxxxxxxx

I've put the 'xxxx's there because there's no way in a hot day in Hell I'm going to share my encryption with the world. Replace the x's with your own key. To check the WEP status:

 root@toshi:~# iwconfig
 lo        no wireless extensions.
 eth0      no wireless extensions.
 eth1      IEEE 802.11-DS  ESSID:"applejack"  Nickname:"Prism  I"
           Mode:Managed  Frequency:2.437GHz  Access Point: 00:07:23:78:95:80
           Bit Rate:2Mb/s   Tx-Power=15 dBm   Sensitivity:1/3  
           Retry min limit:8   RTS thr:off   Fragment thr:off
           Encryption key:xxxxxxxxxxxxxxxxxxxxxxxxxx   Security mode:open
           Power Management:off
           Link Quality:88/92  Signal level:5/153  Noise level:117/153
           Rx invalid nwid:0  Rx invalid crypt:291  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

If you haven't set your interface IP yet, try this: 'ifconfig eth1 10.150.1.171'. Now you'll have to set your routing table up (if you're running two interfaces like I am):

 root@toshi:~#  route add -net 10.150.1.0 netmask 255.255.255.0 dev eth1
 root@toshi:~#  route add default gw 10.150.1.1 eth1
 root@toshi:~# route
 Kernel IP routing table
 Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
 10.150.1.0      *               255.255.255.0   U     0      0        0 eth1
 10.150.1.0      *               255.255.255.0   U     0      0        0 eth0
 10.0.0.0        *               255.0.0.0       U     0      0        0 eth1
 loopback        *               255.0.0.0       U     0      0        0 lo
 default         10.150.1.1      0.0.0.0         UG    0      0        0 eth1
 default         10.150.1.1      0.0.0.0         UG    1      0        0 eth0

Lastly, check to see that you can get outside of your local network:

 root@toshi:~# ping -I eth1 www.unixfool.com
 PING www.unixfool.com (216.0.115.49) from 10.150.1.171 eth1: 56(84) bytes of data.
 64 bytes from www.unixfool.com (216.0.115.49): icmp_seq=1 ttl=240 time=207 ms
 64 bytes from www.unixfool.com (216.0.115.49): icmp_seq=2 ttl=240 time=199 ms
 64 bytes from www.unixfool.com (216.0.115.49): icmp_seq=3 ttl=240 time=138 ms

 --- www.unixfool.com ping statistics ---
 3 packets transmitted, 3 received, 0% packet loss, time 2016ms
 rtt min/avg/max/mdev = 138.879/181.863/207.709/30.605 ms
 root@toshi:~#

I created a script that gets my wifi card online. Because I sometimes use both the wifi card and the integrated ethernet card simultaneously (as you can see in the about routing output), getting them both running is sometimes cumbersome. Usually, I will be online with one of the two interfaces and I'll decide I want to use them both. I'll post the script sometime soon.

You can also use 'ping www.unixfool.com' if you've no other interfaces to deal with.

Let me know if any of this is faulty and keep in mind that not every system's going to be set up as mine is, so you may still run into problems if you've modified your Slackware setup beyond a fresh install.

______


The below are instructions to get the D-Link DWL-650 (revision M) working with Linux.  I've added this because I had difficulty getting this card to work and because, when doing research, noticed that many others had issues with this card.

I bought a D-Link DWL-650 without doing extensive research on if it would work with Linux.  Since I dual-boot the Toshiba Satellite 1805-S274, I got it to work with Windows XP but not Slackware-current.  I tried using Linuxant's product but had little success at the time (early 2004).

Yesterday, I did extensive research on this card and its chipset.  I utilizes the Atmel chipset.  I'd tried using drivers from Atmel's page with little good results so I decided to try ndiswrapper.  Tonight, I can attest that ndiswrapper works with this card.  I'll document the process here:

I downloaded [http://sourceforge.net/projects/ndiswrapper/ ndiswrapper-0.11.tar.gz] and moved the file to /usr/local/src.  After moving the file, I ran:

 tar xvzf ndiswrapper-0.11.tar.gz
 cd ndiswrapper-0.11

As root, run:

 make install

After compilation, you'll need your Windows driver installed.  I got ndis5x-8180(173).zip from [http://www.opendrivers.com/categorycompany/1113/1358/RealTek.html opendrivers.com].  Unzip it using the unzip command:

 unzip ndis5x-8180(173).zip
 ndiswrapper -i &lt;/path/to/inffile.inf&gt;

Example:
 ndiswrapper -i /usr/local/src/ndis-drivers/net8180.inf

Running "ndiswrapper -l" shows the status of the installed driver.  In my case, this command shows:

 root@toshi:/usr/local/src/ndis-drivers# ndiswrapper -l
 Installed ndis drivers:
 net8180 driver present, hardware present

Next, load the module:

 modprobe ndiswrapper

Now we need to locate the wireless interface:

 iwconfig

You may need to set the IP of the interface (if you like using static IPs):

 ifconfig wlan0 10.150.1.170

I used "10.150.1.170", as I use the 10.150.0.0 netblock.  Use whatever IP is appropriate for your network.

Next, run all your "iwconfig" settings.  Mine is below:

 iwconfig wlan0 essid h@m mode auto enc xxxxxxxxxxxxxxxxxxxxx

I had to add routes to get my wifi card functional:

 route add -net 10.150.1.0 netmask 255.255.255.0 dev wlan0

 route add default gw 10.150.1.1 wlan0

This concludes my notes for utilizing the D-Link DWL-650, revision M wifi card.  Keep in mind that certain revisions use certain chipsets.  I couldn't use Prism-based drivers for my card since it uses the Atmel chipset.  I've yet to get Atmel's Linux drivers to work, but I may continue to try as a side project.

Let me know if you've comments to make this tutorial better.

''This tutorial is a [http://www.unixfool.com/toshiba_notes.html#wifi] mirror ''

''A wifi security perspective is [http://slackfiles.blogspot.com/2006/05/shell-scripting-creation-of-subnet-and.html here] ''

--[[User:Unixfool|Ron]] 00:46, 16 September 2007 (EDT)</text>
    <sha1>1ef92fa06230af4a5774672ff3aa58b71abe5866</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>ZSH</title>
  <ns>0</ns>
  <id>180</id>
  <revision>
    <id>208</id>
    <timestamp>2009-06-06T23:41:54Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Copy from old</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2427" xml:space="preserve">Zsh is one of the most powerfull shells you can get on the face of the planet, and is my favorate ([[Sandman1]]) 

Now its easier to show you the wonders of zsh with my config below, just copy this and rename it to /.zshrc: 


* Copy what is in the box below
 
 zstyle ':completion:*' completer _complete _correct _approximate 
 zstyle ':completion:*' max-errors 3 numeric 
 zstyle ':completion:*' prompt '&gt;' 
 zstyle :compinstall filename '/home/$USER/.zshrc' 
 autoload -U compinit 
 compinit 
 PS1=$'%{\e[01;32m%}%n@%m:%d%{\e[00m%}&gt; ' 
 autoload -U zfinit #This is for the built in ftp client 
 EMAIL_ADDR="Hi@hi.com" 
 HISTSIZE=50000 
 HISTFILE="$HOME/.zsh_history" 
 SAVEHIST=50000 
 setopt APPEND_HISTORY 
 setopt NO_BEEP 
 setopt CD_ABLE_VARS 
 setopt AUTO_CD 
 setopt CORRECT 
 setopt NO_HUP 
 bindkey "\e[1" beginning-of-line 
 bindkey "\e[H" beginning-of-line 
 bindkey "\e[2" transpose-words 
 bindkey "\e[3" delete-char 
 bindkey "\e[4" end-of-line 
 bindkey "\e[F" end-of-line 
 

Now you paste this into /.zshrc and restart ZSH. Now you should have a green prompt color:) Now first type: 

 removepkg &lt;tab&gt; 

With this you will recieve a list of packages you can remove, how cool (might need to be root). Another cool thing about zsh is that you can used the "vared" tool to edit variables, example: 
 
 vared PATH 

Now you can see the path variable and you can see that you can edit this and erase an error if you need to. Press enter when you are done editing it. Now speaking on variable editing, you can put variables into the buffer too: 

 print -z $PATH 

Another great feature that i use everyday is using M-q. (Alt-q basicly), For an example following the follow steps: 

type "Echo hi" (without quotes) 
type Alt-q 
type echo woot and press enter 
see that the old command was back on the buffer, so you can execute commands before (incase you forgot somthing) 

Now this is using my config, there is a tool to configure the auto completion stuff so you might want to run these: 

 autoload -U compinit &amp;&amp; compinit -U 
 compinstall 


Now you will have questions to answer about the different tab completion modes. 
 
Another cool Zsh thing is the tetris game that you can play! to get to tetris just follow these following steps: 

 autoload -U tetris 
 tetris 
hit the keys M-x and then type tetris and hit RET.


You can do quick math problems on the fly
 print $(( 2 + 2 ))

[[Category:Tutorials]]</text>
    <sha1>47b6e02f737dd65b1565439505e6505040afc0a3</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>209</id>
    <parentid>171</parentid>
    <timestamp>2009-06-06T23:44:47Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Manual copy of old wiki pages complete.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3294" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>3b4ac0ee8e991072c11078b6521a420f19f8fb73</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>User:Trashbird1240</title>
  <ns>2</ns>
  <id>181</id>
  <revision>
    <id>210</id>
    <timestamp>2009-06-08T13:37:15Z</timestamp>
    <contributor>
      <username>Trashbird1240</username>
      <id>18</id>
    </contributor>
    <minor/>
    <comment>user page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="219" xml:space="preserve">Hello Fellow Slackers,

I am a biology Ph.D. student at the University of North Carolina at Chapel Hill.  Being a Unix-nut, Slackware was the logical choice for me.  See my homepage [http://www.unc.edu/~adamsonj here] .</text>
    <sha1>322f3221ba700dd8e5e1a205f8e545a044dc96c8</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>EeePC</title>
  <ns>0</ns>
  <id>86</id>
  <revision>
    <id>211</id>
    <parentid>108</parentid>
    <timestamp>2009-06-09T10:50:54Z</timestamp>
    <contributor>
      <username>Chopp</username>
      <id>10</id>
    </contributor>
    <comment>/* Network */ changed driver patch url</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4870" xml:space="preserve">[[Category:Hardware]]
== Kernel ==
=== 2.6.24.4 ===
This is the default kernel that comes with Xandros. It is patched to work with a few things. It's ugly and some of the modules don't work correctly when the kernel is transplanted into Slackware.

The source is available from Asus.

=== 2.6.26.3 ===
As of writing, 2.6.26.3 is the latest stable kernel.

The acpi functionality has been merged into the kernel. but the ethernet and wireless require patching / external code to work

=== 2.6.27rc5 ===
As of writing this is still in testing.

The ethernet patch is now in-kernel, not requiring a patch.  The wireless still requires external code.

== 701 ==
===Wireless===
The 701 uses the Atheros chipset.  Use madwifi-hal-0.10.5.6.

*http://madwifi.org/ticket/1192
*http://wiki.eeeuser.com/ubuntu?s=madwifi#wireless_internet_using_native_madwifi_drivers

== 901 ==
===Network===
The network card uses the atl1e module, which requires a patch for the 2.6.26.3 kernel.  as of writing it is slated to be merged into the 2.6.27 kernel.

http://www.rootshell.be/~nix4me/EeePC/0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch

&lt;pre&gt;cd /usr/src/linux-2.6.26.3/
patch -p1 &lt; 0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch&lt;/pre&gt;

The following instructions have been tested (and work) on a fresh installation of Slackware 12.1 on the EEE 901 running the generic kernel 2.26.24-5-smp:

http://www.patch-village.com/2008/oct/23/installing-ubuntu-804-server-asus-p5q/

The kernel source code was installed from the second installation disk (in directory 'k').

===Wireless===
The wireless uses the rt2860sta module, an open source module from ralink.com. The source code can be downloaded from here:

http://www.ralinktech.com/ralink/Home/Support/Linux.html

Compiling is straightforward in Slackware 12.1  (see instructions below).    It does however require patching to work with the 2.6.26.3 kernel.

http://chopp.homelinux.com/EeePC/rt2860sta-patched.tar.gz

There are some patches which need to be applied to this source both to get it to work, and to modify the code to the 2.6.26 way of using network devices, namely dev_nd-&gt;net is now dev_net(dev).

The source above has the patches applied and the code fixed to work with 2.6.26.3

It should work with WPA, but I haven't tested it.

&lt;pre&gt;
tar -xzf rt2860sta-patched.tar.gz
cd 2008_0708_RT2860_Linux_STA_v1.7.0.0
make
make install
modprobe rt2860sta
&lt;/pre&gt;

===Sound===
Front Mic does not work out of the box with Slackware 12.1.  Compiling Alsa driver 1.0.18 solves this problem.  However, doing this seems to remove the USB sound driver (copying back snd-usb-audio.ko resolves it).  Be warned that other sound modules are missing after this procedure.    This is a useful link:

http://wiki.debian.org/DebianEeePC/HowTo/Sound

===ACPI===
The acpi extras require the eeepc_laptop module, kernel config is CONFIG_EEEPC_LAPTOP.
In make menuconfig, it is under device drivers -&gt; misc devices, near the bottom.

You need to configure /etc/acpi to make acpi act on events. By default nothing happens.

/etc/acpi/events/hotkey
&lt;pre&gt;
event=hotkey ATKD .*
action=/etc/acpi/hotkey.sh %e
&lt;/pre&gt;
/etc/acpi/hotkey.sh
&lt;pre&gt;
#!/bin/sh

case $3 in
    #Fn+F2
        #Wireless/Bluetooth button
    #Fn+F7
    00000013)
        #Mute button
        amixer set Master toggle
    ;;
    #Fn+F8
    00000014)
        #Volume Down
        amixer set Master 10%-
    ;;
    #Fn+F9
    00000015)
        #Volume Up
        amixer set Master 10%+
    ;;
esac
&lt;/pre&gt;

===Camera===
The camera uses uvcvideo module:
http://www.slackware.com/~alien/slackbuilds/linux-uvc/
{| border="1"
|-
! module
! used by
|-
| uvcvideo
|
|-
| compat_ioctl32
| uvcvideo
|-
| videodev
| uvcvideo
|-
| v4l1_compat
| uvcvideo,videodev
|-
| usbcore
| uvcvideo
|}

===X===
Slack 12.1 uses the same xorg version as the xandros that comes with the 901 linux eee currently.

====xorg.conf====
For the 901, for basic functionality, no configuration of X is required (no xorg.conf).  The intel video driver from the 'x' directory of disc 1 is needed.

This xorg.conf is a copy of the xandros one with a few changes.  It allows you to scroll using two fingers and dragging, and middle click by tapping with two fingers.

[[EeePC/xorg.conf|xorg.conf]]

====Touchpad====
http://rlworkman.net/pkgs/
Grab the xf86-input-synaptics package.

Need synaptics for the touchpad.

====Battery Display====
gkrellm is a nice little program that can be made to show battery life. It comes with slack 12.1

====Wireless Configuration====
Wicd works nicely to make connecting to wireless networks easy.

http://rlworkman.net/pkgs/
Grab the Wicd package.

==Files==
*http://chopp.homelinux.com/EeePC/
*http://www.ksandro.info/
*http://www.ksandro.info/rt2860sta-patched.tar.gz
*http://www.ksandro.info/0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch
*http://rlworkman.net/pkgs/</text>
    <sha1>6fdb65891bea45b8a84fc3ccc1aa28642489eb9f</sha1>
  </revision>
  <revision>
    <id>212</id>
    <parentid>211</parentid>
    <timestamp>2009-06-09T10:53:30Z</timestamp>
    <contributor>
      <username>Chopp</username>
      <id>10</id>
    </contributor>
    <comment>/* Wireless */ changed patched driver url</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4875" xml:space="preserve">[[Category:Hardware]]
== Kernel ==
=== 2.6.24.4 ===
This is the default kernel that comes with Xandros. It is patched to work with a few things. It's ugly and some of the modules don't work correctly when the kernel is transplanted into Slackware.

The source is available from Asus.

=== 2.6.26.3 ===
As of writing, 2.6.26.3 is the latest stable kernel.

The acpi functionality has been merged into the kernel. but the ethernet and wireless require patching / external code to work

=== 2.6.27rc5 ===
As of writing this is still in testing.

The ethernet patch is now in-kernel, not requiring a patch.  The wireless still requires external code.

== 701 ==
===Wireless===
The 701 uses the Atheros chipset.  Use madwifi-hal-0.10.5.6.

*http://madwifi.org/ticket/1192
*http://wiki.eeeuser.com/ubuntu?s=madwifi#wireless_internet_using_native_madwifi_drivers

== 901 ==
===Network===
The network card uses the atl1e module, which requires a patch for the 2.6.26.3 kernel.  as of writing it is slated to be merged into the 2.6.27 kernel.

http://www.rootshell.be/~nix4me/EeePC/0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch

&lt;pre&gt;cd /usr/src/linux-2.6.26.3/
patch -p1 &lt; 0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch&lt;/pre&gt;

The following instructions have been tested (and work) on a fresh installation of Slackware 12.1 on the EEE 901 running the generic kernel 2.26.24-5-smp:

http://www.patch-village.com/2008/oct/23/installing-ubuntu-804-server-asus-p5q/

The kernel source code was installed from the second installation disk (in directory 'k').

===Wireless===
The wireless uses the rt2860sta module, an open source module from ralink.com. The source code can be downloaded from here:

http://www.ralinktech.com/ralink/Home/Support/Linux.html

Compiling is straightforward in Slackware 12.1  (see instructions below).    It does however require patching to work with the 2.6.26.3 kernel.

http://www.rootshell.be/~nix4me/EeePC/rt2860sta-patched.tar.gz

There are some patches which need to be applied to this source both to get it to work, and to modify the code to the 2.6.26 way of using network devices, namely dev_nd-&gt;net is now dev_net(dev).

The source above has the patches applied and the code fixed to work with 2.6.26.3

It should work with WPA, but I haven't tested it.

&lt;pre&gt;
tar -xzf rt2860sta-patched.tar.gz
cd 2008_0708_RT2860_Linux_STA_v1.7.0.0
make
make install
modprobe rt2860sta
&lt;/pre&gt;

===Sound===
Front Mic does not work out of the box with Slackware 12.1.  Compiling Alsa driver 1.0.18 solves this problem.  However, doing this seems to remove the USB sound driver (copying back snd-usb-audio.ko resolves it).  Be warned that other sound modules are missing after this procedure.    This is a useful link:

http://wiki.debian.org/DebianEeePC/HowTo/Sound

===ACPI===
The acpi extras require the eeepc_laptop module, kernel config is CONFIG_EEEPC_LAPTOP.
In make menuconfig, it is under device drivers -&gt; misc devices, near the bottom.

You need to configure /etc/acpi to make acpi act on events. By default nothing happens.

/etc/acpi/events/hotkey
&lt;pre&gt;
event=hotkey ATKD .*
action=/etc/acpi/hotkey.sh %e
&lt;/pre&gt;
/etc/acpi/hotkey.sh
&lt;pre&gt;
#!/bin/sh

case $3 in
    #Fn+F2
        #Wireless/Bluetooth button
    #Fn+F7
    00000013)
        #Mute button
        amixer set Master toggle
    ;;
    #Fn+F8
    00000014)
        #Volume Down
        amixer set Master 10%-
    ;;
    #Fn+F9
    00000015)
        #Volume Up
        amixer set Master 10%+
    ;;
esac
&lt;/pre&gt;

===Camera===
The camera uses uvcvideo module:
http://www.slackware.com/~alien/slackbuilds/linux-uvc/
{| border="1"
|-
! module
! used by
|-
| uvcvideo
|
|-
| compat_ioctl32
| uvcvideo
|-
| videodev
| uvcvideo
|-
| v4l1_compat
| uvcvideo,videodev
|-
| usbcore
| uvcvideo
|}

===X===
Slack 12.1 uses the same xorg version as the xandros that comes with the 901 linux eee currently.

====xorg.conf====
For the 901, for basic functionality, no configuration of X is required (no xorg.conf).  The intel video driver from the 'x' directory of disc 1 is needed.

This xorg.conf is a copy of the xandros one with a few changes.  It allows you to scroll using two fingers and dragging, and middle click by tapping with two fingers.

[[EeePC/xorg.conf|xorg.conf]]

====Touchpad====
http://rlworkman.net/pkgs/
Grab the xf86-input-synaptics package.

Need synaptics for the touchpad.

====Battery Display====
gkrellm is a nice little program that can be made to show battery life. It comes with slack 12.1

====Wireless Configuration====
Wicd works nicely to make connecting to wireless networks easy.

http://rlworkman.net/pkgs/
Grab the Wicd package.

==Files==
*http://chopp.homelinux.com/EeePC/
*http://www.ksandro.info/
*http://www.ksandro.info/rt2860sta-patched.tar.gz
*http://www.ksandro.info/0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch
*http://rlworkman.net/pkgs/</text>
    <sha1>b07de0c1ef10c3b5c55e936b6215aea33c7ef54b</sha1>
  </revision>
  <revision>
    <id>213</id>
    <parentid>212</parentid>
    <timestamp>2009-06-09T11:32:52Z</timestamp>
    <contributor>
      <username>Chopp</username>
      <id>10</id>
    </contributor>
    <comment>/* Files */ updated a Files url</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4880" xml:space="preserve">[[Category:Hardware]]
== Kernel ==
=== 2.6.24.4 ===
This is the default kernel that comes with Xandros. It is patched to work with a few things. It's ugly and some of the modules don't work correctly when the kernel is transplanted into Slackware.

The source is available from Asus.

=== 2.6.26.3 ===
As of writing, 2.6.26.3 is the latest stable kernel.

The acpi functionality has been merged into the kernel. but the ethernet and wireless require patching / external code to work

=== 2.6.27rc5 ===
As of writing this is still in testing.

The ethernet patch is now in-kernel, not requiring a patch.  The wireless still requires external code.

== 701 ==
===Wireless===
The 701 uses the Atheros chipset.  Use madwifi-hal-0.10.5.6.

*http://madwifi.org/ticket/1192
*http://wiki.eeeuser.com/ubuntu?s=madwifi#wireless_internet_using_native_madwifi_drivers

== 901 ==
===Network===
The network card uses the atl1e module, which requires a patch for the 2.6.26.3 kernel.  as of writing it is slated to be merged into the 2.6.27 kernel.

http://www.rootshell.be/~nix4me/EeePC/0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch

&lt;pre&gt;cd /usr/src/linux-2.6.26.3/
patch -p1 &lt; 0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch&lt;/pre&gt;

The following instructions have been tested (and work) on a fresh installation of Slackware 12.1 on the EEE 901 running the generic kernel 2.26.24-5-smp:

http://www.patch-village.com/2008/oct/23/installing-ubuntu-804-server-asus-p5q/

The kernel source code was installed from the second installation disk (in directory 'k').

===Wireless===
The wireless uses the rt2860sta module, an open source module from ralink.com. The source code can be downloaded from here:

http://www.ralinktech.com/ralink/Home/Support/Linux.html

Compiling is straightforward in Slackware 12.1  (see instructions below).    It does however require patching to work with the 2.6.26.3 kernel.

http://www.rootshell.be/~nix4me/EeePC/rt2860sta-patched.tar.gz

There are some patches which need to be applied to this source both to get it to work, and to modify the code to the 2.6.26 way of using network devices, namely dev_nd-&gt;net is now dev_net(dev).

The source above has the patches applied and the code fixed to work with 2.6.26.3

It should work with WPA, but I haven't tested it.

&lt;pre&gt;
tar -xzf rt2860sta-patched.tar.gz
cd 2008_0708_RT2860_Linux_STA_v1.7.0.0
make
make install
modprobe rt2860sta
&lt;/pre&gt;

===Sound===
Front Mic does not work out of the box with Slackware 12.1.  Compiling Alsa driver 1.0.18 solves this problem.  However, doing this seems to remove the USB sound driver (copying back snd-usb-audio.ko resolves it).  Be warned that other sound modules are missing after this procedure.    This is a useful link:

http://wiki.debian.org/DebianEeePC/HowTo/Sound

===ACPI===
The acpi extras require the eeepc_laptop module, kernel config is CONFIG_EEEPC_LAPTOP.
In make menuconfig, it is under device drivers -&gt; misc devices, near the bottom.

You need to configure /etc/acpi to make acpi act on events. By default nothing happens.

/etc/acpi/events/hotkey
&lt;pre&gt;
event=hotkey ATKD .*
action=/etc/acpi/hotkey.sh %e
&lt;/pre&gt;
/etc/acpi/hotkey.sh
&lt;pre&gt;
#!/bin/sh

case $3 in
    #Fn+F2
        #Wireless/Bluetooth button
    #Fn+F7
    00000013)
        #Mute button
        amixer set Master toggle
    ;;
    #Fn+F8
    00000014)
        #Volume Down
        amixer set Master 10%-
    ;;
    #Fn+F9
    00000015)
        #Volume Up
        amixer set Master 10%+
    ;;
esac
&lt;/pre&gt;

===Camera===
The camera uses uvcvideo module:
http://www.slackware.com/~alien/slackbuilds/linux-uvc/
{| border="1"
|-
! module
! used by
|-
| uvcvideo
|
|-
| compat_ioctl32
| uvcvideo
|-
| videodev
| uvcvideo
|-
| v4l1_compat
| uvcvideo,videodev
|-
| usbcore
| uvcvideo
|}

===X===
Slack 12.1 uses the same xorg version as the xandros that comes with the 901 linux eee currently.

====xorg.conf====
For the 901, for basic functionality, no configuration of X is required (no xorg.conf).  The intel video driver from the 'x' directory of disc 1 is needed.

This xorg.conf is a copy of the xandros one with a few changes.  It allows you to scroll using two fingers and dragging, and middle click by tapping with two fingers.

[[EeePC/xorg.conf|xorg.conf]]

====Touchpad====
http://rlworkman.net/pkgs/
Grab the xf86-input-synaptics package.

Need synaptics for the touchpad.

====Battery Display====
gkrellm is a nice little program that can be made to show battery life. It comes with slack 12.1

====Wireless Configuration====
Wicd works nicely to make connecting to wireless networks easy.

http://rlworkman.net/pkgs/
Grab the Wicd package.

==Files==
*http://www.rootshell.be/~nix4me/EeePC/
*http://www.ksandro.info/
*http://www.ksandro.info/rt2860sta-patched.tar.gz
*http://www.ksandro.info/0001-atl1e-Atheros-L1E-Gigabit-Ethernet-driver.patch
*http://rlworkman.net/pkgs/</text>
    <sha1>2dc1da276434c2b64303667a57e715dece3ad7aa</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Forced Fsck</title>
  <ns>0</ns>
  <id>92</id>
  <revision>
    <id>214</id>
    <parentid>114</parentid>
    <timestamp>2009-06-23T20:29:14Z</timestamp>
    <contributor>
      <username>RobRistroph</username>
      <id>23</id>
    </contributor>
    <comment>/* Bypassing A Hung Forced Fsck */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3071" xml:space="preserve">[[Category:Tips]]

A Forced Fsck (forced file check) happens on boot up due to one of three things:

:1) The system was not cleanly shutdown previously (you just turned off the power) and the file system was not cleanly un-mounted.

:2) The maximum number of sucessive re-boots (re-mounts ([[Mount Count|mount count]])) between fsck checks has been reached (you have reached [[Maximum Mount Count]]).

:3) A period of time has passed between fscks that exceed the filesystem's last checked criteria.

==Manually Forcing a Forced Fsck==

To force a check on the next boot, simply create the file '/etc/forcefsck' and reboot:
:&lt;code&gt;touch /etc/forcefsck&lt;/code&gt;


==Bypassing A Forced Fsck==

&lt;b&gt;METHOD 1: Increase the Mount Count/Last-checked time span-&lt;/b&gt;&lt;br&gt;
The only way to bypass a Forced Fsck is to boot the machine from another boot medium (e.g. a boot CD) and use &lt;code&gt;tune2fs&lt;/code&gt; to increase the Maximum Mount Count or the Last-checked Time span.

To increase the Maximum Mount Count: &lt;code&gt;tune2fs -c &lt;i&gt;new_mount_count filesystem&lt;/i&gt;&lt;/code&gt;&lt;br&gt;
EXAMPLE: &lt;code&gt;tune2fs -c 50 /dev/hda1&lt;/code&gt; - This will cause a fsck after 50 re-mounts.

To increase the Last-checked Time span: &lt;code&gt;tune2fs -i &lt;i&gt;new_time_span filesystem&lt;/i&gt;&lt;/code&gt;&lt;br&gt;
EXAMPLE: &lt;code&gt;tune2fs -i 3m /dev/hda1&lt;/code&gt; - This will cause a fsck after 3 months.

&lt;b&gt;GOTCHA:&lt;/b&gt; If you are running a RAID Array, make sure you load a kernel image that supports RAID when booting! See the RAID Array tips.


&lt;b&gt;METHOD 2: Manually run fsck-&lt;/b&gt;&lt;br&gt;
See &lt;i&gt;Bypassing A Hung Forced Fsck&lt;/i&gt; instructions below.


==Bypassing A Hung Forced Fsck==
Sometimes, a forced fsck will occur and may not complete.  It may hang or just keep starting over.  To (down and dirty) fix this, boot the machine from a bootable disk (3.5" or CD), DO NOT mount the unchecked filesystem and manually run fsck.  You may have to run any one of three modes to complete the check:&lt;br&gt;
::&lt;code&gt;fsck -f &lt;i&gt;filesystem&lt;/i&gt;&lt;/code&gt; - Force checking even if the file system seems clean.&lt;br&gt;
::&lt;code&gt;fsck -c &lt;i&gt;filesystem&lt;/i&gt;&lt;/code&gt; - This option causes e2fsck to run the badblocks program to find any blocks which are bad on the filesystem, and then marks them as bad by adding them to the bad block inode. If this option is specified twice, then the bad block scan will be done using a non-destructive read-write test.  Be aware that this takes a long time, such as days on large disk with the the double -c set, but it does tend to fix problematic disks when it does complete.&lt;br&gt;
::&lt;code&gt;fsck -p &lt;i&gt;filesystem&lt;/i&gt;&lt;/code&gt; - Automatically repair ("preen") the file system without any questions.&lt;br&gt;
:::&lt;b&gt;NOTE: &lt;code&gt;&lt;i&gt;filesystem&lt;/i&gt;&lt;/code&gt; = boot partition (e.g. &lt;code&gt;/dev/hda1&lt;/code&gt;)&lt;/b&gt;

&lt;b&gt;GOTCHA:&lt;/b&gt; If you are running a RAID Array, make sure you load a kernel image that supports RAID when booting! See the [[RAID_Array_%28Hardware%29|RAID Array tips]].

After a successful completion of anyone of the above, your filesystem's [[Mount Count|mount count]] will be reset to zero and you should be able to boot normally again.</text>
    <sha1>d675eb21f50bc6b4a7061585ea369d88f51e5c77</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Zip 2GB Limit</title>
  <ns>0</ns>
  <id>182</id>
  <revision>
    <id>215</id>
    <timestamp>2009-06-23T21:55:02Z</timestamp>
    <contributor>
      <username>RobRistroph</username>
      <id>23</id>
    </contributor>
    <comment>Created page with '[[Catagory:Tips]]  On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB.  This applies to the file that is created  ...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2743" xml:space="preserve">[[Catagory:Tips]]

On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB.  This applies to the file that is created  being 2 GB, the .zip compressed file might be less than 2 GB.  When the unzip command attempts to create the greater than 2 GB file, it makes the file up until it is 2 GB, and then produces this error message (PROP_ENT.TXT is the file that is bigger than 2 GB in this case) :

&lt;pre&gt;
PROP_ENT.TXT:  write error (disk full?).  Continue? (y/n/^C) y
&lt;/pre&gt;

This procedure will update the unzip command to fix this.  It may also fix problems in creating a .zip file that is bigger than 2 GB, but I have not been able to test that.

With these commands I retrieved the source package and unpacked the source trees:

&lt;pre&gt;
mkdir infozip
cd infozip
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/infozip.SlackBuild
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/slack-desc
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/unzip552.tar.bz2
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/zip232.tar.bz2
tar xjvf unzip552.tar.bz2
tar xjvf zip232.tar.bz2
&lt;/pre&gt;

I next modified the Makefiles in the two source trees to use the flags "-DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" as described here: http://www.info-zip.org/FAQ.html#limits

To do that, I edited the file unzip-5.52/unix/Makefile and changed line 50 from "CF = -O -I. -DUNIX $(LOC)" to "CF = -O -I. -DUNIX $(LOC) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64".  I then editted zip-2.32/unix/Makefile and changed line 49 from "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP)" to "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" .  The second Makefile edit might not be necessary, it should fix any problems you are having with the "zip" command (the first Makefile fixes problems with the "unzip" command).

After editing those files, I re-tarred up the directories with the now fixed Makefiles, and then removed the source trees:

&lt;pre&gt;
tar cjvf unzip552.tar.bz2 unzip-5.52/ 
tar cjvf zip232.tar.bz2 zip-2.32/
rm -rf unzip-5.52/ zip-2.32/
&lt;/pre&gt;

I then ran the SlackBuild to make the package:

&lt;pre&gt;
chmod a+x infozip.SlackBuild
./infozip.SlackBuild
&lt;/pre&gt;

At this point the slackware package will be in /tmp/infozip-5.52-i486-2.tgz.  You might wish to copy it somewhere if you are going to install it on a number of computers or save it.  You can install it with "installpkg /tmp/infozip-5.52-i486-2.tgz" like a normal package.

If someone knows this is fixed in recent SlackWare versions, or has uploaded a precompiled package somewhere, please update this wiki.</text>
    <sha1>51fe8089e0d0faa71cc35fb7aa6877e4bd105fe7</sha1>
  </revision>
  <revision>
    <id>216</id>
    <parentid>215</parentid>
    <timestamp>2009-06-23T21:57:08Z</timestamp>
    <contributor>
      <username>RobRistroph</username>
      <id>23</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2790" xml:space="preserve">[[Catagory:Tips]]

== Fixing the 2GB file size limit in unzip ==

On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB.  This applies to the file that is created  being 2 GB, the .zip compressed file might be less than 2 GB.  When the unzip command attempts to create the greater than 2 GB file, it makes the file up until it is 2 GB, and then produces this error message (PROP_ENT.TXT is the file that is bigger than 2 GB in this case) :

&lt;pre&gt;
PROP_ENT.TXT:  write error (disk full?).  Continue? (y/n/^C) y
&lt;/pre&gt;

This procedure will update the unzip command to fix this.  It may also fix problems in creating a .zip file that is bigger than 2 GB, but I have not been able to test that.

With these commands I retrieved the source package and unpacked the source trees:

&lt;pre&gt;
mkdir infozip
cd infozip
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/infozip.SlackBuild
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/slack-desc
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/unzip552.tar.bz2
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/zip232.tar.bz2
tar xjvf unzip552.tar.bz2
tar xjvf zip232.tar.bz2
&lt;/pre&gt;

I next modified the Makefiles in the two source trees to use the flags "-DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" as described here: http://www.info-zip.org/FAQ.html#limits

To do that, I edited the file unzip-5.52/unix/Makefile and changed line 50 from "CF = -O -I. -DUNIX $(LOC)" to "CF = -O -I. -DUNIX $(LOC) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64".  I then editted zip-2.32/unix/Makefile and changed line 49 from "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP)" to "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" .  The second Makefile edit might not be necessary, it should fix any problems you are having with the "zip" command (the first Makefile fixes problems with the "unzip" command).

After editing those files, I re-tarred up the directories with the now fixed Makefiles, and then removed the source trees:

&lt;pre&gt;
tar cjvf unzip552.tar.bz2 unzip-5.52/ 
tar cjvf zip232.tar.bz2 zip-2.32/
rm -rf unzip-5.52/ zip-2.32/
&lt;/pre&gt;

I then ran the SlackBuild to make the package:

&lt;pre&gt;
chmod a+x infozip.SlackBuild
./infozip.SlackBuild
&lt;/pre&gt;

At this point the slackware package will be in /tmp/infozip-5.52-i486-2.tgz.  You might wish to copy it somewhere if you are going to install it on a number of computers or save it.  You can install it with "installpkg /tmp/infozip-5.52-i486-2.tgz" like a normal package.

If someone knows this is fixed in recent SlackWare versions, or has uploaded a precompiled package somewhere, please update this wiki.</text>
    <sha1>82e611ee0851b8c6d2d8be6d4aaafd52b178e35b</sha1>
  </revision>
  <revision>
    <id>217</id>
    <parentid>216</parentid>
    <timestamp>2009-06-24T05:37:35Z</timestamp>
    <contributor>
      <username>RobRistroph</username>
      <id>23</id>
    </contributor>
    <comment>/* Fixing the 2GB file size limit in unzip */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2849" xml:space="preserve">[[Catagory:Tips]]

== Fixing the 2GB file size limit in unzip ==

On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB.  This applies to the file that is created  being 2 GB, the .zip compressed file might be less than 2 GB.  When the unzip command attempts to create the greater than 2 GB file, it makes the file up until it is 2 GB, and then produces this error message (PROP_ENT.TXT is the file that is bigger than 2 GB in this case) :

&lt;pre&gt;
PROP_ENT.TXT:  write error (disk full?).  Continue? (y/n/^C) y
&lt;/pre&gt;

This procedure will update the unzip command to fix this.  It may also fix problems in creating a .zip file that is bigger than 2 GB, but I have not been able to test that.

With these commands I retrieved the source package and unpacked the source trees:

&lt;pre&gt;
mkdir infozip
cd infozip
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/infozip.SlackBuild
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/slack-desc
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/unzip552.tar.bz2
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/zip232.tar.bz2
tar xjvf unzip552.tar.bz2
tar xjvf zip232.tar.bz2
&lt;/pre&gt;

I next modified the Makefiles in the two source trees to use the flags "-DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" as described here: http://www.info-zip.org/FAQ.html#limits

To do that, I edited the file unzip-5.52/unix/Makefile and changed line 776 from "&lt;nowiki&gt;CF="-O3 -Wall -I. -DASM_CRC $(LOC)"&lt;/nowiki&gt;" to "&lt;nowiki&gt;CF="-O3 -Wall -I. -DASM_CRC $(LOC) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"&lt;/nowiki&gt;".  

I then editted zip-2.32/unix/Makefile and changed line 49 from "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP)" to "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" .  

The second Makefile edit might not be necessary, it should fix any problems you are having with the "zip" command (the first Makefile fixes problems with the "unzip" command).

After editing those files, I re-tarred up the directories with the now fixed Makefiles, and then removed the source trees:

&lt;pre&gt;
tar cjvf unzip552.tar.bz2 unzip-5.52/ 
tar cjvf zip232.tar.bz2 zip-2.32/
rm -rf unzip-5.52/ zip-2.32/
&lt;/pre&gt;

I then ran the SlackBuild to make the package:

&lt;pre&gt;
chmod a+x infozip.SlackBuild
./infozip.SlackBuild
&lt;/pre&gt;

At this point the slackware package will be in /tmp/infozip-5.52-i486-2.tgz.  You might wish to copy it somewhere if you are going to install it on a number of computers or save it.  You can install it with "installpkg /tmp/infozip-5.52-i486-2.tgz" like a normal package.

If someone knows this is fixed in recent SlackWare versions, or has uploaded a precompiled package somewhere, please update this wiki.</text>
    <sha1>ac065e580cdb4d0f72e8c9bfa6a133161530c47b</sha1>
  </revision>
  <revision>
    <id>218</id>
    <parentid>217</parentid>
    <timestamp>2009-06-24T05:39:32Z</timestamp>
    <contributor>
      <username>RobRistroph</username>
      <id>23</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2849" xml:space="preserve">[[Category:Tips]]

== Fixing the 2GB file size limit in unzip ==

On some SlackWare versions, up to at least 12.0, the "unzip" command cannot unpack a file that is bigger than 2 GB.  This applies to the file that is created  being 2 GB, the .zip compressed file might be less than 2 GB.  When the unzip command attempts to create the greater than 2 GB file, it makes the file up until it is 2 GB, and then produces this error message (PROP_ENT.TXT is the file that is bigger than 2 GB in this case) :

&lt;pre&gt;
PROP_ENT.TXT:  write error (disk full?).  Continue? (y/n/^C) y
&lt;/pre&gt;

This procedure will update the unzip command to fix this.  It may also fix problems in creating a .zip file that is bigger than 2 GB, but I have not been able to test that.

With these commands I retrieved the source package and unpacked the source trees:

&lt;pre&gt;
mkdir infozip
cd infozip
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/infozip.SlackBuild
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/slack-desc
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/unzip552.tar.bz2
wget ftp://slackware.cs.utah.edu/pub/slackware/slackware-12.0/source/a/infozip/zip232.tar.bz2
tar xjvf unzip552.tar.bz2
tar xjvf zip232.tar.bz2
&lt;/pre&gt;

I next modified the Makefiles in the two source trees to use the flags "-DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" as described here: http://www.info-zip.org/FAQ.html#limits

To do that, I edited the file unzip-5.52/unix/Makefile and changed line 776 from "&lt;nowiki&gt;CF="-O3 -Wall -I. -DASM_CRC $(LOC)"&lt;/nowiki&gt;" to "&lt;nowiki&gt;CF="-O3 -Wall -I. -DASM_CRC $(LOC) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64"&lt;/nowiki&gt;".  

I then editted zip-2.32/unix/Makefile and changed line 49 from "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP)" to "CFLAGS_NOOPT = -I. -DUNIX $(LOCAL_ZIP) -DLARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" .  

The second Makefile edit might not be necessary, it should fix any problems you are having with the "zip" command (the first Makefile fixes problems with the "unzip" command).

After editing those files, I re-tarred up the directories with the now fixed Makefiles, and then removed the source trees:

&lt;pre&gt;
tar cjvf unzip552.tar.bz2 unzip-5.52/ 
tar cjvf zip232.tar.bz2 zip-2.32/
rm -rf unzip-5.52/ zip-2.32/
&lt;/pre&gt;

I then ran the SlackBuild to make the package:

&lt;pre&gt;
chmod a+x infozip.SlackBuild
./infozip.SlackBuild
&lt;/pre&gt;

At this point the slackware package will be in /tmp/infozip-5.52-i486-2.tgz.  You might wish to copy it somewhere if you are going to install it on a number of computers or save it.  You can install it with "installpkg /tmp/infozip-5.52-i486-2.tgz" like a normal package.

If someone knows this is fixed in recent SlackWare versions, or has uploaded a precompiled package somewhere, please update this wiki.</text>
    <sha1>ed4ca597fd364e6f681c977e7794f636710e499b</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Dependency Discovery</title>
  <ns>0</ns>
  <id>183</id>
  <revision>
    <id>219</id>
    <timestamp>2009-07-08T13:12:27Z</timestamp>
    <contributor>
      <username>Gabim</username>
      <id>27</id>
    </contributor>
    <comment>Created page with '[[Category:Information]] [[Category:Tutorials]]   == Introduction ==  "Slackware users typically prefer their method of manual dependency resolution, citing the level of system c...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5054" xml:space="preserve">[[Category:Information]]
[[Category:Tutorials]]


== Introduction ==

"Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them." - as the [http://wiki.archlinux.org/index.php/Arch_Compared_To_Other_Distros#Arch_vs_Slackware ArchWiki] says. This total control over the system is one of the main strength of the Slackware distribution.

If the administrator of the system knows every package on the system and ensures their every dependencies, then the system is stable, well usable. If the administrator installs a new, (until now) unknown application, then he/she needs to discover its dependencies via the attached README or documentations, or from starting the application (if something is not installed on the system, then the application won't start).

== Dependency resolution at package installation ==

The dependency resolution can be performed at package installation, if we use a third party package manager, see [[Third_Party_Package_Managers]]. This is very easy, but we should use that third party package manager and maybe we don't want to do it just for a simple package installation. We would like a more Slackware like solution.

== Dependency discovery as a separate task ==

We can discover the dependencies of our system in separate task using the '&lt;code&gt;ldd&lt;/code&gt;' command. This is not third party application, it is the part of our system.

We can scan the binaries in our PATH:
 #!/bin/bash
 
 ECHO=/usr/bin/echo
 SED=/usr/bin/sed
 FILE=/usr/bin/file
 CUT=/usr/bin/cut
 LDD=/usr/bin/ldd
 GREP=/usr/bin/grep
 AWK=/usr/bin/awk
 
 for p in `$ECHO $PATH | $SED 's/:/ /g'`
 do
     for f in $p/*
     do
         if [ 'ELF' == `$FILE -b $f | $CUT -d' ' -f1` ]; then
             if $LDD $f | $GREP -q 'not found'; then
                 $ECHO "$f"
                 $LDD $f | $GREP 'not found' | $AWK '{print "Not found:", $1}'
             fi
         fi
     done
 done

Or, we can print the missing package names instead of the missing library names, so we have to install only the given packages mentioned by this script (I used the concatenated MANIFEST file of '&lt;code&gt;slackpkg&lt;/code&gt;' on Slackware64, this file list is more friendlier for scripting):
 #!/bin/bash
 # This is the concatenated MANIFEST file of slackpkg on Slackware64
 MANIFEST=/var/lib/slackpkg/slackware64-filelist.gz
 
 # Do not trust in any command in PATH, shell builtins, etc.
 ECHO=/usr/bin/echo
 PRINTF=/usr/bin/printf
 CUT=/usr/bin/cut
 SORT=/usr/bin/sort
 GREP=/usr/bin/grep
 ZGREP=/usr/bin/zgrep
 SED=/usr/bin/sed
 AWK=/usr/bin/awk
 FILE=/usr/bin/file
 LDD=/usr/bin/ldd
 NULL=/dev/null
 
 # Check all directories in PATH
 for directory in `$ECHO $PATH | $SED 's/:/ /g'`
 do
     # Check all binaries in PATH directories
     for binary in $directory/*
     do
         # If it is true ELF binary
         if [ 'ELF' == `$FILE -b $binary | $CUT -d' ' -f1` ]; then
             # Show the progress by printing of actual filename on standard error
             $PRINTF "%-70s\r" $binary &gt;&amp;2
             # Check the missing shared library dependencies
             $LDD $binary 2&gt;$NULL | $GREP 'not found' | $AWK '{print $1}' | while read missing_lib
             do
                 # Print the package name of the missing library
                 $ZGREP $missing_lib $MANIFEST | $AWK '{print $1}'
             done
         fi
     done
     # Clear the progress info
     $PRINTF "%-80s\r" "" &gt;&amp;2
 # Ignore the duplicated package names
 done | $SORT -u

If we would like to scan the binaries of the PATH and the shared libraries of our system, then we need a deeper directory discovery:
 #!/bin/bash                                                             
 
 # This is the concatenated MANIFEST file of slackpkg on Slackware64
 MANIFEST=/var/lib/slackpkg/slackware64-filelist.gz
 
 # Do not trust in any command in PATH, shell builtins, etc.
 SYSPATH=$PATH
 PATH=/bin:/usr/bin:/usr/sbin
 ECHO=/usr/bin/echo
 PRINTF=/usr/bin/printf
 
 # Check all directories in PATH and ld.so.conf
 # If it is true ELF binary
 find `$ECHO $SYSPATH | sed 's/:/ /g'` \
      `sed 's/\(\/.*\/.*\)\/.*/\1/' /etc/ld.so.conf | sort -u` \
      -perm -100 -a -type f \
      -exec sh -c 'filename="{}"; /usr/bin/echo -n "." &gt;&amp;2; \
                   [ "ELF" = `file -b $filename | cut -d" " -f1` ] &amp;&amp; \
                   ldd $filename 2&gt;/dev/null | fgrep "not found" \
                       | cut -d" " -f1' \; | while read missing_lib
 do
     # Print the missing library and its package name
     $ECHO $missing_lib ": `zgrep $missing_lib $MANIFEST | cut -d" " -f1`"
 done | sort -u

This small script will browse huge amount of directories and will scan a lot of ELF binaries, so it can run for a long time.
There are more effective ways of the dependency discovery, this is only a very simple solution for a natural system administrator need. It demonstrates that a Slackware user does not need a package manager with dependency resolution, but even so can have a stable, well configured system.</text>
    <sha1>48d9d81b7225e7b3a975215a8f953513c4dd0476</sha1>
  </revision>
  <revision>
    <id>220</id>
    <parentid>219</parentid>
    <timestamp>2009-07-08T13:32:56Z</timestamp>
    <contributor>
      <username>Gabim</username>
      <id>27</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5022" xml:space="preserve">[[Category:Tips]]
== Introduction ==

"Slackware users typically prefer their method of manual dependency resolution, citing the level of system control it grants them." - as the [http://wiki.archlinux.org/index.php/Arch_Compared_To_Other_Distros#Arch_vs_Slackware ArchWiki] says. This total control over the system is one of the main strength of the Slackware distribution.

If the administrator of the system knows every package on the system and ensures their every dependencies, then the system is stable, well usable. If the administrator installs a new, (until now) unknown application, then he/she needs to discover its dependencies via the attached README or documentations, or from starting the application (if something is not installed on the system, then the application won't start).

== Dependency resolution at package installation ==

The dependency resolution can be performed at package installation, if we use a third party package manager, see [[Third_Party_Package_Managers]]. This is very easy, but we should use that third party package manager and maybe we don't want to do it just for a simple package installation. We would like a more Slackware like solution.

== Dependency discovery as a separate task ==

We can discover the dependencies of our system in separate task using the '&lt;code&gt;ldd&lt;/code&gt;' command. This is not third party application, it is the part of our system.

We can scan the binaries in our PATH:
 #!/bin/bash
 
 ECHO=/usr/bin/echo
 SED=/usr/bin/sed
 FILE=/usr/bin/file
 CUT=/usr/bin/cut
 LDD=/usr/bin/ldd
 GREP=/usr/bin/grep
 AWK=/usr/bin/awk
 
 for p in `$ECHO $PATH | $SED 's/:/ /g'`
 do
     for f in $p/*
     do
         if [ 'ELF' == `$FILE -b $f | $CUT -d' ' -f1` ]; then
             if $LDD $f | $GREP -q 'not found'; then
                 $ECHO "$f"
                 $LDD $f | $GREP 'not found' | $AWK '{print "Not found:", $1}'
             fi
         fi
     done
 done

Or, we can print the missing package names instead of the missing library names, so we have to install only the given packages mentioned by this script (I used the concatenated MANIFEST file of '&lt;code&gt;slackpkg&lt;/code&gt;' on Slackware64, this file list is more friendlier for scripting):
 #!/bin/bash
 # This is the concatenated MANIFEST file of slackpkg on Slackware64
 MANIFEST=/var/lib/slackpkg/slackware64-filelist.gz
 
 # Do not trust in any command in PATH, shell builtins, etc.
 ECHO=/usr/bin/echo
 PRINTF=/usr/bin/printf
 CUT=/usr/bin/cut
 SORT=/usr/bin/sort
 GREP=/usr/bin/grep
 ZGREP=/usr/bin/zgrep
 SED=/usr/bin/sed
 AWK=/usr/bin/awk
 FILE=/usr/bin/file
 LDD=/usr/bin/ldd
 NULL=/dev/null
 
 # Check all directories in PATH
 for directory in `$ECHO $PATH | $SED 's/:/ /g'`
 do
     # Check all binaries in PATH directories
     for binary in $directory/*
     do
         # If it is true ELF binary
         if [ 'ELF' == `$FILE -b $binary | $CUT -d' ' -f1` ]; then
             # Show the progress by printing of actual filename on standard error
             $PRINTF "%-70s\r" $binary &gt;&amp;2
             # Check the missing shared library dependencies
             $LDD $binary 2&gt;$NULL | $GREP 'not found' | $AWK '{print $1}' | while read missing_lib
             do
                 # Print the package name of the missing library
                 $ZGREP $missing_lib $MANIFEST | $AWK '{print $1}'
             done
         fi
     done
     # Clear the progress info
     $PRINTF "%-80s\r" "" &gt;&amp;2
 # Ignore the duplicated package names
 done | $SORT -u

If we would like to scan the binaries of the PATH and the shared libraries of our system, then we need a deeper directory discovery:
 #!/bin/bash                                                             
 
 # This is the concatenated MANIFEST file of slackpkg on Slackware64
 MANIFEST=/var/lib/slackpkg/slackware64-filelist.gz
 
 # Do not trust in any command in PATH, shell builtins, etc.
 SYSPATH=$PATH
 PATH=/bin:/usr/bin:/usr/sbin
 ECHO=/usr/bin/echo
 PRINTF=/usr/bin/printf
 
 # Check all directories in PATH and ld.so.conf
 # If it is true ELF binary
 find `$ECHO $SYSPATH | sed 's/:/ /g'` \
      `sed 's/\(\/.*\/.*\)\/.*/\1/' /etc/ld.so.conf | sort -u` \
      -perm -100 -a -type f \
      -exec sh -c 'filename="{}"; /usr/bin/echo -n "." &gt;&amp;2; \
                   [ "ELF" = `file -b $filename | cut -d" " -f1` ] &amp;&amp; \
                   ldd $filename 2&gt;/dev/null | fgrep "not found" \
                       | cut -d" " -f1' \; | while read missing_lib
 do
     # Print the missing library and its package name
     $ECHO $missing_lib ": `zgrep $missing_lib $MANIFEST | cut -d" " -f1`"
 done | sort -u

This small script will browse huge amount of directories and will scan a lot of ELF binaries, so it can run for a long time.
There are more effective ways of the dependency discovery, this is only a very simple solution for a natural system administrator need. It demonstrates that a Slackware user does not need a package manager with dependency resolution, but even so can have a stable, well configured system.</text>
    <sha1>1093f8c82682b83ffa0425112d7b300d2eb6c91e</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Links</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>221</id>
    <parentid>54</parentid>
    <timestamp>2009-07-08T13:57:13Z</timestamp>
    <contributor>
      <username>Gabim</username>
      <id>27</id>
    </contributor>
    <comment>/* Slackware Links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3982" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.org - our ugly mugs :)
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/ BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for 8.1 through -current</text>
    <sha1>bbf5e74621054e565d0aaefe3bc44bff7cf31ed2</sha1>
  </revision>
  <revision>
    <id>242</id>
    <parentid>221</parentid>
    <timestamp>2009-08-24T14:20:43Z</timestamp>
    <contributor>
      <username>Aaarnt</username>
      <id>37</id>
    </contributor>
    <comment>/* Slackware Links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4084" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.org - our ugly mugs :)
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://jtgzmanager.sf.net/ - A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/ BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for 8.1 through -current</text>
    <sha1>e7088e87c55e225dddf23c5856d08d921b5d21e1</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Mutt</title>
  <ns>0</ns>
  <id>117</id>
  <revision>
    <id>222</id>
    <parentid>140</parentid>
    <timestamp>2009-07-11T20:24:23Z</timestamp>
    <contributor>
      <username>Dwr</username>
      <id>28</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5959" xml:space="preserve">[[Category:Tutorials]]
= Mutt =

Mutt is a text-based mail client renowned for its powerful features and the fact that it is almost totally customizable. This article will cover the installation and configuration of mutt in order to use it as your daily email client. Please note that I use GMail as my primary email address, so the examples are designed for GMail users. Not much differs though other than the fact that GMail uses SSL.


== Installation ==

Slackware comes with a package for mutt v1.4. If you did a full install, you already have it installed. If not, it can be located on the 'n' series on your Slackware install CD or favourite mirror. This tutorial also uses getmail, procmail and msmtp. procmail and getmail are available as Slackware packages, and can be installed in the same manner...

If you have the CD, follow these steps as root to install it:

  mount /mnt/cdrom
  installpkg /mnt/cdrom/slackware/n/mutt-1.4.2.1i-i486-2.tgz
  installpkg /mnt/cdrom/slackware/n/getmail-4.4.4-noarch-1.tgz
  installpkg /mnt/cdrom/slackware/n/procmail-3.22-i486-1.tgz

If you would rather install it from a mirror:

  wget http://www.slackware.at/data/slackware-current/slackware/n/mutt-1.4.2.1i-i486-2.tgz
  wget http://www.slackware.at/data/slackware-current/slackware/n/getmail-4.4.4-noarch-1.tgz
  wget http://www.slackware.at/data/slackware-current/slackware/n/procmail-3.22-i486-1.tgz
  installpkg mutt-1.4.2.1i-i486-2.tgz getmail-4.4.4-noarch-1.tgz procmail-3.22-i486-1.tgz

Be sure to replace 'slackware-current' with the actual version of Slackware you are using.

msmtp is not part of Slackware, and will need to be installed separately. It can be downloaded from [http://msmtp.sourceforge.net/ here]. If you need information on building Slackware packages, click [[Building_A_Package]] for an excellent tutorial.

== Configuration ==

=== Mutt ===
First, let start with mutt, and a very simple ''~/.muttrc'':
 # Name
 set realname='Slackware User'
 
 # Where we store our emails
 set folder=~/mail
 set mbox=+mbox
 set spoolfile=+inbox
 set record=+sent
 set sort=threads # sort by emails by thread ;-)
 set postponed=+drafts
 set mbox_type=Maildir 
 mailboxes +inbox
 
 # my favourite editor is 'joe'
 set editor=joe
 
 ignore *	# this means "ignore all headers by default"
 # I still want to see some basic details
 unignore	date from subject to cc
 
 # Mutt options
 set edit_headers=yes
 set hdrs # Allows us to create our own headers
 my_hdr From: Slackware User &lt;user@slackware.com&gt;
 my_hdr X-Mailer: `mutt -v| head -n 1`

So far, it's simple, and cannot do much. We can almost read emails stored in ~/mail, compose and save drafts.

In order for us to read emails, first, we need to create our mail folders. We are using the Maildir format, so we need to create them using:

 mkdir -p ~/mail/inbox/{,cur,tmp,new}
 mkdir -p ~/mail/sent/{,cur,tmp,new}
 mkdir -p ~/mail/drafts/{,cur,tmp,new}

Now, when we have an email in ~/mail/inbox, we will be able to read it. Postponed messages will also be saved in ~/mail/drafts. But want to be able to send emails too, right? That's where msmtp comes into play.

For this part, we will assume that msmtp is installed. msmtp is basically a SMTP client that will be called by mutt when sending an email. So we need to have added to the mutt config like this:

 set sendmail="/usr/bin/msmtp"

Now, that's useless by itself. We need to setup msmtp to send emails...
Open up ~/.msmtprc with your favourite editor. This is a copy of mine, setup to use GMail's smtp server:

 account default
 host smtp.gmail.com
 port 587
 protocol smtp
 auth on
 from username@gmail.com
 user username@gmail.com
 password mypassword
 tls on
 tls_starttls on


So, after going through this and identifying what we need for our SMTP server, we are ready to send emails... Let's test it:

Launch mutt by running:
 mutt -y

Running mutt without '-y' will ignore our mailboxes statement, so we won't see any emails...

You can see in mutt the key shortcuts at the top of the screen: 'm' for composing a new message.
After we save the message, we see a new shortcut at the top: 'y' to send the message.

We now have mutt that can read emails from ~/mail/inbox, and send emails!!! 
The next step is to get the emails in ~/mail, and that's getmail's job.

=== Getmail ===

Getmail is a Python application that's included with Slackware. Similar to fetchmail, many people prefer it, saying it's easier to configure. Just like mutt, getmail is in the 'n' series, and should already be installed if you chose to do a full install. If not, just check out the mutt section above to install what's needed for this tutorial.

Once we have it all installed, let's create a basic getmail configuration. This configuration sits in ''~/.getmail/getmailrc'':

 [retriever]
 type = SimplePOP3SSLRetriever
 server = pop.gmail.com
 username = username@gmail.com
 port = 995
 password = password
 
 [destination]
 type = Maildir
 path = ~/mail/inbox

If you use a standard POP3 account that doesn't use SSL, use something like:

 [retriever]
 type = SimplePOP3Retriever
 server = pop.isp.net
 username = username
 port = 110
 password = password
 
 [destination]
 type = Maildir
 path = ~/mail/inbox

As simple as that. Now, it will connect to your email account, and download all your emails to ~/mail/inbox. Please note that if you want to fetch mail for multiple accounts, unlike fetchmail, getmail works with a single account per config file. So if you have two email accounts, you can have each account configured in their own config file like ''~/.getmail/getmailrc'' and ''~/.getmail/getmailrc-isp''

If you want automatic check, just add the following lines to your crontab by running ''crontab -e'' for each one of your email accounts:

 /5 * * * * /usr/bin/getmail
 /30 * * * * /usr/bin/getmail -r ~/.getmail/getmailrc-isp

=== Procmail ===

Procmail is an advanced mail filtering solution. More to come

== Todo ==
The rest...</text>
    <sha1>34f6607c7aabe3c606afaa3442e2addede802376</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Synaptics Touchpad</title>
  <ns>0</ns>
  <id>184</id>
  <revision>
    <id>227</id>
    <timestamp>2009-07-30T05:29:00Z</timestamp>
    <contributor>
      <username>Hiptobecubic</username>
      <id>30</id>
    </contributor>
    <comment>IPage Created.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1969" xml:space="preserve">=Small description of how to change your Synaptics touchpad using HAL instead of xorg.conf.=

In this example, I'll disable twofinger scrolling and enable the vertical scrolling on the right side of the touchpad as well as the tap-to-click feature:

# Copy &lt;tt&gt;/usr/share/hal/fdi/policy/10osvendor/11-x11-synaptics.fdi&lt;/tt&gt; to &lt;tt&gt;/etc/hal/fdi/policy&lt;/tt&gt;&lt;br/&gt;
# Now open a terminal and check out the man page for synaptics. "man synaptics". This is beautifully documented description of every option you're looking for as well as many you probably had no idea about.&lt;br/&gt;Search for the option that you wish to change and read about the appropriate setting to get the behavior you want.&lt;br/&gt;
# Open the 11-x11-synaptics.fdi file that you've copied to /etc/hal/fdi/policy. There will be a large commented section full of examples which we will model our options after. All options are passed to the synaptics driver using the:&lt;br/&gt;&lt;tt&gt;&lt;merge key="input.x11_options.OPTIONNAME" type="string"&gt;OPTIONVALUE&lt;/merge&gt;&lt;/tt&gt;&lt;br/&gt;construct.&lt;br/&gt;
#So let's add the vertical scrolling option with the line:&lt;br/&gt;&lt;tt&gt;&lt;merge key="input.x11_options.VertEdgeScroll" type="string"&gt;true&lt;/merge&gt;&lt;/tt&gt;&lt;br/&gt;
#And the tap-to-click feature:&lt;br/&gt;&lt;tt&gt;&lt;merge key="input.x11_options.TabButton1" type="string"&gt;1&lt;/merge&gt;&lt;/tt&gt;&lt;br/&gt;
#Now we disable the two-finger scrollers:&lt;br/&gt;&lt;tt&gt;&lt;merge key="input.x11_options.VertTwoFingerScroll" type="string"&gt;false&lt;/merge&gt;&lt;/tt&gt;&lt;br/&gt;&lt;tt&gt;&lt;merge key="input.x11_options.HorizTwoFingerScroll" type="string"&gt;false&lt;/merge&gt;&lt;/tt&gt;&lt;br/&gt;
&lt;br/&gt;Note that even though the man page says that different options take type 'boolean' 'integer' 'float' etc, in the policy file everything is type string'. Simply use the appropriate type as the value. TapButton1 takes an integer where VertEdgeScroll takes a boolean, for example.

#After this file has been edited. Close X and restart hal with &lt;tt&gt;sh /etc/rc.d/rc.hald restart&lt;/tt&gt;.
Now restart X and enjoy your new touchpad features.</text>
    <sha1>7014b9ef1f310c3000c632ea4dbc7b4edc451fdd</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>229</id>
    <parentid>20</parentid>
    <timestamp>2009-08-11T03:08:14Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1395" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please post a message on my [[User_talk:FredEmmott|user talk]] page if you think you'd be a suitable admin.</text>
    <sha1>c6c6329cf0b9ea5f484d22f9054717a9b5b54e12</sha1>
  </revision>
  <revision>
    <id>230</id>
    <parentid>229</parentid>
    <timestamp>2009-08-11T03:24:57Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Rewording</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1346" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>d02fe849995d712438b2bbd4fba7e980ae701653</sha1>
  </revision>
  <revision>
    <id>245</id>
    <parentid>230</parentid>
    <timestamp>2009-08-31T14:32:03Z</timestamp>
    <contributor>
      <username>Zordrak</username>
      <id>40</id>
    </contributor>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1373" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>d0b3b5754861cff710472279bcd504cb34ae6a05</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>FreeNX</title>
  <ns>0</ns>
  <id>185</id>
  <revision>
    <id>231</id>
    <timestamp>2009-08-13T17:00:35Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <comment>Created page with 'Getting FreeNX working on Slackware (12.2 as of writing).  == Build it ==  Get Eric Hameleers' build script:  :&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/fr...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1978" xml:space="preserve">Getting FreeNX working on Slackware (12.2 as of writing).

== Build it ==

Get Eric Hameleers' build script:

:&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/&lt;/code&gt;
:&lt;code&gt;cd connie.slackware.com/\~alien/slackbuilds/freenx/build/&lt;/code&gt;

Build nx and freenx:

:&lt;code&gt;./nx.SlackBuild &amp;&amp; ./freenx.SlackBuild --cleanup&lt;/code&gt;

Install the resultant packages:

:&lt;code&gt;installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz&lt;/code&gt;

The installer runs the initial configuration (including adding a new user "nx" to the system). 

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
   #SSHD_PORT=22
and replace 22 with whatever you port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:&lt;code&gt;/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start&lt;/code&gt;

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:&lt;code&gt;nxserver --status&lt;/code&gt;

If you see:

   root@darkstar:~# nxserver --status
   NX&gt; 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
   NX&gt; 110 NX Server is running
   NX&gt; 999 Bye

you're good to go. Otherwise, run:
:&lt;code&gt;nxserver --restart&lt;/code&gt;

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.</text>
    <sha1>87a91a215d77011a533350b7d5f920c639ffe8dd</sha1>
  </revision>
  <revision>
    <id>232</id>
    <parentid>231</parentid>
    <timestamp>2009-08-13T17:01:31Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <minor/>
    <comment>moved [[Freenx]] to [[FreeNX]]:&amp;#32;Added correct name.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1978" xml:space="preserve">Getting FreeNX working on Slackware (12.2 as of writing).

== Build it ==

Get Eric Hameleers' build script:

:&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/&lt;/code&gt;
:&lt;code&gt;cd connie.slackware.com/\~alien/slackbuilds/freenx/build/&lt;/code&gt;

Build nx and freenx:

:&lt;code&gt;./nx.SlackBuild &amp;&amp; ./freenx.SlackBuild --cleanup&lt;/code&gt;

Install the resultant packages:

:&lt;code&gt;installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz&lt;/code&gt;

The installer runs the initial configuration (including adding a new user "nx" to the system). 

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
   #SSHD_PORT=22
and replace 22 with whatever you port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:&lt;code&gt;/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start&lt;/code&gt;

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:&lt;code&gt;nxserver --status&lt;/code&gt;

If you see:

   root@darkstar:~# nxserver --status
   NX&gt; 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
   NX&gt; 110 NX Server is running
   NX&gt; 999 Bye

you're good to go. Otherwise, run:
:&lt;code&gt;nxserver --restart&lt;/code&gt;

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.</text>
    <sha1>87a91a215d77011a533350b7d5f920c639ffe8dd</sha1>
  </revision>
  <revision>
    <id>234</id>
    <parentid>232</parentid>
    <timestamp>2009-08-13T17:04:23Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <comment>/* Configure it */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1979" xml:space="preserve">Getting FreeNX working on Slackware (12.2 as of writing).

== Build it ==

Get Eric Hameleers' build script:

:&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/&lt;/code&gt;
:&lt;code&gt;cd connie.slackware.com/\~alien/slackbuilds/freenx/build/&lt;/code&gt;

Build nx and freenx:

:&lt;code&gt;./nx.SlackBuild &amp;&amp; ./freenx.SlackBuild --cleanup&lt;/code&gt;

Install the resultant packages:

:&lt;code&gt;installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz&lt;/code&gt;

The installer runs the initial configuration (including adding a new user "nx" to the system). 

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
   #SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:&lt;code&gt;/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start&lt;/code&gt;

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:&lt;code&gt;nxserver --status&lt;/code&gt;

If you see:

   root@darkstar:~# nxserver --status
   NX&gt; 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
   NX&gt; 110 NX Server is running
   NX&gt; 999 Bye

you're good to go. Otherwise, run:
:&lt;code&gt;nxserver --restart&lt;/code&gt;

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.</text>
    <sha1>ce2da7f65127ac33ffe11f6a575e804cf126e873</sha1>
  </revision>
  <revision>
    <id>235</id>
    <parentid>234</parentid>
    <timestamp>2009-08-13T19:44:57Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <comment>/* Connect to it */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2452" xml:space="preserve">Getting FreeNX working on Slackware (12.2 as of writing).

== Build it ==

Get Eric Hameleers' build script:

:&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/&lt;/code&gt;
:&lt;code&gt;cd connie.slackware.com/\~alien/slackbuilds/freenx/build/&lt;/code&gt;

Build nx and freenx:

:&lt;code&gt;./nx.SlackBuild &amp;&amp; ./freenx.SlackBuild --cleanup&lt;/code&gt;

Install the resultant packages:

:&lt;code&gt;installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz&lt;/code&gt;

The installer runs the initial configuration (including adding a new user "nx" to the system). 

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
   #SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:&lt;code&gt;/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start&lt;/code&gt;

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:&lt;code&gt;nxserver --status&lt;/code&gt;

If you see:

   root@darkstar:~# nxserver --status
   NX&gt; 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
   NX&gt; 110 NX Server is running
   NX&gt; 999 Bye

you're good to go. Otherwise, run:
:&lt;code&gt;nxserver --restart&lt;/code&gt;

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz), unpack it and run bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.</text>
    <sha1>8e08a815be6d96cf6c2e5cbdd5cc4555dcc545fd</sha1>
  </revision>
  <revision>
    <id>236</id>
    <parentid>235</parentid>
    <timestamp>2009-08-13T20:40:02Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2469" xml:space="preserve">Getting FreeNX working on Slackware (-current as of writing (13/08/2009)).

== Build it ==

Get Eric Hameleers' build script:

:&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/&lt;/code&gt;
:&lt;code&gt;cd connie.slackware.com/\~alien/slackbuilds/freenx/build/&lt;/code&gt;

Build nx and freenx:

:&lt;code&gt;./nx.SlackBuild &amp;&amp; ./freenx.SlackBuild --cleanup&lt;/code&gt;

Install the resultant packages:

:&lt;code&gt;installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz&lt;/code&gt;

The installer runs the initial configuration (including adding a new user "nx" to the system). 

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
   #SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:&lt;code&gt;/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start&lt;/code&gt;

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:&lt;code&gt;nxserver --status&lt;/code&gt;

If you see:

   root@darkstar:~# nxserver --status
   NX&gt; 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
   NX&gt; 110 NX Server is running
   NX&gt; 999 Bye

you're good to go. Otherwise, run:
:&lt;code&gt;nxserver --restart&lt;/code&gt;

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz), unpack it and run bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.</text>
    <sha1>07d87e00b4db3aecc7f183b8d8482a5184ecf859</sha1>
  </revision>
  <revision>
    <id>237</id>
    <parentid>236</parentid>
    <timestamp>2009-08-13T20:40:24Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2467" xml:space="preserve">Getting FreeNX working on Slackware -current as of writing (13/08/2009).

== Build it ==

Get Eric Hameleers' build script:

:&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/&lt;/code&gt;
:&lt;code&gt;cd connie.slackware.com/\~alien/slackbuilds/freenx/build/&lt;/code&gt;

Build nx and freenx:

:&lt;code&gt;./nx.SlackBuild &amp;&amp; ./freenx.SlackBuild --cleanup&lt;/code&gt;

Install the resultant packages:

:&lt;code&gt;installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz&lt;/code&gt;

The installer runs the initial configuration (including adding a new user "nx" to the system). 

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
   #SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:&lt;code&gt;/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start&lt;/code&gt;

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:&lt;code&gt;nxserver --status&lt;/code&gt;

If you see:

   root@darkstar:~# nxserver --status
   NX&gt; 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
   NX&gt; 110 NX Server is running
   NX&gt; 999 Bye

you're good to go. Otherwise, run:
:&lt;code&gt;nxserver --restart&lt;/code&gt;

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz), unpack it and run bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.</text>
    <sha1>30baf7bfd50a4991eb3e95fb49adab8542bf3931</sha1>
  </revision>
  <revision>
    <id>240</id>
    <parentid>237</parentid>
    <timestamp>2009-08-17T12:00:10Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <comment>/* Connect to it */ Added 64bit client download location</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2575" xml:space="preserve">Getting FreeNX working on Slackware -current as of writing (13/08/2009).

== Build it ==

Get Eric Hameleers' build script:

:&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/&lt;/code&gt;
:&lt;code&gt;cd connie.slackware.com/\~alien/slackbuilds/freenx/build/&lt;/code&gt;

Build nx and freenx:

:&lt;code&gt;./nx.SlackBuild &amp;&amp; ./freenx.SlackBuild --cleanup&lt;/code&gt;

Install the resultant packages:

:&lt;code&gt;installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz&lt;/code&gt;

The installer runs the initial configuration (including adding a new user "nx" to the system). 

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
   #SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:&lt;code&gt;/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start&lt;/code&gt;

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:&lt;code&gt;nxserver --status&lt;/code&gt;

If you see:

   root@darkstar:~# nxserver --status
   NX&gt; 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
   NX&gt; 110 NX Server is running
   NX&gt; 999 Bye

you're good to go. Otherwise, run:
:&lt;code&gt;nxserver --restart&lt;/code&gt;

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz or http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.x86_64.tar.gz, depending on your architecture), unpack it and run bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.</text>
    <sha1>523a2610431eafc8dda53115bf6a37c0a854e9b8</sha1>
  </revision>
  <revision>
    <id>241</id>
    <parentid>240</parentid>
    <timestamp>2009-08-17T12:48:21Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <comment>/* Connect to it */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2578" xml:space="preserve">Getting FreeNX working on Slackware -current as of writing (13/08/2009).

== Build it ==

Get Eric Hameleers' build script:

:&lt;code&gt;wget -np -r http://connie.slackware.com/~alien/slackbuilds/freenx/build/&lt;/code&gt;
:&lt;code&gt;cd connie.slackware.com/\~alien/slackbuilds/freenx/build/&lt;/code&gt;

Build nx and freenx:

:&lt;code&gt;./nx.SlackBuild &amp;&amp; ./freenx.SlackBuild --cleanup&lt;/code&gt;

Install the resultant packages:

:&lt;code&gt;installpkg /tmp/{nx-3.3.0-i486-1alien,freenx-0.7.3-i486-2alien}.tgz&lt;/code&gt;

The installer runs the initial configuration (including adding a new user "nx" to the system). 

== Configure it ==

The main config file is /etc/nxserver/node.conf. The comments are helpful, so read them.

Of interest to me was specifying the port that the system's sshd listens on. If you run your sshd on a non-standard port (i.e. not 22), then uncomment the line:
   #SSHD_PORT=22
and replace 22 with whatever your port number is.

If you're a bit paranoid with your security settings in /etc/ssh/sshd_config (like I am), make sure you add the user nx to AllowUsers, otherwise the client you choose will fail to connect to your ssh daemon.

If you've made changes in /etc/ssh/sshd_config, then restart sshd. This is the command I use when I'm logged in remotely and I need to restart sshd:
:&lt;code&gt;/etc/rc.d/rc.sshd stop; sleep 5; /etc/rc.d/rc.sshd start&lt;/code&gt;

== Run it ==

Check to see if the server is running (it was after my installation, but your mileage may vary):

:&lt;code&gt;nxserver --status&lt;/code&gt;

If you see:

   root@darkstar:~# nxserver --status
   NX&gt; 100 NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
   NX&gt; 110 NX Server is running
   NX&gt; 999 Bye

you're good to go. Otherwise, run:
:&lt;code&gt;nxserver --restart&lt;/code&gt;

== Connect to it ==

http://en.opensuse.org/FreeNX_Server_HOWTO lists a number of clients able to connect to a (free)nx server. Since my main interest was in accessing my Linux box at home from my Windows box at work, I used the NoMachine client for Windows.

The NoMachine Linux client works just as well. Simply download the archive (http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.i386.tar.gz or http://64.34.161.181/download/3.3.0/Linux/nxclient-3.3.0-6.x86_64.tar.gz, depending on your architecture), unpack it and run NX/bin/nxclient. When prompted, enter the IP or hostname of the machine you wish to connect to, the port through which you would SSH into it and which DE you want to run (KDE, Gnome etc.). Obviously Slackware doesn't ship with Gnome, but I've successfully tested it with KDE. I have yet to get XFCE to work.</text>
    <sha1>957056c1d39df5c62f475dd2599e00187649d05e</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Freenx</title>
  <ns>0</ns>
  <id>186</id>
  <revision>
    <id>233</id>
    <timestamp>2009-08-13T17:01:32Z</timestamp>
    <contributor>
      <username>Pwc101</username>
      <id>33</id>
    </contributor>
    <comment>moved [[Freenx]] to [[FreeNX]]:&amp;#32;Added correct name.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20" xml:space="preserve">#REDIRECT [[FreeNX]]</text>
    <sha1>34dddc51dccd5bae601d37233a09512faf0d919c</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>SysRq</title>
  <ns>0</ns>
  <id>168</id>
  <revision>
    <id>238</id>
    <parentid>196</parentid>
    <timestamp>2009-08-14T04:47:03Z</timestamp>
    <contributor>
      <username>NickC</username>
      <id>35</id>
    </contributor>
    <minor/>
    <comment>SysRq list into different order; corrected SysRq+I definition error; added mnemonics.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2900" xml:space="preserve">[[Category:Tips]]
--[[User:Drijen|Drijen]] 15:06, 22 September 2007 (EDT)

==Recovering from a System Lock==
Sometimes a process can go out to lunch, or the system will simply stop responding to user input. This could be from a process waiting for resources or a zombie, but in any case there is no reason to have to reach for that reset button!

==The Magic SysRq==
The SysRq can be used as a means to save your work, sync the file system(s) and reboot the computer in a clean manner. If you don't know where the SysRq key is, look for the "Prt Scr" (Print Screen) button on your keyboard. SysRq is generally assigned to the same keypress.

===Enabling the SysRq Function===
To enable the SysRq functionality, you must have a 2.6.15 or higher kernel, and it must be compiled directly in.  Not as a Module!

To check that you have it enabled you may run this command:


:&lt;pre&gt;cat /boot/config |grep CONFIG_MAGIC_SYSRQ&lt;/pre&gt;


OR

:&lt;pre&gt;zcat /proc/config.gz |grep SYSRQ&lt;/pre&gt;


if you have /proc/.config support compiled in. (All base slack kernels do)


which should return:


:&lt;pre&gt;CONFIG_MAGIC_SYSRQ=y&lt;/pre&gt;


If you find that you need to compile it in, the option can be found under the heading ''Kernel Hacking'' on your make &lt;(x)(menu)config&gt; screen.


Once you are satisfied that you have the SysRq funtion correctly compiled, ensure that it has not been disabled at boot:


:&lt;pre&gt;cat /proc/sys/kernel/sysrq&lt;/pre&gt;


If the response is &lt;tt&gt;0&lt;/tt&gt; :

:&lt;pre&gt;echo 1 &gt; /proc/sys/kernel/sysrq&lt;/pre&gt;


===Recovering from a Lock Up using SysRq===
If your system has gone out to lunch, you can now use the Magic SysRq key to save your work and reboot. The basic commands are as follows:

   &lt;tt&gt;Alt+SysRq+R&lt;/tt&gt; :Attempts to remove keyboard from Raw mode
   &lt;tt&gt;Alt+SysRq+E&lt;/tt&gt; :Terminate request sent to all processes (SIGTERM / kill -15)
   &lt;tt&gt;Alt+SysRq+I&lt;/tt&gt; :Kills all processes (SIGKILL / kill -9)
   &lt;tt&gt;Alt+SysRq+S&lt;/tt&gt; :Syncs all disks  
   &lt;tt&gt;Alt+SysRq+U&lt;/tt&gt; :Force unmount and remount of all filesystems readonly
   &lt;tt&gt;Alt+SysRq+B&lt;/tt&gt; :Reboots (INIT 6)

and roughly in that order.  You should wait several seconds between each keystroke to let the system complete your request before you issue a new one.

There are several mnemonics to help you remember the key sequence:
    &lt;tt&gt;Raising Elephants Is So Utterly Boring&lt;/tt&gt;
    &lt;tt&gt;Reboot Even If System Utterly Broken&lt;/tt&gt;
    &lt;tt&gt;BUSIER, spelt backwards&lt;/tt&gt;

An alternative method is to:

:&lt;pre&gt;Alt+SysRq+R CTRL+ALT+DEL&lt;/pre&gt;

This command will move the keyboard out of raw mode, and attempt to issue a &lt;tt&gt;SHUTDOWN NOW&lt;/tt&gt; command. However, this will not work under some configurations, or if tty1 is defunct.

==Futher Information==
Further instructions and other options can be found at:

Wikipedia article on MagicSysRq [http://en.wikipedia.org/wiki/Magic_SysRq_key]

&lt;pre&gt;/usr/src/&lt;linux-version&gt;/Documentation/sysrq.txt&lt;/pre&gt;</text>
    <sha1>e15e11d4ae885652e4d3d7fe154180d78653322e</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>User:Aaarnt</title>
  <ns>2</ns>
  <id>187</id>
  <revision>
    <id>239</id>
    <timestamp>2009-08-15T17:07:04Z</timestamp>
    <contributor>
      <username>Aaarnt</username>
      <id>37</id>
    </contributor>
    <comment>Created page with 'My name is Alexandre Albuquerque Arnt. Brazilian. Took my BS in Computer Science in 1999. I develop software and happen to be a Slackware user since 2003 (or would it be 2002, we...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="576" xml:space="preserve">My name is Alexandre Albuquerque Arnt. Brazilian. Took my BS in Computer Science in 1999.
I develop software and happen to be a Slackware user since 2003 (or would it be 2002, well it doesn't matter).

I use to run the stable version, while at times with a couple of current packages. Now using version 12.2 with KDE 4.2 and Xfce 4.6.1, as well as Linux kernel 2.6.30.4.

I have a project called [http://jtgzmanager.sf.net QTGZManager] - a frontend to ''pkgtools'' written from scratch with the help of Qt4 C++ libs.

Why Slackware? Because it's always been unbreakable to me.</text>
    <sha1>a4d78f2e9491a138740545ef726d20556ed6ad4e</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Binary Numbers</title>
  <ns>0</ns>
  <id>188</id>
  <revision>
    <id>243</id>
    <timestamp>2009-08-31T13:39:49Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Initial import from webarchive - how to do exponents?</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6049" xml:space="preserve">Based on Sandman1's tutorial, with heavy edits and additions by rworkman.

You probably remember from learning numbers in elementary/primary school how you have the 'ones' place and the 'tens' place and the 'hundreds' place and so on... Let's take the number 4,728 for an example: 

 The digit in the 'ones' place is 8
 The digit in the 'tens' place is 2
 The digit in the 'hundreds' place is 7
 The digit in the 'thousands' place is 4

The ones/tens/hundreds/etcetera come from the fact that in base 10, the digits of a number are laid out like this: 

 10^0 = 1 -----&gt; 'ones' place
 10^1 = 10 ----&gt; 'tens' place
 10^2 = 100 ---&gt; 'hundreds' place
 10^3 = 1000 --&gt; 'thousands' place 
 10^4 = 10000 -&gt; 'ten-thousands' place
 and so on...

So, in the number given above (4,728), we have: 

 8 'ones' -------&gt; 8 x 1 = 8
 2 'tens' -------&gt; 2 x 10 = 20
 7 'hundreds' ---&gt; 7 x 100 = 700
 4 'thousands' --&gt; 4 x 1000 = 4000

 Add up these totals:
 8 + 20 + 700 + 4000 = 4728

The Binary Number system works the same way, and is a pretty easy thing to learn, but may be confusing at first. The first thing you need to memorize is 2 raised to the powers, for instance:
 2^0 2^1  2^2  2^3   2^4   2^5   2^6   2^7   2^8
 1   2   4   8   16  32  64  128 256

Instead of a 'ones' place, a 'tens' place, a 'hundreds' place, and so on like in base 10, there is a 'ones' place (2^0), and 'twos' place (2^1), a 'fours' place (2^2), an 'eights' place (2^3), and so on...

Now we first want to be able to take a binary number and turn it into decimal format or base 10. So the first example:

 1   1   1   1
 *   *   *   *
 8   4   2   1
 ^   ^   ^   ^
 8 + 4 + 2 + 1 = 15

Now from the example above you see how the 8 is on the left and the 1 is on the right. This will always be that order. You see above that you multiply the 1's with the actual digit it's located in. Now this is all hard to explain so I am going to show you another example: 

 1   0   0   0   0
 *   *   *   *   *
 16  8   4   2   1
 ^   ^   ^   ^   ^
 16 +0 + 0 + 0 + 0 = 16

Now from the example above you see how it is 16 because all of the other placements are 0's and everything multiplied by zero is zero. Now converting from decimal to binary is a bit trickier, here is a simple example:

20 is the number we will be converting. We first need to find the highest value of the binary numbers above so we can subtract from it. 32 is to high because it is a bigger than 20. So we will use 16. We put a 1 in the 16 place and subtract from 20: 

 20 - 16 = 4

Now the next power is the 2^3 and that is 8. Since 8 is bigger than 4 we can put a zero. So we now are at 22 which is 4. Well, 4 is not bigger than 4 because it is the same number, so we subtract 4 and put a 1 there. 

 4 - 4 = 0

Since we have nothing left we just fill the rest of the placements with zeros: 

 10100

Now you can double check the work and find out that it is 20. Now I will show one more example, this time I will convert 25 to binary. For this example I will start by putting a 1 in the 2^4's place and subtract:

 25 - 16 = 9

Now we have 9, so we look at the next power and see if it can go into 9. Which the next number is 8 and we can so we put a 1 in the 2^3's place. Now we subtract again: 

 9 - 8 = 1

Now we have 1 left over, now we want to put this in 20's place. So we skip over the 2^2 and 2^1. The reason why we skip this is because 1 cannot go into 4 and 2 equally. Now we have this binary number: 

 11001

This leads to a discussion about ipv4 addressing. An ipv4 address consists of 32 bits. 8 bits = 1 byte ; therefore, an ipv4 address is 4 bytes long. For example, 192.168.10.100 is an ipv4 address. Each byte of the address is separated by a dot (.) - in other words, the first byte (or eight bits) of the address is 192, the next is 168, the next is 10, the last is 100. You're probably wondering where the "eight bits" comes into play, right?  :-)

In binary, 192 = 11000000 and 168=10101000 and 10 = 00001010 and 100 = 01100100 Work it out for yourself (based on the information above) if you don't believe me.

You've probably seen the CIDR notation before - maybe an address block was written like this: 192.168.10.1/24 What that tells you is that only the first 24 bits of the address are important. That one's easy, as 24 bits equals 3 bytes; therefore, only the first three octets are important. In other words, 192.168.10.1/24 would match any ip address from 192.168.10.1 through 192.186.10.255. That same pattern applies for a netmask of /8, /16, or /32. 192.0.0.0/8 would match any ip address that begins with 192. 192.168.0.0/16 would match any ip address that begins with 192.168. 192.168.10.100/32 will match *only* .100 -- this netmask means that *all* 32 bits are important; they must all match (as opposed to only 8 or 16 or 24 or whatever other number matching).

So what if the netmask doesn't work out to a nice and easy byte boundary? Well... let's look at our original ip address again. 

 192.168.10.100 = 11000000.10101000.00001010.01100100

Suppose you're given 192.168.10.100/29 and asked to calculate a valid range of ip addresses. This tells you that the first 29 bits are important, but the others can change and still match the netmask. The first 29 bits are: 11000000.10101000.00001010.01100*** The *** represents the three bits that can change. For those three bits, here are your options (I'm leaving a space between the 29th and 30th bit): 

 11000000.10101000.00001010.01100 000 = 192.168.10.96
 11000000.10101000.00001010.01100 001 = 192.168.10.97
 11000000.10101000.00001010.01100 010 = 192.168.10.98
 11000000.10101000.00001010.01100 011 = 192.168.10.99
 11000000.10101000.00001010.01100 100 = 192.168.10.100
 11000000.10101000.00001010.01100 101 = 192.168.10.101
 11000000.10101000.00001010.01100 110 = 192.168.10.102
 11000000.10101000.00001010.01100 111 = 192.168.10.103

Typically, this would be denoted as 192.168.10.96/29 The next /29 block would be 192.168.10.104/29, and then 192.168.10.112/29, and so on.

Hopefully that helped a bit :) --rworkman</text>
    <sha1>06d0fb92aa2e0bd42c9ce9d3966031fccab6bd51</sha1>
  </revision>
  <revision>
    <id>244</id>
    <parentid>243</parentid>
    <timestamp>2009-08-31T13:40:47Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Fixed some formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6061" xml:space="preserve">Based on Sandman1's tutorial, with heavy edits and additions by rworkman.

You probably remember from learning numbers in elementary/primary school how you have the 'ones' place and the 'tens' place and the 'hundreds' place and so on... Let's take the number 4,728 for an example: 

 The digit in the 'ones' place is 8
 The digit in the 'tens' place is 2
 The digit in the 'hundreds' place is 7
 The digit in the 'thousands' place is 4

The ones/tens/hundreds/etcetera come from the fact that in base 10, the digits of a number are laid out like this: 

 10^0 = 1 -----&gt; 'ones' place
 10^1 = 10 ----&gt; 'tens' place
 10^2 = 100 ---&gt; 'hundreds' place
 10^3 = 1000 --&gt; 'thousands' place 
 10^4 = 10000 -&gt; 'ten-thousands' place
 and so on...

So, in the number given above (4,728), we have: 

 8 'ones' -------&gt; 8 x 1 = 8
 2 'tens' -------&gt; 2 x 10 = 20
 7 'hundreds' ---&gt; 7 x 100 = 700
 4 'thousands' --&gt; 4 x 1000 = 4000

 Add up these totals:
 8 + 20 + 700 + 4000 = 4728

The Binary Number system works the same way, and is a pretty easy thing to learn, but may be confusing at first. The first thing you need to memorize is 2 raised to the powers, for instance:
 2^0 2^1  2^2  2^3   2^4   2^5   2^6   2^7   2^8
  1   2    4    8     16   32    64    128   256

Instead of a 'ones' place, a 'tens' place, a 'hundreds' place, and so on like in base 10, there is a 'ones' place (2^0), and 'twos' place (2^1), a 'fours' place (2^2), an 'eights' place (2^3), and so on...

Now we first want to be able to take a binary number and turn it into decimal format or base 10. So the first example:

 1   1   1   1
 *   *   *   *
 8   4   2   1
 ^   ^   ^   ^
 8 + 4 + 2 + 1 = 15

Now from the example above you see how the 8 is on the left and the 1 is on the right. This will always be that order. You see above that you multiply the 1's with the actual digit it's located in. Now this is all hard to explain so I am going to show you another example: 

 1   0   0   0   0
 *   *   *   *   *
 16  8   4   2   1
 ^   ^   ^   ^   ^
 16 +0 + 0 + 0 + 0 = 16

Now from the example above you see how it is 16 because all of the other placements are 0's and everything multiplied by zero is zero. Now converting from decimal to binary is a bit trickier, here is a simple example:

20 is the number we will be converting. We first need to find the highest value of the binary numbers above so we can subtract from it. 32 is to high because it is a bigger than 20. So we will use 16. We put a 1 in the 16 place and subtract from 20: 

 20 - 16 = 4

Now the next power is the 2^3 and that is 8. Since 8 is bigger than 4 we can put a zero. So we now are at 22 which is 4. Well, 4 is not bigger than 4 because it is the same number, so we subtract 4 and put a 1 there. 

 4 - 4 = 0

Since we have nothing left we just fill the rest of the placements with zeros: 

 10100

Now you can double check the work and find out that it is 20. Now I will show one more example, this time I will convert 25 to binary. For this example I will start by putting a 1 in the 2^4's place and subtract:

 25 - 16 = 9

Now we have 9, so we look at the next power and see if it can go into 9. Which the next number is 8 and we can so we put a 1 in the 2^3's place. Now we subtract again: 

 9 - 8 = 1

Now we have 1 left over, now we want to put this in 20's place. So we skip over the 2^2 and 2^1. The reason why we skip this is because 1 cannot go into 4 and 2 equally. Now we have this binary number: 

 11001

This leads to a discussion about ipv4 addressing. An ipv4 address consists of 32 bits. 8 bits = 1 byte ; therefore, an ipv4 address is 4 bytes long. For example, 192.168.10.100 is an ipv4 address. Each byte of the address is separated by a dot (.) - in other words, the first byte (or eight bits) of the address is 192, the next is 168, the next is 10, the last is 100. You're probably wondering where the "eight bits" comes into play, right?  :-)

In binary, 192 = 11000000 and 168=10101000 and 10 = 00001010 and 100 = 01100100 Work it out for yourself (based on the information above) if you don't believe me.

You've probably seen the CIDR notation before - maybe an address block was written like this: 192.168.10.1/24 What that tells you is that only the first 24 bits of the address are important. That one's easy, as 24 bits equals 3 bytes; therefore, only the first three octets are important. In other words, 192.168.10.1/24 would match any ip address from 192.168.10.1 through 192.186.10.255. That same pattern applies for a netmask of /8, /16, or /32. 192.0.0.0/8 would match any ip address that begins with 192. 192.168.0.0/16 would match any ip address that begins with 192.168. 192.168.10.100/32 will match *only* .100 -- this netmask means that *all* 32 bits are important; they must all match (as opposed to only 8 or 16 or 24 or whatever other number matching).

So what if the netmask doesn't work out to a nice and easy byte boundary? Well... let's look at our original ip address again. 

 192.168.10.100 = 11000000.10101000.00001010.01100100

Suppose you're given 192.168.10.100/29 and asked to calculate a valid range of ip addresses. This tells you that the first 29 bits are important, but the others can change and still match the netmask. The first 29 bits are: 11000000.10101000.00001010.01100*** The *** represents the three bits that can change. For those three bits, here are your options (I'm leaving a space between the 29th and 30th bit): 

 11000000.10101000.00001010.01100 000 = 192.168.10.96
 11000000.10101000.00001010.01100 001 = 192.168.10.97
 11000000.10101000.00001010.01100 010 = 192.168.10.98
 11000000.10101000.00001010.01100 011 = 192.168.10.99
 11000000.10101000.00001010.01100 100 = 192.168.10.100
 11000000.10101000.00001010.01100 101 = 192.168.10.101
 11000000.10101000.00001010.01100 110 = 192.168.10.102
 11000000.10101000.00001010.01100 111 = 192.168.10.103

Typically, this would be denoted as 192.168.10.96/29 The next /29 block would be 192.168.10.104/29, and then 192.168.10.112/29, and so on.

Hopefully that helped a bit :) --rworkman</text>
    <sha1>9db0783b2a3cda22b772557d3550b3151e6d3a5c</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>User:Zordrak</title>
  <ns>2</ns>
  <id>189</id>
  <revision>
    <id>246</id>
    <timestamp>2009-08-31T14:33:28Z</timestamp>
    <contributor>
      <username>Zordrak</username>
      <id>40</id>
    </contributor>
    <comment>Created page with 'I’m a UK-based Systems Administrator, a Slackware user and a F/OSS contributor.'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="81" xml:space="preserve">I’m a UK-based Systems Administrator, a Slackware user and a F/OSS contributor.</text>
    <sha1>6052466138fd3601548e7581cbe4c246966e7c9c</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Kdebluetooth4</title>
  <ns>0</ns>
  <id>190</id>
  <revision>
    <id>247</id>
    <timestamp>2009-09-02T20:56:55Z</timestamp>
    <contributor>
      <username>Lynchmv</username>
      <id>39</id>
    </contributor>
    <comment>How to get kdebluetooth4 to build on Slackware 13.0</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1603" xml:space="preserve">Out of the box, Slackware 13.0 will not compile kdebluetooth4, and the SlackBuild package of 1.0_beta8 will not build due to it not liking QT4.  After some digging around, I found a patch that allowed me to build kdebluetooth4.  The patch can be found here:

[http://bugsfiles.kde.org/attachment.cgi?id=30865 KDE Bugfiles]

Save it as kdebase-workspace-4.2.4.patch
To apply this patch, download the kdebase-workspace-4.2.4.tar.bz2 package

[http://mirrors.isc.org/pub/kde/stable/4.2.4/src/kdebase-workspace-4.2.4.tar.bz2 isc.org mirror]

Extract the contents then apply the patch

 tar vxf kdebase-workspace-4.2.4.tar.bz2
 cd kdebase-workspace-4.2.4
 patch -p0 &lt; ../kdebase-workspace-4.2.4.patch

Tar everything back up

 tar cvvf kdebase-workspace-4.2.4.tar kdebase-workspace-4.2.4
 bzip2 -9 kdebase-workspace-4.2.4.tar

Create a working folder and copy the slackbuild from the 13.0 dvd

 mkdir /tmp/kdebase-workspace
 cd /tmp/kdebase-workspace
 cp -r /path/to/dvd/source/kde/kdebase-workspace/* .

Edit line 47 of kdebase-workspace.SlackBuild then build the package

 tar xvf $CWD/kdebase-workspace-$VERSION.tar.?z* || exit 1
 ./kdebase-workspace.SlackBuild

This may or may not take some time, depending on your hardware, but you already knew that.  After it is done building your new package, upgrade the old package with your new package

 upgradepkg kdebase-workspace-4.2.4-i486-1%kdebase-workspace-4.2.4.txz

Now, you should have a patched version of kdebase-workspace installed and be able to install kdebluetooth4.  I'll have to finish that part of this article when I get home, as it's 5:00...</text>
    <sha1>6919d491a1f9bc0d358dc61e6af52edd6ce339a1</sha1>
  </revision>
  <revision>
    <id>248</id>
    <parentid>247</parentid>
    <timestamp>2009-09-03T01:13:37Z</timestamp>
    <contributor>
      <username>Lynchmv</username>
      <id>39</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1856" xml:space="preserve">== This Does Not Work Yet ==

Out of the box, Slackware 13.0 will not compile kdebluetooth4, and the SlackBuild package of 1.0_beta8 will not build due to it not liking QT4.  After some digging around, I found a patch that allowed me to build kdebluetooth4.  The patch can be found here:

[http://bugsfiles.kde.org/attachment.cgi?id=30865 KDE Bugfiles]

Save it as kdebase-workspace-4.2.4.patch
To apply this patch, download the kdebase-workspace-4.2.4.tar.bz2 package

[http://mirrors.isc.org/pub/kde/stable/4.2.4/src/kdebase-workspace-4.2.4.tar.bz2 isc.org mirror]

Extract the contents then apply the patch

 tar vxf kdebase-workspace-4.2.4.tar.bz2
 cd kdebase-workspace-4.2.4
 patch -p0 &lt; ../kdebase-workspace-4.2.4.patch

Tar everything back up

 tar cvvf kdebase-workspace-4.2.4.tar kdebase-workspace-4.2.4
 bzip2 -9 kdebase-workspace-4.2.4.tar

Create a working folder and copy the slackbuild from the 13.0 dvd

 mkdir /tmp/kdebase-workspace
 cd /tmp/kdebase-workspace
 cp -r /path/to/dvd/source/kde/kdebase-workspace/* .

Edit line 47 of kdebase-workspace.SlackBuild then build the package

 tar xvf $CWD/kdebase-workspace-$VERSION.tar.?z* || exit 1
 ./kdebase-workspace.SlackBuild

This may or may not take some time, depending on your hardware, but you already knew that.  After it is done building your new package, upgrade the old package with your new package

 upgradepkg kdebase-workspace-4.2.4-i486-1%kdebase-workspace-4.2.4.txz

Now, you should have a patched version of kdebase-workspace installed and be able to install kdebluetooth4.  I'll have to finish that part of this article when I get home, as it's 5:00...


...and now that I'm home, I see that my newly compiled kbluetooth4 Slackware package still doesn't work after instllation...grr...maybe this process will spawn an idea of someone much smarter than I on how to fix this...</text>
    <sha1>586c539c5c55ca9faf0b5f96eabda15b3f831949</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Slack-desc</title>
  <ns>0</ns>
  <id>17</id>
  <revision>
    <id>249</id>
    <parentid>24</parentid>
    <timestamp>2009-09-07T06:50:00Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <minor/>
    <comment>remove comment about space after :</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1560" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.
 
        |-----handy-ruler------------------------------------------------------|
 appname: Summary of application name and function (one line only)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname: 
 appname: It's a good idea to include a link to the application's homepage too.
 appname: 

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>56d4b251bb87bbc38a2285df2e118e5d5c6d035d</sha1>
  </revision>
  <revision>
    <id>250</id>
    <parentid>249</parentid>
    <timestamp>2009-09-07T06:56:29Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <comment>Undo revision 249 by [[Special:Contributions/Sahko|Sahko]] ([[User talk:Sahko|Talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1618" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: Summary of application name and function (one line only)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname: 
 appname: It's a good idea to include a link to the application's homepage too.
 appname: 

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>c24c887449d4942b75d125ca6278c76190d4c962</sha1>
  </revision>
  <revision>
    <id>251</id>
    <parentid>250</parentid>
    <timestamp>2009-09-07T06:59:54Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1687" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: Summary of application name and function (one line only)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname: 
 appname: It's a good idea to include a link to the application's homepage too.
 appname: 

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :

=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>367ff913c08f6237c70dcce32a463d1410f75dd9</sha1>
  </revision>
  <revision>
    <id>252</id>
    <parentid>251</parentid>
    <timestamp>2009-09-07T07:02:15Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1757" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: Summary of application name and function (one line only)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname:
 appname: It's a good idea to include a link to the application's homepage too.
 appname:

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 2,9 &amp; 11 should not have a space after the :

=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>2d14b63f32078586bd2efb2e120560322cce3e28</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Talk:SSH Keys</title>
  <ns>1</ns>
  <id>191</id>
  <revision>
    <id>253</id>
    <timestamp>2009-09-07T18:41:48Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Created page with 'Is rsa better? Should a bitsize (-b) be specified? ~~~~'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="99" xml:space="preserve">Is rsa better? Should a bitsize (-b) be specified? [[User:Erik|Erik]] 18:41, 7 September 2009 (UTC)</text>
    <sha1>1af7572b05240d2e56d09e600eb7adffedc2e22f</sha1>
  </revision>
</page>
<page arvcontinue="20090606233738|205">
  <title>Recompile php with mcrypt</title>
  <ns>0</ns>
  <id>139</id>
  <revision>
    <id>254</id>
    <parentid>165</parentid>
    <timestamp>2009-10-05T16:55:09Z</timestamp>
    <contributor>
      <username>Trashbird1240</username>
      <id>18</id>
    </contributor>
    <comment>removed note about editing slackbuild</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2583" xml:space="preserve">[[Category:Tutorials]]
PhpMyAdmin (available at [http://www.SlackBuilds.org/ SlackBuilds.org]) works well when you compile PHP with the mcrypt extension.  After installing PhpMyAdmin, you may see a warning that it cannot find the mcrypt extension.    Unfortunately the official Slackware package does not include this extension.  Recompiling PHP is necessary, as is enabling the mcrypt.so extension in /etc/httpd/php.ini.  The first step is a little tricky, since compiling PHP requires a little trick: you must compile alpine during the PHP build.  It is fairly simple once you have things in place, but this tripped me up when I first tried to recompile PHP.

== Install mcrypt and libmcrypt ==

mcrypt is available from [http://www.SlackBuilds.org SlackBuilds.org].  First build and install mcrypt and libmcrypt before compiling PHP.

== Recompile PHP ==

Go to a Slackware mirror and download Pat's Slackbuild directory for php from the source/n directory.  I used 

&lt;code&gt;# wget --mirror &lt;mirror&gt;/n/php&lt;/code&gt;

to download the whole directory.  You will also need to download the alpine/ directory into the parent of the newly-created php/.  In other words, you should have a parent directory with both php and alpine.  For example, mine is ~/SlackBuilds/n, where I have two subdirectories: one for alpine/ and one for php/.  An alternative to wget is to use a file manager capable of ftp with drag and drop, such as Nautilus.

'''
Be sure to chmod +x both the alpine and php SlackBuilds before attempting to build.'''  If you don't, things may go for quite a while depending on the speed of the machine you're building on before you get an error (and you ''will'' get an error).

The official PHP SlackBuild includes a configure flag for mcrypt, so there is no need to edit the SlackBuild.  You may want to specify a BUILD variable on the command line, so the package does not appear to be official (it is ''not'' official):

&lt;code&gt;# BUILD=3_&lt;your initials&gt; sudo ./php.SlackBuild&lt;/code&gt;

=== Upgrade PHP ===
Install the new package with upgradepkg.  Keep in mind that you will need to repeat this process whenever there is a security alert for php.  In that case, download the new source, update the VERSION variable, recompile and upgrade.  For this reason, I've kept ~/SlackBuilds/n the way it is with alpine and php subdirectories.

== Configure PHP ==

Configuring PHP to use mcrypt is easy: add the line

&lt;code&gt;extension=mcrypt.so&lt;/code&gt;

to /etc/httpd/php.ini and then restart apache.  Now when you log in to PhpMyAdmin, you should no longer see the warning about mcrypt.</text>
    <sha1>ac181c7e0d3ea43b696be19446f8fc0abda8f6d4</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Bootsplash (old)</title>
  <ns>0</ns>
  <id>55</id>
  <revision>
    <id>255</id>
    <parentid>76</parentid>
    <timestamp>2009-10-06T13:30:13Z</timestamp>
    <contributor>
      <username>Fuli</username>
      <id>47</id>
    </contributor>
    <minor/>
    <comment>moved [[Bootsplash]] to [[Bootsplash (new)]]:&amp;#32;It had to be done some changes in the adding the splash to the initrd.gz section.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12340" xml:space="preserve">[[Category:Tutorials]]

== Prerequisites ==
* kernel source
* a bootsplash patch for your kernel version [http://www.stadtwald21.de/mcbeister/bootsplash/index.html] bootsplash patch.
* A bootsplash theme [http://kde-look.org/index.php?xcontentmode=61 kde-look themes]
* Bootsplash utilites [http://www.yzzerdd.net/slackware/files/bootsplash/bootsplash-3.1.tar.bz2 download]

== Setup ==
Start by patching and building a new kernel.

Assuming Stock kernel configuration/source. And all your downloads are in /home/username/Downloads.

  &lt;sub&gt; cd /usr/src/linux
        patch -p1&lt;/home/username/Downloads/bootsplash*.diff
        rm .config
        zcat /proc/config.gz &gt; .config
        make menuconfig&lt;/sub&gt;

   *Note: If you insist on using the generic kernel. And are currently using it.
        Check to see if the .config in your /usr/src/linux directory matches /proc/config.gz
          &lt;sub&gt; zdiff /proc/config.gz /usr/src/linux/.config &lt;/sub&gt;
        If they match, skip the "rm .config &amp;&amp; zcat ..." part above
        You'll also want to converge your initrd.gz and bootsplash's initrd. More on that below.

Edit these 2 options:

  &lt;sub&gt;  Device Drivers ---&gt;
             Graphics support ---&gt;
                  Logo configuration ---&gt;
                      [ ] Bootup logo
                  Bootsplash configuration ---&gt;
                      [*] Bootup splash screen&lt;/sub&gt;
* If you aren't using a stock kernel configuration, or on another distro check these settings whileyou are still in the kernel configuration dialog:
  &lt;sub&gt;&lt;nowiki&gt;  Device Drivers ---&gt;
            Block devices ---&gt;
                   &lt;*&gt; RAM disk support
            Graphics support ---&gt;
                   &lt;*&gt; Support for frame buffer devices&lt;/nowiki&gt;&lt;/sub&gt;
Now to make the patched kernel and install it

  &lt;sub&gt; make ; cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;
For slamd64, thats:
  &lt;sub&gt; make ; cp /usr/src/linux/arch/x86_64/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;

On to making a new bootsplash initrd.
Compile and install the splash utility.
  &lt;sub&gt; cd /home/username/Downloads
        tar xf bootsplash-3.0.7.tar.bz2
        cd bootsplash-3.0.7/Utilities/
        make splash
        cp splash /usr/bin/ &lt;/sub&gt;
And use it to build your new initrd.
Untar the theme file you downloaded, and check to see if it has a config directory and an image/s directory.
Look in the config directory for an appropriately sized config file (usually bootsplash-1024x768.cfg).
Edit this file, changing the directory it looks for images in (jpeg= option and silentjpeg= option) to point to the correct directory of the images for that theme. Example: /home/username/Downloads/bootsplashtheme/images/foo-bar.jpg
Finish by making the initrd with splash:
  &lt;sub&gt; splash -s -f /home/username/Downloads/bootsplashtheme/config/bootsplash-1024x768.cfg &gt;&gt; /boot/initrd.splash &lt;/sub&gt;
    For generic kernel users, you'll have to converge your stock initrd.gz and the bootsplash initrds.
       &lt;sub&gt;mkinitrd
            cp /boot/initrd.splash /boot/initrd-tree/
       &lt;/sub&gt;
After putting the initrd-splash into the mkinitrd's initrd-tree you'll need to run mkinitrd again with some computer specific options. Example:
      &lt;sub&gt;mkinitrd -c -m reiserfs&lt;/sub&gt;
Remember to do this every time you make a new initrd.splash.
Now edit /etc/lilo.conf with your favorite editor, adding the new kernel and bootsplash options.
Sample:
  &lt;sub&gt; boot = /dev/hda
        message = /boot/boot_message.txt
        prompt
        timeout = 300
        change-rules
         reset
        vga = 791
        image = /boot/vmlinuz
          root = /dev/hda1
          label = Linux
          read-only
        image = /boot/vmlinuz-bootsplash
          root = /dev/hda1
          label = Bootsplash
          initrd=/boot/initrd.splash
          append="splash=silent" &lt;/sub&gt;
Substitue "initrd=/boot/initrd.gz" if you had to run mkinitrd for a generic kernel, then run lilo to update and you're set.
  &lt;sub&gt;root@slackware:~# lilo
       Added Linux
       Added Bootsplash &lt;/sub&gt;
Now you can Reboot to test everything. If boot fails for some reason. You still have your stock kernel and entry in lilo to boot into without worries.

== Progressbar - rc.progress ==
Theres no set way to do this, you just need init to update /proc/splash correctly.
The way I do it (with help from LinuxQuestiosn forums):
create a new file in /etc/rc.d/ named rc.progress
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.progress &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
#rc.progress  This file has a common subroutine used to update a
#             bootsplash progress bar.
#

# Count the number of times the progress bar is likely to gbe increased
numu=$((`cat /etc/rc.d/rc.* | grep -c "^progressup"`));
numd=$((`cat /etc/rc.d/rc.* | grep -c "^progressdown"`));

function progressup(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress+1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numu ))" &gt; /proc/splash
}

function progressdown(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress-1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numd ))" &gt; /proc/splash
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.progress &lt;/sub&gt;
The . tells your system to include the functionality described in /etc/rc.d/rc.progress.
Now scroll through and add "progressup" (the defined trigger in rc.progress) on a new line
at the end of every subroutine where you want the progressbar to incriment up.
Example section of my rc.S:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.S:  System initialization script.
#
# Mostly written by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.progress
PATH=/sbin:/usr/sbin:/bin:/usr/bin

# Mount /proc right away: 
  &lt;/nowiki&gt;&lt;/sub&gt;
Don't add progressup till after your partition is mounted read/write
it'll be at the end of a long segment of echo .. echo.. echo like this.
  &lt;sub&gt;&lt;nowiki&gt;  echo -n "Press ENTER to continue. "
  read junk;
fi # Done checking root filesystem
progressup
  &lt;/nowiki&gt;&lt;/sub&gt;
Do the same for /etc/rc.d/rc.6 adding progressdown instead of progressup.
After you've finished that, you need to delete your temporary progressbar output cache.
Since rc.local is run last during startup, it's best to accomplish this here.
Edit rc.local:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

rm -fr /var/run/progressbar &lt;/nowiki&gt;&lt;/sub&gt;

== Progressbar - rc.bootsplash ==
An alternate script can also be used if you should have problems implementing the rc.progress script.
In my case the prior script was not able to delete its progressbar file, and adding progressdown entries to rc.6 resulted in odd behaviors even during bootup when rc.6 should not of been a factor. 
Create a new file in /etc/rc.d/ named rc.bootsplash
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.bootsplash &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# /etc/rc.d/rc.bootsplash: bootsplash functions.
# This file does nothing if run, and is called by other rc.
# files in order to make the progress bar and animations works.

function progressbar()
{
        if [ $# != 1 ]
                then
                echo "Usage: progressbar {progress}"
                exit 1
        fi
        if [ -a /proc/splash ] ; then
                echo "show $(( 65534 * $1 / 100 ))" &gt; /proc/splash
        fi
}
#
function animate()
{
        if [ $# = 0 ]
                then
                echo "Usage: animate {hook}"
                exit 1
        fi
        splash "$*"
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.bootsplash &lt;/sub&gt;
Now scroll through and add "progressbar X" (where X is a number representing the percent to incriment to) on a new line
at the end of every subroutine where you want the progressbar to incriment up. 0 is not a valid incriment. Only 1 - 100 are valid. 

Example rc.S
  &lt;sub&gt;&lt;nowiki&gt;
# Scan for new volume groups:
  /sbin/vgscan --mknodes --ignorelockingfailure 2&gt; /dev/null
  if [ $? = 0 ]; then
    # Make volume groups available to the kernel.
    # This should also make logical volumes available.
    /sbin/vgchange -ay --ignorelockingfailure
  fi
fi
progressbar 5

# Open any volumes created by cryptsetup:
if [ -f /etc/crypttab -a -x /sbin/cryptsetup.static ]; then
  # First, check for device-mapper support.
  if ! grep -wq device-mapper /proc/devices ; then
    # If device-mapper exists as a module, try to load it.
    # Try to load a device-mapper kernel module:
    /sbin/modprobe -q dm-mod
  fi
  cat /etc/crypttab | grep -v "^#" | grep -v "^$" | while read line; do
    LUKS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f1 -d' ')
    DEV=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f2 -d' ')
    PASS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f3 -d' ')
    OPTS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f4 -d' ')
    LUKSOPTS=""
    if echo $OPTS | grep -wq ro ; then LUKSOPTS="${LUKSOPTS} --readonly" ; fi

    # NOTE: we only support LUKS formatted volumes (except for swap)!
    if /sbin/cryptsetup.static isLuks $DEV 2&gt;/dev/null ; then
      echo "Unlocking LUKS crypt volume '${LUKS}' on device '$DEV':"
      if [ -n "${PASS}" ]; then
        if [ -f ${PASS} ]; then
          /sbin/cryptsetup.static ${LUKSOPTS} --key-file=${PASS} luksOpen $DEV $LUKS
        elif [ "${PASS}" != "none" ]; then
          echo "${PASS}" | /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS
        fi
      else
        for i in seq 1 3 ; do
          /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS &lt;/dev/tty0 &gt;/dev/tty0 2&gt;&amp;1
          [ $? -eq 0 ] &amp;&amp; break
        done
      fi
    elif echo $OPTS | grep -wq swap ; then
      # If any of the volumes is to be used as encrypted swap,
      # then encrypt it using a random key and run mkswap:
      echo "Creating encrypted swap on device '$DEV' mapped to '${LUKS}':"
      /sbin/cryptsetup.static --cipher=aes --key-file=/dev/urandom --key-size=256 create $LUKS $DEV
      mkswap /dev/mapper/$LUKS
    fi
  done
fi

# Enable swapping:
/sbin/swapon -a
progressbar 10
&lt;/nowiki&gt;&lt;/sub&gt;

Continue adding "progressbar X" entries in both rc.S and rc.M

Do the same for rc.6 but instead incrimenting down 'X'. 

Example rc.6
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# rc.6          This file is executed by init when it goes into runlevel
#               0 (halt) or runlevel 6 (reboot). It kills all processes,
#               unmounts file systems and then either halts or reboots.
#
# Version:      @(#)/etc/rc.d/rc.6      2.47 Sat Jan 13 13:37:26 PST 2001
#
# Author:       Miquel van Smoorenburg &lt;miquels@drinkel.nl.mugnet.org&gt;
# Modified by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.bootsplash

# Set the path.
PATH=/sbin:/etc:/bin:/usr/bin
progressbar 100

# If there are SystemV init scripts for this runlevel, run them.
if [ -x /etc/rc.d/rc.sysvinit ]; then
  . /etc/rc.d/rc.sysvinit
fi
progressbar 90

# Set linefeed mode to avoid staircase effect.
/bin/stty onlcr

echo "Running shutdown script $0:"

# Find out how we were called.
case "$0" in
        *0)
                command="halt"
                ;;
        *6)
                command=reboot
                ;;
        *)
                echo "$0: call me as \"rc.0\" or \"rc.6\" please!"
                exit 1
                ;;
esac

# Save the system time to the hardware clock using hwclock --systohc.
if [ -x /sbin/hwclock ]; then
  # Check for a broken motherboard RTC clock (where ioports for rtc are
  # unknown) to prevent hwclock causing a hang:
  if ! grep -q -w rtc /proc/ioports ; then
    CLOCK_OPT="--directisa"
  fi
  if grep -q "^UTC" /etc/hardwareclock 2&gt; /dev/null ; then
    echo "Saving system time to the hardware clock (UTC)."
    /sbin/hwclock $CLOCK_OPT --utc --systohc
  else
    echo "Saving system time to the hardware clock (localtime)."
    /sbin/hwclock  $CLOCK_OPT --localtime --systohc
  fi
fi
progressbar 80
&lt;/nowiki&gt;&lt;/sub&gt;</text>
    <sha1>6d57a57211dc8013b3497e5c44ab1d5c10ddc57c</sha1>
  </revision>
  <revision>
    <id>257</id>
    <parentid>255</parentid>
    <timestamp>2009-10-06T13:34:00Z</timestamp>
    <contributor>
      <username>Fuli</username>
      <id>47</id>
    </contributor>
    <minor/>
    <comment>moved [[Bootsplash (new)]] to [[Bootsplash (old)]]:&amp;#32;It had to be done some changes in the adding the splash to the initrd.gz section.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12340" xml:space="preserve">[[Category:Tutorials]]

== Prerequisites ==
* kernel source
* a bootsplash patch for your kernel version [http://www.stadtwald21.de/mcbeister/bootsplash/index.html] bootsplash patch.
* A bootsplash theme [http://kde-look.org/index.php?xcontentmode=61 kde-look themes]
* Bootsplash utilites [http://www.yzzerdd.net/slackware/files/bootsplash/bootsplash-3.1.tar.bz2 download]

== Setup ==
Start by patching and building a new kernel.

Assuming Stock kernel configuration/source. And all your downloads are in /home/username/Downloads.

  &lt;sub&gt; cd /usr/src/linux
        patch -p1&lt;/home/username/Downloads/bootsplash*.diff
        rm .config
        zcat /proc/config.gz &gt; .config
        make menuconfig&lt;/sub&gt;

   *Note: If you insist on using the generic kernel. And are currently using it.
        Check to see if the .config in your /usr/src/linux directory matches /proc/config.gz
          &lt;sub&gt; zdiff /proc/config.gz /usr/src/linux/.config &lt;/sub&gt;
        If they match, skip the "rm .config &amp;&amp; zcat ..." part above
        You'll also want to converge your initrd.gz and bootsplash's initrd. More on that below.

Edit these 2 options:

  &lt;sub&gt;  Device Drivers ---&gt;
             Graphics support ---&gt;
                  Logo configuration ---&gt;
                      [ ] Bootup logo
                  Bootsplash configuration ---&gt;
                      [*] Bootup splash screen&lt;/sub&gt;
* If you aren't using a stock kernel configuration, or on another distro check these settings whileyou are still in the kernel configuration dialog:
  &lt;sub&gt;&lt;nowiki&gt;  Device Drivers ---&gt;
            Block devices ---&gt;
                   &lt;*&gt; RAM disk support
            Graphics support ---&gt;
                   &lt;*&gt; Support for frame buffer devices&lt;/nowiki&gt;&lt;/sub&gt;
Now to make the patched kernel and install it

  &lt;sub&gt; make ; cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;
For slamd64, thats:
  &lt;sub&gt; make ; cp /usr/src/linux/arch/x86_64/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;

On to making a new bootsplash initrd.
Compile and install the splash utility.
  &lt;sub&gt; cd /home/username/Downloads
        tar xf bootsplash-3.0.7.tar.bz2
        cd bootsplash-3.0.7/Utilities/
        make splash
        cp splash /usr/bin/ &lt;/sub&gt;
And use it to build your new initrd.
Untar the theme file you downloaded, and check to see if it has a config directory and an image/s directory.
Look in the config directory for an appropriately sized config file (usually bootsplash-1024x768.cfg).
Edit this file, changing the directory it looks for images in (jpeg= option and silentjpeg= option) to point to the correct directory of the images for that theme. Example: /home/username/Downloads/bootsplashtheme/images/foo-bar.jpg
Finish by making the initrd with splash:
  &lt;sub&gt; splash -s -f /home/username/Downloads/bootsplashtheme/config/bootsplash-1024x768.cfg &gt;&gt; /boot/initrd.splash &lt;/sub&gt;
    For generic kernel users, you'll have to converge your stock initrd.gz and the bootsplash initrds.
       &lt;sub&gt;mkinitrd
            cp /boot/initrd.splash /boot/initrd-tree/
       &lt;/sub&gt;
After putting the initrd-splash into the mkinitrd's initrd-tree you'll need to run mkinitrd again with some computer specific options. Example:
      &lt;sub&gt;mkinitrd -c -m reiserfs&lt;/sub&gt;
Remember to do this every time you make a new initrd.splash.
Now edit /etc/lilo.conf with your favorite editor, adding the new kernel and bootsplash options.
Sample:
  &lt;sub&gt; boot = /dev/hda
        message = /boot/boot_message.txt
        prompt
        timeout = 300
        change-rules
         reset
        vga = 791
        image = /boot/vmlinuz
          root = /dev/hda1
          label = Linux
          read-only
        image = /boot/vmlinuz-bootsplash
          root = /dev/hda1
          label = Bootsplash
          initrd=/boot/initrd.splash
          append="splash=silent" &lt;/sub&gt;
Substitue "initrd=/boot/initrd.gz" if you had to run mkinitrd for a generic kernel, then run lilo to update and you're set.
  &lt;sub&gt;root@slackware:~# lilo
       Added Linux
       Added Bootsplash &lt;/sub&gt;
Now you can Reboot to test everything. If boot fails for some reason. You still have your stock kernel and entry in lilo to boot into without worries.

== Progressbar - rc.progress ==
Theres no set way to do this, you just need init to update /proc/splash correctly.
The way I do it (with help from LinuxQuestiosn forums):
create a new file in /etc/rc.d/ named rc.progress
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.progress &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
#rc.progress  This file has a common subroutine used to update a
#             bootsplash progress bar.
#

# Count the number of times the progress bar is likely to gbe increased
numu=$((`cat /etc/rc.d/rc.* | grep -c "^progressup"`));
numd=$((`cat /etc/rc.d/rc.* | grep -c "^progressdown"`));

function progressup(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress+1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numu ))" &gt; /proc/splash
}

function progressdown(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress-1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numd ))" &gt; /proc/splash
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.progress &lt;/sub&gt;
The . tells your system to include the functionality described in /etc/rc.d/rc.progress.
Now scroll through and add "progressup" (the defined trigger in rc.progress) on a new line
at the end of every subroutine where you want the progressbar to incriment up.
Example section of my rc.S:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.S:  System initialization script.
#
# Mostly written by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.progress
PATH=/sbin:/usr/sbin:/bin:/usr/bin

# Mount /proc right away: 
  &lt;/nowiki&gt;&lt;/sub&gt;
Don't add progressup till after your partition is mounted read/write
it'll be at the end of a long segment of echo .. echo.. echo like this.
  &lt;sub&gt;&lt;nowiki&gt;  echo -n "Press ENTER to continue. "
  read junk;
fi # Done checking root filesystem
progressup
  &lt;/nowiki&gt;&lt;/sub&gt;
Do the same for /etc/rc.d/rc.6 adding progressdown instead of progressup.
After you've finished that, you need to delete your temporary progressbar output cache.
Since rc.local is run last during startup, it's best to accomplish this here.
Edit rc.local:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

rm -fr /var/run/progressbar &lt;/nowiki&gt;&lt;/sub&gt;

== Progressbar - rc.bootsplash ==
An alternate script can also be used if you should have problems implementing the rc.progress script.
In my case the prior script was not able to delete its progressbar file, and adding progressdown entries to rc.6 resulted in odd behaviors even during bootup when rc.6 should not of been a factor. 
Create a new file in /etc/rc.d/ named rc.bootsplash
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.bootsplash &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# /etc/rc.d/rc.bootsplash: bootsplash functions.
# This file does nothing if run, and is called by other rc.
# files in order to make the progress bar and animations works.

function progressbar()
{
        if [ $# != 1 ]
                then
                echo "Usage: progressbar {progress}"
                exit 1
        fi
        if [ -a /proc/splash ] ; then
                echo "show $(( 65534 * $1 / 100 ))" &gt; /proc/splash
        fi
}
#
function animate()
{
        if [ $# = 0 ]
                then
                echo "Usage: animate {hook}"
                exit 1
        fi
        splash "$*"
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.bootsplash &lt;/sub&gt;
Now scroll through and add "progressbar X" (where X is a number representing the percent to incriment to) on a new line
at the end of every subroutine where you want the progressbar to incriment up. 0 is not a valid incriment. Only 1 - 100 are valid. 

Example rc.S
  &lt;sub&gt;&lt;nowiki&gt;
# Scan for new volume groups:
  /sbin/vgscan --mknodes --ignorelockingfailure 2&gt; /dev/null
  if [ $? = 0 ]; then
    # Make volume groups available to the kernel.
    # This should also make logical volumes available.
    /sbin/vgchange -ay --ignorelockingfailure
  fi
fi
progressbar 5

# Open any volumes created by cryptsetup:
if [ -f /etc/crypttab -a -x /sbin/cryptsetup.static ]; then
  # First, check for device-mapper support.
  if ! grep -wq device-mapper /proc/devices ; then
    # If device-mapper exists as a module, try to load it.
    # Try to load a device-mapper kernel module:
    /sbin/modprobe -q dm-mod
  fi
  cat /etc/crypttab | grep -v "^#" | grep -v "^$" | while read line; do
    LUKS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f1 -d' ')
    DEV=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f2 -d' ')
    PASS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f3 -d' ')
    OPTS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f4 -d' ')
    LUKSOPTS=""
    if echo $OPTS | grep -wq ro ; then LUKSOPTS="${LUKSOPTS} --readonly" ; fi

    # NOTE: we only support LUKS formatted volumes (except for swap)!
    if /sbin/cryptsetup.static isLuks $DEV 2&gt;/dev/null ; then
      echo "Unlocking LUKS crypt volume '${LUKS}' on device '$DEV':"
      if [ -n "${PASS}" ]; then
        if [ -f ${PASS} ]; then
          /sbin/cryptsetup.static ${LUKSOPTS} --key-file=${PASS} luksOpen $DEV $LUKS
        elif [ "${PASS}" != "none" ]; then
          echo "${PASS}" | /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS
        fi
      else
        for i in seq 1 3 ; do
          /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS &lt;/dev/tty0 &gt;/dev/tty0 2&gt;&amp;1
          [ $? -eq 0 ] &amp;&amp; break
        done
      fi
    elif echo $OPTS | grep -wq swap ; then
      # If any of the volumes is to be used as encrypted swap,
      # then encrypt it using a random key and run mkswap:
      echo "Creating encrypted swap on device '$DEV' mapped to '${LUKS}':"
      /sbin/cryptsetup.static --cipher=aes --key-file=/dev/urandom --key-size=256 create $LUKS $DEV
      mkswap /dev/mapper/$LUKS
    fi
  done
fi

# Enable swapping:
/sbin/swapon -a
progressbar 10
&lt;/nowiki&gt;&lt;/sub&gt;

Continue adding "progressbar X" entries in both rc.S and rc.M

Do the same for rc.6 but instead incrimenting down 'X'. 

Example rc.6
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# rc.6          This file is executed by init when it goes into runlevel
#               0 (halt) or runlevel 6 (reboot). It kills all processes,
#               unmounts file systems and then either halts or reboots.
#
# Version:      @(#)/etc/rc.d/rc.6      2.47 Sat Jan 13 13:37:26 PST 2001
#
# Author:       Miquel van Smoorenburg &lt;miquels@drinkel.nl.mugnet.org&gt;
# Modified by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.bootsplash

# Set the path.
PATH=/sbin:/etc:/bin:/usr/bin
progressbar 100

# If there are SystemV init scripts for this runlevel, run them.
if [ -x /etc/rc.d/rc.sysvinit ]; then
  . /etc/rc.d/rc.sysvinit
fi
progressbar 90

# Set linefeed mode to avoid staircase effect.
/bin/stty onlcr

echo "Running shutdown script $0:"

# Find out how we were called.
case "$0" in
        *0)
                command="halt"
                ;;
        *6)
                command=reboot
                ;;
        *)
                echo "$0: call me as \"rc.0\" or \"rc.6\" please!"
                exit 1
                ;;
esac

# Save the system time to the hardware clock using hwclock --systohc.
if [ -x /sbin/hwclock ]; then
  # Check for a broken motherboard RTC clock (where ioports for rtc are
  # unknown) to prevent hwclock causing a hang:
  if ! grep -q -w rtc /proc/ioports ; then
    CLOCK_OPT="--directisa"
  fi
  if grep -q "^UTC" /etc/hardwareclock 2&gt; /dev/null ; then
    echo "Saving system time to the hardware clock (UTC)."
    /sbin/hwclock $CLOCK_OPT --utc --systohc
  else
    echo "Saving system time to the hardware clock (localtime)."
    /sbin/hwclock  $CLOCK_OPT --localtime --systohc
  fi
fi
progressbar 80
&lt;/nowiki&gt;&lt;/sub&gt;</text>
    <sha1>6d57a57211dc8013b3497e5c44ab1d5c10ddc57c</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Bootsplash</title>
  <ns>0</ns>
  <id>192</id>
  <revision>
    <id>256</id>
    <timestamp>2009-10-06T13:30:13Z</timestamp>
    <contributor>
      <username>Fuli</username>
      <id>47</id>
    </contributor>
    <comment>moved [[Bootsplash]] to [[Bootsplash (new)]]:&amp;#32;It had to be done some changes in the adding the splash to the initrd.gz section.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="30" xml:space="preserve">#REDIRECT [[Bootsplash (new)]]</text>
    <sha1>5c8cb522f164c3d2eed340a067e0327a274bad5e</sha1>
  </revision>
  <revision>
    <id>259</id>
    <parentid>256</parentid>
    <timestamp>2009-10-06T13:37:54Z</timestamp>
    <contributor>
      <username>Fuli</username>
      <id>47</id>
    </contributor>
    <comment>it was just a small change to correct the splash adding to initrd.gz info.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12309" xml:space="preserve">[[Category:Tutorials]]

== Prerequisites ==
* kernel source
* a bootsplash patch for your kernel version [http://www.stadtwald21.de/mcbeister/bootsplash/index.html] bootsplash patch.
* A bootsplash theme [http://kde-look.org/index.php?xcontentmode=61 kde-look themes]
* Bootsplash utilites [http://www.yzzerdd.net/slackware/files/bootsplash/bootsplash-3.1.tar.bz2 download]

== Setup ==
Start by patching and building a new kernel.

Assuming Stock kernel configuration/source. And all your downloads are in /home/username/Downloads.

  &lt;sub&gt; cd /usr/src/linux
        patch -p1&lt;/home/username/Downloads/bootsplash*.diff
        rm .config
        zcat /proc/config.gz &gt; .config
        make menuconfig&lt;/sub&gt;

   *Note: If you insist on using the generic kernel. And are currently using it.
        Check to see if the .config in your /usr/src/linux directory matches /proc/config.gz
          &lt;sub&gt; zdiff /proc/config.gz /usr/src/linux/.config &lt;/sub&gt;
        If they match, skip the "rm .config &amp;&amp; zcat ..." part above
        You'll also want to converge your initrd.gz and bootsplash's initrd. More on that below.

Edit these 2 options:

  &lt;sub&gt;  Device Drivers ---&gt;
             Graphics support ---&gt;
                  Logo configuration ---&gt;
                      [ ] Bootup logo
                  Bootsplash configuration ---&gt;
                      [*] Bootup splash screen&lt;/sub&gt;
* If you aren't using a stock kernel configuration, or on another distro check these settings whileyou are still in the kernel configuration dialog:
  &lt;sub&gt;&lt;nowiki&gt;  Device Drivers ---&gt;
            Block devices ---&gt;
                   &lt;*&gt; RAM disk support
            Graphics support ---&gt;
                   &lt;*&gt; Support for frame buffer devices&lt;/nowiki&gt;&lt;/sub&gt;
Now to make the patched kernel and install it

  &lt;sub&gt; make ; cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;
For slamd64, thats:
  &lt;sub&gt; make ; cp /usr/src/linux/arch/x86_64/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;

On to making a new bootsplash initrd.
Compile and install the splash utility.
  &lt;sub&gt; cd /home/username/Downloads
        tar xf bootsplash-3.0.7.tar.bz2
        cd bootsplash-3.0.7/Utilities/
        make splash
        cp splash /usr/bin/ &lt;/sub&gt;
And use it to build your new initrd.
Untar the theme file you downloaded, and check to see if it has a config directory and an image/s directory.
Look in the config directory for an appropriately sized config file (usually bootsplash-1024x768.cfg).
Edit this file, changing the directory it looks for images in (jpeg= option and silentjpeg= option) to point to the correct directory of the images for that theme. Example: /home/username/Downloads/bootsplashtheme/images/foo-bar.jpg
Finish by making the initrd with splash:
  &lt;sub&gt; splash -s -f /home/username/Downloads/bootsplashtheme/config/bootsplash-1024x768.cfg &gt;&gt; /boot/initrd.splash &lt;/sub&gt;
    For generic kernel users, you'll have to converge your stock initrd.gz and the bootsplash initrds.
For example:
      &lt;sub&gt;mkinitrd -c -m reiserfs&lt;/sub&gt;
      &lt;sub&gt;
            cp /boot/initrd.splash /boot/initrd-tree/bootsplash
      &lt;/sub&gt;
After putting the initrd-splash into the mkinitrd's initrd-tree you'll need to run mkinitrd again.

Remember to do this every time you make a new initrd.splash.
Now edit /etc/lilo.conf with your favorite editor, adding the new kernel and bootsplash options.
Sample:
  &lt;sub&gt; boot = /dev/hda
        message = /boot/boot_message.txt
        prompt
        timeout = 300
        change-rules
         reset
        vga = 791
        image = /boot/vmlinuz
          root = /dev/hda1
          label = Linux
          read-only
        image = /boot/vmlinuz-bootsplash
          root = /dev/hda1
          label = Bootsplash
          initrd=/boot/initrd.splash
          append="splash=silent" &lt;/sub&gt;
Substitue "initrd=/boot/initrd.gz" if you had to run mkinitrd for a generic kernel, then run lilo to update and you're set.
  &lt;sub&gt;root@slackware:~# lilo
       Added Linux
       Added Bootsplash &lt;/sub&gt;
Now you can Reboot to test everything. If boot fails for some reason. You still have your stock kernel and entry in lilo to boot into without worries.

== Progressbar - rc.progress ==
Theres no set way to do this, you just need init to update /proc/splash correctly.
The way I do it (with help from LinuxQuestiosn forums):
create a new file in /etc/rc.d/ named rc.progress
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.progress &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
#rc.progress  This file has a common subroutine used to update a
#             bootsplash progress bar.
#

# Count the number of times the progress bar is likely to gbe increased
numu=$((`cat /etc/rc.d/rc.* | grep -c "^progressup"`));
numd=$((`cat /etc/rc.d/rc.* | grep -c "^progressdown"`));

function progressup(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress+1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numu ))" &gt; /proc/splash
}

function progressdown(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress-1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numd ))" &gt; /proc/splash
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.progress &lt;/sub&gt;
The . tells your system to include the functionality described in /etc/rc.d/rc.progress.
Now scroll through and add "progressup" (the defined trigger in rc.progress) on a new line
at the end of every subroutine where you want the progressbar to incriment up.
Example section of my rc.S:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.S:  System initialization script.
#
# Mostly written by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.progress
PATH=/sbin:/usr/sbin:/bin:/usr/bin

# Mount /proc right away: 
  &lt;/nowiki&gt;&lt;/sub&gt;
Don't add progressup till after your partition is mounted read/write
it'll be at the end of a long segment of echo .. echo.. echo like this.
  &lt;sub&gt;&lt;nowiki&gt;  echo -n "Press ENTER to continue. "
  read junk;
fi # Done checking root filesystem
progressup
  &lt;/nowiki&gt;&lt;/sub&gt;
Do the same for /etc/rc.d/rc.6 adding progressdown instead of progressup.
After you've finished that, you need to delete your temporary progressbar output cache.
Since rc.local is run last during startup, it's best to accomplish this here.
Edit rc.local:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

rm -fr /var/run/progressbar &lt;/nowiki&gt;&lt;/sub&gt;

== Progressbar - rc.bootsplash ==
An alternate script can also be used if you should have problems implementing the rc.progress script.
In my case the prior script was not able to delete its progressbar file, and adding progressdown entries to rc.6 resulted in odd behaviors even during bootup when rc.6 should not of been a factor. 
Create a new file in /etc/rc.d/ named rc.bootsplash
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.bootsplash &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# /etc/rc.d/rc.bootsplash: bootsplash functions.
# This file does nothing if run, and is called by other rc.
# files in order to make the progress bar and animations works.

function progressbar()
{
        if [ $# != 1 ]
                then
                echo "Usage: progressbar {progress}"
                exit 1
        fi
        if [ -a /proc/splash ] ; then
                echo "show $(( 65534 * $1 / 100 ))" &gt; /proc/splash
        fi
}
#
function animate()
{
        if [ $# = 0 ]
                then
                echo "Usage: animate {hook}"
                exit 1
        fi
        splash "$*"
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.bootsplash &lt;/sub&gt;
Now scroll through and add "progressbar X" (where X is a number representing the percent to incriment to) on a new line
at the end of every subroutine where you want the progressbar to incriment up. 0 is not a valid incriment. Only 1 - 100 are valid. 

Example rc.S
  &lt;sub&gt;&lt;nowiki&gt;
# Scan for new volume groups:
  /sbin/vgscan --mknodes --ignorelockingfailure 2&gt; /dev/null
  if [ $? = 0 ]; then
    # Make volume groups available to the kernel.
    # This should also make logical volumes available.
    /sbin/vgchange -ay --ignorelockingfailure
  fi
fi
progressbar 5

# Open any volumes created by cryptsetup:
if [ -f /etc/crypttab -a -x /sbin/cryptsetup.static ]; then
  # First, check for device-mapper support.
  if ! grep -wq device-mapper /proc/devices ; then
    # If device-mapper exists as a module, try to load it.
    # Try to load a device-mapper kernel module:
    /sbin/modprobe -q dm-mod
  fi
  cat /etc/crypttab | grep -v "^#" | grep -v "^$" | while read line; do
    LUKS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f1 -d' ')
    DEV=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f2 -d' ')
    PASS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f3 -d' ')
    OPTS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f4 -d' ')
    LUKSOPTS=""
    if echo $OPTS | grep -wq ro ; then LUKSOPTS="${LUKSOPTS} --readonly" ; fi

    # NOTE: we only support LUKS formatted volumes (except for swap)!
    if /sbin/cryptsetup.static isLuks $DEV 2&gt;/dev/null ; then
      echo "Unlocking LUKS crypt volume '${LUKS}' on device '$DEV':"
      if [ -n "${PASS}" ]; then
        if [ -f ${PASS} ]; then
          /sbin/cryptsetup.static ${LUKSOPTS} --key-file=${PASS} luksOpen $DEV $LUKS
        elif [ "${PASS}" != "none" ]; then
          echo "${PASS}" | /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS
        fi
      else
        for i in seq 1 3 ; do
          /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS &lt;/dev/tty0 &gt;/dev/tty0 2&gt;&amp;1
          [ $? -eq 0 ] &amp;&amp; break
        done
      fi
    elif echo $OPTS | grep -wq swap ; then
      # If any of the volumes is to be used as encrypted swap,
      # then encrypt it using a random key and run mkswap:
      echo "Creating encrypted swap on device '$DEV' mapped to '${LUKS}':"
      /sbin/cryptsetup.static --cipher=aes --key-file=/dev/urandom --key-size=256 create $LUKS $DEV
      mkswap /dev/mapper/$LUKS
    fi
  done
fi

# Enable swapping:
/sbin/swapon -a
progressbar 10
&lt;/nowiki&gt;&lt;/sub&gt;

Continue adding "progressbar X" entries in both rc.S and rc.M

Do the same for rc.6 but instead incrimenting down 'X'. 

Example rc.6
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# rc.6          This file is executed by init when it goes into runlevel
#               0 (halt) or runlevel 6 (reboot). It kills all processes,
#               unmounts file systems and then either halts or reboots.
#
# Version:      @(#)/etc/rc.d/rc.6      2.47 Sat Jan 13 13:37:26 PST 2001
#
# Author:       Miquel van Smoorenburg &lt;miquels@drinkel.nl.mugnet.org&gt;
# Modified by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.bootsplash

# Set the path.
PATH=/sbin:/etc:/bin:/usr/bin
progressbar 100

# If there are SystemV init scripts for this runlevel, run them.
if [ -x /etc/rc.d/rc.sysvinit ]; then
  . /etc/rc.d/rc.sysvinit
fi
progressbar 90

# Set linefeed mode to avoid staircase effect.
/bin/stty onlcr

echo "Running shutdown script $0:"

# Find out how we were called.
case "$0" in
        *0)
                command="halt"
                ;;
        *6)
                command=reboot
                ;;
        *)
                echo "$0: call me as \"rc.0\" or \"rc.6\" please!"
                exit 1
                ;;
esac

# Save the system time to the hardware clock using hwclock --systohc.
if [ -x /sbin/hwclock ]; then
  # Check for a broken motherboard RTC clock (where ioports for rtc are
  # unknown) to prevent hwclock causing a hang:
  if ! grep -q -w rtc /proc/ioports ; then
    CLOCK_OPT="--directisa"
  fi
  if grep -q "^UTC" /etc/hardwareclock 2&gt; /dev/null ; then
    echo "Saving system time to the hardware clock (UTC)."
    /sbin/hwclock $CLOCK_OPT --utc --systohc
  else
    echo "Saving system time to the hardware clock (localtime)."
    /sbin/hwclock  $CLOCK_OPT --localtime --systohc
  fi
fi
progressbar 80
&lt;/nowiki&gt;&lt;/sub&gt;</text>
    <sha1>36488c030ff4c0a5b90539c6bda058f21ffeb37e</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Bootsplash (new)</title>
  <ns>0</ns>
  <id>193</id>
  <revision>
    <id>258</id>
    <timestamp>2009-10-06T13:34:00Z</timestamp>
    <contributor>
      <username>Fuli</username>
      <id>47</id>
    </contributor>
    <comment>moved [[Bootsplash (new)]] to [[Bootsplash (old)]]:&amp;#32;It had to be done some changes in the adding the splash to the initrd.gz section.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="30" xml:space="preserve">#REDIRECT [[Bootsplash (old)]]</text>
    <sha1>be06724b14e543d85a2a288c2e7308c86d5a3adb</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>User:Slakmagik</title>
  <ns>2</ns>
  <id>195</id>
  <revision>
    <id>261</id>
    <timestamp>2009-10-11T04:55:19Z</timestamp>
    <contributor>
      <username>Slakmagik</username>
      <id>49</id>
    </contributor>
    <comment>Created page with 'Dedicated [http://slackware.com/ Slackware] user.&lt;br/&gt; Maintainer of a few [http://slackbuilds.org/ SlackBuilds].&lt;br/&gt; Member of the [http://www.sbopkg.org/ sbopkg] project.  Can...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="263" xml:space="preserve">Dedicated [http://slackware.com/ Slackware] user.&lt;br/&gt;
Maintainer of a few [http://slackbuilds.org/ SlackBuilds].&lt;br/&gt;
Member of the [http://www.sbopkg.org/ sbopkg] project.

Can often be found in ##slackware, #slackbuilds, and #sbopkg on freenode as 'slakmagik'.</text>
    <sha1>031144f64c82a27f1fd22fc7caa865f37cd26266</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>User:Erik</title>
  <ns>2</ns>
  <id>2</id>
  <revision>
    <id>262</id>
    <parentid>4</parentid>
    <timestamp>2009-10-18T13:01:17Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="268" xml:space="preserve">Real Name: Erik Hanson&lt;br&gt;
Web: [http://slackbuilds.org/~erik/ http://slackbuilds.org/~erik/]&lt;br&gt;
EMail: [mailto:erik@slackbuilds.org erik@slackbuilds.org]&lt;br&gt;
IRC: erik @ [irc://frop.taphouse.org/ Taphouse Cabal] and [irc://chat.freenode.net The Freenode Network]&lt;br&gt;</text>
    <sha1>bc3e84a0de1b3a214bc06162bddf8b1cf074875b</sha1>
  </revision>
  <revision>
    <id>301</id>
    <parentid>262</parentid>
    <timestamp>2010-02-25T00:53:12Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="231" xml:space="preserve">Name: [mailto:erik@slackbuilds.org Erik Hanson]&lt;br&gt;
Web: [http://slackbuilds.org/~erik/ http://slackbuilds.org/~erik/]&lt;br&gt;
IRC: erik @ [irc://frop.taphouse.org/ Taphouse Cabal] and [irc://chat.freenode.net The Freenode Network]&lt;br&gt;</text>
    <sha1>51cb2648a05bed1d6cb560e82ced7cb09c0c61ac</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>263</id>
    <parentid>209</parentid>
    <timestamp>2009-11-03T06:06:25Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Noted registration lapse</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3438" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>6b3b81a3a9d0d4d69d7c37ee6df9263adf3cfe14</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>3ware 3DM2</title>
  <ns>0</ns>
  <id>34</id>
  <revision>
    <id>264</id>
    <parentid>55</parentid>
    <timestamp>2009-11-23T04:40:43Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <comment>typographical fixes</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5076" xml:space="preserve">[[Category:Tutorials]]
==3DM2==

3DM2 is 3ware's web-based interface for controlling and status checks for their RAID cards.  It contains a small web server that allows configuration and maintenance to the RAID array and provides status reports.  It has an email notification feature that reports RAID problems and glitches.


==Installing 3DM2 On A Slackware Box==
(written from a 3DM2 V9.3.0.7 and Slackware 11 perspective)

1) Gunzip and un-tar the 3DM2 archive.

2) As root, run &lt;code&gt;install.3dm install&lt;/code&gt; to install.

::This script does four things-

:::a) It complains that you aren't running RedHat or Suse and therefore will not automatically install the 3DM2 init scripts in the &lt;code&gt;/etc/rc.d&lt;/code&gt; directory.  You have to manually do this, this is explained later in this instruction.

:::b) It makes a &lt;code&gt;/tmp/3ware&lt;/code&gt; directory and decompresses the 3DM2 files there.

:::c) It copies the &lt;code&gt;3dm2&lt;/code&gt; binary to &lt;code&gt;/usr/sbin&lt;/code&gt;.

:::d) It makes a &lt;code&gt;/etc/3dm2&lt;/code&gt; directory.

::''NOTE: the &lt;code&gt;/tmp/3ware&lt;/code&gt; directory is NOT removed after install.  It is not necessary to keep but, you may want to keep the &lt;code&gt;install.3dm2&lt;/code&gt; binary in case you ever want to uninstall 3DM2.''

3) Edit &lt;code&gt;/etc/rc.d/rc.local&lt;/code&gt; and add the following line:
::&lt;code&gt;/usr/sbin/3dm2&lt;/code&gt;

4) ''If you are running a restrictive firewall'', open port 888.

5) Start 3DM2 by: &lt;code&gt;3dm2&lt;/code&gt;

6) Using a web browser, browse to your RAID machine, port 888.

::'''If your web-browser is on the same box as your RAID array'''- click here:[https://localhost:888 http'''s'''://localhost:888]

::'''If your web-browser is NOT on the same box as your RAID array'''-
::::a) Edit your &lt;code&gt;/etc/3dm2/3dm2.conf&lt;/code&gt; file and change the &lt;code&gt;RemoteAccess 0&lt;/code&gt; to &lt;code&gt;RemoteAccess 1&lt;/code&gt;
::::b) Browse to your machine using HTTPS and port 888-
::::::EXAMPLE: &lt;code&gt; https://192.186.1.2:888&lt;/code&gt;
::::::::or &lt;code&gt;https://server.mydomain.net:888&lt;/code&gt;

7) Once the web interface loads up, log in as ADMINISTRATOR (default password is "3ware") and complete the configuration.

8) To activate the help files, you'll need to copy them to the correct location.
::::a) View your /etc/3dm2/3dm2.conf file.  
::::b) Make a note of the Help entry.

9) Go to /tmp/3ware/.

10) Untar the file 3dm-help.tgz.  A directory corresponding to your language with all the help files in it will be created.  For this example (English), the directory was called en.

11) Copy the en directory into the location you made a note of in 8b above.  Copy the whole directory, not just the files inside the directory.

12) Now when you are logged in to the 3dm2 application inside a browser and you click on help, you will get the help screens.


--------------------------------------------------------------------------------------------
(written from a 3DM2-Linux-9.3.0.4 and Slackware '''12.0''' perspective)

Using the 3DM2-Linux-9.3.0.4 seems to be ideal for slackware.  I have it running on

 Slackware 10.2
 Slackware 11.0 (2.4 and 2.6 kernels)
 Slackware 12.0 (Defult 2.6 kernel)

with the following cards:

 7006-2 Series
 8006-2LP Serise
 9500S Series

The directions I found to work best are as follows.

  1a) Download 3DM2-Linux-9.3.0.4.tgz from:
  http://www.3ware.com/support/download.asp

  2a) Please select your 3ware product. = $YOUR_CARD_MODEL

  3a) Please Select Item = *LEAVE BLANK*

  4a) Latest = 9.3.0.4

  5a) Please select the item to download = 3DMD2 Management Utility

6a) Then select Linux as your OS, select 3DM2-Linux-9.3.0.4.tgz to download, read the EULA, and 
download somewhere reachable by your Linux OS.  For the sake of instructions, we'll say /usr/src/3ware.

01) cd /usr/src/3ware

02) tar xfvz 3DM2-Linux-9.3.0.4.tgz

03) run: ./install -i

This extracts files to: /tmp/3ware

...moves the appropriate binary to:
/usr/sbin/3dm2

...and creates the directory:
/etc/3dm2

Now we need to create another directory.  For the sake of instructions, we'll say /3ware/.

04) mkdir /3ware

05) run: cp -rf /tmp/3ware/* /3ware/

06) run: cp /usr/src/3ware/3dm-lnx.tgz /3ware/

07) run: cd /3ware

08) run: ./install

To the following questions, answer the defaults:

 Was RPM used to install the Escalade driver and/or 3dm?? (Y/N) [N]
 Please enter the location of the help documentation. [/usr/local/doc/3dm]

Now you will get what appears to be an error. "3dm binary missing. Installation stopping."  Don't worry, the binary file is already in place.  If you notice though, the /etc/3dm2 directory is empty.

09) run: /usr/sbin/3dm2

This will populate that directory with the default config file, that you may edit to your satisfaction.  If you leave the config file as is, you should be able to connect to your server from the local host at https://localhost:888 (*https* is very important).

In order to connect from another PC, edit /etc/3dmd2/3dmd2.conf line

 RemoteAccess 0
     to
 RemoteAccess 1

1b) run: killall 3dm2

2b) run: /usr/sbin/3dm2

 The default password for both "USER" and "ADMINISTRATOR" = "3ware"</text>
    <sha1>2a600d54d73bc13545f828cbe811be01f65a3393</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>OpenVPN(EN)</title>
  <ns>0</ns>
  <id>197</id>
  <revision>
    <id>266</id>
    <timestamp>2009-12-01T17:18:06Z</timestamp>
    <contributor>
      <username>Seekret</username>
      <id>59</id>
    </contributor>
    <comment>This is just an English version of the existing OpenVPN page.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14175" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.

__TOC__
== Installation ==

Download source from [http://openvpn.net openvpn.net]

Download verison 2.0

install Lzo
&lt;pre&gt;
tar zxvf lzo-1.08.tar.gz
cd lzo-1-08.tar.gz
./configure --prefix=/usr
make ; make install-strip
&lt;/pre&gt;
install OpenVPN
&lt;pre&gt;
tar zxvf openvpn-2.0.tar.gz
cd openvpn-2.0
./configure --prefix=/usr \
--sysconfdir=/etc/openvpn \
--enable-pthread \
--enable-iproute2 \
--with-ssl \
--with-lzo-header=/usr/include \
--with-lzo-lib=/usr/lib \
--with-ifconfig \
--with-route \
--with-mem-check=dmalloc 
make ; make install-strip
&lt;/pre&gt;
== Configuration ==

==Configuring Certificates==

Save all certificates in '''''/etc/openvpn/certs'''''
&lt;pre&gt;
This is a small RSA key management package,
based on the openssl command line tool, that
can be found in the easy-rsa subdirectory
of the OpenVPN distribution.

These are reference notes.  For step
by step instructions, see the HOWTO:

http://openvpn.net/howto.html

INSTALL

1. Edit vars.
2. Set KEY_CONFIG to point to the openssl.cnf file
   included in this distribution.
3. Set KEY_DIR to point to a directory which will
   contain all keys, certificates, etc.  This
   directory need not exist, and if it does,
   it will be deleted with rm -rf, so BE
   CAREFUL how you set KEY_DIR.
4. (Optional) Edit other fields in vars
   per your site data.  You may want to
   increase KEY_SIZE to 2048 if you are
   paranoid and don't mind slower key
   processing, but certainly 1024 is
   fine for testing purposes.  KEY_SIZE
   must be compatible across both peers
   participating in a secure SSL/TLS
   connection.
5  . vars
6. ./clean-all
7. As you create certificates, keys, and
   certificate signing requests, understand that
   only .key files should be kept confidential.
   .crt and .csr files can be sent over insecure
   channels such as plaintext email.
8. You should never need to copy a .key file
   between computers.  Normally each computer
   will have its own certificate/key pair.

BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY

1. ./build-ca
2. ca.crt and ca.key will be built in your KEY_DIR
   directory

BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)

1. ./build-inter inter
2. inter.crt and inter.key will be built in your KEY_DIR
   directory and signed with your root certificate.

BUILD DIFFIE-HELLMAN PARAMETERS (necessary for
the server end of a SSL/TLS connection).

1. ./build-dh

BUILD A CERTIFICATE SIGNING REQUEST (If
you want to sign your certificate with a root
certificate controlled by another individual
or organization, or residing on a different machine).

1. Get ca.crt (the root certificate) from your
   certificate authority.  Though this
   transfer can be over an insecure channel, to prevent
   man-in-the-middle attacks you must confirm that
   ca.crt was not tampered with.  Large CAs solve this
   problem by hardwiring their root certificates into
   popular web browsers.  A simple way to verify a root
   CA is to call the issuer on the telephone and confirm
   that the md5sum or sha1sum signatures on the ca.crt
   files match (such as with the command: "md5sum ca.crt").
2. Choose a name for your certificate such as your computer
   name.  In our example we will use "mycert".
3. ./build-req mycert
4. You can ignore most of the fields, but set
   "Common Name" to something unique such as your
   computer's host name.  Leave all password
   fields blank, unless you want your private key
   to be protected by password.  Using a password
   is not required -- it will make your key more secure
   but also more inconvenient to use, because you will
   need to supply your password anytime the key is used.
   NOTE: if you are using a password, use ./build-req-pass
   instead of ./build-req
5. Your key will be written to $KEY_DIR/mycert.key
6. Your certificate signing request will be written to
   to $KEY_DIR/mycert.csr
7. Email mycert.csr to the individual or organization
   which controls the root certificate.  This can be
   done over an insecure channel.
8. After the .csr file is signed by the root certificate
   authority, you will receive a file mycert.crt
   (your certificate).  Place mycert.crt in your
   KEY_DIR directory.
9. The combined files of mycert.crt, mycert.key,
   and ca.crt can now be used to secure one end of
   an SSL/TLS connection.

SIGN A CERTIFICATE SIGNING REQUEST

1. ./sign-req mycert
2. mycert.crt will be built in your KEY_DIR
   directory using mycert.csr and your root CA
   file as input.

BUILD AND SIGN A CERTIFICATE SIGNING REQUEST
USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY -- this
script generates and signs a certificate in one step,
but it requires that the generated certificate and private
key files be copied to the destination host over a
secure channel.

1. ./build-key mycert (no password protection)
2. OR ./build-key-pass mycert (with password protection)
3. OR ./build-key-pkcs12 mycert (PKCS #12 format)
4. OR ./build-key-server mycert (with nsCertType=server)
5. mycert.crt and mycert.key will be built in your
   KEY_DIR directory, and mycert.crt will be signed
   by your root CA. If ./build-key-pkcs12 was used a
   mycert.p12 file will also be created including the
   private key, certificate and the ca certificate.

IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.
IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.

(4) Sign server certificates with one CA and client certificates
    with a different CA.  The client config "ca" directive should
    reference the server-signing CA while the server config "ca"
    directive should reference the client-signing CA.

NOTES

Show certificate fields:
  openssl x509 -in cert.crt -text
&lt;/pre&gt;
&lt;pre&gt;
# cd easy-rsa
# vi vars
. vars
./clean-all

## BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY
./build.ca

## BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)
./build-inter inter

## BUILD DIFFIE-HELLMAN PARAMETERS (necessary for the server end of a SSL/TLS connection).
./build.dh

## BUILD A CERTIFICATE SIGNING REQUEST 
## (If you want to sign your certificate with a root certificate controlled by another individual 
## or organization, or residing on a different machine)

./build-req mycert
## SIGN A CERTIFICATE SIGNING REQUEST
./sign-req mycert

## BUILD AND SIGN A CERTIFICATE SIGNING REQUEST USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY
./build-key mycert (no password protection)
OR 
./build-key-pass mycert (with password protection)
OR 
./build-key-pkcs12 mycert (PKCS #12 format)
OR 
./build-key-server mycert (with nsCertType=server)
&lt;/pre&gt;

==Configuring the Server==

Edit the server.conf file with vi '''''vi /etc/openvpn/server.conf'''''
&lt;pre&gt;
## Mode Server
mode server

## Local Host Name/IP Server
;local 127.0.0.1

## Protocol
;proto tcp
proto udp

## Port
; port 1194

## Device Interface
;dev tap
dev tun

## TAP-Win32 adapter name
;dev-node MyTap

## SSL/TLS 
## root certificate (ca)
## certificate (cert)
## private key (key)
ca /etc/openvpn/certs/ca.crt
cert /etc/openvpn/certs/server.crt
key /etc/openvpn/certs/server.key

## Diffie hellman parameters
dh dh1024.pem

## VPN subnet
server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

##ethernet bridging
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

## dhcpcaveats
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

;learn-address ./script

## dhcpcaveats
;push "redirect-gateway"
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

##
;client-to-client

## same "COMMON NAME" certificate/key
;duplicate-cn

## Status Connection
keepalive 10 120

## tls-auth key
;tls-auth ta.key 0 

## Cryptographic cipher
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

## Link Compresion
comp-lzo

## Max Client Connections
;max-clients 100

## daemon privileges (non windows saja)
user nobody
group nobody

persist-key
persist-tun

## Openvpn Log
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

## Output Log
status /var/log/openvpn/openvpn-status.log

## Log Verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## Repeating Messages
;mute 20

## Pid File
writepid /var/run/openvpn.pid
&lt;/pre&gt;

'''Routing'''

&lt;pre&gt;
echo 1 &gt; /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.4.0.2
&lt;/pre&gt;

'''Firewall'''
&lt;pre&gt;
iptables -A INPUT -p udp -s 1.2.3.4 --dport 1194 -j ACCEPT
OR
iptables -A INPUT -p udp --dport 1194 -j ACCEPT

## Tun Device
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT

## Tap Device
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
&lt;/pre&gt;

==Configuring the Client==

Edit the client.conf file with vi '''''vi /etc/openvpn/client.conf'''''
&lt;pre&gt;
## Config
client

## Device Interface
;dev tap
dev tun

## Tap adapter name (Win only)
;dev-node MyTap

## Conectivity
;proto tcp
proto udp

## Server [hostname/ip] [port]
remote my-server-1 1194
;remote my-server-2 1194

## load-balancing
;remote-random

## resolve host name OpenVPN server
resolv-retry infinite

# local port
nobind

## privileges (non windows saja)
user nobody
group nobody

## preserve
persist-key
persist-tun

## HTTP proxy
;http-proxy-retry 
;http-proxy [proxy server] [proxy port]

## duplicate packet warnings
;mute-replay-warnings

## SSL/TLS parms
/etc/openvpn/certs/ca ca.crt
/etc/openvpn/certs/cert client.crt
/etc/openvpn/certs/key client.key

## nsCertType key
;ns-cert-type server

## tls-auth key
;tls-auth /etc/openvpn/certs/ta.key 1

## Cryptographic cipher
;cipher x

## Link compression
comp-lzo

## verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## repeating messages
;mute 20
&lt;/pre&gt;
'''Routing'''
&lt;pre&gt;
route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.4.0.1 
&lt;/pre&gt;


==Example==

'''Example 1:''' A simple tunnel without security&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 --verb 9
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 --verb 9 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 2:''' A tunnel with static-key security (i.e. using a pre-shared secret)&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--verb 5 --secret key
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--verb 5 --secret key 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 3:''' A tunnel with full TLS-based security &lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--tls-client --ca tmp-ca.crt --cert client.crt --key client.key \
--reneg-sec 60 --verb 5 
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--tls-server --ca tmp-ca.crt --cert server.crt --key server.key \
--reneg-sec 60 --verb 5 --dh dh1024.pem
&lt;/pre&gt;

On May:

    ping 10.4.0.2 

On Jun:

    ping 10.4.0.1

== External Links ==

* http://dmalloc.com/
* http://valgrind.org/
* http://www.oberhumer.com/opensource/lzo/
* http://openvpn.net/
* http://openvpn.net/howto.html
* http://openvpn.net/1xhowto.html (Old-v1.06)
* http://openvpn.net/man.html</text>
    <sha1>8d0505df62558c99ad0a3a49399000dc0bb8bd3e</sha1>
  </revision>
  <revision>
    <id>267</id>
    <parentid>266</parentid>
    <timestamp>2009-12-01T17:18:48Z</timestamp>
    <contributor>
      <username>Seekret</username>
      <id>59</id>
    </contributor>
    <minor/>
    <comment>/* Configuring the Server */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14168" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.

__TOC__
== Installation ==

Download source from [http://openvpn.net openvpn.net]

Download verison 2.0

install Lzo
&lt;pre&gt;
tar zxvf lzo-1.08.tar.gz
cd lzo-1-08.tar.gz
./configure --prefix=/usr
make ; make install-strip
&lt;/pre&gt;
install OpenVPN
&lt;pre&gt;
tar zxvf openvpn-2.0.tar.gz
cd openvpn-2.0
./configure --prefix=/usr \
--sysconfdir=/etc/openvpn \
--enable-pthread \
--enable-iproute2 \
--with-ssl \
--with-lzo-header=/usr/include \
--with-lzo-lib=/usr/lib \
--with-ifconfig \
--with-route \
--with-mem-check=dmalloc 
make ; make install-strip
&lt;/pre&gt;
== Configuration ==

==Configuring Certificates==

Save all certificates in '''''/etc/openvpn/certs'''''
&lt;pre&gt;
This is a small RSA key management package,
based on the openssl command line tool, that
can be found in the easy-rsa subdirectory
of the OpenVPN distribution.

These are reference notes.  For step
by step instructions, see the HOWTO:

http://openvpn.net/howto.html

INSTALL

1. Edit vars.
2. Set KEY_CONFIG to point to the openssl.cnf file
   included in this distribution.
3. Set KEY_DIR to point to a directory which will
   contain all keys, certificates, etc.  This
   directory need not exist, and if it does,
   it will be deleted with rm -rf, so BE
   CAREFUL how you set KEY_DIR.
4. (Optional) Edit other fields in vars
   per your site data.  You may want to
   increase KEY_SIZE to 2048 if you are
   paranoid and don't mind slower key
   processing, but certainly 1024 is
   fine for testing purposes.  KEY_SIZE
   must be compatible across both peers
   participating in a secure SSL/TLS
   connection.
5  . vars
6. ./clean-all
7. As you create certificates, keys, and
   certificate signing requests, understand that
   only .key files should be kept confidential.
   .crt and .csr files can be sent over insecure
   channels such as plaintext email.
8. You should never need to copy a .key file
   between computers.  Normally each computer
   will have its own certificate/key pair.

BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY

1. ./build-ca
2. ca.crt and ca.key will be built in your KEY_DIR
   directory

BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)

1. ./build-inter inter
2. inter.crt and inter.key will be built in your KEY_DIR
   directory and signed with your root certificate.

BUILD DIFFIE-HELLMAN PARAMETERS (necessary for
the server end of a SSL/TLS connection).

1. ./build-dh

BUILD A CERTIFICATE SIGNING REQUEST (If
you want to sign your certificate with a root
certificate controlled by another individual
or organization, or residing on a different machine).

1. Get ca.crt (the root certificate) from your
   certificate authority.  Though this
   transfer can be over an insecure channel, to prevent
   man-in-the-middle attacks you must confirm that
   ca.crt was not tampered with.  Large CAs solve this
   problem by hardwiring their root certificates into
   popular web browsers.  A simple way to verify a root
   CA is to call the issuer on the telephone and confirm
   that the md5sum or sha1sum signatures on the ca.crt
   files match (such as with the command: "md5sum ca.crt").
2. Choose a name for your certificate such as your computer
   name.  In our example we will use "mycert".
3. ./build-req mycert
4. You can ignore most of the fields, but set
   "Common Name" to something unique such as your
   computer's host name.  Leave all password
   fields blank, unless you want your private key
   to be protected by password.  Using a password
   is not required -- it will make your key more secure
   but also more inconvenient to use, because you will
   need to supply your password anytime the key is used.
   NOTE: if you are using a password, use ./build-req-pass
   instead of ./build-req
5. Your key will be written to $KEY_DIR/mycert.key
6. Your certificate signing request will be written to
   to $KEY_DIR/mycert.csr
7. Email mycert.csr to the individual or organization
   which controls the root certificate.  This can be
   done over an insecure channel.
8. After the .csr file is signed by the root certificate
   authority, you will receive a file mycert.crt
   (your certificate).  Place mycert.crt in your
   KEY_DIR directory.
9. The combined files of mycert.crt, mycert.key,
   and ca.crt can now be used to secure one end of
   an SSL/TLS connection.

SIGN A CERTIFICATE SIGNING REQUEST

1. ./sign-req mycert
2. mycert.crt will be built in your KEY_DIR
   directory using mycert.csr and your root CA
   file as input.

BUILD AND SIGN A CERTIFICATE SIGNING REQUEST
USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY -- this
script generates and signs a certificate in one step,
but it requires that the generated certificate and private
key files be copied to the destination host over a
secure channel.

1. ./build-key mycert (no password protection)
2. OR ./build-key-pass mycert (with password protection)
3. OR ./build-key-pkcs12 mycert (PKCS #12 format)
4. OR ./build-key-server mycert (with nsCertType=server)
5. mycert.crt and mycert.key will be built in your
   KEY_DIR directory, and mycert.crt will be signed
   by your root CA. If ./build-key-pkcs12 was used a
   mycert.p12 file will also be created including the
   private key, certificate and the ca certificate.

IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.
IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.

(4) Sign server certificates with one CA and client certificates
    with a different CA.  The client config "ca" directive should
    reference the server-signing CA while the server config "ca"
    directive should reference the client-signing CA.

NOTES

Show certificate fields:
  openssl x509 -in cert.crt -text
&lt;/pre&gt;
&lt;pre&gt;
# cd easy-rsa
# vi vars
. vars
./clean-all

## BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY
./build.ca

## BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)
./build-inter inter

## BUILD DIFFIE-HELLMAN PARAMETERS (necessary for the server end of a SSL/TLS connection).
./build.dh

## BUILD A CERTIFICATE SIGNING REQUEST 
## (If you want to sign your certificate with a root certificate controlled by another individual 
## or organization, or residing on a different machine)

./build-req mycert
## SIGN A CERTIFICATE SIGNING REQUEST
./sign-req mycert

## BUILD AND SIGN A CERTIFICATE SIGNING REQUEST USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY
./build-key mycert (no password protection)
OR 
./build-key-pass mycert (with password protection)
OR 
./build-key-pkcs12 mycert (PKCS #12 format)
OR 
./build-key-server mycert (with nsCertType=server)
&lt;/pre&gt;

==Configuring the Server==

Edit the server.conf file: '''''vi /etc/openvpn/server.conf'''''
&lt;pre&gt;
## Mode Server
mode server

## Local Host Name/IP Server
;local 127.0.0.1

## Protocol
;proto tcp
proto udp

## Port
; port 1194

## Device Interface
;dev tap
dev tun

## TAP-Win32 adapter name
;dev-node MyTap

## SSL/TLS 
## root certificate (ca)
## certificate (cert)
## private key (key)
ca /etc/openvpn/certs/ca.crt
cert /etc/openvpn/certs/server.crt
key /etc/openvpn/certs/server.key

## Diffie hellman parameters
dh dh1024.pem

## VPN subnet
server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

##ethernet bridging
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

## dhcpcaveats
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

;learn-address ./script

## dhcpcaveats
;push "redirect-gateway"
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

##
;client-to-client

## same "COMMON NAME" certificate/key
;duplicate-cn

## Status Connection
keepalive 10 120

## tls-auth key
;tls-auth ta.key 0 

## Cryptographic cipher
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

## Link Compresion
comp-lzo

## Max Client Connections
;max-clients 100

## daemon privileges (non windows saja)
user nobody
group nobody

persist-key
persist-tun

## Openvpn Log
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

## Output Log
status /var/log/openvpn/openvpn-status.log

## Log Verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## Repeating Messages
;mute 20

## Pid File
writepid /var/run/openvpn.pid
&lt;/pre&gt;

'''Routing'''

&lt;pre&gt;
echo 1 &gt; /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.4.0.2
&lt;/pre&gt;

'''Firewall'''
&lt;pre&gt;
iptables -A INPUT -p udp -s 1.2.3.4 --dport 1194 -j ACCEPT
OR
iptables -A INPUT -p udp --dport 1194 -j ACCEPT

## Tun Device
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT

## Tap Device
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
&lt;/pre&gt;

==Configuring the Client==

Edit the client.conf file with vi '''''vi /etc/openvpn/client.conf'''''
&lt;pre&gt;
## Config
client

## Device Interface
;dev tap
dev tun

## Tap adapter name (Win only)
;dev-node MyTap

## Conectivity
;proto tcp
proto udp

## Server [hostname/ip] [port]
remote my-server-1 1194
;remote my-server-2 1194

## load-balancing
;remote-random

## resolve host name OpenVPN server
resolv-retry infinite

# local port
nobind

## privileges (non windows saja)
user nobody
group nobody

## preserve
persist-key
persist-tun

## HTTP proxy
;http-proxy-retry 
;http-proxy [proxy server] [proxy port]

## duplicate packet warnings
;mute-replay-warnings

## SSL/TLS parms
/etc/openvpn/certs/ca ca.crt
/etc/openvpn/certs/cert client.crt
/etc/openvpn/certs/key client.key

## nsCertType key
;ns-cert-type server

## tls-auth key
;tls-auth /etc/openvpn/certs/ta.key 1

## Cryptographic cipher
;cipher x

## Link compression
comp-lzo

## verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## repeating messages
;mute 20
&lt;/pre&gt;
'''Routing'''
&lt;pre&gt;
route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.4.0.1 
&lt;/pre&gt;


==Example==

'''Example 1:''' A simple tunnel without security&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 --verb 9
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 --verb 9 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 2:''' A tunnel with static-key security (i.e. using a pre-shared secret)&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--verb 5 --secret key
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--verb 5 --secret key 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 3:''' A tunnel with full TLS-based security &lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--tls-client --ca tmp-ca.crt --cert client.crt --key client.key \
--reneg-sec 60 --verb 5 
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--tls-server --ca tmp-ca.crt --cert server.crt --key server.key \
--reneg-sec 60 --verb 5 --dh dh1024.pem
&lt;/pre&gt;

On May:

    ping 10.4.0.2 

On Jun:

    ping 10.4.0.1

== External Links ==

* http://dmalloc.com/
* http://valgrind.org/
* http://www.oberhumer.com/opensource/lzo/
* http://openvpn.net/
* http://openvpn.net/howto.html
* http://openvpn.net/1xhowto.html (Old-v1.06)
* http://openvpn.net/man.html</text>
    <sha1>7b9043410e28cfdc391434c89d54809e144ccff4</sha1>
  </revision>
  <revision>
    <id>268</id>
    <parentid>267</parentid>
    <timestamp>2009-12-01T17:19:13Z</timestamp>
    <contributor>
      <username>Seekret</username>
      <id>59</id>
    </contributor>
    <minor/>
    <comment>/* Configuring the Client */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14159" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.

__TOC__
== Installation ==

Download source from [http://openvpn.net openvpn.net]

Download verison 2.0

install Lzo
&lt;pre&gt;
tar zxvf lzo-1.08.tar.gz
cd lzo-1-08.tar.gz
./configure --prefix=/usr
make ; make install-strip
&lt;/pre&gt;
install OpenVPN
&lt;pre&gt;
tar zxvf openvpn-2.0.tar.gz
cd openvpn-2.0
./configure --prefix=/usr \
--sysconfdir=/etc/openvpn \
--enable-pthread \
--enable-iproute2 \
--with-ssl \
--with-lzo-header=/usr/include \
--with-lzo-lib=/usr/lib \
--with-ifconfig \
--with-route \
--with-mem-check=dmalloc 
make ; make install-strip
&lt;/pre&gt;
== Configuration ==

==Configuring Certificates==

Save all certificates in '''''/etc/openvpn/certs'''''
&lt;pre&gt;
This is a small RSA key management package,
based on the openssl command line tool, that
can be found in the easy-rsa subdirectory
of the OpenVPN distribution.

These are reference notes.  For step
by step instructions, see the HOWTO:

http://openvpn.net/howto.html

INSTALL

1. Edit vars.
2. Set KEY_CONFIG to point to the openssl.cnf file
   included in this distribution.
3. Set KEY_DIR to point to a directory which will
   contain all keys, certificates, etc.  This
   directory need not exist, and if it does,
   it will be deleted with rm -rf, so BE
   CAREFUL how you set KEY_DIR.
4. (Optional) Edit other fields in vars
   per your site data.  You may want to
   increase KEY_SIZE to 2048 if you are
   paranoid and don't mind slower key
   processing, but certainly 1024 is
   fine for testing purposes.  KEY_SIZE
   must be compatible across both peers
   participating in a secure SSL/TLS
   connection.
5  . vars
6. ./clean-all
7. As you create certificates, keys, and
   certificate signing requests, understand that
   only .key files should be kept confidential.
   .crt and .csr files can be sent over insecure
   channels such as plaintext email.
8. You should never need to copy a .key file
   between computers.  Normally each computer
   will have its own certificate/key pair.

BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY

1. ./build-ca
2. ca.crt and ca.key will be built in your KEY_DIR
   directory

BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)

1. ./build-inter inter
2. inter.crt and inter.key will be built in your KEY_DIR
   directory and signed with your root certificate.

BUILD DIFFIE-HELLMAN PARAMETERS (necessary for
the server end of a SSL/TLS connection).

1. ./build-dh

BUILD A CERTIFICATE SIGNING REQUEST (If
you want to sign your certificate with a root
certificate controlled by another individual
or organization, or residing on a different machine).

1. Get ca.crt (the root certificate) from your
   certificate authority.  Though this
   transfer can be over an insecure channel, to prevent
   man-in-the-middle attacks you must confirm that
   ca.crt was not tampered with.  Large CAs solve this
   problem by hardwiring their root certificates into
   popular web browsers.  A simple way to verify a root
   CA is to call the issuer on the telephone and confirm
   that the md5sum or sha1sum signatures on the ca.crt
   files match (such as with the command: "md5sum ca.crt").
2. Choose a name for your certificate such as your computer
   name.  In our example we will use "mycert".
3. ./build-req mycert
4. You can ignore most of the fields, but set
   "Common Name" to something unique such as your
   computer's host name.  Leave all password
   fields blank, unless you want your private key
   to be protected by password.  Using a password
   is not required -- it will make your key more secure
   but also more inconvenient to use, because you will
   need to supply your password anytime the key is used.
   NOTE: if you are using a password, use ./build-req-pass
   instead of ./build-req
5. Your key will be written to $KEY_DIR/mycert.key
6. Your certificate signing request will be written to
   to $KEY_DIR/mycert.csr
7. Email mycert.csr to the individual or organization
   which controls the root certificate.  This can be
   done over an insecure channel.
8. After the .csr file is signed by the root certificate
   authority, you will receive a file mycert.crt
   (your certificate).  Place mycert.crt in your
   KEY_DIR directory.
9. The combined files of mycert.crt, mycert.key,
   and ca.crt can now be used to secure one end of
   an SSL/TLS connection.

SIGN A CERTIFICATE SIGNING REQUEST

1. ./sign-req mycert
2. mycert.crt will be built in your KEY_DIR
   directory using mycert.csr and your root CA
   file as input.

BUILD AND SIGN A CERTIFICATE SIGNING REQUEST
USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY -- this
script generates and signs a certificate in one step,
but it requires that the generated certificate and private
key files be copied to the destination host over a
secure channel.

1. ./build-key mycert (no password protection)
2. OR ./build-key-pass mycert (with password protection)
3. OR ./build-key-pkcs12 mycert (PKCS #12 format)
4. OR ./build-key-server mycert (with nsCertType=server)
5. mycert.crt and mycert.key will be built in your
   KEY_DIR directory, and mycert.crt will be signed
   by your root CA. If ./build-key-pkcs12 was used a
   mycert.p12 file will also be created including the
   private key, certificate and the ca certificate.

IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.
IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.

(4) Sign server certificates with one CA and client certificates
    with a different CA.  The client config "ca" directive should
    reference the server-signing CA while the server config "ca"
    directive should reference the client-signing CA.

NOTES

Show certificate fields:
  openssl x509 -in cert.crt -text
&lt;/pre&gt;
&lt;pre&gt;
# cd easy-rsa
# vi vars
. vars
./clean-all

## BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY
./build.ca

## BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)
./build-inter inter

## BUILD DIFFIE-HELLMAN PARAMETERS (necessary for the server end of a SSL/TLS connection).
./build.dh

## BUILD A CERTIFICATE SIGNING REQUEST 
## (If you want to sign your certificate with a root certificate controlled by another individual 
## or organization, or residing on a different machine)

./build-req mycert
## SIGN A CERTIFICATE SIGNING REQUEST
./sign-req mycert

## BUILD AND SIGN A CERTIFICATE SIGNING REQUEST USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY
./build-key mycert (no password protection)
OR 
./build-key-pass mycert (with password protection)
OR 
./build-key-pkcs12 mycert (PKCS #12 format)
OR 
./build-key-server mycert (with nsCertType=server)
&lt;/pre&gt;

==Configuring the Server==

Edit the server.conf file: '''''vi /etc/openvpn/server.conf'''''
&lt;pre&gt;
## Mode Server
mode server

## Local Host Name/IP Server
;local 127.0.0.1

## Protocol
;proto tcp
proto udp

## Port
; port 1194

## Device Interface
;dev tap
dev tun

## TAP-Win32 adapter name
;dev-node MyTap

## SSL/TLS 
## root certificate (ca)
## certificate (cert)
## private key (key)
ca /etc/openvpn/certs/ca.crt
cert /etc/openvpn/certs/server.crt
key /etc/openvpn/certs/server.key

## Diffie hellman parameters
dh dh1024.pem

## VPN subnet
server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

##ethernet bridging
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

## dhcpcaveats
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

;learn-address ./script

## dhcpcaveats
;push "redirect-gateway"
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

##
;client-to-client

## same "COMMON NAME" certificate/key
;duplicate-cn

## Status Connection
keepalive 10 120

## tls-auth key
;tls-auth ta.key 0 

## Cryptographic cipher
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

## Link Compresion
comp-lzo

## Max Client Connections
;max-clients 100

## daemon privileges (non windows saja)
user nobody
group nobody

persist-key
persist-tun

## Openvpn Log
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

## Output Log
status /var/log/openvpn/openvpn-status.log

## Log Verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## Repeating Messages
;mute 20

## Pid File
writepid /var/run/openvpn.pid
&lt;/pre&gt;

'''Routing'''

&lt;pre&gt;
echo 1 &gt; /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.4.0.2
&lt;/pre&gt;

'''Firewall'''
&lt;pre&gt;
iptables -A INPUT -p udp -s 1.2.3.4 --dport 1194 -j ACCEPT
OR
iptables -A INPUT -p udp --dport 1194 -j ACCEPT

## Tun Device
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT

## Tap Device
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
&lt;/pre&gt;

==Configuring the Client==

Edit the client.conf file: '''''vi /etc/openvpn/client.conf'''''
&lt;pre&gt;
## Config
client

## Device Interface
;dev tap
dev tun

## Tap adapter name (Win only)
;dev-node MyTap

## Conectivity
;proto tcp
proto udp

## Server [hostname/ip] [port]
remote my-server-1 1194
;remote my-server-2 1194

## load-balancing
;remote-random

## resolve host name OpenVPN server
resolv-retry infinite

# local port
nobind

## privileges (non windows saja)
user nobody
group nobody

## preserve
persist-key
persist-tun

## HTTP proxy
;http-proxy-retry 
;http-proxy [proxy server] [proxy port]

## duplicate packet warnings
;mute-replay-warnings

## SSL/TLS parms
/etc/openvpn/certs/ca ca.crt
/etc/openvpn/certs/cert client.crt
/etc/openvpn/certs/key client.key

## nsCertType key
;ns-cert-type server

## tls-auth key
;tls-auth /etc/openvpn/certs/ta.key 1

## Cryptographic cipher
;cipher x

## Link compression
comp-lzo

## verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## repeating messages
;mute 20
&lt;/pre&gt;
'''Routing'''
&lt;pre&gt;
route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.4.0.1 
&lt;/pre&gt;

==Example==

'''Example 1:''' A simple tunnel without security&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 --verb 9
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 --verb 9 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 2:''' A tunnel with static-key security (i.e. using a pre-shared secret)&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--verb 5 --secret key
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--verb 5 --secret key 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 3:''' A tunnel with full TLS-based security &lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--tls-client --ca tmp-ca.crt --cert client.crt --key client.key \
--reneg-sec 60 --verb 5 
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--tls-server --ca tmp-ca.crt --cert server.crt --key server.key \
--reneg-sec 60 --verb 5 --dh dh1024.pem
&lt;/pre&gt;

On May:

    ping 10.4.0.2 

On Jun:

    ping 10.4.0.1

== External Links ==

* http://dmalloc.com/
* http://valgrind.org/
* http://www.oberhumer.com/opensource/lzo/
* http://openvpn.net/
* http://openvpn.net/howto.html
* http://openvpn.net/1xhowto.html (Old-v1.06)
* http://openvpn.net/man.html</text>
    <sha1>52333963aecd5c87f7ae948650847baa21b86ca2</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Talk:OpenVPN(EN)</title>
  <ns>1</ns>
  <id>198</id>
  <revision>
    <id>269</id>
    <timestamp>2009-12-01T17:21:45Z</timestamp>
    <contributor>
      <username>Seekret</username>
      <id>59</id>
    </contributor>
    <comment>Created page with 'This is an English version of the existing OpenVPN file. I simply translated the instructions with Google Translate and made the translation grammatically correct.'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="163" xml:space="preserve">This is an English version of the existing OpenVPN file. I simply translated the instructions with Google Translate and made the translation grammatically correct.</text>
    <sha1>0d092baf93eb939908209483fc2d19f9a3c5521b</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Writing A SlackBuild Script</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>273</id>
    <parentid>22</parentid>
    <timestamp>2009-12-14T19:30:00Z</timestamp>
    <contributor>
      <username>SiegeX</username>
      <id>64</id>
    </contributor>
    <comment>/* Initial Setup */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19605" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/</text>
    <sha1>292b77163684b3b1836f33a1053ee77516b47303</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>RAID Array (Hardware)</title>
  <ns>0</ns>
  <id>137</id>
  <revision>
    <id>276</id>
    <parentid>163</parentid>
    <timestamp>2010-01-09T01:01:16Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>/* My Card Is In, Now What? */  ADDED the fact that this was with Slackware 10</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6029" xml:space="preserve">[[Category:Tips]]
[[Category:Tutorials]]
[[Category:Hardware]]

==My Card Is In, Now What?==
-Written from a Slackware 10 perspective-
1) SET UP THE ARRAY- If you are using a hardware RAID card (like ones made by 3ware), on boot you must enter the card's BIOS and set up your array.  This is done by hitting a hotkey (ALT-3 for 3ware cards).  Read your card's instructions for details on how to configure your array.

2) BOOT WITH THE CORRECT KERNEL- After you have set up your array, boot the computer with the Slackware Install CD (CD1) like normal. &lt;b&gt;At the &lt;code&gt;boot:&lt;/code&gt; prompt, choose a RAID supporting image (e.g. &lt;code&gt;raid.s&lt;/code&gt;).&lt;/b&gt;  YOU CAN NOT USE THE DEFAULT KERNEL (bare.i) to boot into set-up, you have to use a boot kernel that supports RAID arrays.

:EXAMPLE: &lt;code&gt;boot: raid.s&lt;/code&gt;

3) PROCEED NORMALLY- Once you boot the RAID kernel, everything else proceeds normally except the hard-drive is (usually) &lt;code&gt;/dev/sda&lt;/code&gt;. Go ahead set up your partitions (&lt;code&gt;fdisk /dev/sda&lt;/code&gt;) and continue the normal Slackware install.

==FAQs==

Q: What device is my RAID array?&lt;br&gt;
A: You are most likely running RAID.S kernel so therefore it is probably &lt;code&gt;/dev/sda&lt;/code&gt;

Q: It's not &lt;code&gt;/dev/sda&lt;/code&gt; where is it really?&lt;br&gt;
A: I don't know. Reboot your machine and watch the messages scroll by.  If you don't see the info, you don't have RAID support compiled into your kernel or as a module and you need to fix that.

Q: My system has a [[forced fsck]] and it starts but after awhile, it resets and re-boots.  How do I fix this?&lt;br&gt;
A: Re-boot the system using a Slackware install CD (make sure you boot with a RAID kernel) then get to a command line prompt and manually run &lt;code&gt;fsck&lt;/code&gt;.
: EXAMPLE: &lt;code&gt;fsck -p /dev/sda1&lt;/code&gt;

Q: I'm trying to run &lt;code&gt;fsck&lt;/code&gt; manually but I get an "&lt;code&gt;The superblock cannot be read...&lt;/code&gt;" error.  How do I fix this?&lt;br&gt;
A: MOST LIKELY, you're not running a RAID supporting kernel.  Re-boot and choose a RAID kernel like &lt;code&gt;raid.s&lt;/code&gt;.

Q: I'm running &lt;code&gt;fsck&lt;/code&gt; manually and I am getting a "&lt;code&gt;error allocating inode bitmap (2)&lt;/code&gt;".  How do I fix this?&lt;br&gt;
A: No clue. I haven't been able to find out what that means.  If you do, let us know please.

==Hardware RAID Specific Help==

[[3ware 3DM2]] - Help with 3ware's 3DM2 program.

==Hardware RAID Specific Help==

[[3ware 3ware 8006-2LP Installation]] - 

Installed slackware 12.2 with the 3ware 8006-2LP card today. I chose this hardware due to the fanfare I found on the net. It is supported with RedHat and Suse (presumably because they have a preinstall driver installation dialog) 

Installing with slack was not as easy as was hoped. Lilo choked twice, first by installing to the MBR which the 3ware bios simply didn't see, and second after installing to the root partition, lilo complained with error 99 which is apparently a BIOS disk address mismatch of some sort. 

What worked was this: 

1. Install the card, or receive the machine with the card already installed. 

2. Double check that all your cable connections are tight. mine were loose when the chassis arrived from the vendor. I am sincerely glad I found this now rather than later. 

3. Slackware 12.2 has the 3ware driver in it, so it should boot from CD and see the disk as: 

   /dev/sda  

4. fdisk /dev/sda and create some partitions, mine are as follows: 

   /dev/sda1 50G (/ this is the root partition) set bootable
   /dev/sda2 2G  (for /boot)  
   /dev/sda3 2G  ( for swap) toggle to type 82
   /dev/sda4 (extended) 
   /dev/sda5 25G (for /var) 
   /dev/sda6 25G (for /home) 
   /dev/sda7 50G (for the webserver) 
   /dev/sda8 50G (for the database) 
   /dev/sda9 10G (for source code) 

You will note seperate /boot and /home partitions. Configuring the disk this way adds some security, which we will discuss in a moment. 

5. Run setup and select your packages. 

6. Do the configuration dialog: Generally I believe all network enabled devices should be on UTC so I set both system and hardware clocks accordingly.  ignore gpm, ignore fancy fonts, and number the network interface... Then make sure the network interface _isn't_ connected.  

7. Let the lilo configurator screw up lilo by select "Guess my lilo config" or whatever. 

8. exit setup, DO NOT REBOOT! 

9. chroot /mnt 

10. vi /etc/lilo and make it point at your root partition. My lilo.conf is as follows: 

   lba32 # any modern drive should be able to do this. 
   boot = /dev/sda1
   append = " vt.default_utf8=0"
   vga = normal
   image = /boot/vmlinuz
   root = /dev/sda1
   Label = Linux
   read-only # for fscking during bootup. 

11. Note above that /dev/sda1 is the root partition, or "/" if you stick it somewhere else, change as appropriate. 

12. obliterate the master boot record: (prevents lilo from getting confused for some reason): 
    lilo -z -M /dev/sda

13. run lilo and listen to it complain: 
   lilo 

14. If you don't get any fatals errors (warnings are ok), remove the cd then: 
    exit 
    reboot

15. Do your little chair dance, and irritate your coworkers. 

16. vi /etc/fstab and adjust the following partitions:
 
   /dev/sda2         /boot            ext2        defaults,ro         1   2
   /dev/sda6         /home            ext2        defaults,nosuid         1   2

Leave your partitions ext3 if they are configured that way, but note the addition of "ro" to /boot and "nosuid" to /home. This makes the kernel secure from modification until the next reboot, and prevents root privileged code from being executed from /home. Generally good and fairly unintrusive security policy. 

Now proceed onward oh great progenitors of slack. Your next steps should probably be using "find" to locate and disable most of what has a suid bit set, and then installing and configuring tripwire or some equivilant, then making a brutal set of access controls with iptables, and _then_.... _maybe_ you can connect the box to a public network. 

But don't take my word for it.  

Good Luck!</text>
    <sha1>18d884c2e5392567f61331b3aa89a0335dd94c76</sha1>
  </revision>
  <revision>
    <id>277</id>
    <parentid>276</parentid>
    <timestamp>2010-01-09T01:03:30Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>/* My Card Is In, Now What? */  TYPO fix</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6120" xml:space="preserve">[[Category:Tips]]
[[Category:Tutorials]]
[[Category:Hardware]]

==My Card Is In, Now What?==
-Written from a Slackware 10 perspective-

1) SET UP THE ARRAY- If you are using a hardware RAID card (like ones made by 3ware), on boot you must enter the card's BIOS and set up your array.  This is done by hitting a hotkey (ALT-3 for 3ware cards).  Read your card's instructions for details on how to configure your array.

2) BOOT WITH THE CORRECT KERNEL- After you have set up your array, boot the computer with the Slackware Install CD (CD1) like normal. &lt;b&gt;At the &lt;code&gt;boot:&lt;/code&gt; prompt, choose a RAID supporting image (e.g. &lt;code&gt;raid.s&lt;/code&gt;).&lt;/b&gt;  YOU CAN NOT USE THE DEFAULT KERNEL (bare.i) to boot into set-up, you have to use a boot kernel that supports RAID arrays.

:EXAMPLE: &lt;code&gt;boot: raid.s&lt;/code&gt;

'''NOTE: I don't believe STEP 2 applies to newer versions of Slackware. (e.g Slack13)'''

3) PROCEED NORMALLY- Once you boot the RAID kernel, everything else proceeds normally except the hard-drive is (usually) &lt;code&gt;/dev/sda&lt;/code&gt;. Go ahead set up your partitions (&lt;code&gt;fdisk /dev/sda&lt;/code&gt;) and continue the normal Slackware install.

==FAQs==

Q: What device is my RAID array?&lt;br&gt;
A: You are most likely running RAID.S kernel so therefore it is probably &lt;code&gt;/dev/sda&lt;/code&gt;

Q: It's not &lt;code&gt;/dev/sda&lt;/code&gt; where is it really?&lt;br&gt;
A: I don't know. Reboot your machine and watch the messages scroll by.  If you don't see the info, you don't have RAID support compiled into your kernel or as a module and you need to fix that.

Q: My system has a [[forced fsck]] and it starts but after awhile, it resets and re-boots.  How do I fix this?&lt;br&gt;
A: Re-boot the system using a Slackware install CD (make sure you boot with a RAID kernel) then get to a command line prompt and manually run &lt;code&gt;fsck&lt;/code&gt;.
: EXAMPLE: &lt;code&gt;fsck -p /dev/sda1&lt;/code&gt;

Q: I'm trying to run &lt;code&gt;fsck&lt;/code&gt; manually but I get an "&lt;code&gt;The superblock cannot be read...&lt;/code&gt;" error.  How do I fix this?&lt;br&gt;
A: MOST LIKELY, you're not running a RAID supporting kernel.  Re-boot and choose a RAID kernel like &lt;code&gt;raid.s&lt;/code&gt;.

Q: I'm running &lt;code&gt;fsck&lt;/code&gt; manually and I am getting a "&lt;code&gt;error allocating inode bitmap (2)&lt;/code&gt;".  How do I fix this?&lt;br&gt;
A: No clue. I haven't been able to find out what that means.  If you do, let us know please.

==Hardware RAID Specific Help==

[[3ware 3DM2]] - Help with 3ware's 3DM2 program.

==Hardware RAID Specific Help==

[[3ware 3ware 8006-2LP Installation]] - 

Installed slackware 12.2 with the 3ware 8006-2LP card today. I chose this hardware due to the fanfare I found on the net. It is supported with RedHat and Suse (presumably because they have a preinstall driver installation dialog) 

Installing with slack was not as easy as was hoped. Lilo choked twice, first by installing to the MBR which the 3ware bios simply didn't see, and second after installing to the root partition, lilo complained with error 99 which is apparently a BIOS disk address mismatch of some sort. 

What worked was this: 

1. Install the card, or receive the machine with the card already installed. 

2. Double check that all your cable connections are tight. mine were loose when the chassis arrived from the vendor. I am sincerely glad I found this now rather than later. 

3. Slackware 12.2 has the 3ware driver in it, so it should boot from CD and see the disk as: 

   /dev/sda  

4. fdisk /dev/sda and create some partitions, mine are as follows: 

   /dev/sda1 50G (/ this is the root partition) set bootable
   /dev/sda2 2G  (for /boot)  
   /dev/sda3 2G  ( for swap) toggle to type 82
   /dev/sda4 (extended) 
   /dev/sda5 25G (for /var) 
   /dev/sda6 25G (for /home) 
   /dev/sda7 50G (for the webserver) 
   /dev/sda8 50G (for the database) 
   /dev/sda9 10G (for source code) 

You will note seperate /boot and /home partitions. Configuring the disk this way adds some security, which we will discuss in a moment. 

5. Run setup and select your packages. 

6. Do the configuration dialog: Generally I believe all network enabled devices should be on UTC so I set both system and hardware clocks accordingly.  ignore gpm, ignore fancy fonts, and number the network interface... Then make sure the network interface _isn't_ connected.  

7. Let the lilo configurator screw up lilo by select "Guess my lilo config" or whatever. 

8. exit setup, DO NOT REBOOT! 

9. chroot /mnt 

10. vi /etc/lilo and make it point at your root partition. My lilo.conf is as follows: 

   lba32 # any modern drive should be able to do this. 
   boot = /dev/sda1
   append = " vt.default_utf8=0"
   vga = normal
   image = /boot/vmlinuz
   root = /dev/sda1
   Label = Linux
   read-only # for fscking during bootup. 

11. Note above that /dev/sda1 is the root partition, or "/" if you stick it somewhere else, change as appropriate. 

12. obliterate the master boot record: (prevents lilo from getting confused for some reason): 
    lilo -z -M /dev/sda

13. run lilo and listen to it complain: 
   lilo 

14. If you don't get any fatals errors (warnings are ok), remove the cd then: 
    exit 
    reboot

15. Do your little chair dance, and irritate your coworkers. 

16. vi /etc/fstab and adjust the following partitions:
 
   /dev/sda2         /boot            ext2        defaults,ro         1   2
   /dev/sda6         /home            ext2        defaults,nosuid         1   2

Leave your partitions ext3 if they are configured that way, but note the addition of "ro" to /boot and "nosuid" to /home. This makes the kernel secure from modification until the next reboot, and prevents root privileged code from being executed from /home. Generally good and fairly unintrusive security policy. 

Now proceed onward oh great progenitors of slack. Your next steps should probably be using "find" to locate and disable most of what has a suid bit set, and then installing and configuring tripwire or some equivilant, then making a brutal set of access controls with iptables, and _then_.... _maybe_ you can connect the box to a public network. 

But don't take my word for it.  

Good Luck!</text>
    <sha1>fd2215c672acfa131593022c6c30d0de3496639d</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Routing Tricks</title>
  <ns>0</ns>
  <id>204</id>
  <revision>
    <id>278</id>
    <timestamp>2010-01-09T01:27:56Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>CREATED THIS PAGE</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2754" xml:space="preserve">==Weighted Routing==
(aka Load Balancing, Net Balancing)

'''What is Weighted Routing'''
Simply put, distributing network traffic over multiple paths based on load.

EXAMPLE 1: You have two DSL connections incoming and you distribute your connection traffic between them.

EXAMPLE 2: You have a 1.5Mbs DSL connection and a 3MBs cable connection, therefore you set up your routing to send 1/3 of the traffic out the DSL connection and 2/3 out the cable connection.


'''How do I do it?'''

Niels Horn has written a slick little script to do the weighted routing for you.  He has given me permission to copy it here.  


 #!/bin/bash
 #
 # bal_local		Load-balance internet connection over two local links 
 #
 # Version:		1.0.0 - Fri, Sep 26, 2008
 #
 # Author:		Niels Horn &lt;niels.horn(at symbol)gmail.com&gt;
 #
 #
 # Set devices:
 DEV1=${1-eth0}	# default eth0
 DEV2=${2-ppp0}	# default ppp0
 #
 # Get IP addresses of our devices:
 ip1=`ifconfig $DEV1 | grep inet | awk '{ print $2 }' | awk -F: '{ print $2 }'`
 ip2=`ifconfig $DEV2 | grep inet | awk '{ print $2 }' | awk -F: '{ print $2 }'`
 #
 # Get default gateway for our devices:
 gw1=`route -n | grep $DEV1 | grep '^0.0.0.0' | awk '{ print $2 }'`
 gw2=`route -n | grep $DEV2 | grep '^0.0.0.0' | awk '{ print $2 }'`
 #
 echo "$DEV1: IP=$ip1 GW=$gw1"
 echo "$DEV2: IP=$ip2 GW=$gw2"
 #
 ### Definition of routes ###
 #
 # Check if tables exists, if not -&gt; create them:
 if [ -z "`cat /etc/iproute2/rt_tables | grep '^251'`" ] ; then
 	echo "251	rt_dev1" &gt;&gt; /etc/iproute2/rt_tables
 fi
 if [ -z "`cat /etc/iproute2/rt_tables | grep '^252'`" ] ; then
 	echo "252	rt_dev2" &gt;&gt; /etc/iproute2/rt_tables
 fi
 #
 # Define routing tables:
 ip route add default via $gw1 table rt_dev1
 ip route add default via $gw2 table rt_dev2
 #
 # Create rules:
 ip rule add from $ip1 table rt_dev1
 ip rule add from $ip2 table rt_dev2
 #
 # If we already have a 'nexthop' route, delete it:
 if [ ! -z "`ip route show table main | grep 'nexthop'`" ] ; then
 	ip route del default scope global
 fi
 #
 # Balance links based on routes:
 ip route add default scope global nexthop via $gw1 dev $DEV1 weight 1 nexthop via $gw2 dev $DEV2 weight 1
 #
 # Flush cache table:
 ip route flush cache  
 #
 # All done...

To use the script, copy it to /usr/local/bin, make it executable with 'chmod +x' and call it with:
Code:

 bal_local &lt;dev1&gt; &lt;dev2&gt;

filling in &lt;dev1&gt; and &lt;dev2&gt; with your network-devices.
If you call the script without any parameters, it tries to balance eth0 and ppp0 (because this works in my case ).

[http://www.linuxquestions.org/questions/slackware-14/script-to-load-balance-two-isps-with-ip-route-and-ip-rules-672602 HERE IS HIS ORIGINAL POSTING]

(ALSO, I copied a copy of his permission on my DISCUSSION page)</text>
    <sha1>3fd8159bbe2f424a8461cec2568b5b7d949352c5</sha1>
  </revision>
  <revision>
    <id>280</id>
    <parentid>278</parentid>
    <timestamp>2010-01-09T01:34:53Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>/* Weighted Routing */  FIXED the screwed up link. And added the category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2774" xml:space="preserve">==Weighted Routing==
(aka Load Balancing, Net Balancing)

'''What is Weighted Routing'''
Simply put, distributing network traffic over multiple paths based on load.

EXAMPLE 1: You have two DSL connections incoming and you distribute your connection traffic between them.

EXAMPLE 2: You have a 1.5Mbs DSL connection and a 3MBs cable connection, therefore you set up your routing to send 1/3 of the traffic out the DSL connection and 2/3 out the cable connection.


'''How do I do it?'''

Niels Horn has written a slick little script to do the weighted routing for you.  He has given me permission to copy it here.  


 #!/bin/bash
 #
 # bal_local		Load-balance internet connection over two local links 
 #
 # Version:		1.0.0 - Fri, Sep 26, 2008
 #
 # Author:		Niels Horn &lt;niels.horn(at symbol)gmail.com&gt;
 #
 #
 # Set devices:
 DEV1=${1-eth0}	# default eth0
 DEV2=${2-ppp0}	# default ppp0
 #
 # Get IP addresses of our devices:
 ip1=`ifconfig $DEV1 | grep inet | awk '{ print $2 }' | awk -F: '{ print $2 }'`
 ip2=`ifconfig $DEV2 | grep inet | awk '{ print $2 }' | awk -F: '{ print $2 }'`
 #
 # Get default gateway for our devices:
 gw1=`route -n | grep $DEV1 | grep '^0.0.0.0' | awk '{ print $2 }'`
 gw2=`route -n | grep $DEV2 | grep '^0.0.0.0' | awk '{ print $2 }'`
 #
 echo "$DEV1: IP=$ip1 GW=$gw1"
 echo "$DEV2: IP=$ip2 GW=$gw2"
 #
 ### Definition of routes ###
 #
 # Check if tables exists, if not -&gt; create them:
 if [ -z "`cat /etc/iproute2/rt_tables | grep '^251'`" ] ; then
 	echo "251	rt_dev1" &gt;&gt; /etc/iproute2/rt_tables
 fi
 if [ -z "`cat /etc/iproute2/rt_tables | grep '^252'`" ] ; then
 	echo "252	rt_dev2" &gt;&gt; /etc/iproute2/rt_tables
 fi
 #
 # Define routing tables:
 ip route add default via $gw1 table rt_dev1
 ip route add default via $gw2 table rt_dev2
 #
 # Create rules:
 ip rule add from $ip1 table rt_dev1
 ip rule add from $ip2 table rt_dev2
 #
 # If we already have a 'nexthop' route, delete it:
 if [ ! -z "`ip route show table main | grep 'nexthop'`" ] ; then
 	ip route del default scope global
 fi
 #
 # Balance links based on routes:
 ip route add default scope global nexthop via $gw1 dev $DEV1 weight 1 nexthop via $gw2 dev $DEV2 weight 1
 #
 # Flush cache table:
 ip route flush cache  
 #
 # All done...

To use the script, copy it to /usr/local/bin, make it executable with 'chmod +x' and call it with:
Code:

 bal_local &lt;dev1&gt; &lt;dev2&gt;

filling in &lt;dev1&gt; and &lt;dev2&gt; with your network-devices.
If you call the script without any parameters, it tries to balance eth0 and ppp0 (because this works in my case ).

[http://www.linuxquestions.org/questions/slackware-14/script-to-load-balance-two-isps-with-ip-route-and-ip-rules-672602/ HERE IS HIS ORIGINAL POSTING]

(ALSO, I copied a copy of his permission on my DISCUSSION page)

[[Category:Tips]]</text>
    <sha1>e85ee5bc100367aeefa4cebf25af7e92c81f5627</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Talk:Routing Tricks</title>
  <ns>1</ns>
  <id>205</id>
  <revision>
    <id>279</id>
    <timestamp>2010-01-09T01:29:01Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Created page with 'Neils Horn's permission to repost his weighted routing info-   Hi,  I'm hopelessly without time these days (last days before going on  vacation), so feel free to post it on slack...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="381" xml:space="preserve">Neils Horn's permission to repost his weighted routing info-

 Hi,
 I'm hopelessly without time these days (last days before going on
 vacation), so feel free to post it on slackwiki.org for me.
 I would appreciate it if you could send me the link afterwards so that
 I can take a look  :) 
 Thanks,
 Niels

-------------------------------------------------------------------------</text>
    <sha1>15d7010809e6d414bf7cc164619d19b0458cc8a3</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>User:Crudo</title>
  <ns>2</ns>
  <id>206</id>
  <revision>
    <id>281</id>
    <timestamp>2010-01-20T01:24:57Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>Created page with '* Real Name: Alexandre Mulatinho * IRC Nickname: crudo, crudo|home, crudo|work :P * E-Mail: alex 'at' mulatinho.net * My Homepage: http://alex.mulatinho.net * From: Brazil  I hav...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="367" xml:space="preserve">* Real Name: Alexandre Mulatinho
* IRC Nickname: crudo, crudo|home, crudo|work :P
* E-Mail: alex 'at' mulatinho.net
* My Homepage: http://alex.mulatinho.net
* From: Brazil

I have been using linux to about 12 years, and my first experience with Slakware was in 3.4 version, until then i use Slakware in my work, home and in all my machines :) Thanks to Slakware team!</text>
    <sha1>cd6e42aace5f7b2a412d9606e26c6ac654ece5cf</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>ToshibaNB205</title>
  <ns>0</ns>
  <id>207</id>
  <revision>
    <id>282</id>
    <timestamp>2010-01-20T02:27:02Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>Created page with '-NOT FINISHED-  =Intro= Hello Slakers!  I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1107" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit,

=Network Informations=
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;</text>
    <sha1>5463f63af4a51ec005181c8446cab08111180064</sha1>
  </revision>
  <revision>
    <id>283</id>
    <parentid>282</parentid>
    <timestamp>2010-01-20T02:31:47Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>/* Technical Details */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3728" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit,

PCI Devices:
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Network Informations=
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;</text>
    <sha1>03e702cd395150eb14b42ca615ea1442f4862dc9</sha1>
  </revision>
  <revision>
    <id>284</id>
    <parentid>283</parentid>
    <timestamp>2010-01-20T02:46:43Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4993" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit,
==CPU==
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

==PCI Devices==
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

==USB Devices==
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

==Hard Disk==
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Network Informations=
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
==Bluetooth==
==Ethernet==
==Wifi==
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
=My Opinion About the Slakware in this Netbook=</text>
    <sha1>657989bda2c9efec444373d55bc936616996c942</sha1>
  </revision>
  <revision>
    <id>285</id>
    <parentid>284</parentid>
    <timestamp>2010-01-20T02:48:06Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4978" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit,

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Network Informations=
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
==Bluetooth==
==Ethernet==
==Wifi==
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
=My Opinion About the Slakware in this Netbook=</text>
    <sha1>4b5ea9344e6d03167c2931ec8789cf462ed46c46</sha1>
  </revision>
  <revision>
    <id>286</id>
    <parentid>285</parentid>
    <timestamp>2010-01-20T03:03:35Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5439" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit, Battery Life is 8 Hours!!!

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Netbook Slakware Configuration=
==Screen==

==Network==
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
===Bluetooth===
===Ethernet===
===Wifi===
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
&lt;pre&gt;# time dd bs=1k count=1000 if=/dev/urandom of=/dev/zero
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB) copied, 0.588823 s, 1.7 MB/s

real	0m0.593s
user	0m0.003s
sys	0m0.582s
# time dd bs=1k count=100000 if=/dev/urandom of=/dev/zero
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 56.0481 s, 1.8 MB/s

real	0m56.053s
user	0m0.131s
sys	0m55.874s&lt;/pre&gt;
=My Opinion About the Slakware in this Netbook=</text>
    <sha1>b59ca4a5f63cb31cd24332e6aa8766cd640cd112</sha1>
  </revision>
  <revision>
    <id>287</id>
    <parentid>286</parentid>
    <timestamp>2010-01-20T03:05:52Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>/* Tests of Performance */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5637" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit, Battery Life is 8 Hours!!!

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Netbook Slakware Configuration=
==Screen==

==Network==
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
===Bluetooth===
===Ethernet===
===Wifi===
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
&lt;pre&gt;# time dd bs=1k count=1000 if=/dev/urandom of=/dev/zero
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB) copied, 0.588823 s, 1.7 MB/s

real	0m0.593s
user	0m0.003s
sys	0m0.582s
# time dd bs=1k count=100000 if=/dev/urandom of=/dev/zero
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 56.0481 s, 1.8 MB/s

real	0m56.053s
user	0m0.131s
sys	0m55.874s
# time dd bs=1k count=200000 if=/dev/urandom of=/tmp/mkshit
100000+0 records in
100000+0 records out
204800000 bytes (205 MB) copied, 120.184 s, 1.7 MB/s

real	2m0.189s
user	0m0.445s
sys	1m58.237s&lt;/pre&gt;

=My Opinion About the Slakware in this Netbook=</text>
    <sha1>527384379dd0022e9d535e994e67c1d5902abc02</sha1>
  </revision>
  <revision>
    <id>288</id>
    <parentid>287</parentid>
    <timestamp>2010-01-20T03:14:30Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>/* Bluetooth */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6206" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit, Battery Life is 8 Hours!!!

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Netbook Slakware Configuration=
==Screen==

==Network==
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
===Bluetooth===
To get things done you will need to download the 'omnibook' package and compile in your slackware version. Once you do it you can follow these commands to test your connection:
&lt;pre&gt;# modprobe -v omnibook
insmod /lib/modules/2.6.29.6-smp/extra/omnibook.ko ectype=12 userset=1 wifi=1 bluetooth=1
# hciconfig   
hci0:	Type: USB
	BD Address: 00:22:58:FF:C2:DC ACL MTU: 310:10 SCO MTU: 64:8
	UP RUNNING PSCAN ISCAN 
	RX bytes:692 acl:0 sco:0 events:24 errors:0
	TX bytes:581 acl:0 sco:0 commands:24 errors:0

# hcitool scan
Scanning ...
	00:21:FC:B1:AC:97	Rosangela&lt;/pre&gt;

===Ethernet===
===Wifi===
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
&lt;pre&gt;# time dd bs=1k count=1000 if=/dev/urandom of=/dev/zero
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB) copied, 0.588823 s, 1.7 MB/s

real	0m0.593s
user	0m0.003s
sys	0m0.582s
# time dd bs=1k count=100000 if=/dev/urandom of=/dev/zero
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 56.0481 s, 1.8 MB/s

real	0m56.053s
user	0m0.131s
sys	0m55.874s
# time dd bs=1k count=200000 if=/dev/urandom of=/tmp/mkshit
100000+0 records in
100000+0 records out
204800000 bytes (205 MB) copied, 120.184 s, 1.7 MB/s

real	2m0.189s
user	0m0.445s
sys	1m58.237s&lt;/pre&gt;

=My Opinion About the Slakware in this Netbook=</text>
    <sha1>429f005d200a12843f3670bdd99c986c20986954</sha1>
  </revision>
  <revision>
    <id>289</id>
    <parentid>288</parentid>
    <timestamp>2010-01-20T03:34:56Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>/* Screen */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8701" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit, Battery Life is 8 Hours!!!

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Netbook Slakware Configuration=
==Screen==
&lt;pre&gt;Section "Module"
          Load        "dbe"   # Double buffer extension
          SubSection  "extmod"
            Option    "omit xfree86-dga"   # don't initialise the DGA extension
          EndSubSection
          Load        "type1"
          Load        "freetype"
          Load       "glx"
EndSection

Section "Files"
          RgbPath     "/usr/share/X11/rgb"
          FontPath   "/usr/share/fonts/local/"
          FontPath   "/usr/share/fonts/misc/"
          FontPath   "/usr/share/fonts/OTF/"
          FontPath   "/usr/share/fonts/TTF/"
          FontPath   "/usr/share/fonts/Type1/"
          FontPath   "/usr/share/fonts/CID/"
          FontPath   "/usr/share/fonts/Speedo/"
          FontPath   "/usr/share/fonts/75dpi/:unscaled"
          FontPath   "/usr/share/fonts/100dpi/:unscaled"
          FontPath   "/usr/share/fonts/75dpi/"
          FontPath   "/usr/share/fonts/100dpi/"
          FontPath   "/usr/share/fonts/cyrillic/"
EndSection

Section "InputDevice"
          Driver      "kbd"
          Option     "XkbRules"      "xorg"
          Option     "XkbModel"      "pc105"
          Option     "XkbLayout"     "us"
EndSection

Section "InputDevice"
          Identifier  "Mouse1"
          Driver      "mouse"
          Option "Protocol"    "PS/2"
          Option "Device"      "/dev/mouse"
EndSection

Section "Monitor"
          Identifier  "My Monitor"
          HorizSync   31.5 - 50.0
          VertRefresh 40-90
EndSection

Section "Device"
          Identifier  "VESA Framebuffer"
          Driver      "vesa"
EndSection

Section "Screen"
          Device      "VESA Framebuffer"
          Monitor     "My Monitor"
          DefaultDepth 24
          Subsection "Display"
              Depth       8
              Modes "1024x600" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       16
              Modes "1024x768" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       24
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
          Subsection "Display"
              Depth       32
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
EndSection

Section "ServerLayout"
          Identifier  "Simple Layout"
          Screen "Screen 1"
          InputDevice "Mouse1" "CorePointer"
          InputDevice "Keyboard1" "CoreKeyboard"
EndSection&lt;/pre&gt;

==Network==
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
===Bluetooth===
To get things done you will need to download the 'omnibook' package and compile in your slackware version. Once you do it you can follow these commands to test your connection:
&lt;pre&gt;# modprobe -v omnibook
insmod /lib/modules/2.6.29.6-smp/extra/omnibook.ko ectype=12 userset=1 wifi=1 bluetooth=1
# hciconfig   
hci0:	Type: USB
	BD Address: 00:22:58:FF:C2:DC ACL MTU: 310:10 SCO MTU: 64:8
	UP RUNNING PSCAN ISCAN 
	RX bytes:692 acl:0 sco:0 events:24 errors:0
	TX bytes:581 acl:0 sco:0 commands:24 errors:0

# hcitool scan
Scanning ...
	00:21:FC:B1:AC:97	Rosangela&lt;/pre&gt;

===Ethernet===
===Wifi===
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
&lt;pre&gt;# time dd bs=1k count=1000 if=/dev/urandom of=/dev/zero
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB) copied, 0.588823 s, 1.7 MB/s

real	0m0.593s
user	0m0.003s
sys	0m0.582s
# time dd bs=1k count=100000 if=/dev/urandom of=/dev/zero
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 56.0481 s, 1.8 MB/s

real	0m56.053s
user	0m0.131s
sys	0m55.874s
# time dd bs=1k count=200000 if=/dev/urandom of=/tmp/mkshit
100000+0 records in
100000+0 records out
204800000 bytes (205 MB) copied, 120.184 s, 1.7 MB/s

real	2m0.189s
user	0m0.445s
sys	1m58.237s&lt;/pre&gt;

=My Opinion About the Slakware in this Netbook=</text>
    <sha1>dfbfa4f56732f7a1d47d66e2c27d46dd19aafad6</sha1>
  </revision>
  <revision>
    <id>290</id>
    <parentid>289</parentid>
    <timestamp>2010-01-20T03:40:17Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>/* Screen */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8712" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit, Battery Life is 8 Hours!!!

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Netbook Slakware Configuration=
==Screen /etc/X11/org.conf==
&lt;pre&gt;Section "Module"
          Load        "dbe"   # Double buffer extension
          SubSection  "extmod"
            Option    "omit xfree86-dga"   # don't initialise the DGA extension
          EndSubSection
          Load        "type1"
          Load        "freetype"
          Load       "glx"
EndSection

Section "Files"
          RgbPath     "/usr/share/X11/rgb"
          FontPath   "/usr/share/fonts/local/"
          FontPath   "/usr/share/fonts/misc/"
          FontPath   "/usr/share/fonts/OTF/"
          FontPath   "/usr/share/fonts/TTF/"
          FontPath   "/usr/share/fonts/Type1/"
          FontPath   "/usr/share/fonts/CID/"
          FontPath   "/usr/share/fonts/Speedo/"
          FontPath   "/usr/share/fonts/75dpi/:unscaled"
          FontPath   "/usr/share/fonts/100dpi/:unscaled"
          FontPath   "/usr/share/fonts/75dpi/"
          FontPath   "/usr/share/fonts/100dpi/"
          FontPath   "/usr/share/fonts/cyrillic/"
EndSection

Section "InputDevice"
          Driver      "kbd"
          Option     "XkbRules"      "xorg"
          Option     "XkbModel"      "pc105"
          Option     "XkbLayout"     "us"
EndSection

Section "InputDevice"
          Identifier  "Mouse1"
          Driver      "mouse"
          Option "Protocol"    "PS/2"
          Option "Device"      "/dev/mouse"
EndSection

Section "Monitor"
          Identifier  "My Monitor"
          HorizSync   31.5 - 50.0
          VertRefresh 40-90
EndSection

Section "Device"
          Identifier  "Intel GMA950"
          Driver      "intel"
EndSection

Section "Screen"
          Device      "Intel GMA950"
          Monitor     "My Monitor"
          DefaultDepth 24
          Subsection "Display"
              Depth       8
              Modes "1024x600" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       16
              Modes "1024x768" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       24
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
          Subsection "Display"
              Depth       32
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
EndSection

Section "ServerLayout"
          Identifier  "Simple Layout"
          Screen "Screen 1"
          InputDevice "Mouse1" "CorePointer"
          InputDevice "Keyboard1" "CoreKeyboard"
EndSection&lt;/pre&gt;

==Network==
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
===Bluetooth===
To get things done you will need to download the 'omnibook' package and compile in your slackware version. Once you do it you can follow these commands to test your connection:
&lt;pre&gt;# modprobe -v omnibook
insmod /lib/modules/2.6.29.6-smp/extra/omnibook.ko ectype=12 userset=1 wifi=1 bluetooth=1
# hciconfig   
hci0:	Type: USB
	BD Address: 00:22:58:FF:C2:DC ACL MTU: 310:10 SCO MTU: 64:8
	UP RUNNING PSCAN ISCAN 
	RX bytes:692 acl:0 sco:0 events:24 errors:0
	TX bytes:581 acl:0 sco:0 commands:24 errors:0

# hcitool scan
Scanning ...
	00:21:FC:B1:AC:97	Rosangela&lt;/pre&gt;

===Ethernet===
===Wifi===
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
&lt;pre&gt;# time dd bs=1k count=1000 if=/dev/urandom of=/dev/zero
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB) copied, 0.588823 s, 1.7 MB/s

real	0m0.593s
user	0m0.003s
sys	0m0.582s
# time dd bs=1k count=100000 if=/dev/urandom of=/dev/zero
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 56.0481 s, 1.8 MB/s

real	0m56.053s
user	0m0.131s
sys	0m55.874s
# time dd bs=1k count=200000 if=/dev/urandom of=/tmp/mkshit
100000+0 records in
100000+0 records out
204800000 bytes (205 MB) copied, 120.184 s, 1.7 MB/s

real	2m0.189s
user	0m0.445s
sys	1m58.237s&lt;/pre&gt;

=My Opinion About the Slakware in this Netbook=</text>
    <sha1>d62eccf0333d085f819ba102c447960a3f998010</sha1>
  </revision>
  <revision>
    <id>291</id>
    <parentid>290</parentid>
    <timestamp>2010-01-20T15:00:37Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>/* Technical Details */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9090" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit, Battery Life is 8 Hours!!!

Even being netbook this machine has a good performance and excelent battery duration time! Generally this happens because of his ATOM N280 1.6GHz that use minus power and are designed for running in two units of execution even that is not a dual-processor. He has a beautiful keyboard design, a nice webcam of 1.3 megapixels and a good acceleration in multimedia applications.

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Netbook Slakware Configuration=
==Screen /etc/X11/org.conf==
&lt;pre&gt;Section "Module"
          Load        "dbe"   # Double buffer extension
          SubSection  "extmod"
            Option    "omit xfree86-dga"   # don't initialise the DGA extension
          EndSubSection
          Load        "type1"
          Load        "freetype"
          Load       "glx"
EndSection

Section "Files"
          RgbPath     "/usr/share/X11/rgb"
          FontPath   "/usr/share/fonts/local/"
          FontPath   "/usr/share/fonts/misc/"
          FontPath   "/usr/share/fonts/OTF/"
          FontPath   "/usr/share/fonts/TTF/"
          FontPath   "/usr/share/fonts/Type1/"
          FontPath   "/usr/share/fonts/CID/"
          FontPath   "/usr/share/fonts/Speedo/"
          FontPath   "/usr/share/fonts/75dpi/:unscaled"
          FontPath   "/usr/share/fonts/100dpi/:unscaled"
          FontPath   "/usr/share/fonts/75dpi/"
          FontPath   "/usr/share/fonts/100dpi/"
          FontPath   "/usr/share/fonts/cyrillic/"
EndSection

Section "InputDevice"
          Driver      "kbd"
          Option     "XkbRules"      "xorg"
          Option     "XkbModel"      "pc105"
          Option     "XkbLayout"     "us"
EndSection

Section "InputDevice"
          Identifier  "Mouse1"
          Driver      "mouse"
          Option "Protocol"    "PS/2"
          Option "Device"      "/dev/mouse"
EndSection

Section "Monitor"
          Identifier  "My Monitor"
          HorizSync   31.5 - 50.0
          VertRefresh 40-90
EndSection

Section "Device"
          Identifier  "Intel GMA950"
          Driver      "intel"
EndSection

Section "Screen"
          Device      "Intel GMA950"
          Monitor     "My Monitor"
          DefaultDepth 24
          Subsection "Display"
              Depth       8
              Modes "1024x600" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       16
              Modes "1024x768" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       24
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
          Subsection "Display"
              Depth       32
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
EndSection

Section "ServerLayout"
          Identifier  "Simple Layout"
          Screen "Screen 1"
          InputDevice "Mouse1" "CorePointer"
          InputDevice "Keyboard1" "CoreKeyboard"
EndSection&lt;/pre&gt;

==Network==
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
===Bluetooth===
To get things done you will need to download the 'omnibook' package and compile in your slackware version. Once you do it you can follow these commands to test your connection:
&lt;pre&gt;# modprobe -v omnibook
insmod /lib/modules/2.6.29.6-smp/extra/omnibook.ko ectype=12 userset=1 wifi=1 bluetooth=1
# hciconfig   
hci0:	Type: USB
	BD Address: 00:22:58:FF:C2:DC ACL MTU: 310:10 SCO MTU: 64:8
	UP RUNNING PSCAN ISCAN 
	RX bytes:692 acl:0 sco:0 events:24 errors:0
	TX bytes:581 acl:0 sco:0 commands:24 errors:0

# hcitool scan
Scanning ...
	00:21:FC:B1:AC:97	Rosangela&lt;/pre&gt;

===Ethernet===
===Wifi===
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
&lt;pre&gt;# time dd bs=1k count=1000 if=/dev/urandom of=/dev/zero
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB) copied, 0.588823 s, 1.7 MB/s

real	0m0.593s
user	0m0.003s
sys	0m0.582s
# time dd bs=1k count=100000 if=/dev/urandom of=/dev/zero
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 56.0481 s, 1.8 MB/s

real	0m56.053s
user	0m0.131s
sys	0m55.874s
# time dd bs=1k count=200000 if=/dev/urandom of=/tmp/mkshit
100000+0 records in
100000+0 records out
204800000 bytes (205 MB) copied, 120.184 s, 1.7 MB/s

real	2m0.189s
user	0m0.445s
sys	1m58.237s&lt;/pre&gt;

=My Opinion About the Slakware in this Netbook=</text>
    <sha1>53b4eddfd46df896c69a24e81225be01f58f3edb</sha1>
  </revision>
  <revision>
    <id>292</id>
    <parentid>291</parentid>
    <timestamp>2010-01-20T15:04:20Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9247" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) Even being netbook this machine has a good performance and excelent battery duration time! Generally this happens because of his ATOM N280 1.6GHz that use minus power and are designed for running in two units of execution even that is not a dual-processor. He has a beautiful keyboard design, a nice webcam of 1.3 megapixels and a good acceleration in multimedia applications. So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit, Battery Life is 8 Hours!!!

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Netbook Slakware Configuration=
==Screen /etc/X11/org.conf==
&lt;pre&gt;Section "Module"
          Load        "dbe"   # Double buffer extension
          SubSection  "extmod"
            Option    "omit xfree86-dga"   # don't initialise the DGA extension
          EndSubSection
          Load        "type1"
          Load        "freetype"
          Load       "glx"
EndSection

Section "Files"
          RgbPath     "/usr/share/X11/rgb"
          FontPath   "/usr/share/fonts/local/"
          FontPath   "/usr/share/fonts/misc/"
          FontPath   "/usr/share/fonts/OTF/"
          FontPath   "/usr/share/fonts/TTF/"
          FontPath   "/usr/share/fonts/Type1/"
          FontPath   "/usr/share/fonts/CID/"
          FontPath   "/usr/share/fonts/Speedo/"
          FontPath   "/usr/share/fonts/75dpi/:unscaled"
          FontPath   "/usr/share/fonts/100dpi/:unscaled"
          FontPath   "/usr/share/fonts/75dpi/"
          FontPath   "/usr/share/fonts/100dpi/"
          FontPath   "/usr/share/fonts/cyrillic/"
EndSection

Section "InputDevice"
          Driver      "kbd"
          Option     "XkbRules"      "xorg"
          Option     "XkbModel"      "pc105"
          Option     "XkbLayout"     "us"
EndSection

Section "InputDevice"
          Identifier  "Mouse1"
          Driver      "mouse"
          Option "Protocol"    "PS/2"
          Option "Device"      "/dev/mouse"
EndSection

Section "Monitor"
          Identifier  "My Monitor"
          HorizSync   31.5 - 50.0
          VertRefresh 40-90
EndSection

Section "Device"
          Identifier  "Intel GMA950"
          Driver      "intel"
EndSection

Section "Screen"
          Device      "Intel GMA950"
          Monitor     "My Monitor"
          DefaultDepth 24
          Subsection "Display"
              Depth       8
              Modes "1024x600" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       16
              Modes "1024x768" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       24
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
          Subsection "Display"
              Depth       32
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
EndSection

Section "ServerLayout"
          Identifier  "Simple Layout"
          Screen "Screen 1"
          InputDevice "Mouse1" "CorePointer"
          InputDevice "Keyboard1" "CoreKeyboard"
EndSection&lt;/pre&gt;

==Network==
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
===Bluetooth===
To get things done you will need to download the 'omnibook' package and compile in your slackware version. Once you do it you can follow these commands to test your connection:
&lt;pre&gt;# modprobe -v omnibook
insmod /lib/modules/2.6.29.6-smp/extra/omnibook.ko ectype=12 userset=1 wifi=1 bluetooth=1
# hciconfig   
hci0:	Type: USB
	BD Address: 00:22:58:FF:C2:DC ACL MTU: 310:10 SCO MTU: 64:8
	UP RUNNING PSCAN ISCAN 
	RX bytes:692 acl:0 sco:0 events:24 errors:0
	TX bytes:581 acl:0 sco:0 commands:24 errors:0

# hcitool scan
Scanning ...
	00:21:FC:B1:AC:97	Rosangela&lt;/pre&gt;

===Ethernet===
===Wifi===
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;
=Tests of Performance=
&lt;pre&gt;# time dd bs=1k count=1000 if=/dev/urandom of=/dev/zero
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB) copied, 0.588823 s, 1.7 MB/s

real	0m0.593s
user	0m0.003s
sys	0m0.582s
# time dd bs=1k count=100000 if=/dev/urandom of=/dev/zero
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 56.0481 s, 1.8 MB/s

real	0m56.053s
user	0m0.131s
sys	0m55.874s
# time dd bs=1k count=200000 if=/dev/urandom of=/tmp/mkshit
100000+0 records in
100000+0 records out
204800000 bytes (205 MB) copied, 120.184 s, 1.7 MB/s

real	2m0.189s
user	0m0.445s
sys	1m58.237s&lt;/pre&gt;

=My Opinion About the Slakware in this Netbook=
* You will not be unsatisfied.
* You need to buy at least one in your life. Only $490.
* Excelent to use like a second 'notebook' in your home and your work.</text>
    <sha1>40e38e547e2f871fbd124dde6fb4239c43cecc04</sha1>
  </revision>
  <revision>
    <id>293</id>
    <parentid>292</parentid>
    <timestamp>2010-01-22T17:58:40Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10168" xml:space="preserve">-NOT FINISHED-

=Intro=
Hello Slakers!

I will talk about how to installing and use Slakware in a NB 205 from Toshiba. First of all i have to admit that i stayed really impressed with the design of NB205, he's fully portable and light, the screen with a 10.1" have a bad news: she only can do 1024x600 of size but not for us, slackers! ;) Even being netbook this machine has a good performance and excelent battery duration time! Generally this happens because of his ATOM N280 1.6GHz that use minus power and are designed for running in two units of execution even that is not a dual-processor. He has a beautiful keyboard design, a nice webcam of 1.3 megapixels and a good acceleration in multimedia applications. So before anything else, lets see some more informations about his technical specifications, down:

=Technical Details = 

* Motherboard: Toshiba KAVAA - Chipset: Intel Callistoga-GSE i945GSE
* Processor: Intel Atom N280 1.6GHz
* Memory: DDR2-800/400/333/266 MHz - Comes to 1GB but you can upgrade to 2 GB.
* Video: Intel GMA 950 (1280x600)
* Hard Disk: 160 GB 5400 RPM SATA-II
* Webcam, Bluetooth, Ether/Wifi Network gigabit, Battery Life is 8 Hours!!!

CPU
&lt;pre&gt;# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N280   @ 1.66GHz
stepping	: 2
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm lahf_lm
bogomips	: 3325.16
clflush size	: 64
power management:&lt;/pre&gt;

PCI Devices
&lt;pre&gt;# lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GME Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)&lt;/pre&gt;

USB Devices
&lt;pre&gt;# lsusb
Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
Bus 001 Device 003: ID 0bda:0159 Realtek Semiconductor Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;/pre&gt;

Hard Disk
&lt;pre&gt;# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x91c391c3&lt;/pre&gt;

=Netbook Slakware Configuration=
Here i post some of my tips to setup slakware with this hardware.

==Screen==
The netbook video driver can only hit a 1024x600 size of screen, but we can change this using the 'xrandr' command to hit 1280x750 virtual. For do that you need to change '~/.xinitrc' and before you call your window manager you make a call of these command:
&lt;pre&gt;xrandr --output LVDS --mode 1024x600 --scale 1.25x1.25&lt;/pre&gt;

Here is my '''/etc/X11/xorg.conf''':
&lt;pre&gt;Section "Module"
          Load        "dbe"   # Double buffer extension
          SubSection  "extmod"
            Option    "omit xfree86-dga"   # don't initialise the DGA extension
          EndSubSection
          Load        "type1"
          Load        "freetype"
          Load       "glx"
EndSection

Section "Files"
          RgbPath     "/usr/share/X11/rgb"
          FontPath   "/usr/share/fonts/local/"
          FontPath   "/usr/share/fonts/misc/"
          FontPath   "/usr/share/fonts/OTF/"
          FontPath   "/usr/share/fonts/TTF/"
          FontPath   "/usr/share/fonts/Type1/"
          FontPath   "/usr/share/fonts/CID/"
          FontPath   "/usr/share/fonts/Speedo/"
          FontPath   "/usr/share/fonts/75dpi/:unscaled"
          FontPath   "/usr/share/fonts/100dpi/:unscaled"
          FontPath   "/usr/share/fonts/75dpi/"
          FontPath   "/usr/share/fonts/100dpi/"
          FontPath   "/usr/share/fonts/cyrillic/"
EndSection

Section "InputDevice"
          Driver      "kbd"
          Option     "XkbRules"      "xorg"
          Option     "XkbModel"      "pc105"
          Option     "XkbLayout"     "us"
EndSection

Section "InputDevice"
          Identifier  "Mouse1"
          Driver      "mouse"
          Option "Protocol"    "PS/2"
          Option "Device"      "/dev/mouse"
EndSection

Section "Monitor"
          Identifier  "My Monitor"
          HorizSync   31.5 - 50.0
          VertRefresh 40-90
EndSection

Section "Device"
          Identifier  "Intel GMA950"
          Driver      "intel"
EndSection

Section "Screen"
          Device      "Intel GMA950"
          Monitor     "My Monitor"
          DefaultDepth 24
          Subsection "Display"
              Depth       8
              Modes "1024x600" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       16
              Modes "1024x768" "800x600" "640x480"
          EndSubsection
          Subsection "Display"
              Depth       24
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
          Subsection "Display"
              Depth       32
              Modes "1024x600" "800x600" "640x480"
              Virtual 1280 750
          EndSubsection
EndSection

Section "ServerLayout"
          Identifier  "Simple Layout"
          Screen "Screen 1"
          InputDevice "Mouse1" "CorePointer"
          InputDevice "Keyboard1" "CoreKeyboard"
EndSection&lt;/pre&gt;

==Network==
* 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
* 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

With those cards the netbook can give a improve in network performance and will grow like a little monster in your network, with a wifi module called 'ath9k' and network module called 'r8169' they can do great things :)
===Bluetooth===
To get things done you will need to download the 'omnibook' package and compile in your slackware version. Once you do it you can follow these commands to test your connection:
&lt;pre&gt;# modprobe -v omnibook
insmod /lib/modules/2.6.29.6-smp/extra/omnibook.ko ectype=12 userset=1 wifi=1 bluetooth=1
# hciconfig   
hci0:	Type: USB
	BD Address: 00:22:58:FF:C2:DC ACL MTU: 310:10 SCO MTU: 64:8
	UP RUNNING PSCAN ISCAN 
	RX bytes:692 acl:0 sco:0 events:24 errors:0
	TX bytes:581 acl:0 sco:0 commands:24 errors:0

# hcitool scan
Scanning ...
	00:21:FC:B1:AC:97	Rosangela&lt;/pre&gt;
To be honest thats the best i could do with Bluetooth right now.

===Ethernet===
The easy way to setup your network is with DHCP. To make this you must change the file: '''/etc/rc.d/rc.inet1.conf''' to:
&lt;pre&gt;IFNAME[0]="eth0"
USE_DHCP[0]="yes"&lt;/pre&gt;
Or with IP fix:
&lt;pre&gt;IFNAME[0]="eth0"
USE_DHCP="no"
IPADDR[0]="192.168.0.10"
NETMASK[0]="255.255.255.0"
GATEWAY="192.168.0.254"&lt;/pre&gt;
Or you can set your ip manually in console with these commands:
&lt;pre&gt;# ifconfig eth0 192.168.0.25
# route add default gw 192.168.0.254&lt;/pre&gt;

===Wifi===
If you want to use WPA/PSK:
&lt;pre&gt;wpa_passphrase &lt;ESSID&gt; &lt;Passphrase&gt;
# wpa_passphrase house littled0g &gt; /etc/wpa_supplicant.conf.home &lt;/pre&gt;
If you see the file '/etc/wpa_supplicant.conf.home'
&lt;pre&gt;network={
	ssid="house"
	#psk="littled0g"
	psk=9dbaaf7031fd8cbc03674337ee9c724b65811b36546d2234676060b4144872b8
}&lt;/pre&gt;

=Tests of Performance=
&lt;pre&gt;# time dd bs=1k count=1000 if=/dev/urandom of=/dev/zero
1000+0 records in
1000+0 records out
1024000 bytes (1.0 MB) copied, 0.588823 s, 1.7 MB/s

real	0m0.593s
user	0m0.003s
sys	0m0.582s
# time dd bs=1k count=100000 if=/dev/urandom of=/dev/zero
100000+0 records in
100000+0 records out
102400000 bytes (102 MB) copied, 56.0481 s, 1.8 MB/s

real	0m56.053s
user	0m0.131s
sys	0m55.874s
# time dd bs=1k count=200000 if=/dev/urandom of=/tmp/mkshit
100000+0 records in
100000+0 records out
204800000 bytes (205 MB) copied, 120.184 s, 1.7 MB/s

real	2m0.189s
user	0m0.445s
sys	1m58.237s&lt;/pre&gt;

=My Opinion About the Slakware in this Netbook=
* You will not be unsatisfied.
* You need to buy at least one in your life. Only $490.
* Excelent to use like a second 'notebook' in your home and your work.</text>
    <sha1>34f6f87911fd14b35fd7c69d3160ab2f24aa4422</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Piping</title>
  <ns>0</ns>
  <id>132</id>
  <revision>
    <id>294</id>
    <parentid>157</parentid>
    <timestamp>2010-02-09T16:07:06Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1851" xml:space="preserve">You can mix [[Common Commands|commands]] to do certain things like [http://www.superiorthesis.com superior thesis]. 

  dmesg | grep hd

That will search dmesg and try to find the string "hd". Now piping is extremely useful. Another example of a pipe:

  dmesg | less

Now this command you can see the dmesg fully and is easier to read. 

You can also make longer 'pipelines' by using a pipe of several commands.  For instance, to browse the last fifty lines of &lt;code&gt;dmesg&lt;/code&gt;:

  dmseg | tail -50 | less

&lt;b&gt;Redirection:&lt;/b&gt;

This will save the dmesg information in your home directory in the file log.txt

  dmesg &gt; ~/log.txt

You can also redirect only the [[standard output|stdout]] by using '1&gt;' or only the [[error messages|stderr]] by using '2&gt;'.

For instance, if you want to run a command that gives a lot of junk as output, and you just want to see any errors, you can redirect the output to the null device (&lt;code&gt;/dev/null&lt;/code&gt;):

  mplayer /path/to/movie.avi 1&gt; /dev/null

You can also use the &gt; and &gt;&gt; to cat stdin into a new or existing file:

  bash-3.1$ cat &gt; newFile
  This is a new file            
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits

* Warning 
* cat &gt; fileThatAlreadExists WILL OVERWRITE THE FILE! be careful :-)

You can use cat to check the text you just added:

  bash-3.1$ cat newFile 
  This is a new file 
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits
  
Now that a file is created you can add to it with the &gt;&gt; operator
 
  bash-3.1$cat &gt;&gt; newFile
  This is a new line to add to newFile

And if you use cat again to read the file 

  bash-3.1$cat newFile
  This is a new file 
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits
  This is a new line to add to newFile


[[Category:Tutorials]]</text>
    <sha1>efd93c5e77022ab2cf624fbcaeaab469a3e2fd45</sha1>
  </revision>
  <revision>
    <id>295</id>
    <parentid>294</parentid>
    <timestamp>2010-02-09T16:16:29Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/LisaClayborn|LisaClayborn]] ([[User talk:LisaClayborn|Talk]]) to last version by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1798" xml:space="preserve">You can mix [[Common Commands|commands]] to do certain things. 

  dmesg | grep hd

That will search dmesg and try to find the string "hd". Now piping is extremely useful. Another example of a pipe:

  dmesg | less

Now this command you can see the dmesg fully and is easier to read. 

You can also make longer 'pipelines' by using a pipe of several commands.  For instance, to browse the last fifty lines of &lt;code&gt;dmesg&lt;/code&gt;:

  dmseg | tail -50 | less

&lt;b&gt;Redirection:&lt;/b&gt;

This will save the dmesg information in your home directory in the file log.txt

  dmesg &gt; ~/log.txt

You can also redirect only the [[standard output|stdout]] by using '1&gt;' or only the [[error messages|stderr]] by using '2&gt;'.

For instance, if you want to run a command that gives a lot of junk as output, and you just want to see any errors, you can redirect the output to the null device (&lt;code&gt;/dev/null&lt;/code&gt;):

  mplayer /path/to/movie.avi 1&gt; /dev/null

You can also use the &gt; and &gt;&gt; to cat stdin into a new or existing file:

  bash-3.1$ cat &gt; newFile
  This is a new file            
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits

* Warning 
* cat &gt; fileThatAlreadExists WILL OVERWRITE THE FILE! be careful :-)

You can use cat to check the text you just added:

  bash-3.1$ cat newFile 
  This is a new file 
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits
  
Now that a file is created you can add to it with the &gt;&gt; operator
 
  bash-3.1$cat &gt;&gt; newFile
  This is a new line to add to newFile

And if you use cat again to read the file 

  bash-3.1$cat newFile
  This is a new file 
  you can type text here and it
  get's redirected to the file newFile
  ctrl-c exits
  This is a new line to add to newFile


[[Category:Tutorials]]</text>
    <sha1>0c88be229e86591eb46af05c311019a8614eee42</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>PDF Printing</title>
  <ns>0</ns>
  <id>208</id>
  <revision>
    <id>296</id>
    <timestamp>2010-02-17T16:14:59Z</timestamp>
    <contributor>
      <username>Allend</username>
      <id>75</id>
    </contributor>
    <comment>Created page with '[[Category:Tips]] == PDF Printing ==  While many applications offer exporting output to portable document format (PDF) files, many others do not. It is easy to add a virtual PDF ...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4721" xml:space="preserve">[[Category:Tips]]
== PDF Printing ==

While many applications offer exporting output to portable document format (PDF) files, many others do not.
It is easy to add a virtual PDF printer to CUPS by installing the cups-pdf package that is available at http://www.slackbuilds.org

This works well for single documents, but if you print multiple documents that are parsed as having the same name then the older documents will be overwritten.
A solution to this is to run a script that watches for the creation of the PDF document in the spool directory (/var/spool/cups-pdf/&lt;username&gt; by default) and then moves the document to another directory (USERS_DIR). The script below (watch_for_spooled_pdf.sh kept in /home/xx/pdf_printing) also prepends a date and time string to keep the document names unique.
A user xx should start this script as a background process i.e. /home/xx/pdf_printing/watch_for_spooled_pdf.sh &amp;

&lt;pre&gt;
#!/bin/sh

# Script to watch for creation of .pdf files by CUPS-PDF in spool directory
#  and move to users directory prepending the creation date and time.
#
# This script uses the -m option to inotifywait and should never exit.

SPOOL_DIR=/var/spool/cups-pdf/xx/
USERS_DIR=/home/xx/Desktop/PDF_Files/

inotifywait  -mq --timefmt '%Y%m%d %H%M%S' --format '%T %f' \
  -e close_write $SPOOL_DIR \
  | while read date time file; do
      mv $SPOOL_DIR${file} $USERS_DIR${date}${time}_${file}
    done
&lt;/pre&gt;

What if printed PDF documents should be combined into one large PDF document?
A user could move the files to be combined to a new subdirectory and then run the script (combine.sh) shown below.
This script creates a single PDF document with bookmark entries to each of the individual documents using the facilities in the pdfpages and hyperref packages of LaTeX. The page order is in the order of creation date and time.
 
&lt;pre&gt;
#!/bin/sh

# Script to combine .pdf files
# Intended to be run from within a directory containing files to be concatenated.
# The directory name is accepted as a parameter

# First create a .tex file  for processing using pdflatex
OUTFILE=out2.tex
BKMK_TEXT=Contents
BKMK_ANCHOR=Beginning
BKMK_LEVEL=0

# If the directory name has been passed, then make it the working directory.
if [[ $1 ]]; then cd $1; fi

echo "\documentclass{article}" &gt; $OUTFILE
echo "\usepackage{pdfpages}" &gt;&gt; $OUTFILE
echo "\usepackage[bookmarksopen]{hyperref}" &gt;&gt; $OUTFILE

echo "\begin{document}" &gt;&gt; $OUTFILE
echo "\pdfbookmark["$BKMK_LEVEL"]{"$BKMK_TEXT"}{"$BKMK_ANCHOR"}" &gt;&gt; $OUTFILE

BKMK_LEVEL=1
for FILENAME in $( ls ./*.pdf ); do
# Create the text to be used in the bookmark entry.
#  NB. Need to substitute 'space' for 'underscore' to be valid bookmark text.
  BKMK_TEXT=$(echo $FILENAME | cut -b1-17 --complement | sed s/_/\ /g | sed s/\.pdf$//g)
# Create a unique anchor point based on date and time prepended to filename
  BKMK_ANCHOR=$(echo $FILENAME | cut -b3-16)
  echo "\pdfbookmark["$BKMK_LEVEL"]{"$BKMK_TEXT"}{"$BKMK_ANCHOR"}" &gt;&gt; $OUTFILE
  echo "\includepdf[pages=-,fitpaper]{"$FILENAME"}" &gt;&gt; $OUTFILE
done

echo "\end{document}" &gt;&gt; $OUTFILE

# Now process the .tex file
# Do a second run so that bookmark entries are resolved
pdflatex $OUTFILE; pdflatex $OUTFILE
wait

# Rename the created .pdf file
mv $(basename $OUTFILE .tex).pdf $(date +%Y%m%d%H%M%S)_All.pdf

# Cleanup files left by pdflatex processing
rm $(basename $OUTFILE .tex)*

# Cleanup trigger file if this script has been started from watch_for_combine_start.sh script
if [ -f combine.start ]; then rm combine.start; fi

# Remove this script
rm $0
&lt;/pre&gt;

As a convenience, the user could also have a second background process running the script (watch_for_combine_start.sh) shown below. This script watches for the creation of a 'trigger' file (combine.start) in the directory tree and then executes the 'combine.sh' script shown above. This is useful in a network environment, so that a Windows user manipulating the files via a Samba share can create the combined PDF file without having to log in to the Slackware Linux server.

&lt;pre&gt;
#!/bin/sh

# Script to watch for creation of a trigger file in a directory tree.
#  This event causes another script to be copied into the tree subdirectory and run.
#  The tree subdirectory name is passed as a parameter.
#
# This script should never exit

WATCH_DIR=/home/xx/Desktop/PDF_Files
TRIGGER_FILE=combine.start
SCRIPT_FILE=/home/xx/pdf_printing/combine.sh

inotifywait  -mqr --timefmt '%Y%m%d %H%M%S' --format '%T %w %f' \
  -e close_write $WATCH_DIR \
  | while read date time path file; do
      if [ ${file} == $TRIGGER_FILE ]; then
        cp $SCRIPT_FILE ${path}
        sh ${path}/$(basename $SCRIPT_FILE) ${path} &gt; /dev/null &amp;
      fi
    done
&lt;/pre&gt;</text>
    <sha1>c78d766e919a6ac76bf2cd3f4714fcaf2c2f2d5c</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Timidity++</title>
  <ns>0</ns>
  <id>209</id>
  <revision>
    <id>297</id>
    <timestamp>2010-02-20T22:55:11Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Created page with '[[category:tutorials]] '''TiMidity++''' is a software synthesizer. It can play MIDI files by converting them into PCM waveform data; give it a MIDI data along with digital instru...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1832" xml:space="preserve">[[category:tutorials]]
'''TiMidity++''' is a software synthesizer. It can play MIDI files by converting them into PCM waveform data; give it a MIDI data along with digital instrument data files, then it synthesizes them in real-time, and plays. It can not only play sounds, but also can save the generated waveforms into hard disks as various audio file formats.

== Prerequisities ==
=== Timidity ===
* Timidity++
=== Patchset ===
A patchset is required for
MIDI files to be audible through TiMidity++. Choose one of them.
* Freepats 
* Eawpats - Sounds nicer, but may have some intellectual property issues. If this is a concern to you, use freepats instead (For more information, see /usr/doc/eawpats-12/copyrigh.txt).  
 
== Installation ==
Compile it from source or use slackbuild.

== Configuration ==
Timidity++ won't play any sound by default. If you encounter this error, you have to tell Timidity++ where to find patchset.
&lt;pre&gt;
No instrument mapped to tone bank X, program YY - this instrument will not be heard
&lt;/pre&gt;
To do so, add following line to ''/etc/timidity.cfg''

For Freepats:
&lt;pre&gt;
source /etc/timidity/freepats.cfg
&lt;/pre&gt;
For Eawpats:
&lt;pre&gt;
source /etc/timidity/eawpats.cfg
&lt;/pre&gt;

== Using ==
At this point, you should have Timidity++ working. Test it by command:
&lt;pre&gt;# timidity somemidifile.mid&lt;/pre&gt;

=== Playback ===
To play MIDI type previous command
&lt;pre&gt; # timidity &lt;somemidifile&gt;&lt;/pre&gt;

=== Sound server for other apps ===
This is useful, when application native sound engine doesn't work or Timidity++ sounds nicer than the application native sound engine (eg. TuxGuitar using Java soundbanks).

To start a sound server using ALSA
&lt;pre&gt;# timidity -iA -Os&lt;/pre&gt;
where
* -iA means Launch TiMidity++ as ALSA sequencer client
* -Os means Output to ALSA

=== Other usage ===
For other usage see manpage.</text>
    <sha1>36e32489d7aa74bc19660f20ee348fa26359703f</sha1>
  </revision>
  <revision>
    <id>298</id>
    <parentid>297</parentid>
    <timestamp>2010-02-20T22:55:42Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1834" xml:space="preserve">[[category:tutorials]]
'''TiMidity++''' is a software synthesizer. It can play MIDI files by converting them into PCM waveform data; give it a MIDI data along with digital instrument data files, then it synthesizes them in real-time, and plays. It can not only play sounds, but also can save the generated waveforms into hard disks as various audio file formats.

== Prerequisities ==
=== Timidity++ ===
* Timidity++
=== Patchset ===
A patchset is required for
MIDI files to be audible through TiMidity++. Choose one of them.
* Freepats 
* Eawpats - Sounds nicer, but may have some intellectual property issues. If this is a concern to you, use freepats instead (For more information, see /usr/doc/eawpats-12/copyrigh.txt).  
 
== Installation ==
Compile it from source or use slackbuild.

== Configuration ==
Timidity++ won't play any sound by default. If you encounter this error, you have to tell Timidity++ where to find patchset.
&lt;pre&gt;
No instrument mapped to tone bank X, program YY - this instrument will not be heard
&lt;/pre&gt;
To do so, add following line to ''/etc/timidity.cfg''

For Freepats:
&lt;pre&gt;
source /etc/timidity/freepats.cfg
&lt;/pre&gt;
For Eawpats:
&lt;pre&gt;
source /etc/timidity/eawpats.cfg
&lt;/pre&gt;

== Using ==
At this point, you should have Timidity++ working. Test it by command:
&lt;pre&gt;# timidity somemidifile.mid&lt;/pre&gt;

=== Playback ===
To play MIDI type previous command
&lt;pre&gt; # timidity &lt;somemidifile&gt;&lt;/pre&gt;

=== Sound server for other apps ===
This is useful, when application native sound engine doesn't work or Timidity++ sounds nicer than the application native sound engine (eg. TuxGuitar using Java soundbanks).

To start a sound server using ALSA
&lt;pre&gt;# timidity -iA -Os&lt;/pre&gt;
where
* -iA means Launch TiMidity++ as ALSA sequencer client
* -Os means Output to ALSA

=== Other usage ===
For other usage see manpage.</text>
    <sha1>b41c471bb79fa931930da479b7b7c4e44141001f</sha1>
  </revision>
  <revision>
    <id>299</id>
    <parentid>298</parentid>
    <timestamp>2010-02-21T15:21:57Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <comment>moved [[Timidity]] to [[Timidity++]]:&amp;#32;A mistake in page name.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1834" xml:space="preserve">[[category:tutorials]]
'''TiMidity++''' is a software synthesizer. It can play MIDI files by converting them into PCM waveform data; give it a MIDI data along with digital instrument data files, then it synthesizes them in real-time, and plays. It can not only play sounds, but also can save the generated waveforms into hard disks as various audio file formats.

== Prerequisities ==
=== Timidity++ ===
* Timidity++
=== Patchset ===
A patchset is required for
MIDI files to be audible through TiMidity++. Choose one of them.
* Freepats 
* Eawpats - Sounds nicer, but may have some intellectual property issues. If this is a concern to you, use freepats instead (For more information, see /usr/doc/eawpats-12/copyrigh.txt).  
 
== Installation ==
Compile it from source or use slackbuild.

== Configuration ==
Timidity++ won't play any sound by default. If you encounter this error, you have to tell Timidity++ where to find patchset.
&lt;pre&gt;
No instrument mapped to tone bank X, program YY - this instrument will not be heard
&lt;/pre&gt;
To do so, add following line to ''/etc/timidity.cfg''

For Freepats:
&lt;pre&gt;
source /etc/timidity/freepats.cfg
&lt;/pre&gt;
For Eawpats:
&lt;pre&gt;
source /etc/timidity/eawpats.cfg
&lt;/pre&gt;

== Using ==
At this point, you should have Timidity++ working. Test it by command:
&lt;pre&gt;# timidity somemidifile.mid&lt;/pre&gt;

=== Playback ===
To play MIDI type previous command
&lt;pre&gt; # timidity &lt;somemidifile&gt;&lt;/pre&gt;

=== Sound server for other apps ===
This is useful, when application native sound engine doesn't work or Timidity++ sounds nicer than the application native sound engine (eg. TuxGuitar using Java soundbanks).

To start a sound server using ALSA
&lt;pre&gt;# timidity -iA -Os&lt;/pre&gt;
where
* -iA means Launch TiMidity++ as ALSA sequencer client
* -Os means Output to ALSA

=== Other usage ===
For other usage see manpage.</text>
    <sha1>b41c471bb79fa931930da479b7b7c4e44141001f</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Timidity</title>
  <ns>0</ns>
  <id>210</id>
  <revision>
    <id>300</id>
    <timestamp>2010-02-21T15:21:57Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>moved [[Timidity]] to [[Timidity++]]:&amp;#32;A mistake in page name.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="24" xml:space="preserve">#REDIRECT [[Timidity++]]</text>
    <sha1>93be92941a720eb3a557a6f078e84d84fe0b2362</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Burning CD/DVD</title>
  <ns>0</ns>
  <id>27</id>
  <revision>
    <id>302</id>
    <parentid>36</parentid>
    <timestamp>2010-02-25T00:56:24Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Added ISO Master</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2742" xml:space="preserve">[[Category:Tutorials]]
Random information about burning CD/DVD's with slack (and linux in general). Feel free to tack on any insight you might have on the subject.

==The Basics==

In most modern situations, you will not have to tell the software which device to use (unless you have more than one device). In case you have older hardware or software, it may be necessary to pass the device info. On a 2.6 kernel, you can use:

 cdrecord dev=/dev/someDevice

On a 2.4 kernel, you use one of these commands:

 cdrdao scanbus
 cdrecord -scanbus dev=ATA
This should present you with some information:
 ATA:1,0,0            DVDRW   , IDE1004         , 0151
 1,0,0   100) 'DVDRW   ' 'IDE1004         ' '0151' Removable CD-ROM
To pass this device (1,0,0) to cdrdao or cdrecord:
 cdrdao --device 1,0,0
 cdrecord dev=ATA:1,0,0
These will be SCSI ID's if you have a SCSI burner, or are using ide-scsi (no-longer necessary)

==CDR==
===Creating an image===
====From a disc====
 readcd dev=ATA:1,0,0 f=image.iso
 dd if=/dev/cdrom of=image.iso
====From a directory of files====
-r provides Rock Ridge extension (for posix)&lt;br&gt;
-J provides Joliet extension (for windows)
 mkisofs -o image.iso -J -r /path/to/files/
===Burning an image===
 cdrdao write image.cue
 cdrecord -dao driveropts=burnfree dev=/dev/cdrom image.iso 

==DVDR==
===From an image===
 growisofs -dvd-compat -Z /dev/dvd=dvd.iso
===A directory of files===
-R provides Rock Ridge extension (for posix)&lt;br&gt;
-J provides Joliet extension (for windows)
 growisofs -dvd-compat -Z /dev/dvd -J -R /path/to/files/
===A DVD Video===
This path must be structured like a DVD, see Authoring.
 growisofs -Z /dev/dvd -dvd-video /path/to/dvd/files/

==Blanking==
===Quick===
 cdrdao blank --blank-mode minimal
 dvd+rw-format -blank /dev/dvd
===Full===
 cdrdao blank --blank-mode full
 dvd+rw-format -blank=full /dev/dvd

==Links==
===Burning Software===
; DVD+RW-Tools : http://fy.chalmers.se/~appro/linux/DVD+RW/
; CDRDAO : http://cdrdao.sourceforge.net/
; Cdrtools : http://www.fokus.fhg.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html

===GUI Frontends===
; X-CD-Roast : http://www.xcdroast.org/
; Gnome CD Master : http://cdrdao.sourceforge.net/gcdmaster/index.html
; Gnome Toaster : http://gnometoaster.rulez.org/
; Nautilus-CD-Burner : http://www.gnome.org/projects/nautilus/
; K3B : http://www.k3b.org/

===Authoring Tools===
; dvdauthor : http://dvdauthor.sourceforge.net/
; DVDStyler : http://dvdstyler.sourceforge.net/
; &amp;lsquo;Q&amp;lsquo; DVD-Author : http://qdvdauthor.sourceforge.net/

===Format Converters===
; CCD2ISO : http://ccd2iso.sourceforge.net/
; NRG2ISO : http://gregory.kokanosky.free.fr/v4/linux/nrg2iso.en.html
; ISO Master : http://www.littlesvr.ca/isomaster/</text>
    <sha1>fff2ee6481a834a93c295f7e78d70b7254b9261a</sha1>
  </revision>
  <revision>
    <id>303</id>
    <parentid>302</parentid>
    <timestamp>2010-02-25T20:51:18Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>K3B issue</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3735" xml:space="preserve">[[Category:Tutorials]]
Random information about burning CD/DVD's with slack (and linux in general). Feel free to tack on any insight you might have on the subject.

==The Basics==

In most modern situations, you will not have to tell the software which device to use (unless you have more than one device). In case you have older hardware or software, it may be necessary to pass the device info. On a 2.6 kernel, you can use:

 cdrecord dev=/dev/someDevice

On a 2.4 kernel, you use one of these commands:

 cdrdao scanbus
 cdrecord -scanbus dev=ATA
This should present you with some information:
 ATA:1,0,0            DVDRW   , IDE1004         , 0151
 1,0,0   100) 'DVDRW   ' 'IDE1004         ' '0151' Removable CD-ROM
To pass this device (1,0,0) to cdrdao or cdrecord:
 cdrdao --device 1,0,0
 cdrecord dev=ATA:1,0,0
These will be SCSI ID's if you have a SCSI burner, or are using ide-scsi (no-longer necessary)

==CDR==
===Creating an image===
====From a disc====
 readcd dev=ATA:1,0,0 f=image.iso
 dd if=/dev/cdrom of=image.iso
====From a directory of files====
-r provides Rock Ridge extension (for posix)&lt;br&gt;
-J provides Joliet extension (for windows)
 mkisofs -o image.iso -J -r /path/to/files/
===Burning an image===
 cdrdao write image.cue
 cdrecord -dao driveropts=burnfree dev=/dev/cdrom image.iso 

==DVDR==
===From an image===
 growisofs -dvd-compat -Z /dev/dvd=dvd.iso
===A directory of files===
-R provides Rock Ridge extension (for posix)&lt;br&gt;
-J provides Joliet extension (for windows)
 growisofs -dvd-compat -Z /dev/dvd -J -R /path/to/files/
===A DVD Video===
This path must be structured like a DVD, see Authoring.
 growisofs -Z /dev/dvd -dvd-video /path/to/dvd/files/

==Blanking==
===Quick===
 cdrdao blank --blank-mode minimal
 dvd+rw-format -blank /dev/dvd
===Full===
 cdrdao blank --blank-mode full
 dvd+rw-format -blank=full /dev/dvd

==Links==
===Burning Software===
; DVD+RW-Tools : http://fy.chalmers.se/~appro/linux/DVD+RW/
; CDRDAO : http://cdrdao.sourceforge.net/
; Cdrtools : http://www.fokus.fhg.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html

===GUI Frontends===
; X-CD-Roast : http://www.xcdroast.org/
; Gnome CD Master : http://cdrdao.sourceforge.net/gcdmaster/index.html
; Gnome Toaster : http://gnometoaster.rulez.org/
; Nautilus-CD-Burner : http://www.gnome.org/projects/nautilus/
; K3B : http://www.k3b.org/
* As mentioned in [ftp://ftp.slackware.cz/slackware/slackware-13.0/RELEASE_NOTES RELEASE_NOTES] K3B shipped with KDE4 sometimes doesn't recognize CD/DVD writer. 
&lt;pre&gt;
One of the issues we're aware of is that
k3b hasn't been working as well as the KDE3 version for some people
(it works fine here, but we have heard some reports), and there are
some other KDE applications where people still prefer the old versions.
To help with this, there are KDE3 compatibility packages that can
be found in /extra/kde3-compat/.  With these installed, most KDE3
programs will run.  A KDE3 version of k3b is also included in that
directory.
&lt;/pre&gt;
You can still read, mount, rip CD/DVD, but it's annoying. 
If K3B gives you following error:
&lt;pre&gt;No CD/DVD writer found.&lt;/pre&gt;
use "old" K3B 1.0.5 from KDE 3.5.10 (in Slackware 13.0 it's ''k3b3'' package inside from ''extra/kde3-compat'' directory) or try Slackware-current where K3B (1.69.0 Alpha 4) is reported as again working (despite it's Alpha state).

===Authoring Tools===
; dvdauthor : http://dvdauthor.sourceforge.net/
; DVDStyler : http://dvdstyler.sourceforge.net/
; &amp;lsquo;Q&amp;lsquo; DVD-Author : http://qdvdauthor.sourceforge.net/

===Format Converters===
; CCD2ISO : http://ccd2iso.sourceforge.net/
; NRG2ISO : http://gregory.kokanosky.free.fr/v4/linux/nrg2iso.en.html
; ISO Master : http://www.littlesvr.ca/isomaster/</text>
    <sha1>102775f41885cc29c3fa3aa8bb49371d557fb4e6</sha1>
  </revision>
  <revision>
    <id>304</id>
    <parentid>303</parentid>
    <timestamp>2010-02-25T20:53:51Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <comment>correction of typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3723" xml:space="preserve">[[Category:Tutorials]]
Random information about burning CD/DVD's with slack (and linux in general). Feel free to tack on any insight you might have on the subject.

==The Basics==

In most modern situations, you will not have to tell the software which device to use (unless you have more than one device). In case you have older hardware or software, it may be necessary to pass the device info. On a 2.6 kernel, you can use:

 cdrecord dev=/dev/someDevice

On a 2.4 kernel, you use one of these commands:

 cdrdao scanbus
 cdrecord -scanbus dev=ATA
This should present you with some information:
 ATA:1,0,0            DVDRW   , IDE1004         , 0151
 1,0,0   100) 'DVDRW   ' 'IDE1004         ' '0151' Removable CD-ROM
To pass this device (1,0,0) to cdrdao or cdrecord:
 cdrdao --device 1,0,0
 cdrecord dev=ATA:1,0,0
These will be SCSI ID's if you have a SCSI burner, or are using ide-scsi (no-longer necessary)

==CDR==
===Creating an image===
====From a disc====
 readcd dev=ATA:1,0,0 f=image.iso
 dd if=/dev/cdrom of=image.iso
====From a directory of files====
-r provides Rock Ridge extension (for posix)&lt;br&gt;
-J provides Joliet extension (for windows)
 mkisofs -o image.iso -J -r /path/to/files/
===Burning an image===
 cdrdao write image.cue
 cdrecord -dao driveropts=burnfree dev=/dev/cdrom image.iso 

==DVDR==
===From an image===
 growisofs -dvd-compat -Z /dev/dvd=dvd.iso
===A directory of files===
-R provides Rock Ridge extension (for posix)&lt;br&gt;
-J provides Joliet extension (for windows)
 growisofs -dvd-compat -Z /dev/dvd -J -R /path/to/files/
===A DVD Video===
This path must be structured like a DVD, see Authoring.
 growisofs -Z /dev/dvd -dvd-video /path/to/dvd/files/

==Blanking==
===Quick===
 cdrdao blank --blank-mode minimal
 dvd+rw-format -blank /dev/dvd
===Full===
 cdrdao blank --blank-mode full
 dvd+rw-format -blank=full /dev/dvd

==Links==
===Burning Software===
; DVD+RW-Tools : http://fy.chalmers.se/~appro/linux/DVD+RW/
; CDRDAO : http://cdrdao.sourceforge.net/
; Cdrtools : http://www.fokus.fhg.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html

===GUI Frontends===
; X-CD-Roast : http://www.xcdroast.org/
; Gnome CD Master : http://cdrdao.sourceforge.net/gcdmaster/index.html
; Gnome Toaster : http://gnometoaster.rulez.org/
; Nautilus-CD-Burner : http://www.gnome.org/projects/nautilus/
; K3B : http://www.k3b.org/
* As mentioned in [ftp://ftp.slackware.cz/slackware/slackware-13.0/RELEASE_NOTES RELEASE_NOTES] K3B shipped with KDE4 sometimes doesn't recognize CD/DVD writer. 
&lt;pre&gt;
One of the issues we're aware of is that
k3b hasn't been working as well as the KDE3 version for some people
(it works fine here, but we have heard some reports), and there are
some other KDE applications where people still prefer the old versions.
To help with this, there are KDE3 compatibility packages that can
be found in /extra/kde3-compat/.  With these installed, most KDE3
programs will run.  A KDE3 version of k3b is also included in that
directory.
&lt;/pre&gt;
You can still read, mount, rip CD/DVD, but it's annoying. 
If K3B gives you following error:
&lt;pre&gt;No CD/DVD writer found.&lt;/pre&gt;
use "old" K3B 1.0.5 from KDE 3.5.10 (in Slackware 13.0 it's ''k3b3'' package found in ''extra/kde3-compat/'') or try Slackware-current where K3B (1.69.0 Alpha 4) is reported as again working (despite it's Alpha state).

===Authoring Tools===
; dvdauthor : http://dvdauthor.sourceforge.net/
; DVDStyler : http://dvdstyler.sourceforge.net/
; &amp;lsquo;Q&amp;lsquo; DVD-Author : http://qdvdauthor.sourceforge.net/

===Format Converters===
; CCD2ISO : http://ccd2iso.sourceforge.net/
; NRG2ISO : http://gregory.kokanosky.free.fr/v4/linux/nrg2iso.en.html
; ISO Master : http://www.littlesvr.ca/isomaster/</text>
    <sha1>e6c8b0b00553eb070c7c612056ac645e75321964</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>305</id>
    <parentid>245</parentid>
    <timestamp>2010-03-01T05:32:39Z</timestamp>
    <contributor>
      <username>Jcm</username>
      <id>85</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1393" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>6a431301a770793e7a1be206b55d79c31f63b40f</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>User:Jcm</title>
  <ns>2</ns>
  <id>211</id>
  <revision>
    <id>306</id>
    <timestamp>2010-03-01T05:33:30Z</timestamp>
    <contributor>
      <username>Jcm</username>
      <id>85</id>
    </contributor>
    <comment>Created page with '[http://www.jonmasters.org/]'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28" xml:space="preserve">[http://www.jonmasters.org/]</text>
    <sha1>874d22a465fe88af2f046291d9ed206815c17db9</sha1>
  </revision>
  <revision>
    <id>307</id>
    <parentid>306</parentid>
    <timestamp>2010-03-01T05:34:23Z</timestamp>
    <contributor>
      <username>Jcm</username>
      <id>85</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="40" xml:space="preserve">Jon Masters [http://www.jonmasters.org/]</text>
    <sha1>62aca99972b3ffacaaac614a7d0af436380e67ad</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>Utf-8 linux console</title>
  <ns>0</ns>
  <id>177</id>
  <revision>
    <id>308</id>
    <parentid>228</parentid>
    <timestamp>2010-03-01T13:37:50Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4418" xml:space="preserve">[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://home.tiscali.nl/t876506/utf8tbl.html]http://home.tiscali.nl/t876506/utf8tbl.html

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>9cde8b79ff70c7b18df1de07eec1e82dc6de4390</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>DVB</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>309</id>
    <parentid>103</parentid>
    <timestamp>2010-03-03T19:45:22Z</timestamp>
    <contributor>
      <username>Linuxman</username>
      <id>87</id>
    </contributor>
    <minor/>
    <comment>/* Udev Rules */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9981" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps
Eventually, my SlackBuild will be hosted here http://slackbuilds.rlworkman.net/CONTRIB/linuxtv-dvb-apps/ (thanks to robw810).

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>75a8ff975f95ea3d57850216885694a0868a88d1</sha1>
  </revision>
</page>
<page arvcontinue="20091006133013|255">
  <title>SLiM</title>
  <ns>0</ns>
  <id>212</id>
  <revision>
    <id>310</id>
    <timestamp>2010-03-06T18:49:21Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Created page with '= SLiM = '''SLiM (Simple Login Manager)''' is a Desktop-independent graphical login manager for X11, derived from [http://largo.windowmaker.org/Login.app/ Login.app].  It aims to...'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3290" xml:space="preserve">= SLiM =
'''SLiM (Simple Login Manager)''' is a Desktop-independent graphical login manager for X11, derived from [http://largo.windowmaker.org/Login.app/ Login.app]. 
It aims to be light and simple, although completely configurable through themes and an option file; is suitable for machines on which remote login functionalities are not needed.

== Features ==
* PNG and XFT support for alpha transparency and antialiased fonts
* External themes support
* Configurable runtime options: X server, login / shutdown / reboot commands
* Single (GDM-like) or double (XDM-like) input control
* Can load predefined user at startup
* Configurable welcome / shutdown messages
* Random theme selection

== Requirements ==
* X11
* libpng
* libjpeg
* freetype
== Instalation ==
Use package, SlackBuild or compile it from source.

== Configuration ==
=== Themes ===
Themes are located in /usr/share/slim/themes. If you want more themes, try themepack or standalone theme from [http://developer.berlios.de/project/showfiles.php?group_id=2663 project download page]. Unpack file there
&lt;pre&gt;
$ tar xvzf themefile.tar.gz -C /usr/share/slim/themes
&lt;/pre&gt;
 
By default SLiM use ''default'' theme. You can change it in it's configuration file /etc/slim.conf by rewriting ''current_theme'' line
&lt;pre&gt;
# current theme, use comma separated list to specify a set to 
# randomly choose from
#current_theme       default
current_theme       theme_you_like
&lt;/pre&gt;
If you use SlackBuild (at least for 13.0) it comes with nice Slackware theme. Rewrite ''current_theme'' line to 
&lt;pre&gt;
current_theme       slackware-black
&lt;/pre&gt; 

=== Startup ===
Edit run level 4 init script - /etc/rc.d/rc.4 - to try start SLiM as default graphical login manager. You have to add these lines '''before''' GDM (or whatever graphical login manager you have as default; GDM is set as first to start by default)
&lt;pre&gt;
#! /bin/sh
#
# rc.4		This file is executed by init(8) when the system is being
#		initialized for run level 4 (XDM)
#
# Version:	@(#)/etc/rc.d/rc.4	2.00	02/17/93
#
# Author:	Fred N. van Kempen, &lt;waltje@uwalt.nl.mugnet.org&gt;
# At least 47% rewritten by:  Patrick J. Volkerding &lt;volkerdi@slackware.com&gt;
#

# Tell the viewers what's going to happen...
echo "Starting up X11 session manager..."

# Add this if statement to the top
# If you have SliM, it goes first
#---------------------------------

if [ -x /usr/bin/slim ]; then
  exec /usr/bin/slim -d 
fi

#---------------------------------
# end of new if statement

# Try to use GNOME's gdm session manager.  This comes first because if
# gdm is on the machine then the user probably installed it and wants
# to use it by default:
if [ -x /usr/bin/gdm ]; then
  exec /usr/bin/gdm -nodaemon
fi
&lt;/pre&gt; 

If you aren't already using this, set run level to 4 in /etc/inittab
&lt;pre&gt;
# These are the default runlevels in Slackware:
#   0 = halt
#   1 = single user mode
#   2 = unused (but configured the same as runlevel 3)
#   3 = multiuser mode (default Slackware runlevel)
#   4 = X11 with KDM/GDM/XDM (session managers)
#   5 = unused (but configured the same as runlevel 3)
#   6 = reboot

# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:
&lt;/pre&gt;
Reboot and you have nice simple login manager running :~)
== Links ==
[http://slim.berlios.de Project homepage]</text>
    <sha1>eaf47d14763bba1b658aafe397c67208e0149bf5</sha1>
  </revision>
  <revision>
    <id>311</id>
    <parentid>310</parentid>
    <timestamp>2010-03-06T18:51:36Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <comment>category added</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3304" xml:space="preserve">[[category:tutorials]]
'''SLiM (Simple Login Manager)''' is a Desktop-independent graphical login manager for X11, derived from [http://largo.windowmaker.org/Login.app/ Login.app]. 
It aims to be light and simple, although completely configurable through themes and an option file; is suitable for machines on which remote login functionalities are not needed.

== Features ==
* PNG and XFT support for alpha transparency and antialiased fonts
* External themes support
* Configurable runtime options: X server, login / shutdown / reboot commands
* Single (GDM-like) or double (XDM-like) input control
* Can load predefined user at startup
* Configurable welcome / shutdown messages
* Random theme selection

== Requirements ==
* X11
* libpng
* libjpeg
* freetype
== Instalation ==
Use package, SlackBuild or compile it from source.

== Configuration ==
=== Themes ===
Themes are located in /usr/share/slim/themes. If you want more themes, try themepack or standalone theme from [http://developer.berlios.de/project/showfiles.php?group_id=2663 project download page]. Unpack file there
&lt;pre&gt;
$ tar xvzf themefile.tar.gz -C /usr/share/slim/themes
&lt;/pre&gt;
 
By default SLiM use ''default'' theme. You can change it in it's configuration file /etc/slim.conf by rewriting ''current_theme'' line
&lt;pre&gt;
# current theme, use comma separated list to specify a set to 
# randomly choose from
#current_theme       default
current_theme       theme_you_like
&lt;/pre&gt;
If you use SlackBuild (at least for 13.0) it comes with nice Slackware theme. Rewrite ''current_theme'' line to 
&lt;pre&gt;
current_theme       slackware-black
&lt;/pre&gt; 

=== Startup ===
Edit run level 4 init script - /etc/rc.d/rc.4 - to try start SLiM as default graphical login manager. You have to add these lines '''before''' GDM (or whatever graphical login manager you have as default; GDM is set as first to start by default)
&lt;pre&gt;
#! /bin/sh
#
# rc.4		This file is executed by init(8) when the system is being
#		initialized for run level 4 (XDM)
#
# Version:	@(#)/etc/rc.d/rc.4	2.00	02/17/93
#
# Author:	Fred N. van Kempen, &lt;waltje@uwalt.nl.mugnet.org&gt;
# At least 47% rewritten by:  Patrick J. Volkerding &lt;volkerdi@slackware.com&gt;
#

# Tell the viewers what's going to happen...
echo "Starting up X11 session manager..."

# Add this if statement to the top
# If you have SliM, it goes first
#---------------------------------

if [ -x /usr/bin/slim ]; then
  exec /usr/bin/slim -d 
fi

#---------------------------------
# end of new if statement

# Try to use GNOME's gdm session manager.  This comes first because if
# gdm is on the machine then the user probably installed it and wants
# to use it by default:
if [ -x /usr/bin/gdm ]; then
  exec /usr/bin/gdm -nodaemon
fi
&lt;/pre&gt; 

If you aren't already using this, set run level to 4 in /etc/inittab
&lt;pre&gt;
# These are the default runlevels in Slackware:
#   0 = halt
#   1 = single user mode
#   2 = unused (but configured the same as runlevel 3)
#   3 = multiuser mode (default Slackware runlevel)
#   4 = X11 with KDM/GDM/XDM (session managers)
#   5 = unused (but configured the same as runlevel 3)
#   6 = reboot

# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:
&lt;/pre&gt;
Reboot and you have nice simple login manager running :~)
== Links ==
[http://slim.berlios.de Project homepage]</text>
    <sha1>036071edc0463993d0459ee168cec6353da76145</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>312</id>
    <parentid>263</parentid>
    <timestamp>2010-03-09T00:20:45Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3518" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.15.2. [[User:Erik|Erik]] 00:20, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>0454a2a7482e27cda2d624f4f2284808b1d81e9b</sha1>
  </revision>
  <revision>
    <id>313</id>
    <parentid>312</parentid>
    <timestamp>2010-03-09T00:24:52Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Erik|Erik]] ([[User talk:Erik|Talk]]) to last revision by [[User:Rworkman|Rworkman]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3438" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>6b3b81a3a9d0d4d69d7c37ee6df9263adf3cfe14</sha1>
  </revision>
  <revision>
    <id>314</id>
    <parentid>313</parentid>
    <timestamp>2010-03-09T00:25:21Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3520" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>2f7fea1e7db732b200c136c9e7858575e233b744</sha1>
  </revision>
  <revision>
    <id>345</id>
    <parentid>314</parentid>
    <timestamp>2010-04-07T09:33:15Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3588" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC) | Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>91dcf0d37788b49b535866645856b7eeb26bf648</sha1>
  </revision>
  <revision>
    <id>364</id>
    <parentid>345</parentid>
    <timestamp>2010-05-30T08:31:44Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>news, patch</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3654" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>75660b4f237ba65fae538c00c3ffeac5aefc2aad</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Kernel-packaging</title>
  <ns>0</ns>
  <id>213</id>
  <revision>
    <id>315</id>
    <timestamp>2010-03-11T04:31:55Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>Created page with '= Creating a Custom Package of Kernel and Modules =  *Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and …'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6338" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.


The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==


From your kernel source directory do 
   
   make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

   make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

   make O=/tmp/kernel-build
   make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot

   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/bash
 
   SOURCE=/usr/src/linux-2.6.29.6-jabberwok
   ARCH=i386
   KARCH=i686
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=2.6.29.6
   BUILD=1
   TAG=_daw
   LOCALNAME=jabberwok
   OUTPUT=/tmp
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   BUILDDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $BUILDDIR
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $BUILDDIR/$(dirname $i)
      install -m 644 -v $i $BUILDDIR/$(dirname $i)
   done
 
   mkdir $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
                   |-----handy-ruler------------------------------------------------------|
   kernel-jabberwok: kernel and modules 2.6.29.6-jabberwok
   kernel-jabberwok:
   kernel-jabberwok: Jabberwokky type kernel!
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>8497101f5ab8034263df0e20756fb5393946ed85</sha1>
  </revision>
  <revision>
    <id>316</id>
    <parentid>315</parentid>
    <timestamp>2010-03-11T04:32:58Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6337" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.


The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==


From your kernel source directory do 
   
   make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

   make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

   make O=/tmp/kernel-build
   make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/bash
 
   SOURCE=/usr/src/linux-2.6.29.6-jabberwok
   ARCH=i386
   KARCH=i686
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=2.6.29.6
   BUILD=1
   TAG=_daw
   LOCALNAME=jabberwok
   OUTPUT=/tmp
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   BUILDDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $BUILDDIR
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $BUILDDIR/$(dirname $i)
      install -m 644 -v $i $BUILDDIR/$(dirname $i)
   done
 
   mkdir $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
                   |-----handy-ruler------------------------------------------------------|
   kernel-jabberwok: kernel and modules 2.6.29.6-jabberwok
   kernel-jabberwok:
   kernel-jabberwok: Jabberwokky type kernel!
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>6841dc5587229bc88ed477ee707a797d8f1216cd</sha1>
  </revision>
  <revision>
    <id>317</id>
    <parentid>316</parentid>
    <timestamp>2010-03-11T05:02:29Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6311" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.


The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==


From your kernel source directory do 
   
   make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

   make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

   make O=/tmp/kernel-build
   make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/bash
 
   SOURCE=/usr/src/linux-2.6.29.6-jabberwok
   ARCH=i386
   KARCH=i686
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=2.6.29.6
   BUILD=1
   TAG=_daw
   LOCALNAME=jabberwok
   OUTPUT=/tmp
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
                   |-----handy-ruler------------------------------------------------------|
   kernel-jabberwok: kernel and modules 2.6.29.6-jabberwok
   kernel-jabberwok:
   kernel-jabberwok: Jabberwokky type kernel!
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>f689e818391a0dd97e8971175e20bbed9e018947</sha1>
  </revision>
  <revision>
    <id>318</id>
    <parentid>317</parentid>
    <timestamp>2010-03-11T05:22:44Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6327" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.


The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==


From your kernel source directory do 
   
   make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

   make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

   make O=/tmp/kernel-build
   make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/bash
 
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
                   |-----handy-ruler------------------------------------------------------|
   kernel-jabberwok: kernel and modules 2.6.29.6-jabberwok
   kernel-jabberwok:
   kernel-jabberwok: Jabberwokky type kernel!
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   kernel-jabberwok:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>67729ffee3efbbd77939fff1251d545571d06634</sha1>
  </revision>
  <revision>
    <id>319</id>
    <parentid>318</parentid>
    <timestamp>2010-03-11T08:34:43Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6354" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.


The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==


From your kernel source directory do 
   
   make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

   make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

   make O=/tmp/kernel-build
   make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/bash
 
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>5e810eeaadac25e45280e860d309255a1c68d108</sha1>
  </revision>
  <revision>
    <id>320</id>
    <parentid>319</parentid>
    <timestamp>2010-03-11T08:42:07Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7536" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.


The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==


From your kernel source directory do 
   
   make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

   make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

   make O=/tmp/kernel-build
   make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/sh
   # Slackware build script for kernel and modules
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>5fd4b65193121cd53a190b8f17cd33a7ad444c38</sha1>
  </revision>
  <revision>
    <id>321</id>
    <parentid>320</parentid>
    <timestamp>2010-03-11T08:42:34Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7539" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does the same thing, although the output might not be exactly what you expect.


The first job is to create an output directory. I will be using '''/tmp/kernel-build''' for this so mkdir it now.

== Output Into a Build Directory ==


From your kernel source directory do 
   
   make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

   make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

   make O=/tmp/kernel-build
   make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/sh
   # Slackware build script for kernel and modules
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>ca2046dc840fdadfe369783b844d9e3a1bdd663f</sha1>
  </revision>
  <revision>
    <id>322</id>
    <parentid>321</parentid>
    <timestamp>2010-03-11T12:37:35Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Kernel Output Target Option */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7430" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect.

== Output Into a Build Directory ==


From your kernel source directory do 
   
   make O=/tmp/kernel-build menuconfig

(or whichever method you prefer.)

   make mrproper

This will delete your .config in the source tree so make sure you have a copy of it somewhere for safe keeping.

Next steps are the same as a normal make and modules_install, but again using the O= switch:

   make O=/tmp/kernel-build
   make O=/tmp/kernel-build modules_install

*Note: Do not use 'make install' as this *will* install it in /boot rather than our build directory.

At this point everything we need is in the build directory. However, taking a look inside it shows many more things have been placed there than we need. The kernel is in arch/x86/boot/ as usual and the modules are in various directories. Luckily for us there is a file, '''modules.order''', which lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/sh
   # Slackware build script for kernel and modules
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>6d453c899b7e398743f8df91cb2459ed7873220e</sha1>
  </revision>
  <revision>
    <id>323</id>
    <parentid>322</parentid>
    <timestamp>2010-03-11T12:41:43Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>/* Output Into a Build Directory */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6980" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect.

== Building ==


From your kernel source directory do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/sh
   # Slackware build script for kernel and modules
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   KOUTPUT=$OUTPUT/$PRGNAM-$LOCALNAME
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   set -e
 
   rm -rf $KOUTPUT
   rm -rf $PKG 
   mkdir -p $KOUTPUT
 
   cd $SOURCE
   make O=$KOUTPUT menuconfig
   make mrproper
   make O=$KOUTPUT 
   make O=$KOUTPUT modules_install
 
   cd $KOUTPUT
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>4fcd082baf2265f6b92e71f4d965b467c2de2ae7</sha1>
  </revision>
  <revision>
    <id>324</id>
    <parentid>323</parentid>
    <timestamp>2010-03-11T12:44:12Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6807" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect.

== Building ==


From your kernel source directory do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
 
   make menuconfig
   make
 
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>ebceb1fda724d506054dd9d1d5511edb16253590</sha1>
  </revision>
  <revision>
    <id>325</id>
    <parentid>324</parentid>
    <timestamp>2010-03-11T12:49:02Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Building */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6821" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
 
   make menuconfig
   make
 
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>99cea2ed4656ab7bc44169fd6ca4c0fcfea5f0a0</sha1>
  </revision>
  <revision>
    <id>327</id>
    <parentid>325</parentid>
    <timestamp>2010-03-11T13:35:27Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Kernel Output Target Option */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6899" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using:

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
 
   make menuconfig
   make
 
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>b52806a7571960c5750495a604fb3e91aa6cd025</sha1>
  </revision>
  <revision>
    <id>328</id>
    <parentid>327</parentid>
    <timestamp>2010-03-11T14:17:42Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6908" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install' as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
 
   make
 
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>4c37e7baef3d2f7a384dbf98a8615b5b34492321</sha1>
  </revision>
  <revision>
    <id>329</id>
    <parentid>328</parentid>
    <timestamp>2010-03-11T15:07:11Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Building */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6935" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   LOCALNAME=${LOCALNAME:-jabberwok}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
 
   make
 
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>3ab57804a8346c840615879a3abcac6d1940e4c3</sha1>
  </revision>
  <revision>
    <id>330</id>
    <parentid>329</parentid>
    <timestamp>2010-03-11T19:24:44Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6969" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install
   echo "/sbin/depmod -a" &gt; /tmp/kernel-package/install/doinst.sh

I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
 
   make
 
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>8dc44447266180feba42196a906c0edc85ba9504</sha1>
  </revision>
  <revision>
    <id>334</id>
    <parentid>330</parentid>
    <timestamp>2010-03-14T16:11:56Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Installing Modules and Kernel to our Package Directory */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7338" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   doinst.sh:
   
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
   ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
   ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
   ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
 
   make
 
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>84f4fd567497f1178b2818baa04b4de5c0a96c11</sha1>
  </revision>
  <revision>
    <id>335</id>
    <parentid>334</parentid>
    <timestamp>2010-03-14T16:13:25Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Installing Modules and Kernel to our Package Directory */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7331" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   doinst.sh:
   
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
 
   make
 
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
 
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
 
   mkdir $PKG/install
   echo "/sbin/depmod -a" &gt; $PKG/install/doinst.sh
 
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>dfac7312de4a12ee9383e4c539da2447187f560a</sha1>
  </revision>
  <revision>
    <id>336</id>
    <parentid>335</parentid>
    <timestamp>2010-03-14T16:15:43Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7648" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   doinst.sh:
   
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   # 
   # Notes:
   # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
   # have problems.
   # Do not omit setting localname in .config.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
   
   make
   
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
   
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
   
   mkdir $PKG/install
   
   cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
   
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>c15b6f9586de3c4ae2a98faa893736dd8d030a4b</sha1>
  </revision>
  <revision>
    <id>337</id>
    <parentid>336</parentid>
    <timestamp>2010-03-14T16:16:27Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Installing Modules and Kernel to our Package Directory */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7671" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir $PKG/install

   doinst.sh:
   
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   # 
   # Notes:
   # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
   # have problems.
   # Do not omit setting localname in .config.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
   
   make
   
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
   
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
   
   mkdir $PKG/install
   
   cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
   
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>1539a2f7afd2701bf7fc33da4f34054ddbc78723</sha1>
  </revision>
  <revision>
    <id>338</id>
    <parentid>337</parentid>
    <timestamp>2010-03-14T16:16:58Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Installing Modules and Kernel to our Package Directory */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7665" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir $PKG/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   # 
   # Notes:
   # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
   # have problems.
   # Do not omit setting localname in .config.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
   
   make
   
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
   
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
   
   mkdir $PKG/install
   
   cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
   
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>5294cb16d220615abe5723f278737f1d3c694ae8</sha1>
  </revision>
  <revision>
    <id>339</id>
    <parentid>338</parentid>
    <timestamp>2010-03-14T16:19:26Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Installing Modules and Kernel to our Package Directory */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7683" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir -p /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   # 
   # Notes:
   # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
   # have problems.
   # Do not omit setting localname in .config.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
   
   make
   
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
   
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
   
   mkdir $PKG/install
   
   cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
   
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>8f45ef7663b5e7b203b97065cab226ed00a2aeee</sha1>
  </revision>
  <revision>
    <id>340</id>
    <parentid>339</parentid>
    <timestamp>2010-03-14T16:19:48Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Installing Modules and Kernel to our Package Directory */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7680" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   # 
   # Notes:
   # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
   # have problems.
   # Do not omit setting localname in .config.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
   
   make
   
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
   
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
   
   mkdir $PKG/install
   
   cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
   
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>a7181a95ac6056d757fe6739ecfa70ccea41e9c3</sha1>
  </revision>
  <revision>
    <id>341</id>
    <parentid>340</parentid>
    <timestamp>2010-03-14T16:21:47Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7992" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   # 
   # Notes:
   # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
   # have problems.
   # Do not omit setting localname in .config.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
   
   make
   
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
   
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
   
   mkdir $PKG/install
   
   cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
    
   ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
   ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
   ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
   ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
   EOF
   
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details. Note that this does not include the firmware so you should keep the relevant kernel-firmware package installed.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>478fbb66be039b6e94e4ae69e78845442d2c1014</sha1>
  </revision>
  <revision>
    <id>342</id>
    <parentid>341</parentid>
    <timestamp>2010-03-14T16:22:55Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Conclusion */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7880" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6_tag-i686-1.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   # 
   # Notes:
   # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
   # have problems.
   # Do not omit setting localname in .config.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
   
   make
   
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
   
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
   
   mkdir $PKG/install
   
   cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
    
   ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
   ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
   ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
   ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
   EOF
   
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>714d2be704fbfa7f16256a73b06c7bacb4085593</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Talk:Kernel-packaging</title>
  <ns>1</ns>
  <id>214</id>
  <revision>
    <id>326</id>
    <timestamp>2010-03-11T12:52:41Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>Created page with 'Originally I used the O= switch to build in a separate build directory. This isn't really necesary, but if you prefer to do this have a look at the README file in top directory a…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="197" xml:space="preserve">Originally I used the O= switch to build in a separate build directory. This isn't really necesary, but if you prefer to do this have a look at the README file in top directory about the O= switch.</text>
    <sha1>4619bc1fd69f06de005618d952320049c5f7487c</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Packages</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>331</id>
    <parentid>25</parentid>
    <timestamp>2010-03-13T13:49:07Z</timestamp>
    <contributor>
      <username>Grissiom</username>
      <id>11</id>
    </contributor>
    <comment>update pkg formats</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1958" xml:space="preserve">Slackware's package management system utilizes .tgz/.txz tarballs as its standard package format. These tarballs are  tar.gz/tar.xz archives which contain Slackware built binaries, support files, a description file and installation script. Although they can be unzipped and untarred like a normal archive, they are (usually) binary-only packages intended to be installed through Slackware's provided package management tools.

Information about a package is stored in two ways, in the filename of the package and a description file inside that package.

==Package Tools==
See the respective manual pages for more information on each of the following commands.

&lt;code&gt;pkgtool&lt;/code&gt;

&lt;code&gt;installpkg&lt;/code&gt;

&lt;code&gt;removepkg&lt;/code&gt;

&lt;code&gt;explodepkg&lt;/code&gt;

&lt;code&gt;makepkg&lt;/code&gt;

&lt;code&gt;upgradepkg&lt;/code&gt;

==Slackware Package Layout==
A typical Slackware package is laid out as such:
 ./
 ./install/doinst.sh
 ./install/slack-desc
 [./usr/bin]
 [./usr/lib]
 [...]

The install directory as well as the files within it will be deleted after the installation of the package to the root install directory (usually '/'). The install directory is not necessarily required for the most basic packages but allows additional functionality: [[slack-desc]] contains the package description, and [[doinst.sh]] contains post-installation instructions such as creating symbolic links.

Every other file within the package is simply untarred (extracted) to the root directory. Most of these files are in standard locations. 

There are other special files within packages: 

'''usr/doc/&lt;appname&gt;&lt;version&gt;'''
All documentation included with the package (such as README, INSTALL, ChangeLog, docs/, etcetera) should be placed in this directory. Some of the files in this directory should be manually copied from the source archive, since Makefiles usually don't copy these documentation files to the package build tree.

==Making Slackware Packages==
See [[Building A Package]]</text>
    <sha1>fe0de126b2c1721187c5b06087f5631486e6a545</sha1>
  </revision>
  <revision>
    <id>333</id>
    <parentid>331</parentid>
    <timestamp>2010-03-13T15:36:21Z</timestamp>
    <contributor>
      <username>Grissiom</username>
      <id>11</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1985" xml:space="preserve">Slackware's package management system utilizes .tgz/.txz tarballs as its standard package format. These tarballs are  tar.gz/tar.xz archives which contain Slackware built binaries, support files, a description file and installation script. Although they can be unzipped and untarred like a normal archive, they are (usually) binary-only packages intended to be installed through Slackware's provided package management tools.

Information about a package is stored in two ways, in the filename of the package and a description file inside that package.

==Package Tools==
See the respective manual pages for more information on each of the following commands.

&lt;code&gt;pkgtool&lt;/code&gt;

&lt;code&gt;installpkg&lt;/code&gt;

&lt;code&gt;removepkg&lt;/code&gt;

&lt;code&gt;explodepkg&lt;/code&gt;

&lt;code&gt;makepkg&lt;/code&gt;

&lt;code&gt;upgradepkg&lt;/code&gt;

==Slackware Package Layout==
A typical Slackware package is laid out as such:
 ./
 ./install/doinst.sh
 ./install/slack-desc
 [./usr/bin]
 [./usr/lib]
 [...]

The install directory as well as the files within it will be deleted after the installation of the package to the root install directory (usually '/'). The install directory is not necessarily required for the most basic packages but allows additional functionality: [[slack-desc]] contains the package description, and [[doinst.sh]] contains post-installation instructions such as creating symbolic links.

Every other file within the package is simply untarred (extracted) to the root directory. Most of these files are in standard locations. 

There are other special files within packages: 

'''usr/doc/&lt;appname&gt;&lt;version&gt;'''
All documentation included with the package (such as README, INSTALL, ChangeLog, docs/, etcetera) should be placed in this directory. Some of the files in this directory should be manually copied from the source archive, since Makefiles usually don't copy these documentation files to the package build tree.

==Making Slackware Packages==
See [[Building A Package]]

[[Category: Information]]</text>
    <sha1>29ecbc47c3624fd37e27efb0674fab3ddecae81e</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Life of a Software Package</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>332</id>
    <parentid>127</parentid>
    <timestamp>2010-03-13T15:32:58Z</timestamp>
    <contributor>
      <username>Grissiom</username>
      <id>11</id>
    </contributor>
    <comment>/* Slackware specifics */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17274" xml:space="preserve">From the programmer's keyboard to your (Slackware) Linux system.

= Introduction =

This article explains how a program someone writes in one side of the world ends up being managed in your system. It's meant to be easy to understand for a novice user coming from Windows, and only requires some basic knowledge of Unix systems. Specifically, the reader should know:

* How basic Unix permissions work.
* How to interpret the basic output of the ''ls'' command.
* How a command line interface works.

It only contains general ideas that could help a novice user understand the existing differences when installing software under Windows and under Unix, but no specific information about how to do it. The distribution manual will give you the specific details you need, and may be a good read after you have read this article.

= From source code to machine language =

'''Note''': You do not need to run any of the commands in this section. It's enough to understand the text and part of the output.

When a programmer creates a program, it's very common to write the program in a so-called high level language. In other words, he doesn't create the program executable directly specifying the intructions for the computer to run. He writes the program in a language that allows him to represent the program structure and logic, and then that logic is translated to a language the bare machine can understand. Let's suppose someone wants to write a ''Hello, World'' program in the C programming language. This is a program that prints a message to the screen and finishes, in order to check your system can translate the language you have used to machine language and to test the basic stuff works, as well as to give the novice programmer an idea on how the high level language works. This would be a very simple ''Hello, World'' program written in C:

 #include &lt;stdio.h&gt;
 
 int main()
 {
 	printf("Hello, World!\n");
 	return 0;
 }

You do not need to understand that program. The above text is what is commonly known as the '''source code''' of the program. The source code of a program in C is usually spread over one or more source files, so this program could very well be stored in a plain text file called ''hello.c''. You could view this file using a plain text editor like the Windows notepad.

This file cannot be executed directly because it's not a real program. First off, it doesn't have execution permissions, and if we tried to give it execution permissions and run it, we would get an error message:

 $ ls -l hello.c
 -rw------- 1 rg3 users 74 2007-10-15 19:27 hello.c
 $ chmod +x hello.c
 $ ./hello.c
 ./hello.c: line 3: syntax error near unexpected token `('
 ./hello.c: line 3: `int main()'

We need to use a program called ''compiler'' to get a binary and executable file. A file in a specific format that the operating system (Linux in our case) can understand. When you run it, the operating system reads the file, copies the different program components to the computer's memory and starts the program execution. If our machine has everything ready to compile C programs and we want to use the GNU C Compiler (''gcc''), we could do something as simple as:

 $ gcc -o hello hello.c

And we would get a file named ''hello'' which is our program ready to be run. As you see, our program is simply called ''hello'' and not ''hello.exe'', which would be a common name if we were working under Windows. In Unix systems, the convention is that programs do not have any file extension in their name (like EXE). We could then run the program and see that it does what we wanted.

 $ ./hello
 Hello, World!
 $

= Complex programs use libraries =

Most programs do a more sophisticated task than printing a message on the screen and finishing. The source code of the program above has 7 lines. It is not uncommon for a simple program to have thousands of lines, and there are a good amount of complex programs out there that have millions of lines of source code. It is also a very common practice to use items called '''libraries''' (usually '''shared''' libraries) to build your program. Libraries are files that contain the machine code to perform several different tasks. For example, let's suppose you were going to create a program that needs to download some data from the Internet, via HTTP (the web) or via FTP or another network service. And also let's suppose you don't have much knowledge on how to create a program that talks to others using the network, or that the focus of your program is on solving some other problem and you don't want to lose time or create a lot of code just because you want it to be able to download a file. Fortunately for you, there is a library called ''libcurl'' that makes retrieving files over the network very easy. The library contains all the code you need, so the source code you are going to create will not contain anything specific to be able to use the network. You simply indicate that you want to use ''libcurl'' and call the library functions everytime you want to download a file. Do you need to learn to sail or fly a plane or a different language if you want to send a letter to a friend in a different continent? No, you put the letter in the mailbox and the postal service does it for you. Libraries work like this.

In the moment you decide to do this, your program starts '''depending''' on ''libcurl''. Some pieces of the library need to be present in your system if you want to compile that program to create an executable, and some other pieces need to be present in the moment you want to ''run'' the program. Else, the program will not compile or will not be able to run. Libraries are convenient because, if managed well, you can install them in your system once and they will be used by every program that needs them. This is why libraries are regarded as a ''good thing'' or a ''good idea'' in the programming world, in most cases.

In Windows, shared libraries are called DLLs, as the library files usually have the DLL extension. In Unix, it's common for them to have the ''.so'' suffix, or some other containing it. For example, I have ''libcurl'' in my system, and the shared library is located in the file ''/usr/lib/libcurl.so.4.0.0''.

= Libraries and programs all over the place need a package manager =

So your system is going to be populated by a lot of programs, many of them using many different libraries for different tasks, some of them having some libraries in common, others having nothing in common. As you can guess, this situation can evolve into a pretty chaotic system. Let's describe how Windows did this in the past, and how Unix systems have been trying to handle the situation for a good amount of years now.

In Windows, most people distribute programs already compiled. You get a group of files or a single file that holds your program already prepared to be run. You extract those contents and place them somewhere in your hard drive, usually all of them under a specific directory (folder). You could then create some shortcuts in the ''start'' menu and the program is ready to be run. A installer program usually does all of this for you, asking some questions. What happens when the program uses a library? If the library is not very common and cannot be assumed to exist in a standard Windows installation, the common practice is to include a copy of the library with the program. If it's a relatively uncommon library, the installer usually puts it in the same place as the program, and when it is run and requests the library, the system first looks in the folder holding the program and finds the library there, and starts to use it. If it's not an uncommon library but you need a specific version of it, the installer may try to install it in a common place so all the programs can use it. It was very typical, when you had a system in which you had installed a lot of software as time passed, that the installer would ask you "I am trying to install the following library, but it appears to be present in your system in a newer version. Do you want me to replace the copy of it with my copy or do I leave it as it is?". And, in the same line, when you removed the program it would say "I was going to remove this library from the common place, but other programs may want to use it. Can I remove it or should I keep it there?". This chaos was called "DLL Hell".

Unix tries to avoid this problem in several ways, and its solutions bring the need of a package manager as we will explain. First off, in Unix the files on your hard drive are not grouped by program, but by their function. All binaries are stored in two or three folders, and the same for libraries or help documents. If all the documentation and help for the different programs is installed in a common location, it's easier to create a help system from which you can browse the documentation of every program installed on the computer, for example. This is generally considered a good idea and it's the tradition, but of course the idea has its detractors. Anyway, a second difference is that in Unix programs are distributed alone. If a program needs a library to be run, it needs to specify that somewhere, but only under special circumstances it's recommended to include the library as part of the program. In most cases, the library is distributed apart. Those two differences avoid the DLL hell. By installing libraries, programs, documentation and other data to common system locations, you avoid duplicating data. If there's a security problem using a library and every program using it could become compromised and make the system vulnerable, you update the library once and all the programs that use it are automatically protected, as each program doesn't include its own copy in its directory. By separating the programs from the libraries they use and distributing them apart, you make sure programs do not overwrite the libraries used by others or remove common libraries when they are removed.

However, the solution itself brings some new problems. For example, if a program installs files all over common system directories and I later want to remove it, how do I know which files need to be removed? And if a program requires a library to run, can I or should I specify that fact somewhere? Package managers are the answer. Under Unix, software is many times distributed as '''packages'''. Packages are groups of files that contain programs, libraries, documentation or simply data. Under Windows, to install a program many times you download an installer file, run it and the program is installed. This installer file that holds inside all the files the program needs and extracts them to the proper location could be considered a form of package, so you get an idea. Packages in Unix are usually managed by a package manager. A package manager is a program that allows you to install packages, check the list of installed packages, remove packages and many more complex tasks depending on how powerful and featureful the package manager itself is.

When you install a program using a package, the package holds the program binary, the program data and the program documentation, typically, along with information on where those files should be installed in the system, all over the place. Fortunately, prior, during or after the installation, after copying the files to your system, the package manager records somewhere the name and version of the package and the files it installed. This is the trick that allows you to later remove the package using the package manager without having to remember which files had been installed where. In addition, the package may hold information about other packages it needs installed for it to run, and this information may be used by the package manager to automatically download and install them too. Hopefully, you now start to understand the practical vision behind packages and package managers.

= Too many package managers =

The problem with package managers is that many Unix systems and even many different Linux distributions use many different package managers. Each one uses different package formats that cannot understand each other. Slackware uses ''pkgtools'', Debian and Ubuntu use ''apt-get'', Red Hat uses ''yum'', Mandriva uses ''urpmi'', Arch uses ''pacman'', etc.

You are a programmer and created the ''Hello, World'' program we saw at the beginning. How do you distribute your program? You have several solutions. If you don't want people to get the source code of your program, you need to distribute the program already compiled and probably packaged. To do that, you could provide your own program to install and uninstall the package cleanly from any system, and distribute it somehow and break some rules to achieve maximum compatibility, so the program will run on many different systems and distributions. Many commercial games are shipped this way. Unreal Tournament 2004 for Linux is distributed this way, for example. You could also provide it as a package for each of a subset of supported systems. Many companies do this. They give you Debian, Red Hat, Suse and Mandriva packages for you to choose, for example, each in the proper format to be used with the package manager from that distribution. If you want to use the software under other system you are out of luck. You can try some tricks but it's not guaranteed to work.

If, on the other hand, your program is open source and you don't mind people reading the source code of your program, the common case is to avoid creating a package for anything. You simply distribute a tarball (similar to a ZIP or RAR file) containing the source code and instructions to compile it. If someone wants a Debian package to install it, someone will have to compile your program under Debian, and make a package with the result. This is a very very very common case. In fact, distributions like Ubuntu or Debian heavily rely on '''package repositories''', network locations from where you can download thousands of packages for your system, created by a myriad of official and unofficial packagers (people that create packages for the system). For example, if you want to install a program under Ubuntu, it's very infrequent for the program not to exist already packaged in a repository, and you can download and install it, together with its dependencies, in a couple of mouse clicks.

= Summing up =

* Many times the programmer creates programs using source code that must be compiled.
* They use libraries to make writing programs easy.
* Distributing the resulting program is easier using a package manager.
* Many programmers only give you the source code due to the diversity of package managers and systems.
* Someone else is responsible for creating a package for a specific system.

= Slackware specifics =

Slackware is, as you may know, a very simple system. Being simple doesn't mean it's simple to use. On the contrary, a system with a simple design and simple tools usually requires the user to do more things to achieve a goal. The advantage of a simple design is that it's easier to understand if you want to know how your system works, and sometimes it's also more stable and has less bugs. As part of its simple design, the package manager in Slackware is also very simple, and its packages are also very simple. Slackware packages are tarballs (again, something like ZIP files) that, if extracted in the right place, will populate the system with the package files, and it also holds some special files with information about the package itself. As they are simple tarballs, Slackware doesn't try to hide this fact, and Slackware packages have the ''tgz/txz'' extension (short for ''tar.gz/tar.xz''), contrary to other systems in which packages have a special extension to make it clear that they are packages, like ''rpm'' or ''deb''.

This is not a problem, but sometimes this confuses novice users. They go to the program webpage and download the program source code in a tarball (usually a file with ''tar.gz'' extension) and think "Hey, if Slackware packages are tarballs and this is a tarball, I'm going to install this file with the package manager". Wrong! Even when the package manager complains that the package name does not end in ''tgz'' but on ''tar.gz'', they many times rename the file and try again. Those are two mistakes in a row. The package manager will try to extact the tarball contents to that special location we mentioned earlier and nothing will happen, as the files inside the tarball are not structured as they need to be, but this is the small problem. The big one is that what you are trying to install is the source code of the program, and not the program itself! Remember, you need to compile it first in the majority of cases.

Under Slackware, you should first check if there is an official package for the program. If there is not, you could try to to download a ready to use package from a place or someone you trust. Else, you could compile the program yourself and create a package for it, and then install the package. The compilation and package creation can be automated sometimes for ease of use, for example using [[SlackBuild Scripts|SlackBuild scripts]].

[[Category:Information]]</text>
    <sha1>712647b02c547102f2dcd6c07bd337eb916207ca</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>SlackRoll Tutorial</title>
  <ns>0</ns>
  <id>157</id>
  <revision>
    <id>344</id>
    <parentid>185</parentid>
    <timestamp>2010-03-23T03:22:16Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>official webpage updated</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16954" xml:space="preserve">&lt;strong&gt;SlackRoll&lt;/strong&gt; is a package or update manager for Slackware Linux. Part of this tutorial has been taken from its [http://rg3.github.com/slackroll/ official webpage] and FAQ. SlackRoll's defining points:

* Its internal mechanism based on package states.
* Like &lt;em&gt;slackpkg&lt;/em&gt;, SlackRoll only works with official mirrors, meaning that to keep third party packages up to date you need to perform the task by hand (recommended practice, using SlackBuild scripts) or use a second different tool.
* It does not try to compare package version numbers to decide if a package should be upgraded or not.
* Partly as a consequence of the previous point, it has no known flaws detecting package updates (including reverts), new packages, removed packages, third party packages getting an official version and blacklisted packages (&lt;em&gt;frozen&lt;/em&gt; in its terminology) being removed.
* It has a broad range of operations and features.
* It attempts to be fast. Most internal operations like listing available upgrades usually take less than one second on a modern computer.


= Installation =

== Requirements ==

* Python 2.4 or later (provided by package &lt;em&gt;python&lt;/em&gt; starting with Slackware 10.1).
* GnuPG (provided by package &lt;em&gt;gnupg&lt;/em&gt; or &lt;em&gt;gnupg2&lt;/em&gt;).
* Vim (provided by package &lt;em&gt;vim&lt;/em&gt;).
* A pager which is &lt;em&gt;less&lt;/em&gt; by default (provided by package &lt;em&gt;less&lt;/em&gt;).

== Procedure ==

Download the SlackRoll package from the [http://github.com/rg3/slackroll/downloads project download page] and install it in your system using &lt;tt&gt;installpkg&lt;/tt&gt;.

= Background Information =

The majority of SlackRoll commands that receive a list of packages expect only the package names (&lt;em&gt;foo&lt;/em&gt; as opposed to &lt;em&gt;foo-1.1-i486-3.tgz&lt;/em&gt;). Some of them also allow using a specific version, but they are the exception.

SlackRoll creates a persistent database of packages in your hard drive. Each package is in one of several possible states. Part of the initial configuration consists in deciding which states some of your packages will have. There are two types of states: states to avoid (temporary states) and normal states. When the remote Slackware official tree is updated, SlackRoll may put some packages in temporary states. By upgrading, installing, removing and marking packages your objective is to correct those packages and put them in a normal state.

== States to Avoid ==

=== New ===

New packages are packages present in the remote tree that weren't present before. You should decide if you want to install them or mark them as not installed.

=== Outdated ===

Outdated packages are present in your system, but the version you have does not match any relevant one in the remote tree. You should upgrade these packages.

=== Unavailable ===

Unavailable packages are packages present in your system. Previously, they probably existed in the remote tree, but now they do not seem to be available for downloading and installing. You should decide if you want to remove them or mark them as foreign.

== Normal States ==

=== Installed ===

Installed packages are very common. They are present in your system and in the remote tree, and both versions match.

=== Not Installed ===

Not installed packages are also very common. They are present in the remote tree but not in your system. They can be downloaded and installed if you want.

=== Foreign ===

Foreign packages are packages present in your system but not in the remote tree. However, unlike unavailable packages, they are supposed to be present in your system. No package will enter this state automatically. Only the ones you mark. It's usually reserved for third party packages and packages you build yourself. It's worth noting that if a foreign package ever appears in the remote official tree, it will be marked as installed or, probably, outdated. Thus, SlackRoll will give priority to the new official package over yours. If you still want to use your own build, mark it as frozen.

=== Frozen ===

Frozen packages are present in your system and in the remote tree. Your version may or may not match the ones from the remote tree, but SlackRoll will not tell you they need to be upgraded. No package will enter this state automatically. It's usually reserved for packages that shouldn't be upgraded automatically or ever (&lt;em&gt;aaa_elflibs&lt;/em&gt;, kernels, etc) and sometimes for customized versions of official packages. It's also worth mentioning that a frozen package will be moved to unavailable if it disappears from the remote tree. It that happens and you want to continue using it, you'll need to mark it as foreign.

= Initial Configuration =

Word of warning: it's highly recommended to do the initial configuration from an up-to-date and controlled system. This will avoid confusion and helps preventing mistakes setting the initial package states.

== Preparing Your System ==

Choose a Slackware mirror for your Slackware version. Use the &lt;em&gt;set-mirror&lt;/em&gt; operation to select one mirror. SlackRoll can work with stable trees as well as the &lt;em&gt;current&lt;/em&gt; tree. Example:

  # slackroll set-mirror 'http://slackware.example.org/slackware-current/'

Do not forget to include the trailing slash in the mirror URL. Import, to your keyring, the GnuPG key used to sign the official Slackware packages. This key can be found in Slackware CDs and DVDs as the file GPG-KEY, and you can import the key to your keyring using the command &lt;em&gt;gpg --import&lt;/em&gt;, but SlackRoll is able to download the key from the mirror and importing it automatically, if you trust the mirror.

  # slackroll import-key

Finally, retrieve the mirror information for the first time. This will download a few metadata files, and this is what you need to do when you're going to handle a new round of updates.

  # slackroll update

== Going Over Package States for The First Time ==

When you run SlackRoll for the first times, it will put every remote package not present in your system in the state New. When your system is up to date and under control, you can blindly mark every new package as not installed with the following command:

  # slackroll new-not-installed

Any third party package present in your system will be put in the state Unavailable. When your system is up to date and under control you can blindly mark all unavailable packages as foreign. &lt;em&gt;However&lt;/em&gt;, the number of foreign packages is usually not very high and forgetting to remove from your system a package that was removed from the remote tree is a common mistake. The Book of Best Practices would suggest that you review the list of unavailable packages once and carefully in order to detect packages that should not be present in your system. To print the list run:

  # slackroll list-unavailable

If you locate any package that needs to be removed, you can remove them using &lt;em&gt;removepkg&lt;/em&gt; or the &lt;em&gt;remove&lt;/em&gt; operation. The later has additional functionality so it's recommended:

  # slackroll remove foo bar

Now you can mark the rest as foreign packages.

  # slackroll unavailable-foreign

Finally, you probably want to mark some packages as frozen. It's usually a good idea to do this with &lt;em&gt;aaa_elflibs&lt;/em&gt;, kernel packages and others.

  # slackroll frozen aaa_elflibs foo bar

= Day to Day Usage =

Apart from the operations listed here, you can run the &lt;em&gt;help&lt;/em&gt; operation to get the full list of supported operations, along with a brief description of each one. A more detailed description can be found in the [http://wiki.github.com/rg3/slackroll/operations-guide operations guide].

== New Round of Updates ==

What to do when there is a new round of updates? The Book of Best Practices suggests taking care of different events in a specific order:

* Updates to glibc-solibs, sed and pkgtools need to be handled first, in that order.
* If there are new packages, handle them second.
* Then, it's time to upgrade outdated packages.
* If packages have been deleted from the remote tree, handle them last.

This is the correct order in 99% of the cases. SlackRoll will attempt to warn you and ask for confirmation if it detects you may be breaking this order. However, &lt;strong&gt;you&lt;/strong&gt; have the last word on what to do, so proceed with caution and don't break your system.

First, update the remote mirror information with the &lt;em&gt;update&lt;/em&gt; operation we mentioned before. New changelog entries will be saved to your hard drive. It's recommended that you take a look at the changelog at this point, using the &lt;em&gt;changelog&lt;/em&gt; operation. Then, get an overview of the events using the &lt;em&gt;list-transient&lt;/em&gt; operation, which will list the new, outdated and unavailable packages along with a big fat warning message if activity in key system packages is detected.

The best way to deal with glibc-solibs, sed and pkgtool updates is to use the &lt;em&gt;upgrade-key-packages&lt;/em&gt; operation.

  # slackroll upgrade-key-packages

You could also use the &lt;em&gt;install&lt;/em&gt; operation. Despite its name, it can be used to both install and upgrade individual packages. Let's suppose packages &lt;em&gt;glibc-solibs&lt;/em&gt; and &lt;em&gt;sed&lt;/em&gt; where updated:

  # slackroll install glibc-solibs sed

The &lt;em&gt;install&lt;/em&gt; operation is one of the few operations allowing you to pass specific package versions. It will proceed in the order you indicate, so remember to give the packages in the correct order if you use this method.

Second, you should handle new packages. You can clearly get a list of new packages with the &lt;em&gt;list-new&lt;/em&gt; operation. New packages can be installed with the &lt;em&gt;install&lt;/em&gt; operation as we just showed. When installing a remote package, SlackRoll will give you the opportunity of selecting the version to install if there are several available in the remote tree. Or, if you are not interested in installing a new package, mark it as not installed:

  # slackroll not-installed foo bar

If the package names are not enough for you to decide if you want to install it or not, you can always use the &lt;em&gt;info&lt;/em&gt; operation and SlackRoll will download and display the package info file (small &lt;em&gt;txt&lt;/em&gt; files in the remote tree). And, of course, be carefull with new libraries as they may have been included to extend the functionality of an existing package you may have installed.

The third step is taking care of outdated packages. For that, a few operations are available. &lt;em&gt;list-upgrades&lt;/em&gt; lets you see a summary of the available upgrades. You can download and install them with &lt;em&gt;upgrade&lt;/em&gt; or download them with &lt;em&gt;download-upgrades&lt;/em&gt; or even print their URLs with &lt;em&gt;urls-upgrades&lt;/em&gt;.

And, finally, review the list of unavailable packages. Be careful with unavailable packages. Sometimes you install a foreign package but forget to mark it as such in SlackRoll. To avoid that problem, it's better to install them with the &lt;em&gt;install-foreign&lt;/em&gt; operation. Individual unavailable packages can be removed with the &lt;em&gt;remove&lt;/em&gt; operation as we showed before, and also all of them at the same time with the &lt;em&gt;remove-unavailable&lt;/em&gt; operation.

== Installing and Removing Individual Packages ==

There are a few operations related to installing and getting some information about individual packages. The most common ones are &lt;em&gt;install&lt;/em&gt; to upgrade or install packages, &lt;em&gt;info&lt;/em&gt; to maybe download and display package info files, &lt;em&gt;urls&lt;/em&gt; to get a list of URLs and &lt;em&gt;remove&lt;/em&gt; to remove individual packages.

Operations that install packages let you manage &lt;em&gt;.new&lt;/em&gt; files after the installation is completed, in a similar way to &lt;em&gt;slackpkg&lt;/em&gt;. You can view the differences between the &lt;em&gt;.new&lt;/em&gt; file and its counterparts with &lt;em&gt;vimdiff&lt;/em&gt; (which provides a nice and colorized way of spotting the differences and maybe porting the old configuration to the new file), you can overwrite the old file with the &lt;em&gt;.new&lt;/em&gt; file, delete the &lt;em&gt;.new&lt;/em&gt; file directly, etc.

Additionally, removal operations also track pairs of &lt;em&gt;.new&lt;/em&gt; files and give you the opportunity of deleting configuration files that have been left behind. You are not forced to remove the files left behind, of course.

Upgrade operations will perform both tasks. First, they will let you review the &lt;em&gt;.new&lt;/em&gt; files and then they will give you the opportunity of deleting obsolete configuration files left behind.

While using &lt;em&gt;vimdiff&lt;/em&gt;, turning off syntax highlighting is recommended. &lt;em&gt;Vim&lt;/em&gt; uses colors to highlight file differences and those can interfere with syntax highlighting colors, making text invisible or hard to read. Syntax highlighting can be turned off temporarily by using "&lt;tt&gt;:syntax off&lt;/tt&gt;" in command mode, or you can disable it permanently putting "&lt;tt&gt;syntax off&lt;/tt&gt;" in your &lt;tt&gt;~/.vimrc&lt;/tt&gt; file (noting that usually you run SlackRoll as the superuser).

== Managing Customized Versions of Official Packages ==

There are at least three ways of dealing with customized versions of official packages. These are custom versions or compilations of packages present in the remote official tree. They are normally used to add or remove features, or activate or apply patches that are disabled by default. For example, if you want to activate the &lt;em&gt;freetype&lt;/em&gt; bytecode interpreter, you need to rebuild that package.

The simplest way of dealing with these packages is to give them the same name and version as the official packages. When they are upgraded in the remote tree, however, SlackRoll will want to upgrade them. You can mark them as frozen before upgrading and only unfreeze them after you have rebuilt the new version, if you want to avoid SlackRoll replacing them with the new official version.

Second, you can give them the same name and version as the official package, &lt;strong&gt;but&lt;/strong&gt; keep them frozen all the time. How would you know then if they need to be rebuilt? With the &lt;em&gt;list-outdated-frozen&lt;/em&gt; operation. Take into account the information given by &lt;em&gt;list-outdated-frozen&lt;/em&gt; is not reflected by any other command. Specifically, it's not reflected as part of &lt;em&gt;list-transient&lt;/em&gt; and friends.

Third, you can give them a name or version different to the official package. Typically this means adding a custom build suffix and marking the package as frozen. How would you know if you need to rebuild it? Paying attention to the changelog specifically searching for upgrades in those packages and also using the &lt;em&gt;list-versions&lt;/em&gt; operation, that lets you view the different known versions of a package, including local and remote ones.

== Maintenance ==

SlackRoll barely requires maintenance. It keeps all downloaded packages in its package cache, located in the &lt;em&gt;/var/slackroll/packages&lt;/em&gt; directory. When downloading files, it keeps them in a temporary directory until they're fully downloaded. If you want to remove every downloaded package, you can simply perform &lt;code&gt;slackroll erase-cache&lt;/code&gt;. There is, however, a &lt;em&gt;clean-cache&lt;/em&gt; operation which does &lt;strong&gt;not&lt;/strong&gt; remove every downloaded package, but only those that are no longer present in the remote tree. Running that operation from time to time keeps your package cache sane and controlled. It may also be a good idea to delete the temporary directory contents from time to time, with &lt;code&gt;slackroll erase-tmp&lt;/code&gt;, but it should be empty unless you interrupt SlackRoll while downloading stuff and never attempt to complete the download.

== Other Operations ==

If you run the &lt;em&gt;help&lt;/em&gt; operation you will see SlackRoll has many other operations, including operations to list packages by state, list local packages, list remote packages and list all known packages. It has operations to put packages in specific states and checking the state of packages. You can also download, install, display info or remove new or unavailable packages or packages with a matching path (like &lt;em&gt;/slackware/kde/&lt;/em&gt;). Finally, there are search operations, to search for packages by name or path, search for files in your local system (like running &lt;em&gt;grep&lt;/em&gt; on the contents of &lt;em&gt;/var/log/packages&lt;/em&gt;), query the Slackware Package Browser, and finally a few very slow but sometimes useful operations to search for broken symlinks under a specific hierarchy and the same for orphan files (files not belonging to any package), as well as searching for missing files.

As a general rule, every operation either does not accept arguments or allows a list of them. Operations accepting packages as arguments expect the package name only unless the help text mentions that they also accept specific package versions. Some operations need regular expressions. For the most part they have the same syntax as they have in &lt;em&gt;grep&lt;/em&gt; or &lt;em&gt;Perl&lt;/em&gt;, but you can read the [http://docs.python.org/lib/re-syntax.html Python regular expressions syntax reference] if you want to perform an unusually complex search.

[[Category:Tutorials]]</text>
    <sha1>bb5d923e18915f5fde77baf9bd05011095b6308d</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>User:Ariarat</title>
  <ns>2</ns>
  <id>216</id>
  <revision>
    <id>346</id>
    <timestamp>2010-04-16T11:16:50Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <comment>Created page with 'http://www.slack-world.com             "Iranian Slackers World" http://www.slack-world.com/forum       "Iranian Slackers World Forums"'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">http://www.slack-world.com             "Iranian Slackers World"
http://www.slack-world.com/forum       "Iranian Slackers World Forums"</text>
    <sha1>395d1c69f27b4eaccf840427b70b5e442f0782cb</sha1>
  </revision>
  <revision>
    <id>347</id>
    <parentid>346</parentid>
    <timestamp>2010-04-16T11:17:31Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="173" xml:space="preserve">http://www.slack-world.com             "Iranian Slackers World"                                       
http://www.slack-world.com/forum       "Iranian Slackers World Forums"</text>
    <sha1>15a25d288ccc959811cac58e8d5f4333e3a84dc1</sha1>
  </revision>
  <revision>
    <id>348</id>
    <parentid>347</parentid>
    <timestamp>2010-04-16T11:19:33Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="168" xml:space="preserve">http://www.slack-world.com             Iranian Slackers World                                      
http://www.slack-world.com/forum       Iranian Slackers World Forums</text>
    <sha1>9bf327ae94323f9ea693fc8c79b8f49bfe0da786</sha1>
  </revision>
  <revision>
    <id>349</id>
    <parentid>348</parentid>
    <timestamp>2010-04-16T11:19:55Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="103" xml:space="preserve">http://www.slack-world.com                                            
http://www.slack-world.com/forum</text>
    <sha1>dd8b238c59b3a664f0bcf8b2d7eddf7069224bff</sha1>
  </revision>
  <revision>
    <id>350</id>
    <parentid>349</parentid>
    <timestamp>2010-04-16T11:20:22Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="109" xml:space="preserve">http://www.slack-world.com  &lt;br /&gt;                                          
http://www.slack-world.com/forum</text>
    <sha1>036011173fc1cc2cbcf92a2288d640d7ccf44885</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Building A Package</title>
  <ns>0</ns>
  <id>23</id>
  <revision>
    <id>358</id>
    <parentid>31</parentid>
    <timestamp>2010-05-18T19:38:37Z</timestamp>
    <contributor>
      <username>Sombriks</username>
      <id>109</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2926" xml:space="preserve">[[Category:Tutorials]]

= Intro =

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

== The good and decent way ==

Configure and compile the source as you usually do:
 ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
 make

Make a temporary destination directory available:
 mkdir /tmp/build

Install into the temporary directory:
 make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
 strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in &lt;tt&gt;/usr/man&lt;/tt&gt; is gzipped before you make the package:
 gzip -9 /tmp/build/usr/man/man?/*.?

Create the &lt;tt&gt;install&lt;/tt&gt; directory, this is where the description and install script will be stored:
 cd /tmp/build
 mkdir install
 cd install

Using a text editor, create a file called &lt;tt&gt;slack-desc&lt;/tt&gt; and fill it with the following contents:

    |-----handy-ruler------------------------------------------------------|
 app: Application Name (Short/Brief description)
 app:
 app: Enter a description of the package you are building.
 app: All 11 "app:" lines must be present
 app: "app" needs to be your application name.
 app: The handy-ruler is there to help you, these lines should not exceed
 app: 79 characters.
 app:
 app:
 app:
 app:

Create the actual package:
 cd /tmp/build
 makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc.  Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say &lt;tt&gt;yes&lt;/tt&gt;&lt;br&gt;
When prompted to reset permissions, say &lt;tt&gt;no&lt;/tt&gt;

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
 cd ..
 installpkg app-version-arch-tag.tgz


== The "i don't have time" way ==

Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this: 
 ./configure --prefix=/usr
 make install DESTDIR=$(pwd)/PACKAGE
 cd $(pwd)/PACKAGE
 makepkg -l y -c n ../app-version-arch-tag.tgz
 installpkg ../app-version-arch-tag.tgz

Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.

----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----</text>
    <sha1>bd4f3c86dc6201263f09ac4219e14291bf53addd</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>User:Sombriks</title>
  <ns>2</ns>
  <id>221</id>
  <revision>
    <id>359</id>
    <timestamp>2010-05-18T21:43:45Z</timestamp>
    <contributor>
      <username>Sombriks</username>
      <id>109</id>
    </contributor>
    <comment>Created page with '= $ whoami =  I'm a slack-user since 10.1 version. Oh i remember, i've started with serious linux with the last Slackware version shipping GNOME by the hands of Pat.  = vmstat = …'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="365" xml:space="preserve">= $ whoami =

I'm a slack-user since 10.1 version. Oh i remember, i've started with serious linux with the last Slackware version shipping GNOME by the hands of Pat.

= vmstat =

Actually i'm mostly a java developer, with some javascript and C over the week. I never tried other distros since then, since slackware have sun jdk/jre, firefox and gcc i'm well served.</text>
    <sha1>f7905e75c9b6e88ee12ef44746f79df0dca72c64</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Emacs from CVS</title>
  <ns>0</ns>
  <id>88</id>
  <revision>
    <id>360</id>
    <parentid>110</parentid>
    <timestamp>2010-05-19T17:15:52Z</timestamp>
    <contributor>
      <username>Lambda-mon key</username>
      <id>110</id>
    </contributor>
    <comment>added note that Emacs no longer maintains CVS source tree -- Use Bazaar!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2520" xml:space="preserve">[[Category:Tutorials]]
The development version of GNU Emacs offers several features over the official Slackware release (Emacs 22), for example Unicode support, multi-TTY, multiple X client frames and font rendering with Xft.  [http://www.unc.edu/~adamsonj/software/emacs-cvs/ Here] is a  SlackBuild that creates a package for Emacs 23.  

Note that the SlackBuild pulls from the CVS server on Savannah, so you do not need to pull the repository first.  If you do, put it in the indicated local cvs directory so that the script will do a "cvs update".

== Installation ==
You should 

&lt;code&gt;
removepkg emacs
&lt;/code&gt;

before installing the Emacs 23 package, which will be installed as package emacs-cvs.

== Emacs Sources Bazaar ==
As of 2009-12-27: GNU Emacs has switched from CVS version control to Bazaar. 

In order to checkout the latest sources the original author's script:
`emacs-cvs.SlackBuild'

The cvs chekcouts in the above script, e.g. lines:
&lt;pre&gt;
cvs -d:pserver:anonymous@cvs.sv.gnu.org:/sources/emacs co emacs 
&lt;/pre&gt;
should be replaced with one line which initializes a branch:
&lt;pre&gt;
bzr branch http://bzr.savannah.gnu.org/r/emacs/trunk emacs
&lt;/pre&gt;
and occurences of:
&lt;pre&gt; 
cvs co 
&lt;/pre&gt;
should be replaced with:
&lt;pre&gt;
bzr update
&lt;/pre&gt;
This assumes you are simply using the bazaar repo to only pull changesets and is
in keeping with the original author's script.

However, if you intend on making local changes to your branch of `Emacs trunk'
it is recomended to first initialize a shared repository e.g.
&lt;pre&gt;
bzr init-repo --2a emacs/
cd emacs/
bzr branch http://bzr.savannah.gnu.org/r/emacs/trunk trunk
&lt;/pre&gt;
and then branch a local tree `quickfixes' of your `local trunk'
&lt;pre&gt;
bzr branch trunk/ quickfixes/
&lt;/pre&gt;
This will help keep your local branch checkout of the `Emacs trunk' pristine and help to avoid breaking 
automated builds of Emacs from bzr while also allowing local edits within the `quickfixes' branch.

Please see http://www.emacswiki.org/emacs/BzrForEmacsDevs for more.

== Automatic Updates ==
I put the following script into /etc/cron.weekly and each Monday I get a newly-updated version of Emacs.  I always keep the old package in case there is any problem with the new version.

&lt;pre&gt;
#! /bin/sh
cd &lt;full path to parent directory&gt;
tar zxvf emacs-cvs.tar.gz
cd emacs-cvs
./emacs-cvs.SlackBuild |mail &lt;yourself&gt;
&lt;/pre&gt;

== Problems? Comments? ==

I have had no problems with the current script.  If you notice anything, please let me know.[[User:Trashbird1240|Trashbird1240]]</text>
    <sha1>3d2534845e3180b0d13b0c3422a03660194a2cba</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>SSL</title>
  <ns>0</ns>
  <id>144</id>
  <revision>
    <id>361</id>
    <parentid>172</parentid>
    <timestamp>2010-05-20T23:49:47Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>/* Client Revokation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12964" xml:space="preserve">[[Category:Tutorials]]
= openSSL 0.9.8e =
'''IMPORTANT: Since this version has a [http://www.mail-archive.com/openssl-users@openssl.org/msg48671.html bug in the blowfish encryption] it is recommended not to use blowfish since it is incompatible with all other openSSL versions!'''

&lt;br&gt;Everything you read here was tested on Slackware 12&lt;br&gt;

; wikipedia says about openSSL:
: ''OpenSSL is an open source implementation of the SSL and TLS protocols. The core library (written in the C programming language) implements the basic cryptographic functions and provides various utility functions. Wrappers allowing the use of the OpenSSL library in a variety of computer languages are available.''

There are many ways to use openSSL. This just covers certificates for use with httpd. You can also use easy-rsa that comes with the openVPN package and can be found in ''/usr/doc/openvpn-2.0.9/easy-rsa/''. For more information read the included ''README'' or look here: [http://openvpn.net/easyrsa.html A Guide to basic RSA Key Management].
Normally you will make a ''Certificate Signing Request (CSR)'' and send this one to a ''Certifying Authority (CA)'' to be signed. But since we don't wanna pay for this and only want to use it for our own special purpose, we don't need to do that and sign everything ourself.

= openSSL + httpd =
Switch to ''/etc/ssl''
&lt;pre&gt;
cd /etc/ssl
&lt;/pre&gt;

In this directory you should see the following listing.  One some non-Slackware linuxes, or if OpenSSL was installed from source, the appropriate directory might be ''/etc/openssl''.
&lt;pre&gt;
root@pecan:/etc/ssl# ls -l
total 24
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 certs/
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 misc/
-rw-r--r-- 1 root root 9374 2007-06-13 12:40 openssl.cnf
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 private/
root@pecan:/etc/ssl# 
&lt;/pre&gt;

We need to generate a private and public RSA key file.
The public key is used to encrypt messages to you and is distributed with your certificate.

== Creating a Self-Signed ''Certificate'' (CRT) ==

=== openssl.cnf + openSSL DB ===
(You should still do this step even if you are buying a commercial certificate.) First things first, so we gotta edit this file, mainly the ''[ CA_default ]'' section.
The 
&lt;pre&gt;
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
...
certificate	= $dir/cacert.pem 	# The CA certificate
...
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
...
&lt;/pre&gt;
to
&lt;pre&gt;
[ CA_default ]

dir		= /etc/ssl		# Where everything is kept
...
certificate	= $dir/certs/ca.crt   	# The CA certificate
...
crl		= $dir/crl/ca.crl	# The current CRL
private_key	= $dir/private/ca.key   # The private key
...
&lt;/pre&gt;
You can even change more options in this file but be aware what you are doing.&lt;br&gt;
openSSL has a database for storing information such as ''Certificate Revocation Lists'' (CRL). Since these files don't exist on startup and we don't use the ''CA.sh'' or ''CA.pl'' scripts we got to create them ourself:
&lt;pre&gt;
mkdir newcerts certs crl private
touch serial index.txt crlnumber crl/ca.crl
echo 01 | tee serial | tee crlnumber
&lt;/pre&gt;
Thanks to ''alienBOB''. Hail to tee king! :p

=== Becoming a ''Certification Authority'' (CA) ===
(Skip this step if you are buying a certificate from a commercial certificate authority such as GoDaddy.) Before you can create and sign your own certificates, you first have to establish yourself as a "Certificate Authority".
To do so, we first create our key file (with a public and a private key) and use it to create our "master certificate" to use when signing other certificates.

; Generate the CA RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/ca.key 4096&lt;/pre&gt;
; Create the CA CRT with the CA RSA Key
: &lt;pre&gt;openssl req -new -x509 -days 3650 -key private/ca.key -out certs/ca.crt&lt;/pre&gt;

=== Create Server CRT ===
A CRT contains your RSA public key, your name, the name of the CA, and is digitally signed by the CA. Browsers that know the CA can verify the signature on that CRT, thereby obtaining your RSA public key. That enables them to send messages which only you can decrypt.
The next step is to create a Server RSA key, generate a ''Certificate Signing Request'' (CSR) out of it and sign it with our CA CRT to get a working SSL CRT for our server.
A CSR is a digital file which contains your public key and your name. Normally you would send the CSR to a CA, who will convert it into a real certificate, by signing it.

; Generate the Server RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/server.key 1024&lt;/pre&gt;
; Create the Server CSR using the Server RSA Key
: '''When asked for the CommonName (CN) enter your domain!'''
: &lt;pre&gt;openssl req -new -key private/server.key -out private/server.csr&lt;/pre&gt;
; Sign the CSR with our CA CRT
: &lt;pre&gt;openssl ca -in private/server.csr -out certs/server.crt&lt;/pre&gt;

You can now delete ''server.csr'' if you want, because it is no longer needed.

(If you are using a commercially signed certificate from a place such as GoDaddy, do the first two commands above but not the last.  Then do ''cat private/server.csr'' to get the text of the certificate request, which you will paste into GoDaddy's web interface to get the certificate.  GoDaddy will then email the email address listed in the ''whois'' information for that domain (Make sure you haven't put in a fake address there to avoid spam!), and after the link in that email is clicked, GoDaddy will email another link to you from which you download a zip file.

The zip file will contain two .crt files, and you should put both of them in /etc/ssl/certs.  Other commerical certificate authorities follow a very similar procedure.)

== Setup httpd ==
=== Edit httpd.conf ===
The whole httpd config is located in ''/etc/httpd''. Fire up your preferred text editor and simply change this at Line 459:
&lt;pre&gt;
# Secure (SSL/TLS) connections
#Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to this
&lt;pre&gt;
# Secure (SSL/TLS) connections
Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to enable SSL support.

You may also have to uncomment the line that starts ''LoadModule ssl_module''.

=== Edit extra/httpd-ssl.conf ===
Now we're going into the guts of the httpd SSL config. Search for ''SSLCertificateFile'' and ''SSLCertificateKeyFile'' change the path to our newly created CRT:
&lt;pre&gt;
...
SSLCertificateFile /etc/ssl/certs/server.crt
...
SSLCertificateKeyFile /etc/ssl/private/server.key
...
SSLCertificateChainFile /etc/ssl/certs/server.crt
...
SSLCACertificatePath /etc/ssl/certs
SSLCACertificateFile /etc/ssl/certs/ca.crt
...
SSLCARevocationPath /etc/ssl/crl
SSLCARevocationFile /etc/ssl/crl/ca.crl
...
&lt;/pre&gt;

(If you have purchased a certificate from a commercial authority, the SSLCertificateFile will be one of the two files you receive from the CA (GoDaddy or VeriSign or whomever), and the SSLCACertificateFile will be the other.  The files will be named such that you can tell which is which -- the SSLCertificateFile will probably be something like ''www.yourdomainname.com.crt'' and the SSLCACertificateFile will be something like ''nameofca-bundle.crt''.)

== Pass-phrase on httpd startup ==
The reason this dialog pops up at startup and every re-start is that the RSA private key inside your ''server.key'' file is stored in encrypted format for security reasons. The pass-phrase is needed decrypt this file, so it can be read and parsed. Removing the pass-phrase removes a layer of security from your server - proceed with caution!
&lt;ol&gt;
&lt;li&gt;
Remove the encryption from the RSA private key (while keeping a backup copy of the original file):
&lt;pre&gt;
cd /etc/ssl
mv private/server.key private/server.key.org
cd private
openssl rsa -in server.key.org -out server.key
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
Make sure the server.key file is only readable by root since it is decrypted:
&lt;pre&gt;
cd /etc/ssl
chmod 0400 private/server.key
&lt;/pre&gt;
&lt;/li&gt;&lt;/ol&gt;
Now server.key contains an unencrypted copy of the key. If you point your server at this file, it will not prompt you for a pass-phrase. HOWEVER, if anyone gets this key they will be able to impersonate you on the net. PLEASE make sure that the permissions on this file are such that only root or the web server user can read it (preferably get your web server to start as root but run as another user, and have the key readable only by root).

As an alternative approach you can use the ''SSLPassPhraseDialog exec:/path/to/program'' facility. Bear in mind that this is neither more nor less secure, of course.

== Verifying and debugging ==
If you simply want to see every information on a CRT:
&lt;pre&gt;openssl x509 -noout -text -in XXX.crt&lt;/pre&gt;

=== Verifying ===
; Verify that a private key matches its Certificate
: Generate a MD5 out of the public key/CRT and compare
: &lt;pre&gt;openssl x509 -noout -modulus -in private/XXX.crt | openssl md5 &amp;&amp; openssl rsa -noout -modulus -in private/XXX.key | openssl md5&lt;/pre&gt;

=== Debugging ===
; s_server - Debugging clients
: &lt;pre&gt;openssl s_server -accept 443 -www&lt;/pre&gt;
; s_client - Debugging servers
: &lt;pre&gt;openssl s_client -connect localhost:443&lt;/pre&gt; or &lt;pre&gt;openssl s_client -connect localhost:443 -state -debug&lt;/pre&gt;

== Security ==
All the files expect the CRTs are only for your eyes, so we change the permissons:
&lt;pre&gt;chmod 0400 private/*.key&lt;/pre&gt;

=== Client Revokation ===
This is only needed if your server certificate is compromised (eg. someone hacked your server and stole your server.key).
&lt;pre&gt;
openssl ca -gencrl -keyfile private/ca.key -cert certs/ca.crt -out crl/ca.crl
&lt;/pre&gt;
That generated us the needed files which we use when we want to revoke a CRT.
&lt;br&gt;&lt;br&gt;
Now that we got a compromised CRT, we got to get rid of it:
&lt;pre&gt;openssl ca -revoke certs/server.crt -keyfile private/ca.key -cert certs/ca.crt&lt;/pre&gt;

== Other ==

=== Change the pass-phrase ===
&lt;pre&gt;
openssl rsa -des3 -in server.key -out server.key.new
mv server.key.new server.key
&lt;/pre&gt;
The first time you're asked for a PEM pass-phrase, you should enter the old pass-phrase. After that, you'll be asked again to enter a pass-phrase - this time, use the new pass-phrase. If you are asked to verify the pass-phrase, you'll need to enter the new pass-phrase a second time.

=== CRT for Clients ===
Ok.. i won't write anything on this, and simply just C/P:
&lt;pre&gt;
openssl genrsa -des3 -out private/client1_priv.key 2048
openssl genrsa -des3 -out private/client2_priv.key 2048
# and so on... depends on how much clients you wanna serv...
openssl req -new -key private/client1_priv.key -out private/client1.csr
openssl req -new -key private/client2_priv.key -out private/client2.csr
# and so on...
openssl ca -in private/client1.csr -out private/client1.crt
openssl ca -in private/client2.csr -out private/client2.crt
cp private/client1.crt private/client1_preconv.crt 
cat private/client1.key &gt;&gt; private/client1_preconv.crt
openssl pkcs12 -export -in private/client1_preconv.crt -out private/client1_postconv.p12 
&lt;/pre&gt;
Install in the clients browser... and change httpd.conf:
&lt;pre&gt;
SSLCACertificateFile PATH/TO/server.crt
SSLVerifyClient require
SSLVerifyDepth 1
&lt;/pre&gt;

=== Convert CRT from PEM to DER format ===
Normally all CRTs are stored in the PEM format.
&lt;pre&gt;openssl x509 -in ca.crt -out ca.crt.der -outform DER&lt;/pre&gt;

== Testing the CRT ==
If you have live web sites, you might wish to test your configuration before restarting apache, to avoid having that panicy few minutes of downtime while you scramble to see what you can do faster, fix the problem or copy back your backup configs.  Test like this:
&lt;pre&gt;httpd -t&lt;/pre&gt;
Look at the error messages it prints out, or the error_log as explained below, if it doesn't work.

Restart your httpd:
&lt;pre&gt;/etc/rc.d/rc.httpd restart&lt;/pre&gt;
Take a look at the httpd ''error_log'' and scroll to the end of the file:
&lt;pre&gt;jed /var/log/httpd/error_log&lt;/pre&gt;
If your getting an error like this:
&lt;pre&gt;[error] Init: Unable to read pass phrase [Hint: key introduced or changed before restart?]&lt;/pre&gt;
... then you should take a look at ''Pass-phrase on httpd startup'' ...

= openSSL + openVPN =
$foo ... maybe next month...

= External Links =
* [http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html SSL/TLS Strong Encryption: FAQ @ httpd.apache.org]
* [http://www.tc.umn.edu/~brams006/selfsign.html Creating a self-signed SSL certificate]
* [http://www.madboa.com/geek/openssl/ OpenSSL Command-Line HOWTO]
* [http://www.5dollarwhitebox.org/wiki/index.php/Howtos_Self_Signed_SSL_Certificates OpenSSL Quick Reference]
* [http://www.opensourcehowto.org/how-to/apache/setup-apache2-with-openssl.html Setup Apache2 with OpenSSL]
* [http://www.marschke.info/admin/ap_opssl_https.html Apache2, OpenSSL und HTTPS: Server- und Client-Authentifizierung mit Zertifikaten über verschlüsselte Internet-Verbindungen]
* [http://www.online-tutorials.net/security/openssl-tutorial/tutorials-t-69-207.html openSSL / openVPN.. comming soon]</text>
    <sha1>4148e01f43b3db7ffa2bad9af9a4ba3ba3e651e3</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Utf-8 linux console</title>
  <ns>0</ns>
  <id>177</id>
  <revision>
    <id>365</id>
    <parentid>308</parentid>
    <timestamp>2010-06-02T13:04:39Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <comment>Added setting LANG in /etc/profile.d/lang.sh</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4707" xml:space="preserve">[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== LANG environment variable ==

I find that typing multibyte characters like "ä" and erasing them with backspace, I can erase much more than what I wrote. It helps to set the LANG variable, preferably by editing /etc/profile.d/lang.sh (or lang.csh) to set it to en_US.UTF-8 or similar.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://home.tiscali.nl/t876506/utf8tbl.html]http://home.tiscali.nl/t876506/utf8tbl.html

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz]http://www.unrealize.co.uk/scripts/misc/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>1f9df45fc81837762eb202abc9e8c1d44ebd88fc</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Hibernate</title>
  <ns>0</ns>
  <id>223</id>
  <revision>
    <id>366</id>
    <timestamp>2010-06-02T13:32:35Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Crude and minimal (but to the point) hibernation help</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="891" xml:space="preserve">In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

 append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''.

----

The above is everything I needed to do with my Slackware64 13.1 on a new laptop. I hope that works for you as well, but there are many requirements and intricacies not mentioned above. Google might help you. Please edit this document accordingly if you find out more.

[[Category:Tutorials]]</text>
    <sha1>f671f80bff839a048076759b5d0a677fcdac222f</sha1>
  </revision>
  <revision>
    <id>368</id>
    <parentid>366</parentid>
    <timestamp>2010-06-02T13:42:09Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <comment>fix + link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1022" xml:space="preserve">In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

 append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''. Afterwards, run lilo.

----

The above is everything I needed to do with my Slackware64 13.1 on a new laptop. I hope that works for you as well, but there are many requirements and intricacies not mentioned above. Google might help you. Please edit this document accordingly if you find out more.

Some more info at [http://www.linuxquestions.org/linux/answers/Hardware/Mini_HOW_TO_Hibernate_and_resume_0]

[[Category:Tutorials]]</text>
    <sha1>d82d505f883f3fdce6be110953b80c0ee752af80</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>Dell Vostro 1310</title>
  <ns>0</ns>
  <id>225</id>
  <revision>
    <id>369</id>
    <timestamp>2010-06-16T19:56:26Z</timestamp>
    <contributor>
      <username>Diegobza</username>
      <id>116</id>
    </contributor>
    <comment>Created page with '[[Category:Hardware]] ==Slackware on a Dell Vostro 1310 Laptop==  ==Hardware== $ lspci &lt;pre&gt; 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2448" xml:space="preserve">[[Category:Hardware]]
==Slackware on a Dell Vostro 1310 Laptop==

==Hardware==
$ lspci
&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
&lt;/pre&gt;

Changes comming...</text>
    <sha1>4c718dd7949063eb82cf737ec9384d8c6f0021ee</sha1>
  </revision>
  <revision>
    <id>372</id>
    <parentid>369</parentid>
    <timestamp>2010-06-16T20:28:39Z</timestamp>
    <contributor>
      <username>Diegobza</username>
      <id>116</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3537" xml:space="preserve">[[Category:Hardware]]
=Slackware on a Dell Vostro 1310 Laptop=

=Hardware=
$ lspci
&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
&lt;/pre&gt;

=Known Problems=

==Keyboard/Touchpad==
When you boot a fresh version of Slackware installed on a Dell Vostro 1310 laptop you may find yourself without control of you keyboard and touchpad, like they were turned off at boottime. As many forums and mailing list have discussed, this is a kernel-related issue, however, you don't need to recompile and/or update the default kernel shipped with your Slackware CD/DVD box.

The fix is real simple, all you have to do is to modify the kernel's append line in the your /etc/lilo.conf in order to add the "i8042.reset" text. Remember you must be logged as the super user to be able to edit lilo's configuration. At the end your append line should be like this (considering you didn't added commands to this line previously):
&lt;pre&gt;
append="i8042.reset vt.default_utf8=0"
&lt;/pre&gt;

This is it. Problem fixed. Just remember to run lilo command to update your changes.

&lt;pre&gt;
# lilo
&lt;/pre&gt;

Note that this change can be done at installation to save you time and avoid stress. Just type "i8042.reset" when the setup script prompts you about any desirable lilo append command.</text>
    <sha1>867da4917c72b321c710da42ee3a72d236cd0326</sha1>
  </revision>
</page>
<page arvcontinue="20100309002045|312">
  <title>SlackWiki:Community Portal</title>
  <ns>4</ns>
  <id>226</id>
  <revision>
    <id>370</id>
    <timestamp>2010-06-16T20:00:45Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Created page with '===BRASIL=== ====[http://www.slackwarebrasil.org GUS-BR]==== Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt; [http://www.slackwarebrasil.org www.slackwar…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="315" xml:space="preserve">===BRASIL===
====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
[http://www.slackwarebrasil.org www.slackwarebrasil.org ]

===ITALY===
====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
[http://slacky.eu/ http://slacky.eu]</text>
    <sha1>d596ad880badd5d709d035b722a6829752d18de1</sha1>
  </revision>
  <revision>
    <id>371</id>
    <parentid>370</parentid>
    <timestamp>2010-06-16T20:10:07Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="429" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
[http://www.slackwarebrasil.org www.slackwarebrasil.org ]
&lt;BR&gt;
====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
[http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
[http://slackware.linux.or.id http://slackware.linux.or.id]</text>
    <sha1>a6674939325940d23ba2bf781ba382a241c15834</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Converting From CRLF To LF</title>
  <ns>0</ns>
  <id>75</id>
  <revision>
    <id>373</id>
    <parentid>96</parentid>
    <timestamp>2010-06-16T23:17:37Z</timestamp>
    <contributor>
      <username>Sombriks</username>
      <id>109</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="573" xml:space="preserve">=Explanation=

There are several ways of converting the CRLF combination to LF and vice-versa. The simplest one under Slackware is to use the tools &lt;code&gt;fromdos&lt;/code&gt; and &lt;code&gt;todos&lt;/code&gt;, which receive the file from the standard input and write the result to the standard output. They are part of the &lt;code&gt;bin&lt;/code&gt; package.

=Examples=

 $ fromdos &lt;input_file &gt;output_file   # Converts CRLF to LF
 $ todos   &lt;input_file &gt;output_file   # Converts LF to CRLF

Also you could play with tr (from CRLF to LF):

 $ tr -d '\r' &lt; input_file &gt; output_file

[[Category:Tips]]</text>
    <sha1>0e1600502b582c7e0b630bbbdb4c7862e924c3d4</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Dell Vostro 1310</title>
  <ns>0</ns>
  <id>225</id>
  <revision>
    <id>374</id>
    <parentid>372</parentid>
    <timestamp>2010-06-17T14:56:19Z</timestamp>
    <contributor>
      <username>Diegobza</username>
      <id>116</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4497" xml:space="preserve">[[Category:Hardware]]
=Slackware on a Dell Vostro 1310 Laptop=

=Hardware=

{| align="center" style="border: 0px; width: 600px"
|+ Slackware Hardware Compatibility
|
! colspan="5" style="background:#ffdead;" | Slackware Versions
|-
|
| style="text-align: center" | 12
| style="text-align: center" | 12.1
| style="text-align: center" | 12.2
| style="text-align: center" | 13
| style="text-align: center" | 13.1
|-
|Wireless
| style="text-align: center; background-color: gray"  | Not Tested
| style="text-align: center" | Not Tested
| style="text-align: center" | Not Tested
| style="text-align: center" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
|-
|Bluetooth || Not Tested || Not Tested || Not Tested || Not Tested || Working
|}

==Hardware Specification==

Output of lspci:
&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
&lt;/pre&gt;

=Known Problems=

==Keyboard/Touchpad==
When you boot a fresh version of Slackware installed on a Dell Vostro 1310 laptop you may find yourself without control of you keyboard and touchpad, like they were turned off at boottime. As many forums and mailing list have discussed, this is a kernel-related issue, however, you don't need to recompile and/or update the default kernel shipped with your Slackware CD/DVD box.

The fix is real simple, all you have to do is to modify the kernel's append line in the your /etc/lilo.conf in order to add the "i8042.reset" text. Remember you must be logged as the super user to be able to edit lilo's configuration. At the end your append line should be like this (considering you didn't added commands to this line previously):
&lt;pre&gt;
append="i8042.reset vt.default_utf8=0"
&lt;/pre&gt;

This is it. Problem fixed. Just remember to run lilo command to update your changes.

&lt;pre&gt;
# lilo
&lt;/pre&gt;

Note that this change can be done at installation to save you time and avoid stress. Just type "i8042.reset" when the setup script prompts you about any desirable lilo append command.

==LCD Brightness Control==

Affected versions:
* Slackware 13: working.
** Console and GUI apps work flawlessly.
* Slackware 13.1: partially working.
** Console apps work as intended.
** GUI app (Xfce4 Power Manager) not working.</text>
    <sha1>63b7de9cf4d476d5f90f6503fe2f3d7c7d98ca25</sha1>
  </revision>
  <revision>
    <id>375</id>
    <parentid>374</parentid>
    <timestamp>2010-06-17T15:18:35Z</timestamp>
    <contributor>
      <username>Diegobza</username>
      <id>116</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6020" xml:space="preserve">[[Category:Hardware]]
=Slackware on a Dell Vostro 1310 Laptop=

=Hardware=

{| align="center" style="border: 0px; width: 600px"
|+ Slackware Hardware Compatibility
|
! colspan="5" style="background:#ffdead;" | Slackware Versions
|-
|
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.1
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.2
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13.1
|-
| style="font-weight: bold; background-color: #9C9CFF" | Ethernet
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | LCD Control
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Wireless
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Bluetooth
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
|}

==Hardware Specification==

Output of lspci:
&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
&lt;/pre&gt;

=Known Problems=

==Keyboard/Touchpad==
When you boot a fresh version of Slackware installed on a Dell Vostro 1310 laptop you may find yourself without control of you keyboard and touchpad, like they were turned off at boottime. As many forums and mailing list have discussed, this is a kernel-related issue, however, you don't need to recompile and/or update the default kernel shipped with your Slackware CD/DVD box.

The fix is real simple, all you have to do is to modify the kernel's append line in the your /etc/lilo.conf in order to add the "i8042.reset" text. Remember you must be logged as the super user to be able to edit lilo's configuration. At the end your append line should be like this (considering you didn't added commands to this line previously):
&lt;pre&gt;
append="i8042.reset vt.default_utf8=0"
&lt;/pre&gt;

This is it. Problem fixed. Just remember to run lilo command to update your changes.

&lt;pre&gt;
# lilo
&lt;/pre&gt;

Note that this change can be done at installation to save you time and avoid stress. Just type "i8042.reset" when the setup script prompts you about any desirable lilo append command.

==LCD Brightness Control==

Affected versions:
* Slackware 13: working.
** Console and GUI apps work flawlessly.
* Slackware 13.1: partially working.
** Console apps work as intended.
** GUI app (Xfce4 Power Manager) not working.</text>
    <sha1>3b1327b0b2f9bc15b20e7c82e279ddd9757d7930</sha1>
  </revision>
  <revision>
    <id>376</id>
    <parentid>375</parentid>
    <timestamp>2010-06-17T16:38:14Z</timestamp>
    <contributor>
      <username>Diegobza</username>
      <id>116</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9966" xml:space="preserve">[[Category:Hardware]]
=Slackware on a Dell Vostro 1310 Laptop=

=Hardware=

{| align="center" style="border: 0px; width: 600px"
|+ Slackware Hardware Compatibility
|
! colspan="5" style="background:#ffdead;" | Slackware Versions
|-
|
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.1
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.2
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13.1
|-
| style="font-weight: bold; background-color: #9C9CFF" | Bluetooth
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Camera
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Ethernet
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Hibernate
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
|-
| style="font-weight: bold; background-color: #9C9CFF" | Keyboard
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | LCD Control
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Sound
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Suspend
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Touchpad
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Wireless
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|}

==Hardware Specification==

Output of lspci:
&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
&lt;/pre&gt;

=Known Problems=

==Keyboard/Touchpad==
When you boot a fresh version of Slackware installed on a Dell Vostro 1310 laptop you may find yourself without control of you keyboard and touchpad, like they were turned off at boottime. As many forums and mailing list have discussed, this is a kernel-related issue, however, you don't need to recompile and/or update the default kernel shipped with your Slackware CD/DVD box.

The fix is real simple, all you have to do is to modify the kernel's append line in the your /etc/lilo.conf in order to add the "i8042.reset" text. Remember you must be logged as the super user to be able to edit lilo's configuration. At the end your append line should be like this (considering you didn't added commands to this line previously):
&lt;pre&gt;
append="i8042.reset vt.default_utf8=0"
&lt;/pre&gt;

This is it. Problem fixed. Just remember to run lilo command to update your changes.

&lt;pre&gt;
# lilo
&lt;/pre&gt;

Note that this change can be done at installation to save you time and avoid stress. Just type "i8042.reset" when the setup script prompts you about any desirable lilo append command.

==LCD Brightness Control==

Affected versions:
* Slackware 13: working.
** Console and GUI apps work flawlessly.
* Slackware 13.1: partially working.
** Console apps work as intended.
** GUI app (Xfce4 Power Manager) not working.

==Suspend to RAM==

As shown on the Slackware Hardware Compatibility table, the Suspend to RAM feature used to work without problems on Slackware 13. But version 13.1 introduced a new flaw where you no longer can suspend the machine using GUI tools. To be more specific, this is a problem related to pm-utils. An workaround to fix it is to create a script at /etc/pm/sleep.d with this content:

&lt;pre&gt;
#!/bin/bash

function unbind_usb {
    for driver in ehci ohci uhci; do
        cd "/sys/bus/pci/drivers/${driver}_hcd";
        ids=$(ls | grep :);
        echo $ids &gt; /tmp/DISABLED_$driver;
        for id in $ids; do
            echo "Unbinding $id";
            echo -n "$id" &gt; unbind;
            disabled="$disabled $id";
        done;
    done;
}

function bind_usb {
    for driver in ehci ohci uhci; do
        cd "/sys/bus/pci/drivers/${driver}_hcd";
        for id in $(cat /tmp/DISABLED_$driver); do
            echo "Binding $id";
            echo -n "$id" &gt; bind;
        done;
        rm /tmp/DISABLED_$driver;
    done;
}

case "$1" in
    hibernate|suspend)
        unbind_usb;
    ;;
    thaw|resume)
        bind_usb;
        # Uncomment the following two lines if USB devices stutter after resume
        # unbind_usb;
        # bind_usb;
    ;;
    *)
    exit 1;
    ;;
esac;
exit 0;
&lt;/pre&gt;

Now you're able to suspend your laptop using GUI tools. Note that you don't need this script to suspend with command line like this:

&lt;pre&gt;
# echo mem &gt; /sys/power/state
&lt;/pre&gt;
=See also=</text>
    <sha1>45871bcf269970c74ed2bbf00ac6717796e7ec68</sha1>
  </revision>
  <revision>
    <id>377</id>
    <parentid>376</parentid>
    <timestamp>2010-06-17T19:03:47Z</timestamp>
    <contributor>
      <username>Diegobza</username>
      <id>116</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10602" xml:space="preserve">[[Category:Hardware]]
=Slackware on a Dell Vostro 1310 Laptop=

=Hardware=
Here is a Hardware Compatibility table for different versions of Slackware.
{| align="center" style="border: 0px; width: 600px"
|+ Slackware Hardware Compatibility
|
! colspan="5" style="background:#ffdead;" | Slackware Versions
|-
|
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.1
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.2
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13.1
|-
| style="font-weight: bold; background-color: #9C9CFF" | Bluetooth
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Camera
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Ethernet
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Hibernate
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
|-
| style="font-weight: bold; background-color: #9C9CFF" | Keyboard
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | LCD Control
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Multimedia Keys
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #FF6F79" | Not Working
| style="text-align: center; background-color: #FF6F79" | Not Working
| style="text-align: center; background-color: #FF6F79" | Not Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Sound
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Suspend
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Touchpad
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Wireless
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|}

Legend:

{|
| style="text-align: center; background-color: #5EFF54" |a
|-
| style="text-align: center; background-color: #5EFF54" |b
|}

==Hardware Specification==

Output of lspci:
&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
&lt;/pre&gt;

=Known Problems=

==Keyboard/Touchpad==
When you boot a fresh version of Slackware installed on a Dell Vostro 1310 laptop you may find yourself without control of you keyboard and touchpad, like they were turned off at boottime. As many forums and mailing list have discussed, this is a kernel-related issue, however, you don't need to recompile and/or update the default kernel shipped with your Slackware CD/DVD box.

The fix is real simple, all you have to do is to modify the kernel's append line in the your /etc/lilo.conf in order to add the "i8042.reset" text. Remember you must be logged as the super user to be able to edit lilo's configuration. At the end your append line should be like this (considering you didn't added commands to this line previously):
&lt;pre&gt;
append="i8042.reset vt.default_utf8=0"
&lt;/pre&gt;

This is it. Problem fixed. Just remember to run lilo command to update your changes.

&lt;pre&gt;
# lilo
&lt;/pre&gt;

Note that this change can be done at installation to save you time and avoid stress. Just type "i8042.reset" when the setup script prompts you about any desirable lilo append command.

==LCD Brightness Control==

Affected versions:
* Slackware 13: working.
** Console and GUI apps work flawlessly.
* Slackware 13.1: partially working.
** Console apps work as intended.
** GUI app (Xfce4 Power Manager) not working.

==Suspend to RAM==

As shown on the Slackware Hardware Compatibility table, the Suspend to RAM feature used to work without problems on Slackware 13. But version 13.1 introduced a new flaw where you no longer can suspend the machine using GUI tools. To be more specific, this is a problem related to pm-utils. An workaround to fix it is to create a script at /etc/pm/sleep.d with this content:

&lt;pre&gt;
#!/bin/bash

function unbind_usb {
    for driver in ehci ohci uhci; do
        cd "/sys/bus/pci/drivers/${driver}_hcd";
        ids=$(ls | grep :);
        echo $ids &gt; /tmp/DISABLED_$driver;
        for id in $ids; do
            echo "Unbinding $id";
            echo -n "$id" &gt; unbind;
            disabled="$disabled $id";
        done;
    done;
}

function bind_usb {
    for driver in ehci ohci uhci; do
        cd "/sys/bus/pci/drivers/${driver}_hcd";
        for id in $(cat /tmp/DISABLED_$driver); do
            echo "Binding $id";
            echo -n "$id" &gt; bind;
        done;
        rm /tmp/DISABLED_$driver;
    done;
}

case "$1" in
    hibernate|suspend)
        unbind_usb;
    ;;
    thaw|resume)
        bind_usb;
        # Uncomment the following two lines if USB devices stutter after resume
        # unbind_usb;
        # bind_usb;
    ;;
    *)
    exit 1;
    ;;
esac;
exit 0;
&lt;/pre&gt;

Now you're able to suspend your laptop using GUI tools. Note that you don't need this script to suspend with command line like this:

&lt;pre&gt;
# echo mem &gt; /sys/power/state
&lt;/pre&gt;
=See also=</text>
    <sha1>f32520c3a960067b746fe6f6ccfe46a8db4c0151</sha1>
  </revision>
  <revision>
    <id>378</id>
    <parentid>377</parentid>
    <timestamp>2010-06-24T17:06:22Z</timestamp>
    <contributor>
      <username>Diegobza</username>
      <id>116</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10991" xml:space="preserve">[[Category:Hardware]]
=Slackware on a Dell Vostro 1310 Laptop=

=Hardware=
Here is a Hardware Compatibility table for different versions of Slackware.
{| align="center" style="border: 0px; width: 600px"
|+ Slackware Hardware Compatibility
|
! colspan="5" style="background:#ffdead;" | Slackware Versions
|-
|
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.1
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.2
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13.1
|-
| style="font-weight: bold; background-color: #9C9CFF" | Bluetooth
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Camera
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Ethernet
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Hibernate
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
|-
| style="font-weight: bold; background-color: #9C9CFF" | Keyboard
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | LCD Control
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Multimedia Keys
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #FF6F79" | Not Working
| style="text-align: center; background-color: #FF6F79" | Not Working
| style="text-align: center; background-color: #FF6F79" | Not Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Sound
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Suspend
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Touchpad
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Wireless
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|}

Legend:

{|
| style="text-align: center; background-color: #5EFF54" |a
|-
| style="text-align: center; background-color: #5EFF54" |b
|}

==Hardware Specification==

Output of lspci:
&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
&lt;/pre&gt;

==Hardware Configuration==

===Multimedia Keys===
One of the ways to configure the multimedia keys is installing an external software called xbindkeys. This software looks for it's configuration file 

&lt;pre&gt;
"amixer set Master 5%+"
XF86AudioRaiseVolume
"amixer set Master 10%-"
XF86AudioLowerVolume
"xmms -t"
XF86AudioPlay
"xmms -s"
XF86AudioStop
"xmms -r"
XF86AudioPrev
"xmms -f"
&lt;/pre&gt;

=Known Problems=

==Keyboard/Touchpad==
When you boot a fresh version of Slackware installed on a Dell Vostro 1310 laptop you may find yourself without control of you keyboard and touchpad, like they were turned off at boottime. As many forums and mailing list have discussed, this is a kernel-related issue, however, you don't need to recompile and/or update the default kernel shipped with your Slackware CD/DVD box.

The fix is real simple, all you have to do is to modify the kernel's append line in the your /etc/lilo.conf in order to add the "i8042.reset" text. Remember you must be logged as the super user to be able to edit lilo's configuration. At the end your append line should be like this (considering you didn't added commands to this line previously):
&lt;pre&gt;
append="i8042.reset vt.default_utf8=0"
&lt;/pre&gt;

This is it. Problem fixed. Just remember to run lilo command to update your changes.

&lt;pre&gt;
# lilo
&lt;/pre&gt;

Note that this change can be done at installation to save you time and avoid stress. Just type "i8042.reset" when the setup script prompts you about any desirable lilo append command.

==LCD Brightness Control==

Affected versions:
* Slackware 13: working.
** Console and GUI apps work flawlessly.
* Slackware 13.1: partially working.
** Console apps work as intended.
** GUI app (Xfce4 Power Manager) not working.

==Suspend to RAM==

As shown on the Slackware Hardware Compatibility table, the Suspend to RAM feature used to work without problems on Slackware 13. But version 13.1 introduced a new flaw where you no longer can suspend the machine using GUI tools. To be more specific, this is a problem related to pm-utils. An workaround to fix it is to create a script at /etc/pm/sleep.d with this content:

&lt;pre&gt;
#!/bin/bash

function unbind_usb {
    for driver in ehci ohci uhci; do
        cd "/sys/bus/pci/drivers/${driver}_hcd";
        ids=$(ls | grep :);
        echo $ids &gt; /tmp/DISABLED_$driver;
        for id in $ids; do
            echo "Unbinding $id";
            echo -n "$id" &gt; unbind;
            disabled="$disabled $id";
        done;
    done;
}

function bind_usb {
    for driver in ehci ohci uhci; do
        cd "/sys/bus/pci/drivers/${driver}_hcd";
        for id in $(cat /tmp/DISABLED_$driver); do
            echo "Binding $id";
            echo -n "$id" &gt; bind;
        done;
        rm /tmp/DISABLED_$driver;
    done;
}

case "$1" in
    hibernate|suspend)
        unbind_usb;
    ;;
    thaw|resume)
        bind_usb;
        # Uncomment the following two lines if USB devices stutter after resume
        # unbind_usb;
        # bind_usb;
    ;;
    *)
    exit 1;
    ;;
esac;
exit 0;
&lt;/pre&gt;

Now you're able to suspend your laptop using GUI tools. Note that you don't need this script to suspend with command line like this:

&lt;pre&gt;
# echo mem &gt; /sys/power/state
&lt;/pre&gt;
=See also=</text>
    <sha1>8eecc42290e50e738e716c54883e31f77bde71ca</sha1>
  </revision>
  <revision>
    <id>379</id>
    <parentid>378</parentid>
    <timestamp>2010-06-26T15:24:45Z</timestamp>
    <contributor>
      <username>Diegobza</username>
      <id>116</id>
    </contributor>
    <comment>/* Multimedia Keys */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11166" xml:space="preserve">[[Category:Hardware]]
=Slackware on a Dell Vostro 1310 Laptop=

=Hardware=
Here is a Hardware Compatibility table for different versions of Slackware.
{| align="center" style="border: 0px; width: 600px"
|+ Slackware Hardware Compatibility
|
! colspan="5" style="background:#ffdead;" | Slackware Versions
|-
|
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.1
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 12.2
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13
| style="font-weight: bold;text-align: center; background-color: #7FD0FF" | 13.1
|-
| style="font-weight: bold; background-color: #9C9CFF" | Bluetooth
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Camera
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Ethernet
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Hibernate
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
|-
| style="font-weight: bold; background-color: #9C9CFF" | Keyboard
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | LCD Control
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Multimedia Keys
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #FF6F79" | Not Working
| style="text-align: center; background-color: #FF6F79" | Not Working
| style="text-align: center; background-color: #FF6F79" | Not Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Sound
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Suspend
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Touchpad
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
| style="text-align: center; background-color: #F7FF17" | P. Working
|-
| style="font-weight: bold; background-color: #9C9CFF" | Wireless
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #E0E0E0" | Not Tested
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
| style="text-align: center; background-color: #5EFF54" | Working
|}

Legend:

{|
| style="text-align: center; background-color: #5EFF54" |a
|-
| style="text-align: center; background-color: #5EFF54" |b
|}

==Hardware Specification==

Output of lspci:
&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
&lt;/pre&gt;

==Hardware Configuration==

===Multimedia Keys===
One of the ways to configure the multimedia keys is installing an external software called xbindkeys. This software looks for it's configuration file $HOME/.xbindkeysrc. The code below shows a simple configuration that uses amixer commands to change volume. The play/pause, stop, previous, next keys were bind to xmms player.

&lt;pre&gt;
"amixer set Master 5%+"
XF86AudioRaiseVolume
"amixer set Master 10%-"
XF86AudioLowerVolume
"xmms -t"
XF86AudioPlay
"xmms -s"
XF86AudioStop
"xmms -r"
XF86AudioPrev
"xmms -f"
&lt;/pre&gt;

=Known Problems=

==Keyboard/Touchpad==
When you boot a fresh version of Slackware installed on a Dell Vostro 1310 laptop you may find yourself without control of you keyboard and touchpad, like they were turned off at boottime. As many forums and mailing list have discussed, this is a kernel-related issue, however, you don't need to recompile and/or update the default kernel shipped with your Slackware CD/DVD box.

The fix is real simple, all you have to do is to modify the kernel's append line in the your /etc/lilo.conf in order to add the "i8042.reset" text. Remember you must be logged as the super user to be able to edit lilo's configuration. At the end your append line should be like this (considering you didn't added commands to this line previously):
&lt;pre&gt;
append="i8042.reset vt.default_utf8=0"
&lt;/pre&gt;

This is it. Problem fixed. Just remember to run lilo command to update your changes.

&lt;pre&gt;
# lilo
&lt;/pre&gt;

Note that this change can be done at installation to save you time and avoid stress. Just type "i8042.reset" when the setup script prompts you about any desirable lilo append command.

==LCD Brightness Control==

Affected versions:
* Slackware 13: working.
** Console and GUI apps work flawlessly.
* Slackware 13.1: partially working.
** Console apps work as intended.
** GUI app (Xfce4 Power Manager) not working.

==Suspend to RAM==

As shown on the Slackware Hardware Compatibility table, the Suspend to RAM feature used to work without problems on Slackware 13. But version 13.1 introduced a new flaw where you no longer can suspend the machine using GUI tools. To be more specific, this is a problem related to pm-utils. An workaround to fix it is to create a script at /etc/pm/sleep.d with this content:

&lt;pre&gt;
#!/bin/bash

function unbind_usb {
    for driver in ehci ohci uhci; do
        cd "/sys/bus/pci/drivers/${driver}_hcd";
        ids=$(ls | grep :);
        echo $ids &gt; /tmp/DISABLED_$driver;
        for id in $ids; do
            echo "Unbinding $id";
            echo -n "$id" &gt; unbind;
            disabled="$disabled $id";
        done;
    done;
}

function bind_usb {
    for driver in ehci ohci uhci; do
        cd "/sys/bus/pci/drivers/${driver}_hcd";
        for id in $(cat /tmp/DISABLED_$driver); do
            echo "Binding $id";
            echo -n "$id" &gt; bind;
        done;
        rm /tmp/DISABLED_$driver;
    done;
}

case "$1" in
    hibernate|suspend)
        unbind_usb;
    ;;
    thaw|resume)
        bind_usb;
        # Uncomment the following two lines if USB devices stutter after resume
        # unbind_usb;
        # bind_usb;
    ;;
    *)
    exit 1;
    ;;
esac;
exit 0;
&lt;/pre&gt;

Now you're able to suspend your laptop using GUI tools. Note that you don't need this script to suspend with command line like this:

&lt;pre&gt;
# echo mem &gt; /sys/power/state
&lt;/pre&gt;
=See also=</text>
    <sha1>6e1c3bf0fb11eb25dacf9966d36e85969a267fd1</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Console-Only Communication</title>
  <ns>0</ns>
  <id>48</id>
  <revision>
    <id>380</id>
    <parentid>69</parentid>
    <timestamp>2010-07-14T09:18:55Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8965" xml:space="preserve">HOWTO: access on-line resorces on the internet using only console-based tools.

== Overview ==
Many times, particularly when things aren't working as expected, you may find yourself restricted to a console-only (non-X or non-graphical) session. If you have networking running, you can still access on-line support tools through your console. This tutorial shows you how to:

* Use virtual consoles to increase the number of consoles you can use simultaneously;
* Use the &lt;tt&gt;screen&lt;/tt&gt; to create sessions that are persistant even after you close the console;
* Use &lt;tt&gt;irssi&lt;/tt&gt; to access the irc network and ##slackware on irc.freenode.org;
* Use &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; to access HTTP (web) server information;
* Use &lt;tt&gt;lynx&lt;/tt&gt; to pastebin a file when you need to send configuration information to an IRC channel, and;
* Use &lt;tt&gt;wget&lt;/tt&gt; to download a pastebin file to your local machine.

== Prerequisites ==
This tutorial will assume you are comfortable with the following concepts:
* Basic file management operations (&lt;tt&gt;cp&lt;/tt&gt;,&lt;tt&gt;rm&lt;/tt&gt;,etc);
* Using a console-based file editor (&lt;tt&gt;pico&lt;/tt&gt;,&lt;tt&gt;vi&lt;/tt&gt;,etc);
* [http://www.casino-spielen.biz online casino spiele]

== Virtual Consoles ==
One of the handiest features if you're relegated to working from a console is the use of virtual consoles. This allows you to start multiple login sessions from the same console keyboard, mouse, and monitor. That way, you can have one virtual console logged into IRC so you can talk to ##slackware, one that you can use for web access, and another that you can use to test commands. 

Using virtual consoles is easy. Simply hold the ALT key while hitting the F2 key (ALT+F2) to switch to the second console. To switch back to the first console, use ALT+F1. You have virtual consoles available on F1 through F6.

If you're using X, you can still access one of the virtual consoles, which is useful if X is hung up for some reason (especially if X won't restart using ctrl+alt+backspace). To access this virtual console, hold CTRL *and* ALT while pressing the F6 key (CTRL+ALT+F6). To switch back to your X session, press CTRL+ALT+F7.

== Using &lt;tt&gt;screen&lt;/tt&gt; ==
The &lt;tt&gt;screen&lt;/tt&gt; utility allows you to start a console session which is persistent across login and logout. This is useful, for example, if you're using IRC -- perhaps you want to stay logged into your IRC channel even after you have logged out of your console session. The concept is straightforward: when you run screen, it gives you a bash prompt "inside of" the screen session. At this new bash prompt you can start your IRC session. When you wish to log out, you can detach from screen and log out -- but screen continues to run in the background. When you log back in, you can re-attach to your screen session and resume your IRC session.

Visit [[Screen|this page]] for the specifics on attaching and detaching sessions using &lt;tt&gt;screen&lt;/tt&gt;.

== Using &lt;tt&gt;irssi&lt;/tt&gt; ==
The &lt;tt&gt;irssi&lt;/tt&gt; program is a console-based IRC client. Using irssi, you can access the ##slackware IRC channel on irc.freenode.net. 

*WARNING*: Whenever you are using any type of IRC client on any type of machine, make sure that you are not doing so as the superuser (root). Doing so is a security risk, since if for some reason an attacker is able to successfully attack your IRC client, the attacker will have root access to your machine.

To access the ##slackware channel on irc.freenode.org using &lt;tt&gt;irssi&lt;/tt&gt;, perform the following steps:

* Start irssi:
 user@slackbox:~$ irssi
* At the (status) prompt, connect to irc.freenode.org:
 [(status)] /connect irc.freenode.org
* Once connected, set your nick:
 [(status)] /nick Myl33tNick
* Join the ##slackware channel:
 [(status)] /join ##slackware
* To exit irssi:
 [(status)] /quit
Visit [[Irssi|this page]] for more information on using irssi.

== Using &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; ==
You can use &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; to access http (web) servers from your console session. Lynx allows you to access a web site interactively, much like using a graphical browser such as Firefox, but through a text-only console session. &lt;tt&gt;Wget&lt;/tt&gt; allows you to retrieve documents from web servers non-interactively, which is handy when you need to retrieve a certain document (say a tarball or a script file) from a web server in a very quick way.

To start using lynx, from a bash prompt simply type:
 user@slackbox:~$ lynx "http://www.slackware.com"
to visit Slackware's official website. To exit lynx, use CTRL+C. In the example above, the double-quotes are not strictly required. However, many URLs contain characters which have special meaning to the bash interpreter (such as the ampersand), and the double-quotes stop bash from trying to interpret those characters.

Although wget has a wide array of options (visit man wget sometime), its basic use is very simple. For example, to download the latest kernel patch (as of this writing) from kernel.org, simply do:
 user@slackbox:~$ wget "http://www.kernel.org/pub/linux/kernel/v2.6/patch-2.6.20.3.bz2"
Again, the quotes here are not strictly required for this URL, but are required for certain URLs. It's good to get in the habit of always double-quoting URLs from a bash prompt.

== Using &lt;tt&gt;lynx&lt;/tt&gt; in conjuction with pastebin ==
You may find yourself on ##slackware and another channel member may ask you to "pastebin" information to them. The purpose of pastebin is so that you can share technical information (for example, the contents of a configuration file) with the other channel members, without pasting that information directly into IRC itself (which is generally disliked by other IRC members and will get you banned if you try it). "Pastebin" is a generic term for a web site which offers this sort of service. There are many pastebin sites out there; for simplicity's sake, this tutorial uses [http://pastebin.ca pastebin.ca].

You can use lynx to access the pastebin site, but what if you need to pastebin the contents of an entire file? You can do this using the &lt;tt&gt;lynx&lt;/tt&gt; program:
* use &lt;tt&gt;lynx&lt;/tt&gt; to access pastebin.ca:
 user@slackbox:~$ lynx "http://pastebin.ca"
* Page down until you see the large textbox area, move your cursor to the first line (where you see the X below):
 Create a New Pastebin Post
 
    Welcome  to the Pastebin. For information on what this is, take a look
    at  the  What  is This? page. You may also want to see the most recent
    post to the pastebin.
  
    Please enter your new post below (or upload a file instead):
 
 paste below
 
 
    X_____________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
 (NORMAL LINK)   Use right-arrow or &lt;return&gt; to activate.
   Arrow keys: Up and Down to move.  Right to follow a link; Left to go back.
  H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list
* Press Ctrl+X, then i, and enter the location of the file you wish to pastebin.
  Enter a filename: /etc/ssh/sshd_config
* Page down until you see the "Submit Post" link, select it (it will turn yellow), and press the enter key.
* On the next page, scroll down until you find the URL to your pastebin file. It will look something like this:
 paste added to database
 
   Your  paste  has  been  accepted an added to the database. You will be
   redirected to it momentarily. The URL for it is:
 
   http://pastebin.ca/398871
 
   You may use that URL for referencing your submission from now on.
* Give this URL to the person who requested the information on IRC.

== Using &lt;tt&gt;wget&lt;/tt&gt; in conjunction with pastebin ==
Every pastebin site should have a way to request any pastebin file in "raw" format, meaning without the added HTML code so that the pastebin information displays properly in a browser. Accessing the "raw" format means you can access exactly what was pastebinned, with nothing else added. This is useful if you want to download a configuration file from pastebin. If you know the raw URL of the pastebin page you need, you can use wget to retrieve the file.
* Find the raw URL associated with the pastebin page. For pastebin.ca, this is just the regular URL with an extra "raw" directory inserted. For example, if your regular pastebin url is http://pastebin.ca/398871, then the raw version is at http://pastebin.ca/raw/398871.
* use wget to retrieve the file, but rename it so that it's not named 398871 (in this example, the output is named "this.cfg"):
 user@slackbox:~$ wget "http://pastebin.ca/raw/398871" -O this.cfg
You'll find you'll use commands like wget over and over again this way, even when you have access to a fully graphical web browser.
[[Category:Tutorials]]</text>
    <sha1>52c5535fc0f285022a8387182ae583843fda65f2</sha1>
  </revision>
  <revision>
    <id>381</id>
    <parentid>380</parentid>
    <timestamp>2010-07-14T16:30:04Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/AmandaCusack|AmandaCusack]] ([[User talk:AmandaCusack|Talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8910" xml:space="preserve">HOWTO: access on-line resorces on the internet using only console-based tools.

== Overview ==
Many times, particularly when things aren't working as expected, you may find yourself restricted to a console-only (non-X or non-graphical) session. If you have networking running, you can still access on-line support tools through your console. This tutorial shows you how to:

* Use virtual consoles to increase the number of consoles you can use simultaneously;
* Use the &lt;tt&gt;screen&lt;/tt&gt; to create sessions that are persistant even after you close the console;
* Use &lt;tt&gt;irssi&lt;/tt&gt; to access the irc network and ##slackware on irc.freenode.org;
* Use &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; to access HTTP (web) server information;
* Use &lt;tt&gt;lynx&lt;/tt&gt; to pastebin a file when you need to send configuration information to an IRC channel, and;
* Use &lt;tt&gt;wget&lt;/tt&gt; to download a pastebin file to your local machine.

== Prerequisites ==
This tutorial will assume you are comfortable with the following concepts:
* Basic file management operations (&lt;tt&gt;cp&lt;/tt&gt;,&lt;tt&gt;rm&lt;/tt&gt;,etc);
* Using a console-based file editor (&lt;tt&gt;pico&lt;/tt&gt;,&lt;tt&gt;vi&lt;/tt&gt;,etc);

== Virtual Consoles ==
One of the handiest features if you're relegated to working from a console is the use of virtual consoles. This allows you to start multiple login sessions from the same console keyboard, mouse, and monitor. That way, you can have one virtual console logged into IRC so you can talk to ##slackware, one that you can use for web access, and another that you can use to test commands. 

Using virtual consoles is easy. Simply hold the ALT key while hitting the F2 key (ALT+F2) to switch to the second console. To switch back to the first console, use ALT+F1. You have virtual consoles available on F1 through F6.

If you're using X, you can still access one of the virtual consoles, which is useful if X is hung up for some reason (especially if X won't restart using ctrl+alt+backspace). To access this virtual console, hold CTRL *and* ALT while pressing the F6 key (CTRL+ALT+F6). To switch back to your X session, press CTRL+ALT+F7.

== Using &lt;tt&gt;screen&lt;/tt&gt; ==
The &lt;tt&gt;screen&lt;/tt&gt; utility allows you to start a console session which is persistent across login and logout. This is useful, for example, if you're using IRC -- perhaps you want to stay logged into your IRC channel even after you have logged out of your console session. The concept is straightforward: when you run screen, it gives you a bash prompt "inside of" the screen session. At this new bash prompt you can start your IRC session. When you wish to log out, you can detach from screen and log out -- but screen continues to run in the background. When you log back in, you can re-attach to your screen session and resume your IRC session.

Visit [[Screen|this page]] for the specifics on attaching and detaching sessions using &lt;tt&gt;screen&lt;/tt&gt;.

== Using &lt;tt&gt;irssi&lt;/tt&gt; ==
The &lt;tt&gt;irssi&lt;/tt&gt; program is a console-based IRC client. Using irssi, you can access the ##slackware IRC channel on irc.freenode.net. 

*WARNING*: Whenever you are using any type of IRC client on any type of machine, make sure that you are not doing so as the superuser (root). Doing so is a security risk, since if for some reason an attacker is able to successfully attack your IRC client, the attacker will have root access to your machine.

To access the ##slackware channel on irc.freenode.org using &lt;tt&gt;irssi&lt;/tt&gt;, perform the following steps:

* Start irssi:
 user@slackbox:~$ irssi
* At the (status) prompt, connect to irc.freenode.org:
 [(status)] /connect irc.freenode.org
* Once connected, set your nick:
 [(status)] /nick Myl33tNick
* Join the ##slackware channel:
 [(status)] /join ##slackware
* To exit irssi:
 [(status)] /quit
Visit [[Irssi|this page]] for more information on using irssi.

== Using &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; ==
You can use &lt;tt&gt;lynx&lt;/tt&gt; and &lt;tt&gt;wget&lt;/tt&gt; to access http (web) servers from your console session. Lynx allows you to access a web site interactively, much like using a graphical browser such as Firefox, but through a text-only console session. &lt;tt&gt;Wget&lt;/tt&gt; allows you to retrieve documents from web servers non-interactively, which is handy when you need to retrieve a certain document (say a tarball or a script file) from a web server in a very quick way.

To start using lynx, from a bash prompt simply type:
 user@slackbox:~$ lynx "http://www.slackware.com"
to visit Slackware's official website. To exit lynx, use CTRL+C. In the example above, the double-quotes are not strictly required. However, many URLs contain characters which have special meaning to the bash interpreter (such as the ampersand), and the double-quotes stop bash from trying to interpret those characters.

Although wget has a wide array of options (visit man wget sometime), its basic use is very simple. For example, to download the latest kernel patch (as of this writing) from kernel.org, simply do:
 user@slackbox:~$ wget "http://www.kernel.org/pub/linux/kernel/v2.6/patch-2.6.20.3.bz2"
Again, the quotes here are not strictly required for this URL, but are required for certain URLs. It's good to get in the habit of always double-quoting URLs from a bash prompt.

== Using &lt;tt&gt;lynx&lt;/tt&gt; in conjuction with pastebin ==
You may find yourself on ##slackware and another channel member may ask you to "pastebin" information to them. The purpose of pastebin is so that you can share technical information (for example, the contents of a configuration file) with the other channel members, without pasting that information directly into IRC itself (which is generally disliked by other IRC members and will get you banned if you try it). "Pastebin" is a generic term for a web site which offers this sort of service. There are many pastebin sites out there; for simplicity's sake, this tutorial uses [http://pastebin.ca pastebin.ca].

You can use lynx to access the pastebin site, but what if you need to pastebin the contents of an entire file? You can do this using the &lt;tt&gt;lynx&lt;/tt&gt; program:
* use &lt;tt&gt;lynx&lt;/tt&gt; to access pastebin.ca:
 user@slackbox:~$ lynx "http://pastebin.ca"
* Page down until you see the large textbox area, move your cursor to the first line (where you see the X below):
 Create a New Pastebin Post
 
    Welcome  to the Pastebin. For information on what this is, take a look
    at  the  What  is This? page. You may also want to see the most recent
    post to the pastebin.
  
    Please enter your new post below (or upload a file instead):
 
 paste below
 
 
    X_____________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
    ______________________________________________________________________
 (NORMAL LINK)   Use right-arrow or &lt;return&gt; to activate.
   Arrow keys: Up and Down to move.  Right to follow a link; Left to go back.
  H)elp O)ptions P)rint G)o M)ain screen Q)uit /=search [delete]=history list
* Press Ctrl+X, then i, and enter the location of the file you wish to pastebin.
  Enter a filename: /etc/ssh/sshd_config
* Page down until you see the "Submit Post" link, select it (it will turn yellow), and press the enter key.
* On the next page, scroll down until you find the URL to your pastebin file. It will look something like this:
 paste added to database
 
   Your  paste  has  been  accepted an added to the database. You will be
   redirected to it momentarily. The URL for it is:
 
   http://pastebin.ca/398871
 
   You may use that URL for referencing your submission from now on.
* Give this URL to the person who requested the information on IRC.

== Using &lt;tt&gt;wget&lt;/tt&gt; in conjunction with pastebin ==
Every pastebin site should have a way to request any pastebin file in "raw" format, meaning without the added HTML code so that the pastebin information displays properly in a browser. Accessing the "raw" format means you can access exactly what was pastebinned, with nothing else added. This is useful if you want to download a configuration file from pastebin. If you know the raw URL of the pastebin page you need, you can use wget to retrieve the file.
* Find the raw URL associated with the pastebin page. For pastebin.ca, this is just the regular URL with an extra "raw" directory inserted. For example, if your regular pastebin url is http://pastebin.ca/398871, then the raw version is at http://pastebin.ca/raw/398871.
* use wget to retrieve the file, but rename it so that it's not named 398871 (in this example, the output is named "this.cfg"):
 user@slackbox:~$ wget "http://pastebin.ca/raw/398871" -O this.cfg
You'll find you'll use commands like wget over and over again this way, even when you have access to a fully graphical web browser.
[[Category:Tutorials]]</text>
    <sha1>efcf19613488e16a82ad6d20051d7720972495f4</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>ACPI Modules</title>
  <ns>0</ns>
  <id>64</id>
  <revision>
    <id>382</id>
    <parentid>85</parentid>
    <timestamp>2010-07-22T07:14:18Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="648" xml:space="preserve">[[Category:Tips]]

These are the kernel modules that need to be loaded in order to use some of the features of ACPI.

* ac - AC adapter information
* battery - Battery information
* fan
* button - Enables accesing info about ACPI-controlled buttons (like the Power button and the LID button)
* video
* thermal - Driver for the Thermal Zone (/proc/acpi/thermal_zone)
* processor - Loads the ACPI processor driver (/proc/acpi/processor)
* container - Loads the ACPI container driver
* vendor-specific drivers (eg acer_acpi, [http://www.thinkwiki.org/wiki/Thinkpad-acpi thinkpad-acpi])
* [http://www.college-paper.org/custom-essay.html college essays]</text>
    <sha1>e92f34fb9325fbde48275aa04ab593c9145e352d</sha1>
  </revision>
  <revision>
    <id>383</id>
    <parentid>382</parentid>
    <timestamp>2010-07-22T08:43:49Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Meghan|Meghan]] ([[User talk:Meghan|Talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="582" xml:space="preserve">[[Category:Tips]]

These are the kernel modules that need to be loaded in order to use some of the features of ACPI.

* ac - AC adapter information
* battery - Battery information
* fan
* button - Enables accesing info about ACPI-controlled buttons (like the Power button and the LID button)
* video
* thermal - Driver for the Thermal Zone (/proc/acpi/thermal_zone)
* processor - Loads the ACPI processor driver (/proc/acpi/processor)
* container - Loads the ACPI container driver
* vendor-specific drivers (eg acer_acpi, [http://www.thinkwiki.org/wiki/Thinkpad-acpi thinkpad-acpi])</text>
    <sha1>a1f62a5b9a0a02eca3d6d924c4076b0ae8077c45</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>SlackRoll Tutorial</title>
  <ns>0</ns>
  <id>157</id>
  <revision>
    <id>384</id>
    <parentid>344</parentid>
    <timestamp>2010-07-23T10:50:35Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17020" xml:space="preserve">&lt;strong&gt;SlackRoll&lt;/strong&gt; is a package or update manager for Slackware Linux. Part of this tutorial has been taken from its [http://rg3.github.com/slackroll/ official webpage] and FAQ. SlackRoll's defining points:

* Its internal mechanism based on package states.
* Like &lt;em&gt;slackpkg&lt;/em&gt;, SlackRoll only works with official mirrors, meaning that to keep third party packages up to date you need to perform the task by hand (recommended practice, using SlackBuild scripts) or use a second different tool.
* It does not try to compare package version numbers to decide if a package should be upgraded or not.
* Partly as a consequence of the previous point, it has no known flaws detecting package updates (including reverts), new packages, removed packages, third party packages getting an official version and blacklisted packages (&lt;em&gt;frozen&lt;/em&gt; in its terminology) being removed.
* It has a broad range of operations and features.
* It attempts to be fast. Most internal operations like listing available upgrades usually take less than one second on a modern computer.


= Installation =

== Requirements ==

* Python 2.4 or later (provided by package &lt;em&gt;python&lt;/em&gt; starting with Slackware 10.1).
* GnuPG (provided by package &lt;em&gt;gnupg&lt;/em&gt; or &lt;em&gt;gnupg2&lt;/em&gt;).
* Vim (provided by package &lt;em&gt;vim&lt;/em&gt;).
* A pager which is &lt;em&gt;less&lt;/em&gt; by default (provided by package &lt;em&gt;less&lt;/em&gt;).

== Procedure ==

Download the SlackRoll package from the [http://github.com/rg3/slackroll/downloads project download page] and install it in your system using &lt;tt&gt;installpkg&lt;/tt&gt;.

= Background Information =

The majority of SlackRoll commands that receive a list of packages expect only the package names (&lt;em&gt;foo&lt;/em&gt; as opposed to &lt;em&gt;foo-1.1-i486-3.tgz&lt;/em&gt;). Some of them also allow using a specific version, but they are the exception.

SlackRoll creates a persistent database of packages in your hard drive. Each package is in one of several possible states. Part of the initial configuration consists in deciding which states some of your packages will have. There are two types of states: states to avoid (temporary states) and normal states. When the remote Slackware official tree is updated, SlackRoll may put some packages in temporary states. By upgrading, installing, removing and marking packages your objective is to correct those packages and put them in a normal state.

== States to Avoid ==

=== New ===

New packages are packages present in the remote tree that weren't present before. You should decide if you want to install them or mark them as not installed.

=== Outdated ===

Outdated packages are present in your system, but the version you have does not match any relevant one in the remote tree. You should upgrade these packages.

=== Unavailable ===

Unavailable packages are packages present in your system. Previously, they probably existed in the remote tree, but now they do not seem to be available for downloading and installing. You should decide if you want to remove them or mark them as foreign.

== Normal States ==

=== Installed ===

Installed packages are very common. They are present in your system and in the remote tree, and both versions match.

=== Not Installed ===

Not installed packages are also very common. They are present in the remote tree but not in your system. They can be downloaded and installed if you want.

=== Foreign ===

Foreign packages are packages present in your system but not in the remote tree. However, unlike unavailable packages, they are supposed to be present in your system. No package will enter this state automatically. Only the ones you mark. It's usually reserved for third party packages and packages you build yourself. It's worth noting that if a foreign package ever appears in the remote official tree, it will be marked as installed or, probably, outdated. Thus, SlackRoll will give priority to the new official package over yours. If you still want to use your own build, mark it as frozen.

=== Frozen ===

Frozen packages are present in your system and in the remote tree. Your version may or may not match the ones from the remote tree, but SlackRoll will not tell you they need to be upgraded. No package will enter this state automatically. It's usually reserved for packages that shouldn't be upgraded automatically or ever (&lt;em&gt;aaa_elflibs&lt;/em&gt;, kernels, etc) and sometimes for customized versions of official packages. It's also worth mentioning that a frozen package will be moved to unavailable if it disappears from the remote tree. It that happens and you want to continue using it, you'll need to mark it as foreign.

= Initial Configuration =

Word of warning: it's highly recommended to do the initial configuration from an up-to-date and controlled system. This will avoid confusion and helps preventing mistakes setting the initial package states.

== Preparing Your System ==

Choose a Slackware mirror for your Slackware version. Use the &lt;em&gt;set-mirror&lt;/em&gt; operation to select one mirror. SlackRoll can work with stable trees as well as the &lt;em&gt;current&lt;/em&gt; tree. Example:

  # slackroll set-mirror 'http://slackware.example.org/slackware-current/'

Do not forget to include the trailing slash in the mirror URL. Import, to your keyring, the GnuPG key used to sign the official Slackware packages. This key can be found in Slackware CDs and DVDs as the file GPG-KEY, and you can import the key to your keyring using the command &lt;em&gt;gpg --import&lt;/em&gt;, but SlackRoll is able to download the key from the mirror and importing it automatically, if you trust the mirror.

  # slackroll import-key

Finally, retrieve the mirror information for the first time. This will download a few metadata files, and this is what you need to do when you're going to handle a new round of updates.

  # slackroll update

== Going Over Package States for The First Time ==

When you run SlackRoll for the first times, it will put every remote package not present in your system in the state New. When your system is up to date and under control, you can blindly mark every new package as not installed with the following command:

  # slackroll new-not-installed

Any third party package present in your system will be put in the state Unavailable. When your system is up to date and under control you can blindly mark all unavailable packages as foreign. &lt;em&gt;However&lt;/em&gt;, the number of foreign packages is usually not very high and forgetting to remove from your system a package that was removed from the remote tree is a common mistake. The Book of Best Practices would suggest that you review the list of unavailable packages once and carefully in order to detect packages that should not be present in your system. To print the list run:

  # slackroll list-unavailable

If you locate any package that needs to be removed, you can remove them using &lt;em&gt;removepkg&lt;/em&gt; or the &lt;em&gt;remove&lt;/em&gt; operation. The later has additional functionality so it's recommended:

  # slackroll remove foo bar

Now you can mark the rest as foreign packages.

  # slackroll unavailable-foreign

Finally, you probably want to mark some packages as frozen. It's usually a good idea to do this with &lt;em&gt;aaa_elflibs&lt;/em&gt;, kernel packages and others.

  # slackroll frozen aaa_elflibs foo bar

= Day to Day Usage =

Apart from the operations listed here, you can run the &lt;em&gt;help&lt;/em&gt; operation to get the full list of supported operations, along with a brief description of each one. A more detailed description can be found in the [http://wiki.github.com/rg3/slackroll/operations-guide operations guide].

== New Round of Updates ==

What to do when there is a new round of updates? The Book of Best Practices suggests taking care of different events in a specific order:

* Updates to glibc-solibs, sed and pkgtools need to be handled first, in that order.
* If there are new packages, handle them second.
* Then, it's time to upgrade outdated packages.
* If packages have been deleted from the remote tree, handle them last.

This is the correct order in 99% of the cases. SlackRoll will attempt to warn you and ask for confirmation if it detects you may be breaking this order. However, &lt;strong&gt;you&lt;/strong&gt; have the last word on what to do, so proceed with caution and don't break your system.

First, update the remote mirror information with the &lt;em&gt;update&lt;/em&gt; operation we mentioned before. New changelog entries will be saved to your hard drive. It's recommended that you take a look at the changelog at this point, using the &lt;em&gt;changelog&lt;/em&gt; operation. Then, get an overview of the events using the &lt;em&gt;list-transient&lt;/em&gt; operation, which will list the new, outdated and unavailable packages along with a big fat warning message if activity in key system packages is detected.

The best way to deal with glibc-solibs, sed and pkgtool updates is to use the &lt;em&gt;upgrade-key-packages&lt;/em&gt; operation.

  # slackroll upgrade-key-packages

You could also use the &lt;em&gt;install&lt;/em&gt; operation. Despite its name, it can be used to both install and upgrade individual packages. Let's suppose packages &lt;em&gt;glibc-solibs&lt;/em&gt; and &lt;em&gt;sed&lt;/em&gt; where updated:

  # slackroll install glibc-solibs sed

The &lt;em&gt;install&lt;/em&gt; operation is one of the few operations allowing you to pass specific package versions. It will proceed in the order you indicate, so remember to give the packages in the correct order if you use this method.

Second, you should handle new packages. You can clearly get a list of new packages with the &lt;em&gt;list-new&lt;/em&gt; operation. New packages can be installed with the &lt;em&gt;install&lt;/em&gt; operation as we just showed. When installing a remote package, SlackRoll will give you the opportunity of selecting the version to install if there are several available in the remote tree. Or, if you are not interested in installing a new package, mark it as not installed:

  # slackroll not-installed foo bar

If the package names are not enough for you to decide if you want to install it or not, you can always use the &lt;em&gt;info&lt;/em&gt; operation and SlackRoll will download and display the package info file (small &lt;em&gt;txt&lt;/em&gt; files in the remote tree). And, of course, be carefull with new libraries as they may have been included to extend the functionality of an existing package you may have installed.

The third step is taking care of outdated packages. For that, a few operations are available. &lt;em&gt;list-upgrades&lt;/em&gt; lets you see a summary of the available upgrades. You can download and install them with &lt;em&gt;upgrade&lt;/em&gt; or download them with &lt;em&gt;download-upgrades&lt;/em&gt; or even print their URLs with &lt;em&gt;urls-upgrades&lt;/em&gt;.

And, finally, review the list of unavailable packages. Be careful with unavailable packages. Sometimes you install a foreign package but forget to mark it as such in SlackRoll. To avoid that problem, it's better to install them with the &lt;em&gt;install-foreign&lt;/em&gt; operation. Individual unavailable packages can be removed with the &lt;em&gt;remove&lt;/em&gt; operation as we showed before, and also all of them at the same time with the &lt;em&gt;remove-unavailable&lt;/em&gt; operation.

== Installing and Removing Individual Packages ==

There are a few operations related to installing and getting some information about individual packages. The most common ones are &lt;em&gt;install&lt;/em&gt; to upgrade or install packages, &lt;em&gt;info&lt;/em&gt; to maybe download and display package info files, &lt;em&gt;urls&lt;/em&gt; to get a list of URLs and &lt;em&gt;remove&lt;/em&gt; to remove individual packages.

Operations that install packages let you manage &lt;em&gt;.new&lt;/em&gt; files after the installation is completed, in a similar way to &lt;em&gt;slackpkg&lt;/em&gt;. You can view the differences between the &lt;em&gt;.new&lt;/em&gt; file and its counterparts with &lt;em&gt;vimdiff&lt;/em&gt; (which provides a nice and colorized way of spotting the differences and maybe porting the old configuration to the new file), you can overwrite the old file with the &lt;em&gt;.new&lt;/em&gt; file, delete the &lt;em&gt;.new&lt;/em&gt; file directly, etc.

Additionally, removal operations also track pairs of &lt;em&gt;.new&lt;/em&gt; files and give you the opportunity of deleting configuration files that have been left behind. You are not forced to remove the files left behind, of course.

Upgrade operations will perform both tasks. First, they will let you review the &lt;em&gt;.new&lt;/em&gt; files and then they will give you the opportunity of deleting obsolete configuration files left behind.

While using &lt;em&gt;vimdiff&lt;/em&gt;, turning off syntax highlighting is recommended. &lt;em&gt;Vim&lt;/em&gt; uses colors to highlight file differences and those can interfere with syntax highlighting colors, making text invisible or hard to read. Syntax highlighting can be turned off temporarily by using "&lt;tt&gt;:syntax off&lt;/tt&gt;" in command mode, or you can disable it permanently putting "&lt;tt&gt;syntax off&lt;/tt&gt;" in your &lt;tt&gt;~/.vimrc&lt;/tt&gt; file (noting that usually you run SlackRoll as the superuser).

== Managing Customized Versions of Official Packages ==

There are at least three ways of dealing with customized versions of official packages. These are custom versions or compilations of packages present in the remote official tree. They are normally used to add or remove features, or activate or apply patches that are disabled by default. For example, if you want to activate the &lt;em&gt;freetype&lt;/em&gt; bytecode interpreter, you need to rebuild that package.

The simplest way of dealing with these packages is to give them the same name and version as the official packages. When they are upgraded in the remote tree, however, SlackRoll will want to upgrade them. You can mark them as frozen before upgrading and only unfreeze them after you have rebuilt the new version, if you want to avoid SlackRoll replacing them with the new official version.

Second, you can give them the same name and version as the official package, &lt;strong&gt;but&lt;/strong&gt; keep them frozen all the time. How would you know then if they need to be rebuilt? With the &lt;em&gt;list-outdated-frozen&lt;/em&gt; operation. Take into account the information given by &lt;em&gt;list-outdated-frozen&lt;/em&gt; is not reflected by any other command. Specifically, it's not reflected as part of &lt;em&gt;list-transient&lt;/em&gt; and friends.

Third, you can give them a name or version different to the official package. Typically this means adding a custom build suffix and marking the package as frozen. How would you know if you need to rebuild it? Paying attention to the changelog specifically searching for upgrades in those packages and also using the &lt;em&gt;list-versions&lt;/em&gt; operation, that lets you view the different known versions of a package, including local and remote ones.

== Maintenance ==

SlackRoll barely requires maintenance. It keeps all downloaded packages in its package cache, located in the &lt;em&gt;/var/slackroll/packages&lt;/em&gt; directory. When downloading files, it keeps them in a temporary directory until they're fully downloaded. If you want to remove every downloaded package, you can simply perform &lt;code&gt;slackroll erase-cache&lt;/code&gt;. There is, however, a &lt;em&gt;clean-cache&lt;/em&gt; operation which does &lt;strong&gt;not&lt;/strong&gt; remove every downloaded package, but only those that are no longer present in the remote tree. Running that operation from time to time keeps your package cache sane and controlled. It may also be a good idea to delete the temporary directory contents from time to time, with &lt;code&gt;slackroll erase-tmp&lt;/code&gt;, but it should be empty unless you interrupt SlackRoll while downloading stuff and never attempt to complete the download.

== Other Operations ==

If you run the &lt;em&gt;help&lt;/em&gt; operation you will see SlackRoll has many other operations, including operations to list packages by state, list local packages, list remote packages and list all known packages. It has operations to put packages in specific states and checking the state of packages. You can also download, install, display info or remove new or unavailable packages or packages with a matching path (like &lt;em&gt;/slackware/kde/&lt;/em&gt;). Finally, there are search operations, to search for packages by name or path, search for files in your local system (like running &lt;em&gt;grep&lt;/em&gt; on the contents of &lt;em&gt;/var/log/packages&lt;/em&gt;), query the Slackware Package Browser, and finally a few very slow but sometimes useful operations to search for broken symlinks under a specific hierarchy and the same for orphan files (files not belonging to any package), as well as searching for missing files.

As a general rule, every operation either does not accept arguments or allows a list of them. Operations accepting packages as arguments expect the package name only unless the help text mentions that they also accept specific package versions. Some operations need regular expressions. For the most part they have the same syntax as they have in &lt;em&gt;grep&lt;/em&gt; or &lt;em&gt;Perl&lt;/em&gt;, but you can read the [http://docs.python.org/lib/re-syntax.html Python regular expressions syntax reference] if you want to perform an unusually complex search.

[[Category:Tutorials]]

==Related Links==

[http://www.cellulite.co.uk/ '''cellulite''']</text>
    <sha1>9692a3579942fa63a5c2b79239e42c7e13fd38a5</sha1>
  </revision>
  <revision>
    <id>385</id>
    <parentid>384</parentid>
    <timestamp>2010-07-23T19:38:20Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Jheena789|Jheena789]] ([[User talk:Jheena789|Talk]]) to last revision by [[User:Johnbristol|Johnbristol]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16954" xml:space="preserve">&lt;strong&gt;SlackRoll&lt;/strong&gt; is a package or update manager for Slackware Linux. Part of this tutorial has been taken from its [http://rg3.github.com/slackroll/ official webpage] and FAQ. SlackRoll's defining points:

* Its internal mechanism based on package states.
* Like &lt;em&gt;slackpkg&lt;/em&gt;, SlackRoll only works with official mirrors, meaning that to keep third party packages up to date you need to perform the task by hand (recommended practice, using SlackBuild scripts) or use a second different tool.
* It does not try to compare package version numbers to decide if a package should be upgraded or not.
* Partly as a consequence of the previous point, it has no known flaws detecting package updates (including reverts), new packages, removed packages, third party packages getting an official version and blacklisted packages (&lt;em&gt;frozen&lt;/em&gt; in its terminology) being removed.
* It has a broad range of operations and features.
* It attempts to be fast. Most internal operations like listing available upgrades usually take less than one second on a modern computer.


= Installation =

== Requirements ==

* Python 2.4 or later (provided by package &lt;em&gt;python&lt;/em&gt; starting with Slackware 10.1).
* GnuPG (provided by package &lt;em&gt;gnupg&lt;/em&gt; or &lt;em&gt;gnupg2&lt;/em&gt;).
* Vim (provided by package &lt;em&gt;vim&lt;/em&gt;).
* A pager which is &lt;em&gt;less&lt;/em&gt; by default (provided by package &lt;em&gt;less&lt;/em&gt;).

== Procedure ==

Download the SlackRoll package from the [http://github.com/rg3/slackroll/downloads project download page] and install it in your system using &lt;tt&gt;installpkg&lt;/tt&gt;.

= Background Information =

The majority of SlackRoll commands that receive a list of packages expect only the package names (&lt;em&gt;foo&lt;/em&gt; as opposed to &lt;em&gt;foo-1.1-i486-3.tgz&lt;/em&gt;). Some of them also allow using a specific version, but they are the exception.

SlackRoll creates a persistent database of packages in your hard drive. Each package is in one of several possible states. Part of the initial configuration consists in deciding which states some of your packages will have. There are two types of states: states to avoid (temporary states) and normal states. When the remote Slackware official tree is updated, SlackRoll may put some packages in temporary states. By upgrading, installing, removing and marking packages your objective is to correct those packages and put them in a normal state.

== States to Avoid ==

=== New ===

New packages are packages present in the remote tree that weren't present before. You should decide if you want to install them or mark them as not installed.

=== Outdated ===

Outdated packages are present in your system, but the version you have does not match any relevant one in the remote tree. You should upgrade these packages.

=== Unavailable ===

Unavailable packages are packages present in your system. Previously, they probably existed in the remote tree, but now they do not seem to be available for downloading and installing. You should decide if you want to remove them or mark them as foreign.

== Normal States ==

=== Installed ===

Installed packages are very common. They are present in your system and in the remote tree, and both versions match.

=== Not Installed ===

Not installed packages are also very common. They are present in the remote tree but not in your system. They can be downloaded and installed if you want.

=== Foreign ===

Foreign packages are packages present in your system but not in the remote tree. However, unlike unavailable packages, they are supposed to be present in your system. No package will enter this state automatically. Only the ones you mark. It's usually reserved for third party packages and packages you build yourself. It's worth noting that if a foreign package ever appears in the remote official tree, it will be marked as installed or, probably, outdated. Thus, SlackRoll will give priority to the new official package over yours. If you still want to use your own build, mark it as frozen.

=== Frozen ===

Frozen packages are present in your system and in the remote tree. Your version may or may not match the ones from the remote tree, but SlackRoll will not tell you they need to be upgraded. No package will enter this state automatically. It's usually reserved for packages that shouldn't be upgraded automatically or ever (&lt;em&gt;aaa_elflibs&lt;/em&gt;, kernels, etc) and sometimes for customized versions of official packages. It's also worth mentioning that a frozen package will be moved to unavailable if it disappears from the remote tree. It that happens and you want to continue using it, you'll need to mark it as foreign.

= Initial Configuration =

Word of warning: it's highly recommended to do the initial configuration from an up-to-date and controlled system. This will avoid confusion and helps preventing mistakes setting the initial package states.

== Preparing Your System ==

Choose a Slackware mirror for your Slackware version. Use the &lt;em&gt;set-mirror&lt;/em&gt; operation to select one mirror. SlackRoll can work with stable trees as well as the &lt;em&gt;current&lt;/em&gt; tree. Example:

  # slackroll set-mirror 'http://slackware.example.org/slackware-current/'

Do not forget to include the trailing slash in the mirror URL. Import, to your keyring, the GnuPG key used to sign the official Slackware packages. This key can be found in Slackware CDs and DVDs as the file GPG-KEY, and you can import the key to your keyring using the command &lt;em&gt;gpg --import&lt;/em&gt;, but SlackRoll is able to download the key from the mirror and importing it automatically, if you trust the mirror.

  # slackroll import-key

Finally, retrieve the mirror information for the first time. This will download a few metadata files, and this is what you need to do when you're going to handle a new round of updates.

  # slackroll update

== Going Over Package States for The First Time ==

When you run SlackRoll for the first times, it will put every remote package not present in your system in the state New. When your system is up to date and under control, you can blindly mark every new package as not installed with the following command:

  # slackroll new-not-installed

Any third party package present in your system will be put in the state Unavailable. When your system is up to date and under control you can blindly mark all unavailable packages as foreign. &lt;em&gt;However&lt;/em&gt;, the number of foreign packages is usually not very high and forgetting to remove from your system a package that was removed from the remote tree is a common mistake. The Book of Best Practices would suggest that you review the list of unavailable packages once and carefully in order to detect packages that should not be present in your system. To print the list run:

  # slackroll list-unavailable

If you locate any package that needs to be removed, you can remove them using &lt;em&gt;removepkg&lt;/em&gt; or the &lt;em&gt;remove&lt;/em&gt; operation. The later has additional functionality so it's recommended:

  # slackroll remove foo bar

Now you can mark the rest as foreign packages.

  # slackroll unavailable-foreign

Finally, you probably want to mark some packages as frozen. It's usually a good idea to do this with &lt;em&gt;aaa_elflibs&lt;/em&gt;, kernel packages and others.

  # slackroll frozen aaa_elflibs foo bar

= Day to Day Usage =

Apart from the operations listed here, you can run the &lt;em&gt;help&lt;/em&gt; operation to get the full list of supported operations, along with a brief description of each one. A more detailed description can be found in the [http://wiki.github.com/rg3/slackroll/operations-guide operations guide].

== New Round of Updates ==

What to do when there is a new round of updates? The Book of Best Practices suggests taking care of different events in a specific order:

* Updates to glibc-solibs, sed and pkgtools need to be handled first, in that order.
* If there are new packages, handle them second.
* Then, it's time to upgrade outdated packages.
* If packages have been deleted from the remote tree, handle them last.

This is the correct order in 99% of the cases. SlackRoll will attempt to warn you and ask for confirmation if it detects you may be breaking this order. However, &lt;strong&gt;you&lt;/strong&gt; have the last word on what to do, so proceed with caution and don't break your system.

First, update the remote mirror information with the &lt;em&gt;update&lt;/em&gt; operation we mentioned before. New changelog entries will be saved to your hard drive. It's recommended that you take a look at the changelog at this point, using the &lt;em&gt;changelog&lt;/em&gt; operation. Then, get an overview of the events using the &lt;em&gt;list-transient&lt;/em&gt; operation, which will list the new, outdated and unavailable packages along with a big fat warning message if activity in key system packages is detected.

The best way to deal with glibc-solibs, sed and pkgtool updates is to use the &lt;em&gt;upgrade-key-packages&lt;/em&gt; operation.

  # slackroll upgrade-key-packages

You could also use the &lt;em&gt;install&lt;/em&gt; operation. Despite its name, it can be used to both install and upgrade individual packages. Let's suppose packages &lt;em&gt;glibc-solibs&lt;/em&gt; and &lt;em&gt;sed&lt;/em&gt; where updated:

  # slackroll install glibc-solibs sed

The &lt;em&gt;install&lt;/em&gt; operation is one of the few operations allowing you to pass specific package versions. It will proceed in the order you indicate, so remember to give the packages in the correct order if you use this method.

Second, you should handle new packages. You can clearly get a list of new packages with the &lt;em&gt;list-new&lt;/em&gt; operation. New packages can be installed with the &lt;em&gt;install&lt;/em&gt; operation as we just showed. When installing a remote package, SlackRoll will give you the opportunity of selecting the version to install if there are several available in the remote tree. Or, if you are not interested in installing a new package, mark it as not installed:

  # slackroll not-installed foo bar

If the package names are not enough for you to decide if you want to install it or not, you can always use the &lt;em&gt;info&lt;/em&gt; operation and SlackRoll will download and display the package info file (small &lt;em&gt;txt&lt;/em&gt; files in the remote tree). And, of course, be carefull with new libraries as they may have been included to extend the functionality of an existing package you may have installed.

The third step is taking care of outdated packages. For that, a few operations are available. &lt;em&gt;list-upgrades&lt;/em&gt; lets you see a summary of the available upgrades. You can download and install them with &lt;em&gt;upgrade&lt;/em&gt; or download them with &lt;em&gt;download-upgrades&lt;/em&gt; or even print their URLs with &lt;em&gt;urls-upgrades&lt;/em&gt;.

And, finally, review the list of unavailable packages. Be careful with unavailable packages. Sometimes you install a foreign package but forget to mark it as such in SlackRoll. To avoid that problem, it's better to install them with the &lt;em&gt;install-foreign&lt;/em&gt; operation. Individual unavailable packages can be removed with the &lt;em&gt;remove&lt;/em&gt; operation as we showed before, and also all of them at the same time with the &lt;em&gt;remove-unavailable&lt;/em&gt; operation.

== Installing and Removing Individual Packages ==

There are a few operations related to installing and getting some information about individual packages. The most common ones are &lt;em&gt;install&lt;/em&gt; to upgrade or install packages, &lt;em&gt;info&lt;/em&gt; to maybe download and display package info files, &lt;em&gt;urls&lt;/em&gt; to get a list of URLs and &lt;em&gt;remove&lt;/em&gt; to remove individual packages.

Operations that install packages let you manage &lt;em&gt;.new&lt;/em&gt; files after the installation is completed, in a similar way to &lt;em&gt;slackpkg&lt;/em&gt;. You can view the differences between the &lt;em&gt;.new&lt;/em&gt; file and its counterparts with &lt;em&gt;vimdiff&lt;/em&gt; (which provides a nice and colorized way of spotting the differences and maybe porting the old configuration to the new file), you can overwrite the old file with the &lt;em&gt;.new&lt;/em&gt; file, delete the &lt;em&gt;.new&lt;/em&gt; file directly, etc.

Additionally, removal operations also track pairs of &lt;em&gt;.new&lt;/em&gt; files and give you the opportunity of deleting configuration files that have been left behind. You are not forced to remove the files left behind, of course.

Upgrade operations will perform both tasks. First, they will let you review the &lt;em&gt;.new&lt;/em&gt; files and then they will give you the opportunity of deleting obsolete configuration files left behind.

While using &lt;em&gt;vimdiff&lt;/em&gt;, turning off syntax highlighting is recommended. &lt;em&gt;Vim&lt;/em&gt; uses colors to highlight file differences and those can interfere with syntax highlighting colors, making text invisible or hard to read. Syntax highlighting can be turned off temporarily by using "&lt;tt&gt;:syntax off&lt;/tt&gt;" in command mode, or you can disable it permanently putting "&lt;tt&gt;syntax off&lt;/tt&gt;" in your &lt;tt&gt;~/.vimrc&lt;/tt&gt; file (noting that usually you run SlackRoll as the superuser).

== Managing Customized Versions of Official Packages ==

There are at least three ways of dealing with customized versions of official packages. These are custom versions or compilations of packages present in the remote official tree. They are normally used to add or remove features, or activate or apply patches that are disabled by default. For example, if you want to activate the &lt;em&gt;freetype&lt;/em&gt; bytecode interpreter, you need to rebuild that package.

The simplest way of dealing with these packages is to give them the same name and version as the official packages. When they are upgraded in the remote tree, however, SlackRoll will want to upgrade them. You can mark them as frozen before upgrading and only unfreeze them after you have rebuilt the new version, if you want to avoid SlackRoll replacing them with the new official version.

Second, you can give them the same name and version as the official package, &lt;strong&gt;but&lt;/strong&gt; keep them frozen all the time. How would you know then if they need to be rebuilt? With the &lt;em&gt;list-outdated-frozen&lt;/em&gt; operation. Take into account the information given by &lt;em&gt;list-outdated-frozen&lt;/em&gt; is not reflected by any other command. Specifically, it's not reflected as part of &lt;em&gt;list-transient&lt;/em&gt; and friends.

Third, you can give them a name or version different to the official package. Typically this means adding a custom build suffix and marking the package as frozen. How would you know if you need to rebuild it? Paying attention to the changelog specifically searching for upgrades in those packages and also using the &lt;em&gt;list-versions&lt;/em&gt; operation, that lets you view the different known versions of a package, including local and remote ones.

== Maintenance ==

SlackRoll barely requires maintenance. It keeps all downloaded packages in its package cache, located in the &lt;em&gt;/var/slackroll/packages&lt;/em&gt; directory. When downloading files, it keeps them in a temporary directory until they're fully downloaded. If you want to remove every downloaded package, you can simply perform &lt;code&gt;slackroll erase-cache&lt;/code&gt;. There is, however, a &lt;em&gt;clean-cache&lt;/em&gt; operation which does &lt;strong&gt;not&lt;/strong&gt; remove every downloaded package, but only those that are no longer present in the remote tree. Running that operation from time to time keeps your package cache sane and controlled. It may also be a good idea to delete the temporary directory contents from time to time, with &lt;code&gt;slackroll erase-tmp&lt;/code&gt;, but it should be empty unless you interrupt SlackRoll while downloading stuff and never attempt to complete the download.

== Other Operations ==

If you run the &lt;em&gt;help&lt;/em&gt; operation you will see SlackRoll has many other operations, including operations to list packages by state, list local packages, list remote packages and list all known packages. It has operations to put packages in specific states and checking the state of packages. You can also download, install, display info or remove new or unavailable packages or packages with a matching path (like &lt;em&gt;/slackware/kde/&lt;/em&gt;). Finally, there are search operations, to search for packages by name or path, search for files in your local system (like running &lt;em&gt;grep&lt;/em&gt; on the contents of &lt;em&gt;/var/log/packages&lt;/em&gt;), query the Slackware Package Browser, and finally a few very slow but sometimes useful operations to search for broken symlinks under a specific hierarchy and the same for orphan files (files not belonging to any package), as well as searching for missing files.

As a general rule, every operation either does not accept arguments or allows a list of them. Operations accepting packages as arguments expect the package name only unless the help text mentions that they also accept specific package versions. Some operations need regular expressions. For the most part they have the same syntax as they have in &lt;em&gt;grep&lt;/em&gt; or &lt;em&gt;Perl&lt;/em&gt;, but you can read the [http://docs.python.org/lib/re-syntax.html Python regular expressions syntax reference] if you want to perform an unusually complex search.

[[Category:Tutorials]]</text>
    <sha1>bb5d923e18915f5fde77baf9bd05011095b6308d</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Kernel-packaging</title>
  <ns>0</ns>
  <id>213</id>
  <revision>
    <id>386</id>
    <parentid>342</parentid>
    <timestamp>2010-07-25T19:42:37Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Making the Package */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7880" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

   #!/bin/sh
   # Slackware build script for kernel and modules
   #
   # Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
   # All rights reserved.
   #
   # Redistribution and use of this script, with or without modification, is
   # permitted provided that the following conditions are met:
   #
   # 1. Redistributions of this script must retain the above copyright
   #    notice, this list of conditions and the following disclaimer.
   #
   # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
   # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
   # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
   # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
   # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
   # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
   # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
   # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
   # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
   # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
   # 
   # Notes:
   # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
   # have problems.
   # Do not omit setting localname in .config.
   
   source .config
   LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
   KARCH=${ARCH:-i486}
   ARCH=x86
   MODULELIST=modules.order
   PRGNAM=kernel
   VERSION=${VERSION:-2.6.29.6}
   BUILD=${BUILD:-1}
   TAG=${TAG:-_daw}
   OUTPUT=${TMP:-/tmp}
   PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
   MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
   
   set -e
 
   rm -rf $PKG 
   
   make
   
   for i in $(cat $MODULELIST | sed "s#^kernel/##")
   do
      mkdir -p $MODDDIR/$(dirname $i)
      install -m 644 -v $i $MODDDIR/$(dirname $i)
   done
   
   mkdir -p $PKG/boot
   cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
   cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
   cp .config $PKG/boot/config-$VERSION-$LOCALNAME
   
   mkdir $PKG/install
   
   cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
   fi
    
   ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
   ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
   ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
   ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
   EOF
   
   cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
   # HOW TO EDIT THIS FILE:
   # The "handy ruler" below makes it easier to edit a package description.  Line
   # up the first '|' above the ':' following the base package name, and the '|'
   # on the right side marks the last column you can put a character in.  You must
   # make exactly 11 lines for the formatting to be correct.  It's also
   # customary to leave one space after the ':'.
 
   $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
   $PRGNAM-$LOCALNAME: kernel and modules 2.6.29.6-jabberwok
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   $PRGNAM-$LOCALNAME:
   EOF
 
   cd $PKG
   /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$LOCALNAME-$VERSION$TAG-$KARCH-$BUILD.${PKGTYPE:-tgz}

And here's a downloadable version: http://www.dawoodfall.net/slackbuilds/13.0/kernel/kernel-jabberwok.SlackBuild

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>9dc128fc20b238bcb417cfc341fcb10304885601</sha1>
  </revision>
  <revision>
    <id>387</id>
    <parentid>386</parentid>
    <timestamp>2010-07-25T19:44:11Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7765" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

#!/bin/sh
# Slackware build script for kernel and modules
#
# Copyright 2009  David Woodfall &lt;dave@dawoodfall.net&gt;
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# 
# Notes: 
# You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
# have problems.
# Do not omit setting localname in .config.


source ./.config
LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
KARCH=${ARCH:-i486}
ARCH=x86
MODULELIST=modules.order
PRGNAM=kernel
VERSION=${VERSION:-2.6.29.6}
BUILD=${BUILD:-1}
TAG=${TAG:-_daw}
OUTPUT=${TMP:-/tmp}
PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME

set -e

rm -rf $PKG 

make

for i in $(cat $MODULELIST | sed "s#^kernel/##" )
do
	mkdir -p $MODDIR/$(dirname $i)
	install -m 644 -v $i $MODDIR/$(dirname $i)
	let nummods=$nummods+1
done

mkdir -p $PKG/install

cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
## Taken from stock modules package
if [ -x sbin/depmod ]; then
  chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
fi

( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
EOF

cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
# HOW TO EDIT THIS FILE:
# The "handy ruler" below makes it easier to edit a package description.  Line
# up the first '|' above the ':' following the base package name, and the '|'
# on the right side marks the last column you can put a character in.  You must
# make exactly 11 lines for the formatting to be correct.  It's also
# customary to leave one space after the ':'.

$PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
$PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME: Jabberwokky type kernel!
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
$PRGNAM-$LOCALNAME:
EOF

mkdir -p $PKG/boot

cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
cp .config $PKG/boot/config-$VERSION-$LOCALNAME

ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')

cd $PKG

PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}

/sbin/makepkg -l y -c n $PACKAGE

echo -ne '\e[01;34m'
printf "$nummods Modules Built\n"
printf "Kernel Size: $ksize\n"
printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
echo -ne '\e[m\017'

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>25fc3974e980411e31b7e1791cea49a289e996df</sha1>
  </revision>
  <revision>
    <id>388</id>
    <parentid>387</parentid>
    <timestamp>2010-07-25T19:52:39Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8217" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    KARCH=${ARCH:-i486}
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(cat $MODULELIST | sed "s#^kernel/##" )
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>ca1b0e453f41752fbead1c21f042110d98758f8c</sha1>
  </revision>
  <revision>
    <id>389</id>
    <parentid>388</parentid>
    <timestamp>2010-07-25T20:03:57Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8419" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]

*Note2: I will be assuming x86 here, but if anyone wants to contribute some notes on x86_64 until I can get a machine setup, please do.

== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    if [ -z "$ARCH" ]; then
      case "$( uname -m )" in
        i?86) ARCH=i486 ;;                      
        arm*) ARCH=arm ;;                       
           *) ARCH=$( uname -m ) ;;
      esac
    fi
    KARCH=$ARCH
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(cat $MODULELIST | sed "s#^kernel/##" )
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>3da38731c8d102c5ac10d14868161e600c2a81fe</sha1>
  </revision>
  <revision>
    <id>390</id>
    <parentid>389</parentid>
    <timestamp>2010-07-25T20:07:37Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>/* Creating a Custom Package of Kernel and Modules */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8283" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]


== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    if [ -z "$ARCH" ]; then
      case "$( uname -m )" in
        i?86) ARCH=i486 ;;                      
        arm*) ARCH=arm ;;                       
           *) ARCH=$( uname -m ) ;;
      esac
    fi
    KARCH=$ARCH
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(cat $MODULELIST | sed "s#^kernel/##" )
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>1b23ba30f539c82c6fec8f58cefd7be72052b93c</sha1>
  </revision>
  <revision>
    <id>391</id>
    <parentid>390</parentid>
    <timestamp>2010-07-25T20:08:30Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8362" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]


== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(cat modules.order | sed "s#^kernel/##")
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    if [ -z "$ARCH" ]; then
      case "$( uname -m )" in
        i?86) ARCH=i486 ;;                      
        arm*) ARCH=arm ;;                       
           *) ARCH=$( uname -m ) ;;
      esac
    fi
    KARCH=$ARCH
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(cat $MODULELIST | sed "s#^kernel/##" )
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>3815c975fba8351ca8dc0134a9d916e962be74c5</sha1>
  </revision>
  <revision>
    <id>399</id>
    <parentid>391</parentid>
    <timestamp>2010-08-16T22:01:10Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Installing Modules and Kernel to our Package Directory */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8356" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]


== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(sed "s#^kernel/##" modules.order)
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    if [ -z "$ARCH" ]; then
      case "$( uname -m )" in
        i?86) ARCH=i486 ;;                      
        arm*) ARCH=arm ;;                       
           *) ARCH=$( uname -m ) ;;
      esac
    fi
    KARCH=$ARCH
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(cat $MODULELIST | sed "s#^kernel/##" )
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>03403ba08b5ea4c609287459d86a2a645ebecb61</sha1>
  </revision>
  <revision>
    <id>400</id>
    <parentid>399</parentid>
    <timestamp>2010-08-16T22:04:03Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Little Automation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8349" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]


== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(sed "s#^kernel/##" modules.order)
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    if [ -z "$ARCH" ]; then
      case "$( uname -m )" in
        i?86) ARCH=i486 ;;                      
        arm*) ARCH=arm ;;                       
           *) ARCH=$( uname -m ) ;;
      esac
    fi
    KARCH=$ARCH
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(sed "s#^kernel/##" $MODULELIST)
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>b0ea2d79b51652fa2b81632457e25973fa068c69</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Kernel Checklist</title>
  <ns>0</ns>
  <id>101</id>
  <revision>
    <id>392</id>
    <parentid>123</parentid>
    <timestamp>2010-07-28T00:45:20Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <comment>just fixed a couple of spelling typos</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1984" xml:space="preserve"># [&amp;radic;] Make sure the filesystem type of your root partition is compiled into the kernel. To check what your root filesystem is type "mount".
# [&amp;radic;] Check that your networking card is compiled as a module or compiled into the kernel.
# [&amp;radic;] If you are using NVIDIA video card make sure you compile the AGP as a module
# [&amp;radic;] The sound card is important for listening to music; module it, or compile it in.
# [&amp;radic;] Another important thing that people miss out is the IDE chipset. This is important because you want to enable DMA on drives, and other important speed enhancements.
# [&amp;radic;] If you are going to use a camera that requires usb mass storage compile in SCSI Generic and USB-Mass storage.
# [&amp;radic;] Compile the sysfs feature in the kernel as that is an important for /sys. It is important for the 2.6 kernel.
# [&amp;radic;] If you must have framebuffer make sure you compile it in with the appropriate things. If you get a black screen set lilo.conf to vga = normal, then mess with it later. Also for nvidia users the rivafb is broken on many cards, so do not compile it in because it effects the nvidia driver for X. So use the vesafb instead.
# [&amp;radic;] Another useful tool that i use is the .config in /proc (A must have I think)
# [&amp;radic;] ATA/ATAPI settings are also useful for people, might want to make sure your kernel has that.
# [&amp;radic;] SATA/SCSI Make SURE YOU COMPILE it into the kernel and make sure you actually compile it in. If you have a SATA or SCSI hardware.
# [&amp;radic;] Iptables modules if you are going to use iptables or make a firewall. I use modules:)
# [&amp;radic;] I always recommend that in ALSA you compile or module OSS Emulation API
# [&amp;radic;] APM or ACPI is always something you might want to enable. This is not a feature needed by the kernel but, some people might need its features.

Just a reminder that the root filesystem (SCSI/SATA/etc) should be compiled into the kernel for obvious reasons.

[[Category:Tips]]</text>
    <sha1>d0efedcf61c6df9cefb729deb09897caecee9ba9</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>393</id>
    <parentid>364</parentid>
    <timestamp>2010-07-28T23:12:30Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Updated</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3722" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>0825ec3bdcfd6cc8db77ecbd7fa92b94b1009f73</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Multilib</title>
  <ns>0</ns>
  <id>228</id>
  <revision>
    <id>396</id>
    <timestamp>2010-08-05T21:03:37Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Link to alienBOB's multilib tutorial and a detail about not using SBo packages for display drivers.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="751" xml:space="preserve">There's a good tutorial (and packages) on how to set up multilib support (32-bit programs on Slackware64) at
[http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib AlienBOB's site]. You'd do well to go there next.

''However'', as that's not complete and clear on all points, here are some details:

==Binary display drivers==

You need to reinstall binary drivers. ATI and Nvidia driver packages contain both 64bit and 32bit libraries to be maximally useful on a 64bit multilib OS. However, the slackbuild scripts available at slackbuilds.org are not up to this task, so if you already installed 64-bit binary drivers from slackbuilds.org, you should remove these and then use ATI's or Nvidia's driver installer.


[[Category:Tutorials]]</text>
    <sha1>c1907982c750d717ec701e87c90a4923a26cebc4</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>NVIDIA Graphics</title>
  <ns>0</ns>
  <id>123</id>
  <revision>
    <id>397</id>
    <parentid>146</parentid>
    <timestamp>2010-08-06T14:47:03Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <comment>Add translation section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2260" xml:space="preserve">[[Category:Hardware]]

= Introduction =

There are three main drivers for nvidia graphics card on linux, one of which is shipped with slackware:

* nv (shipped with slackware) - this provides basic 2d acceleration, not 3d
* nvidia (NVidia's proprietary driver) - this is the generally recommended driver, providing good 2d and 3d performance
* nouveau - an attempt to reverse-engineer the nvidia driver; not particular usable or stable

This article assumes you want the 'nvidia' driver; if you do not, generic (IE not slackware-specific) documentation available.

= Obtaining the driver =

The driver can be found at [http://www.nvidia.com/object/unix.html].

= Installing the driver =

The driver must not be installed while X is running; if X is running, stop X, install the driver, then start X again how you normally would (eg "telinit 4", or "startx").

Download the driver, then "sh FILENAME.run" in the directory you downloaded it do, replacing "FILENAME" with the name of the file you downloaded.

== XOrg config ==

There are two options:

=== nvidia-xconfig ===

This is an automated tool, that the above installer offers to run for you. It attempts to modify your XOrg.conf automatically to use the nvidia driver.

=== Manual Editing ===

Find the section relating to your graphics card in /etc/X11/xorg.conf, and change the driver to "nvidia". If you want to change the default settings, for example, add dual-head support, see the readme installed into /usr/doc/NVIDIA_GLX-1.0/.

= Checking It's Working =

* Check "nvidia-settings" runs in X
* Check "glxinfo | grep direct" returns "direct rendering: Yes"
* Check "glxgears" gives a reasonable result (google for comparisons)

Pay close attention to specific model of graphics card when checking for suitable glxgears results; keep in mind that glxgears isn't really a good 'benchmark', but should indicate if DRI is working properly or not. For example:

* On an Intel X3100, a good result is somewhere around 1000 FPS
* On an NVidia 7800GTX, a good result is somewhere above 12000 (though 15k is fairly normal)

= Translations =

Mehdi Esmaeelpour translate this article to persian - [http://www.slack-world.com/index.php/articles/43-general-system/107-nvidia-driver-installation article link]</text>
    <sha1>f607a51708526096f5edf1dbcbde67bbd2772f5b</sha1>
  </revision>
  <revision>
    <id>398</id>
    <parentid>397</parentid>
    <timestamp>2010-08-10T11:31:26Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <comment>/* Translations */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2261" xml:space="preserve">[[Category:Hardware]]

= Introduction =

There are three main drivers for nvidia graphics card on linux, one of which is shipped with slackware:

* nv (shipped with slackware) - this provides basic 2d acceleration, not 3d
* nvidia (NVidia's proprietary driver) - this is the generally recommended driver, providing good 2d and 3d performance
* nouveau - an attempt to reverse-engineer the nvidia driver; not particular usable or stable

This article assumes you want the 'nvidia' driver; if you do not, generic (IE not slackware-specific) documentation available.

= Obtaining the driver =

The driver can be found at [http://www.nvidia.com/object/unix.html].

= Installing the driver =

The driver must not be installed while X is running; if X is running, stop X, install the driver, then start X again how you normally would (eg "telinit 4", or "startx").

Download the driver, then "sh FILENAME.run" in the directory you downloaded it do, replacing "FILENAME" with the name of the file you downloaded.

== XOrg config ==

There are two options:

=== nvidia-xconfig ===

This is an automated tool, that the above installer offers to run for you. It attempts to modify your XOrg.conf automatically to use the nvidia driver.

=== Manual Editing ===

Find the section relating to your graphics card in /etc/X11/xorg.conf, and change the driver to "nvidia". If you want to change the default settings, for example, add dual-head support, see the readme installed into /usr/doc/NVIDIA_GLX-1.0/.

= Checking It's Working =

* Check "nvidia-settings" runs in X
* Check "glxinfo | grep direct" returns "direct rendering: Yes"
* Check "glxgears" gives a reasonable result (google for comparisons)

Pay close attention to specific model of graphics card when checking for suitable glxgears results; keep in mind that glxgears isn't really a good 'benchmark', but should indicate if DRI is working properly or not. For example:

* On an Intel X3100, a good result is somewhere around 1000 FPS
* On an NVidia 7800GTX, a good result is somewhere above 12000 (though 15k is fairly normal)

= Translations =

Mehdi Esmaeelpour translated this article to persian - [http://www.slack-world.com/index.php/articles/43-general-system/107-nvidia-driver-installation article link]</text>
    <sha1>f4be427d89c06ab03f6212a7d14314e9ca1524ff</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Talk:Editors</title>
  <ns>1</ns>
  <id>229</id>
  <revision>
    <id>401</id>
    <timestamp>2010-08-21T13:54:51Z</timestamp>
    <contributor>
      <username>Dengel</username>
      <id>134</id>
    </contributor>
    <minor/>
    <comment>mc</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="35" xml:space="preserve">Midnight Commander includes mcedit.</text>
    <sha1>0a169821fbe8907192e6cf48abc6bef4c56466bd</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>SlackWiki:Community Portal</title>
  <ns>4</ns>
  <id>226</id>
  <revision>
    <id>402</id>
    <parentid>371</parentid>
    <timestamp>2010-08-21T20:32:16Z</timestamp>
    <contributor>
      <username>Sombriks</username>
      <id>109</id>
    </contributor>
    <comment>/* GUS-BR */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="503" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
[http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
[http://slackware.linux.or.id http://slackware.linux.or.id]</text>
    <sha1>f6372a2df06dff6784982ed5a3769a8f3df3f0b6</sha1>
  </revision>
  <revision>
    <id>403</id>
    <parentid>402</parentid>
    <timestamp>2010-08-21T20:32:48Z</timestamp>
    <contributor>
      <username>Sombriks</username>
      <id>109</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="505" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
 [http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
 [http://slackware.linux.or.id http://slackware.linux.or.id]</text>
    <sha1>ef4e5ae96ab304db049544f4a1e880bb1cdb1b9a</sha1>
  </revision>
  <revision>
    <id>404</id>
    <parentid>403</parentid>
    <timestamp>2010-08-23T09:08:28Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="632" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
 [http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
 [http://slackware.linux.or.id http://slackware.linux.or.id]
&lt;BR&gt;
====[http://www.slack-world.com Iranian Slackware Community]====
 [http://www.slack-world.com http://www.slack-world.com]</text>
    <sha1>1008c600713017e25327dd3edb510660a8d99d96</sha1>
  </revision>
  <revision>
    <id>405</id>
    <parentid>404</parentid>
    <timestamp>2010-08-23T09:10:05Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="657" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
 [http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
 [http://slackware.linux.or.id http://slackware.linux.or.id]
&lt;BR&gt;
====[http://www.slack-world.com Iranian's Slackers World]====
Iranian Slackware Cummunity
 [http://www.slack-world.com http://www.slack-world.com]</text>
    <sha1>fdda82e042397688066ecbf63a18744d15592d99</sha1>
  </revision>
  <revision>
    <id>406</id>
    <parentid>405</parentid>
    <timestamp>2010-08-23T09:10:45Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="657" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
 [http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
 [http://slackware.linux.or.id http://slackware.linux.or.id]
&lt;BR&gt;
====[http://www.slack-world.com Iranian's Slackers World]====
Iranian Slackware Community
 [http://www.slack-world.com http://www.slack-world.com]</text>
    <sha1>2edc3acf820fdf4a906231a353a762ec8118d120</sha1>
  </revision>
  <revision>
    <id>410</id>
    <parentid>406</parentid>
    <timestamp>2010-09-15T21:03:41Z</timestamp>
    <contributor>
      <username>Unixfool</username>
      <id>141</id>
    </contributor>
    <minor/>
    <comment>added ##slackware info</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="865" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
 [http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
 [http://slackware.linux.or.id http://slackware.linux.or.id]
&lt;BR&gt;
====[http://www.slack-world.com Iranian's Slackers World]====
Iranian Slackware Community
 [http://www.slack-world.com http://www.slack-world.com]
&lt;BR&gt;
====##slackware, irc.freenode.net====
Channel site
 [http://freenodeslack.blogspot.com/]
Channel logs
 [http://wigglit.ath.cx/slackware_botlogs/]
Channel stats
 [http://wigglit.ath.cx/slackware_stats2/]</text>
    <sha1>d8d56d257b1c6fafa455b9f7aa8727fea1dd0ed0</sha1>
  </revision>
  <revision>
    <id>411</id>
    <parentid>410</parentid>
    <timestamp>2010-09-15T21:04:54Z</timestamp>
    <contributor>
      <username>Unixfool</username>
      <id>141</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="868" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
 [http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
 [http://slackware.linux.or.id http://slackware.linux.or.id]
&lt;BR&gt;
====[http://www.slack-world.com Iranian's Slackers World]====
Iranian Slackware Community
 [http://www.slack-world.com http://www.slack-world.com]
&lt;BR&gt;
====##slackware, irc.freenode.net====

 [Channel site http://freenodeslack.blogspot.com/]

 [Channel logs http://wigglit.ath.cx/slackware_botlogs/]

 [Channel stats http://wigglit.ath.cx/slackware_stats2/]</text>
    <sha1>7dfced39ba003752053be1de6d6e1f6f1b6cffba</sha1>
  </revision>
  <revision>
    <id>412</id>
    <parentid>411</parentid>
    <timestamp>2010-09-15T21:06:02Z</timestamp>
    <contributor>
      <username>Unixfool</username>
      <id>141</id>
    </contributor>
    <minor/>
    <comment>/* ##slackware, irc.freenode.net */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="867" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
 [http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
 [http://slackware.linux.or.id http://slackware.linux.or.id]
&lt;BR&gt;
====[http://www.slack-world.com Iranian's Slackers World]====
Iranian Slackware Community
 [http://www.slack-world.com http://www.slack-world.com]
&lt;BR&gt;
====##slackware, irc.freenode.net====

 [http://freenodeslack.blogspot.com/ Channel site]

 [http://wigglit.ath.cx/slackware_botlogs/Channel logs]

 [http://wigglit.ath.cx/slackware_stats2/ Channel stats]</text>
    <sha1>d1e133776882a0f968e0bc9fa15dce4584535538</sha1>
  </revision>
  <revision>
    <id>413</id>
    <parentid>412</parentid>
    <timestamp>2010-09-17T13:48:43Z</timestamp>
    <contributor>
      <username>Unixfool</username>
      <id>141</id>
    </contributor>
    <minor/>
    <comment>/* ##slackware, irc.freenode.net */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="868" xml:space="preserve">====[http://www.slackwarebrasil.org GUS-BR]====
Brazilian Slackware User Group (Grupo de Usuários Slackware Brasil)&lt;BR&gt;
 [http://www.slackwarebrasil.org www.slackwarebrasil.org ]
pt-br Wiki
 [http://wiki.slackwarebrasil.org/ wiki.slackwarebrasil.org]
&lt;BR&gt;

====[http://slacky.eu/ Slacky.eu]====
The Italian Slackware Community&lt;BR&gt;
 [http://slacky.eu/ http://slacky.eu]
&lt;BR&gt;
====[http://slackware.linux.or.id Indonesian Slackware Community]====
 [http://slackware.linux.or.id http://slackware.linux.or.id]
&lt;BR&gt;
====[http://www.slack-world.com Iranian's Slackers World]====
Iranian Slackware Community
 [http://www.slack-world.com http://www.slack-world.com]
&lt;BR&gt;
====##slackware, irc.freenode.net====

 [http://freenodeslack.blogspot.com/ Channel site]

 [http://wigglit.ath.cx/slackware_botlogs/ Channel logs]

 [http://wigglit.ath.cx/slackware_stats2/ Channel stats]</text>
    <sha1>30b794518e4a693baa683d07aaf14297c822d9c7</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Links</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>407</id>
    <parentid>242</parentid>
    <timestamp>2010-08-23T09:17:19Z</timestamp>
    <contributor>
      <username>Ariarat</username>
      <id>99</id>
    </contributor>
    <comment>/* Slackware Links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4143" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.slackwaregallery.org - our ugly mugs :)
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://slackware.wordpress.com - Slackware Blog by [[User:Tyler|Tyler]]
* http://www.slackbook.org - updated version of the slackware book
* http://userlocal.com/ - A focal point for the online Slackware Linux community
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.slackbasics.org/ - "Slackware Linux Basics" by Daniel de Kok
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://www.slacklife.com.br - Slackware Brazillian Community - by [[User:Redhate|redhate]]
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://jtgzmanager.sf.net/ - A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://www.slack-world.com - Iranian Slackware Community

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/ BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for 8.1 through -current</text>
    <sha1>d252021f8fceddcf34eb340fcd91fea9c1f86bed</sha1>
  </revision>
  <revision>
    <id>417</id>
    <parentid>407</parentid>
    <timestamp>2010-10-05T17:39:11Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Removed some dead and unmaintained links and a bit of reorg</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3834" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://www.slackbook.org - updated version of the slackware book
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://slackbuilds.org/ - Build scripts for additional software
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://jtgzmanager.sf.net/ - A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://www.slack-world.com - Iranian Slackware Community

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://www.remote-exploit.org/ BackTrack] The result of the merging of two Innovative Penetration Testing live Linux distributions: Whax and Auditor
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for 8.1 through -current</text>
    <sha1>5383bb1f7dfe6d0a453676e1d2ce15822cb21021</sha1>
  </revision>
  <revision>
    <id>418</id>
    <parentid>417</parentid>
    <timestamp>2010-10-05T17:40:36Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Removed backtrack from the list</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3682" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://www.slackbook.org - updated version of the slackware book
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://slackbuilds.org/ - Build scripts for additional software
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://jtgzmanager.sf.net/ - A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://www.slack-world.com - Iranian Slackware Community

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for 8.1 through -current</text>
    <sha1>1855b6041c051c8452e4a01fa0e409e7f237bc15</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>User:Unixfool</title>
  <ns>2</ns>
  <id>230</id>
  <revision>
    <id>408</id>
    <timestamp>2010-09-09T19:08:09Z</timestamp>
    <contributor>
      <username>Unixfool</username>
      <id>141</id>
    </contributor>
    <comment>added URLs</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="134" xml:space="preserve">http://slackfiles.blogspot.com/ &lt;br&gt;
http://freenodeslack.blogspot.com/ &lt;br&gt;
http://wigglit.ath.cx/ &lt;br&gt;
http://www.unixfool.com/ &lt;br&gt;</text>
    <sha1>c6c68f3e4cfb7c57ea08ead7cf6b78616c613f56</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Security Assessment using Nmap</title>
  <ns>0</ns>
  <id>148</id>
  <revision>
    <id>414</id>
    <parentid>176</parentid>
    <timestamp>2010-09-23T19:38:10Z</timestamp>
    <contributor>
      <username>Unixfool</username>
      <id>141</id>
    </contributor>
    <minor/>
    <comment>slight edits made</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7335" xml:space="preserve">[[Category:Tutorials]]
This tutorial will be a general guide on how to determine what ports have listening services and how to assess if those ports are available to the world wide web.  We will be using Nmap, netstat, and telnet.

We are concerned with three different things:

    1. Assessing localhost (127.0.0.1) on a given machine.

    2. Assessing the machine's IP from another machine within the LAN.

    3. Assessing the machine from the internet.

Running Nmap against localhost can be deceiving, as the ports that are listening on the machine may not actually be available to another machine, on or off the LAN. Note that 127.0.0.1 only pertains to the local machine. This is the loopback address that every machine uses to communicate to itself. I'll compare a localhost scan against a scan that was conducted from another machine on the LAN.

I'll scan localhost first:

    -su-2.05b# nmap localhost

    Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-09-12 17:20 EDT
    Interesting ports on localhost.home (127.0.0.1):
    Not shown: 1674 closed ports
    PORT STATE SERVICE
    22/tcp open ssh
    25/tcp open smtp
    3306/tcp open mysql
    5801/tcp open vnc-http-1
    5901/tcp open vnc-1
    6001/tcp open X11:1

    Nmap finished: 1 IP address (1 host up) scanned in 10.662 seconds

Now, I'll scan the machine's IP from another machine:

    root@slackbox:~# nmap 10.150.1.103

    Starting Nmap 4.20 ( http://insecure.org ) at 2007-09-12 17:36 EDT
    Interesting ports on delly (10.150.1.103):
    Not shown: 1693 filtered ports
    PORT STATE SERVICE
    22/tcp open ssh
    80/tcp open http
    3306/tcp open mysql
    5900/tcp closed vnc
    MAC Address: 00:C0:4F:61:28:1F (Dell Computer)

    Nmap finished: 1 IP address (1 host up) scanned in 22.277 seconds

Comparing the two scans, some things are readily apparent: port 25/tcp and 5801/tcp, 5901/tcp, and 6001/tcp aren't as exposed as the other services are. Also, note that certain ports are possibly bound to the IP but not the loopback. The more important aspect of these two scans is the services listening on a non-loopback address, because services use IPs to communicate to other machines, not loopback devices.

So, TCP ports 25, 5801, 5901, and 6001 appear to be open. We can test this. Remember, we're concerned about whether these ports can be seen as open to the internet. We'll test this by using telnet. Below, I'm logged into another machine and attempting to telnet on port 25 to the machine we Nmap'd on localhost:

    root@slackbox:~# telnet 10.150.1.103 25
    Trying 10.150.1.103...
    telnet: connect to address 10.150.1.103: Connection timed out

The connection timed out. This is proof this service isn't exposed beyond the local machine.  It is proof that this machine doesn't have SMTP services linked to the network interface that is assigned the IP of 10.150.1.103.

We can also test by running 'netstat -an' on the machine. While netstat doesn't connect to the port in question, it does indicate what interface services are using:

    -su-2.05b# netstat -an | grep -i listen
    tcp4 0 0 *.5801 *.* LISTEN
    tcp4 0 0 *.5901 *.* LISTEN
    tcp4 0 0 *.6001 *.* LISTEN
    tcp4 0 0 *.3306 *.* LISTEN
    tcp4 0 0 10.150.1.103.8118 *.* LISTEN
    tcp4 0 0 10.150.1.103.80 *.* LISTEN
    tcp4 0 0 127.0.0.1.25 *.* LISTEN
    tcp4 0 0 *.22 *.* LISTEN
    tcp6 0 0 *.22 *.* LISTEN

See port 25? What IP address is assigned to the service? Loopback! This means that this service isn't exposed to any other machine on the LAN or internet. It is a local service (local only internally to the operating system).  The other services are listening (for example, *.22) but the '*' usually means that the service is assigned to an interface (which may have a number of IPs assigned to it). Ports 80 and 8118 have an IP assigned to the service, instead of '*'. This means that only IP 10.150.1.103 is assigned to that interface. Ports 80 and 8118 also do not show up when scanning localhost, but yet I can telnet to port 80 and 8118 when using the telnet command (and also browser), using 'telnet localhost 80' or 'telnet localhost 8118'. Port 80 is a web server. Port 8118 is a Privoxy proxy. The reason is probably because my PF install on that machine filters some loopback traffic. If I scan the IP of the machine, port 80 is then detected. The reason is because PF is configured to allow port 80 traffic to/from 'slackbox' from/to 10.150.1.103.

What's curious is the fact that the VNC ports (5801, 5901) are showing as assigned to an interface, but not 127.0.0.1 and they aren't reachable from the outside of the machine (so sayeth nmap).  They may well be assigned to the 'lo' interface or iptables/pf may be filtering this traffic...this is worth checking out at a later time.

All of this is very elaborate. Everything has to be taken into consideration: what the firewall does/doesn't allow; what services run on 127.0.0.x; what services run on interfaces; what services run on IP addresses.

The last thing we'll do is scan the LAN from the internet. The results will be determined by what ports the gateway router/firewall are forwarding to machines within the LAN. For example, I know I've port 22/tcp open to the world because I've told my gateway firewall to forward any traffic on 22/tcp to 10.150.1.103. I also don't allow much else and also allow some traffic to be forwarded to different machines within the LAN. So, when a scan is being conducted from the outside, the whole LAN's security posture is taken into account. Now, let us scan from the internet:

    Starting nmap V. 3.00 ( www.insecure.org/nmap/ )
    Interesting ports on pool-xx-xxx-xx-xx.washdc.fios.verizon.net  xx.xxx.xx.xxx):
    (The 1599 ports scanned but not shown below are in state: filtered)
    Port State Service
    22/tcp open ssh
    3306/tcp open mysql 

NICE! Of all the scans we've conducted thus far, this is the one that is most important. The other scans paint the smaller picture, but this one puts it all together and is THE security assessment that one wants to conduct. So, you can see, ports 22 and 3306 are open to the world. This could be two different machines that need those ports open to the internet, or this could be one machine that has those two ports open to the world wide web. While I can reach those ports, my firewall is configured to allow communication from the machine I scanned from. If a machine, from Google.com or any other IP/domain that is not accounted for within the FW policy, attempted the same thing, those ports wouldn't show as opened, as the firewall would drop the traffic.  So, while the two ports appear to be open to the world in the above results, they actually aren't, as the traffic is being filtered.

I hope all of this has helped some in understanding security and how to assess your LAN gateway and hosts within the LAN. We've used Nmap, telnet, and netstat to determine the security posture of a given machine. There are other tools that I didn't mention for brevity, (such as socklist, tcpdump, snort, for example) but Unix and Linux machines offer much in the way of testing security of a machine.

''This tutorial is mirrored  [http://slackfiles.blogspot.com/2007/09/assessment-of-hardened-box.html here]''

--[[User:Unixfool|Ron]] 00:44, 16 September 2007 (EDT)</text>
    <sha1>357f961281b7ccfb669b53ec503fc7ae6190645e</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Utf-8 linux console</title>
  <ns>0</ns>
  <id>177</id>
  <revision>
    <id>415</id>
    <parentid>365</parentid>
    <timestamp>2010-09-27T10:20:05Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Keyboard */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4695" xml:space="preserve">[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in #slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== LANG environment variable ==

I find that typing multibyte characters like "ä" and erasing them with backspace, I can erase much more than what I wrote. It helps to set the LANG variable, preferably by editing /etc/profile.d/lang.sh (or lang.csh) to set it to en_US.UTF-8 or similar.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://home.tiscali.nl/t876506/utf8tbl.html]http://home.tiscali.nl/t876506/utf8tbl.html

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/source/uk-utf.map.gz]http://www.unrealize.co.uk/source/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>7fe3881f5bb547a3a55729d6ecb0f75fa6b318a3</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>User:Dive</title>
  <ns>2</ns>
  <id>232</id>
  <revision>
    <id>416</id>
    <timestamp>2010-10-04T14:36:47Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>Created page with 'Homepage: http://dawoodfall.net Email: dave@dawoodfall.net'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="58" xml:space="preserve">Homepage: http://dawoodfall.net
Email: dave@dawoodfall.net</text>
    <sha1>f715beff7072fa6e9a5bc5b0aa2fa6abb950e250</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Basic Security Fixes</title>
  <ns>0</ns>
  <id>69</id>
  <revision>
    <id>419</id>
    <parentid>90</parentid>
    <timestamp>2010-10-05T17:43:04Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>s/too/to/</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3801" xml:space="preserve">Small tips to increase the security of your Slackware box:

* Use strong passwords! The most common way Linux systems get hacked is through weak user passwords and SSH.
* Use a firewall! [http://www.freshmeat.net Freshmeat.net] has lots of automatic tools to help with configuration, and we have some example scripts posted [[Iptables_Scripts|here]].
* Tell X not to listen for TCP connections:
** KDM: Add "ServerArgsLocal=-nolisten tcp" under section [X-:*-Core] to /opt/kde/share/config/kdm/kdmrc
** XDM: Add "-nolisten tcp" to the line calling X in /etc/X11/xdm/Xservers.
** Console: Use 'startx -- -nolisten tcp' rather than 'startx', possibly with the aid of an alias.
***: You can also edit startx and, at line 168 (where it calls xinit), append '-nolisten tcp' at the end, but this is a dirty hack.
* Close any services you do not require, especially since most run as root. Think about what you will use them for. For instance, would you really want to run an sshd 24/7 when you will only perhaps access it remotely once in a blue moon, of which you will most likely know about in advance at which point you can run the required deamon prior to accessing remotely.
** To disable startup services in /etc/rc.d, unset the executable bit of the rc script. You can still start and stop services by executing the rc script later using 'sh'.
** You can also edit /etc/rc.d/rc.M directly and comment out lines that calls the other rc scripts.
* Disable the "time" service, by commenting out lines 22 and 23 in /etc/inetd.conf - you will need to restart inetd after making the changes. (If you need to run inetd at all!)
* Look for any services/daemons that you don't know about by running "netstat -luntp".
* Run 'ps -e u' several times and become familiar with your usual processes to establish a "baseline". Then keep monitoring regularly to spot when something doesn't seem right.
* If you suspect intrusion or have suspicious files, scan your system for rootkits with 'chkrootkit'. You can also scan for win32 "malware" with 'clamav' for instance if you're using your system as a mail/ftp server.
* Add the following line to hosts.deny to disallow access by any host to your system... 'ALL: ALL' - note that this only affects services built with libwrap (tcpwrappers), but it's one layer of security.  A further layer would be to add the following to /etc/hosts.allow... 'ALL: ALL: DENY'
* Fine tune logrotate by editing /etc/logrotate.conf and add more log rotations in /etc/logrotate.d/

* If you want to restrict who is able to use the su command to switch to certain users, you can use /etc/suauth. The basic format for /etc/suauth is "to-id:from-id:ACTION"

:Example:

    root:foobar:DENY 

:would stop the user foobar from using su to become root.

:Another example:

    root:ALL EXCEPT GROUP wheel:DENY

:would only allow users in the wheel group to su to root. 

:You can also allow users to su with no password required (why you would do this is beyond me), and can require that a user enter their OWN password before switching users. For more information, please consult the man page for /etc/suauth. 

:(Thanks to cubicool for informing me of the existence of /etc/suauth)

:A similar, though perhaps not as fine-grained, way to control who can use su is to change ownership and permissions of /bin/su.  First, add the user(s) that you want to be able to use su to the wheel group in /etc/passwd.  Next, change the ownership of /bin/su to group wheel, and change its permissions to 4750.
 chown root:wheel /bin/su
 chmod 4750 /bin/su
:This makes /bin/su executable *only* by members of the wheel group.

* Another way to restrict the users who can become root is to edit the file /etc/login.defs and change the value of SU_WHEEL_ONLY to yes.

[[Category:Tips]]
[[Category:Security]]</text>
    <sha1>17b4b389942c492b4322ef282a428fd47de6ad56</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>ALSA</title>
  <ns>0</ns>
  <id>35</id>
  <revision>
    <id>420</id>
    <parentid>56</parentid>
    <timestamp>2010-10-06T14:18:08Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Modernization</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="971" xml:space="preserve">[[Category:Tutorials]]

Sound problems *should* be rare these days, and of the ones that still exist, they are likely related to suspend/resume.  Those are driver issues which are largely out of your control, but see the documentation with the pm-utils package for details on handling those issues.

: &lt;code&gt;alsaconf&lt;/code&gt; used to be needed to set up sound cards in linux, but even that shouldn't be needed in recent linux distributions - everything should be handled automatically.

: &lt;code&gt;alsamixer&lt;/code&gt; can be used to change the volume.

: &lt;code&gt;alsactl store&lt;/code&gt; is used to save the volume settings.

: &lt;code&gt;alsactl restore&lt;/code&gt; is used to restore the volume settings.  This is automatically run on boot, so you usually won't need to run this command.

There is one tip for the Sound Baster 5.1 cards: sometimes you want to MUTE digital out so you can hear on all the speakers; in alsamixer, you just press M on the &lt;tt&gt;Analog/Digital Output Jack&lt;/tt&gt; item.</text>
    <sha1>ccf2823bf01fa3c8f6a7ea8413679d96cbcfe20c</sha1>
  </revision>
</page>
<page arvcontinue="20100616231737|373">
  <title>Install Slackware Using A USB Flash Drive</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>421</id>
    <timestamp>2010-11-17T23:42:42Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <comment>Created page with '[[Category:Tutorials]]  Installing Slackware using a USB flash drive is very easy.  Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official insta…'</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2273" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image doesnt work for you out of the box.

Additionally AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either [http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will demonstrate yet another way of doing this, which from my experience is easier and often more convenient than all of the above. This document will describe how to create a Hybrid Slackware ISO with [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror.

or b) a local copy of the Slackware tree. That may be the tree of a stable release, or even one the tree of the -current Slackware development cycle.

If you choose to go with b) you should be able to create your own ISO images using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script]

Pat's [http://slackware.osuosl.org/slackware/isolinux/README_SPLIT.TXT split to 3 CDs script]

AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script]

or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

Now all that is left to do is copy the ISO to the USB flash drive.

That can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive.

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should should eg. /dev/sdb and not /dev/sdb1.</text>
    <sha1>2fd8fa10ff6e718b2c9310a65000050e5fd8bc04</sha1>
  </revision>
  <revision>
    <id>422</id>
    <parentid>421</parentid>
    <timestamp>2010-11-17T23:45:26Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2391" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image doesnt work for you out of the box.

Additionally AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either [http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will demonstrate yet another way of doing this, which from my experience is easier and often more convenient than all of the above. This document will describe how to create a Hybrid Slackware ISO with [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror.

or b) a local copy of the Slackware tree. That may be the tree of a stable release, or even one the tree of the -current Slackware development cycle.

If you choose to go with b) you should be able to create your own ISO images using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script]

Pat's [http://slackware.osuosl.org/slackware/isolinux/README_SPLIT.TXT split to 3 CDs script]

AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script]

or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

Now all that is left to do is copy the ISO to the USB flash drive.

That can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive.

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should should eg. /dev/sdb and not /dev/sdb1.

Boot the computer using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>3ac08777daa5639800a7aa9fc538087b83d410c3</sha1>
  </revision>
  <revision>
    <id>423</id>
    <parentid>422</parentid>
    <timestamp>2010-11-17T23:46:56Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2407" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image doesnt work for you out of the box.

Additionally AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either [http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will demonstrate yet another way of doing this, which from my experience is easier and often more convenient than all of the above. This document will describe how to create a Hybrid Slackware ISO with [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror.

or b) a local copy of the Slackware tree. That may be the tree of a stable release, or even one the tree of the -current Slackware development cycle.

If you choose to go with b) you should be able to create your own ISO images using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script]

Pat's [http://slackware.osuosl.org/slackware/isolinux/README_SPLIT.TXT split to 3 CDs script]

AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script]

or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

Now all that is left to do is copy the ISO to the USB flash drive.

That can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive.

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should should eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the computer using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>2a791a6b853031e7f285e00fa5c4a28cd15f1303</sha1>
  </revision>
  <revision>
    <id>424</id>
    <parentid>423</parentid>
    <timestamp>2010-11-17T23:47:51Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2404" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image doesnt work for you out of the box.

Additionally AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either [http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will demonstrate yet another way of doing this, which from my experience is easier and often more convenient than all of the above. This document will describe how to create a Hybrid Slackware ISO with [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror.

or b) a local copy of the Slackware tree. That may be the tree of a stable release, or even one the tree of the -current Slackware development cycle.

If you choose to go with b) you should be able to create your own ISO images using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script]

Pat's [http://slackware.osuosl.org/slackware/isolinux/README_SPLIT.TXT split to 3 CDs script]

AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script]

or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

Now all that is left to do is copy the ISO to the USB flash drive.

That can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive.

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should use eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the computer using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>b9e3eb8d880da8212c2efde52aea6931d60a31ea</sha1>
  </revision>
  <revision>
    <id>425</id>
    <parentid>424</parentid>
    <timestamp>2010-11-17T23:49:00Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2404" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image doesnt work for you out of the box.

Additionally AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either [http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will demonstrate yet another way of doing this, which from my experience is easier and often more convenient than all of the above. This document will describe how to create a Hybrid Slackware ISO with [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror.

or b) a local copy of the Slackware tree. That may be the tree of a stable release, or even one the tree of the -current Slackware development cycle.

If you choose to go with b) you should be able to create your own ISO images using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script]

Pat's [http://slackware.osuosl.org/slackware/isolinux/README_SPLIT.TXT split to 3 CDs script]

AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script]

or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

Now all that is left to do is copy the ISO to the USB flash drive.

That can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should use eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the computer using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>87b5661349d54a7fc6ae1532f0286bd9f9a5c7a8</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>Install Slackware Using A USB Flash Drive</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>426</id>
    <parentid>425</parentid>
    <timestamp>2010-11-17T23:50:39Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2403" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image doesnt work for you out of the box.

Additionally AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either [http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will demonstrate yet another way of doing this, which from my experience is easier and often more convenient than all of the above. This document will describe how to create a Hybrid Slackware ISO with [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror.

or b) a local copy of the Slackware tree. That may be the tree of a stable release, or even one the tree of the -current Slackware development cycle.

If you choose to go with b) you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script]

Pat's [http://slackware.osuosl.org/slackware/isolinux/README_SPLIT.TXT split to 3 CDs script]

AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script]

or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

Now all that is left to do is copy the ISO to the USB flash drive.

That can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should use eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the computer using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>2dd2a272eeb4e7661774abe16c2b51dfce74a2cb</sha1>
  </revision>
  <revision>
    <id>427</id>
    <parentid>426</parentid>
    <timestamp>2010-11-18T00:26:46Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2399" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image doesnt work for you out of the box.

Additionally AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either [http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will demonstrate yet another way of doing this, which from my experience is easier and often more convenient than all of the above. This document will describe how to create a Hybrid Slackware ISO with [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror.

or b) a local copy of the Slackware tree. That may be the tree of a stable release, or even the tree of the -current Slackware development cycle.

If you choose to go with b) you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script]

Pat's [http://slackware.osuosl.org/slackware/isolinux/README_SPLIT.TXT split to 3 CDs script]

AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script]

or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

Now all that is left to do is copy the ISO to the USB flash drive.

That can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should use eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the computer using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>6aa5cd35bff95c6d0015d0720c0b72c9420b10d2</sha1>
  </revision>
  <revision>
    <id>428</id>
    <parentid>427</parentid>
    <timestamp>2010-11-18T00:27:33Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2398" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image doesnt work for you out of the box.

Additionally AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either [http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will demonstrate yet another way of doing this, which from my experience is easier and often more convenient than all of the above. This document will describe how to create a Hybrid Slackware ISO with [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror.

or b) a local copy of the Slackware tree. That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to go with b) you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script]

Pat's [http://slackware.osuosl.org/slackware/isolinux/README_SPLIT.TXT split to 3 CDs script]

AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script]

or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

Now all that is left to do is copy the ISO to the USB flash drive.

That can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should use eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the computer using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>4131eed5da4adde061821d875a7ab277dcd299fd</sha1>
  </revision>
  <revision>
    <id>429</id>
    <parentid>428</parentid>
    <timestamp>2010-11-18T00:44:02Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2177" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will describe yet another way of doing this, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

Syslinux &gt;=3.72 is required

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>9090cb98fadf367b49442dcfd7a0b278f63a508b</sha1>
  </revision>
  <revision>
    <id>430</id>
    <parentid>429</parentid>
    <timestamp>2010-11-20T02:41:16Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <comment>/* Prerequisites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2208" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will describe yet another way of doing this, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit ISO image.

Syslinux &gt;=3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>64b726ac3575197dad55acad10eae5e86b079619</sha1>
  </revision>
  <revision>
    <id>431</id>
    <parentid>430</parentid>
    <timestamp>2010-11-20T02:41:55Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <minor/>
    <comment>/* Prerequisites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2213" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will describe yet another way of doing this, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image.

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>8a95fea9904bd38f12fc5ac97ceb490262f79b84</sha1>
  </revision>
  <revision>
    <id>432</id>
    <parentid>431</parentid>
    <timestamp>2010-11-20T02:44:21Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <comment>/* Copy the ISO to the USB flash drive */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2271" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will describe yet another way of doing this, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image.

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS0. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.
PS1. the USB should NOT be mounted during dd invocation.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>9d465cd6a745ba10b9813da3c1b0ce610f6a199b</sha1>
  </revision>
  <revision>
    <id>433</id>
    <parentid>432</parentid>
    <timestamp>2010-11-20T02:44:50Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <minor/>
    <comment>/* Copy the ISO to the USB flash drive */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2272" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document will describe yet another way of doing this, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image.

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS0. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

PS1. the USB should NOT be mounted during dd invocation.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>2b2133addf23e71b82dbaaff157764a8ecc94294</sha1>
  </revision>
  <revision>
    <id>434</id>
    <parentid>433</parentid>
    <timestamp>2010-11-20T02:46:03Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2268" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of doing this, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image.

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

&lt;code&gt; dd if=slackware-13.1-install-dvd.iso of=/dev/sdX &lt;/code&gt;

PS0. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

PS1. the USB should NOT be mounted during dd invocation.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>9bfd9360809eeabadd98e3d20e7933be40fb0155</sha1>
  </revision>
  <revision>
    <id>435</id>
    <parentid>434</parentid>
    <timestamp>2010-11-20T06:33:09Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <comment>/* Copy the ISO to the USB flash drive */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2254" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of doing this, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image.

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

&lt;code&gt; isohybrid slackware-13.1-install-dvd.iso &lt;/code&gt;

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS0. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

PS1. the USB should NOT be mounted during dd invocation.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>b1b75aed161047b773a6beaf2101f43b623aa44a</sha1>
  </revision>
  <revision>
    <id>436</id>
    <parentid>435</parentid>
    <timestamp>2010-11-20T06:33:52Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <comment>/* Using isohybrid */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2240" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, along with AlienBOB's usbimg2disk.sh in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of doing this, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image.

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk.

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user, that will overwrite all the files currently present on the USB drive:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS0. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

PS1. the USB should NOT be mounted during dd invocation.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>ad7c2ab0d2ada46f2f61999f871d3a8f9d2fdeb1</sha1>
  </revision>
  <revision>
    <id>437</id>
    <parentid>436</parentid>
    <timestamp>2010-11-20T06:50:45Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2562" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The below command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

PS2. the USB should NOT be mounted during dd invocation.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>5fcf79119d568b8c2d3f4e6f4266943486b26c1f</sha1>
  </revision>
  <revision>
    <id>438</id>
    <parentid>437</parentid>
    <timestamp>2010-11-20T15:36:50Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2566" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of the device, not the partition, so you should be using eg. /dev/sdb and not /dev/sdb1.

PS2. the USB should NOT be mounted during dd invocation.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>2d6c9e10c911746d4f6cc29a975b2c722ad0e2a8</sha1>
  </revision>
  <revision>
    <id>439</id>
    <parentid>438</parentid>
    <timestamp>2010-11-20T15:38:11Z</timestamp>
    <contributor>
      <username>Sahko</username>
      <id>43</id>
    </contributor>
    <comment>/* Copy the ISO to the USB flash drive */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2566" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Epilogue ==

Boot the machine using the USB drive. Experience should be no different than using the official installation media.</text>
    <sha1>4dd1c2eaa32b26269c278ba00eb3dc625400916e</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>Dhcp renewal after wakeup</title>
  <ns>0</ns>
  <id>234</id>
  <revision>
    <id>440</id>
    <timestamp>2010-11-27T14:08:58Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>dhcp renew after sleep tip</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="655" xml:space="preserve">[[Category:Tips]]

Sometimes you need a new IP address after waking up from sleep/standby/hibernate modes. Network managers like Wicd can do this and are recommended for laptops, but you can use the pm-utils triggers yourself without installing and running more software too. The following script works for me:

&lt;pre&gt;
#!/bin/sh
#
# put this to:  /usr/lib64/pm-utils/sleep.d/05DhcpcdRenew
# /usr/lib/pm-utils/ .. on 32-bit systems

case "$1" in
        hibernate|suspend)
                ;;  
        thaw|resume)
                dhcpcd -n
                ;; 
        *) exit $NA
                ;; 
esac
&lt;/pre&gt;

The script probably needs to be executable.</text>
    <sha1>d1a8725bc987ff15e9c14f7232671c0e9c6dd0e3</sha1>
  </revision>
  <revision>
    <id>441</id>
    <parentid>440</parentid>
    <timestamp>2010-11-28T15:39:39Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="684" xml:space="preserve">[[Category:Tips]]

Sometimes you need a new IP address after waking up from sleep/standby/hibernate modes. Network managers like Wicd can do this and are recommended for laptops, but you can use the pm-utils triggers yourself without installing and running more software too. The following script works for me:

&lt;pre&gt;
#!/bin/sh
#
# put this to:  /usr/lib64/pm-utils/sleep.d/05DhcpcdRenew
# /usr/lib/pm-utils/ .. on 32-bit systems

case "$1" in
        hibernate|suspend)
                dhcpcd -k eth0
                ;;
        thaw|resume)
                dhcpcd eth0
                ;;
        *) exit $NA
                ;;
esac
&lt;/pre&gt;

The script probably needs to be executable.</text>
    <sha1>65752095814daab5990203864ed6d6dd16570d53</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>Mutt</title>
  <ns>0</ns>
  <id>117</id>
  <revision>
    <id>442</id>
    <parentid>222</parentid>
    <timestamp>2010-12-26T20:36:29Z</timestamp>
    <contributor>
      <username>Lionel</username>
      <id>130</id>
    </contributor>
    <comment>/* Getmail */ Add Gmail IMAP getmail configuration</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6179" xml:space="preserve">[[Category:Tutorials]]
= Mutt =

Mutt is a text-based mail client renowned for its powerful features and the fact that it is almost totally customizable. This article will cover the installation and configuration of mutt in order to use it as your daily email client. Please note that I use GMail as my primary email address, so the examples are designed for GMail users. Not much differs though other than the fact that GMail uses SSL.


== Installation ==

Slackware comes with a package for mutt v1.4. If you did a full install, you already have it installed. If not, it can be located on the 'n' series on your Slackware install CD or favourite mirror. This tutorial also uses getmail, procmail and msmtp. procmail and getmail are available as Slackware packages, and can be installed in the same manner...

If you have the CD, follow these steps as root to install it:

  mount /mnt/cdrom
  installpkg /mnt/cdrom/slackware/n/mutt-1.4.2.1i-i486-2.tgz
  installpkg /mnt/cdrom/slackware/n/getmail-4.4.4-noarch-1.tgz
  installpkg /mnt/cdrom/slackware/n/procmail-3.22-i486-1.tgz

If you would rather install it from a mirror:

  wget http://www.slackware.at/data/slackware-current/slackware/n/mutt-1.4.2.1i-i486-2.tgz
  wget http://www.slackware.at/data/slackware-current/slackware/n/getmail-4.4.4-noarch-1.tgz
  wget http://www.slackware.at/data/slackware-current/slackware/n/procmail-3.22-i486-1.tgz
  installpkg mutt-1.4.2.1i-i486-2.tgz getmail-4.4.4-noarch-1.tgz procmail-3.22-i486-1.tgz

Be sure to replace 'slackware-current' with the actual version of Slackware you are using.

msmtp is not part of Slackware, and will need to be installed separately. It can be downloaded from [http://msmtp.sourceforge.net/ here]. If you need information on building Slackware packages, click [[Building_A_Package]] for an excellent tutorial.

== Configuration ==

=== Mutt ===
First, let start with mutt, and a very simple ''~/.muttrc'':
 # Name
 set realname='Slackware User'
 
 # Where we store our emails
 set folder=~/mail
 set mbox=+mbox
 set spoolfile=+inbox
 set record=+sent
 set sort=threads # sort by emails by thread ;-)
 set postponed=+drafts
 set mbox_type=Maildir 
 mailboxes +inbox
 
 # my favourite editor is 'joe'
 set editor=joe
 
 ignore *	# this means "ignore all headers by default"
 # I still want to see some basic details
 unignore	date from subject to cc
 
 # Mutt options
 set edit_headers=yes
 set hdrs # Allows us to create our own headers
 my_hdr From: Slackware User &lt;user@slackware.com&gt;
 my_hdr X-Mailer: `mutt -v| head -n 1`

So far, it's simple, and cannot do much. We can almost read emails stored in ~/mail, compose and save drafts.

In order for us to read emails, first, we need to create our mail folders. We are using the Maildir format, so we need to create them using:

 mkdir -p ~/mail/inbox/{,cur,tmp,new}
 mkdir -p ~/mail/sent/{,cur,tmp,new}
 mkdir -p ~/mail/drafts/{,cur,tmp,new}

Now, when we have an email in ~/mail/inbox, we will be able to read it. Postponed messages will also be saved in ~/mail/drafts. But want to be able to send emails too, right? That's where msmtp comes into play.

For this part, we will assume that msmtp is installed. msmtp is basically a SMTP client that will be called by mutt when sending an email. So we need to have added to the mutt config like this:

 set sendmail="/usr/bin/msmtp"

Now, that's useless by itself. We need to setup msmtp to send emails...
Open up ~/.msmtprc with your favourite editor. This is a copy of mine, setup to use GMail's smtp server:

 account default
 host smtp.gmail.com
 port 587
 protocol smtp
 auth on
 from username@gmail.com
 user username@gmail.com
 password mypassword
 tls on
 tls_starttls on


So, after going through this and identifying what we need for our SMTP server, we are ready to send emails... Let's test it:

Launch mutt by running:
 mutt -y

Running mutt without '-y' will ignore our mailboxes statement, so we won't see any emails...

You can see in mutt the key shortcuts at the top of the screen: 'm' for composing a new message.
After we save the message, we see a new shortcut at the top: 'y' to send the message.

We now have mutt that can read emails from ~/mail/inbox, and send emails!!! 
The next step is to get the emails in ~/mail, and that's getmail's job.

=== Getmail ===

Getmail is a Python application that's included with Slackware. Similar to fetchmail, many people prefer it, saying it's easier to configure. Just like mutt, getmail is in the 'n' series, and should already be installed if you chose to do a full install. If not, just check out the mutt section above to install what's needed for this tutorial.

Once we have it all installed, let's create a basic getmail configuration. This configuration sits in ''~/.getmail/getmailrc'':

 [retriever]
 type = SimplePOP3SSLRetriever
 server = pop.gmail.com
 username = username@gmail.com
 port = 995
 password = password
 
 [destination]
 type = Maildir
 path = ~/mail/inbox

If you use a standard POP3 account that doesn't use SSL, use something like:

 [retriever]
 type = SimplePOP3Retriever
 server = pop.isp.net
 username = username
 port = 110
 password = password
 
 [destination]
 type = Maildir
 path = ~/mail/inbox

If you use Gmail's IMAP account, use something like:
 [retriever]
 type = SimpleIMAPSSLRetriever
 server = imap.gmail.com
 username = username
 password = password
 
 [destination]
 type = Maildir
 path = ~/mail/inbox


As simple as that. Now, it will connect to your email account, and download all your emails to ~/mail/inbox. Please note that if you want to fetch mail for multiple accounts, unlike fetchmail, getmail works with a single account per config file. So if you have two email accounts, you can have each account configured in their own config file like ''~/.getmail/getmailrc'' and ''~/.getmail/getmailrc-isp''

If you want automatic check, just add the following lines to your crontab by running ''crontab -e'' for each one of your email accounts:

 /5 * * * * /usr/bin/getmail
 /30 * * * * /usr/bin/getmail -r ~/.getmail/getmailrc-isp

=== Procmail ===

Procmail is an advanced mail filtering solution. More to come

== Todo ==
The rest...</text>
    <sha1>1cc7b9ab34626ad0a0016f889446defce25da419</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>443</id>
    <parentid>393</parentid>
    <timestamp>2011-01-05T17:43:35Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3804" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.16.1. [[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>47ef67699b75145f212f029858584c7c950923f0</sha1>
  </revision>
  <revision>
    <id>449</id>
    <parentid>443</parentid>
    <timestamp>2011-02-01T23:53:51Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Patched to 1.16.2.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3877" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST) | Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>b846a902fcf48e513817e20caedec8bb1bb58432</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>Samba</title>
  <ns>0</ns>
  <id>145</id>
  <revision>
    <id>445</id>
    <parentid>173</parentid>
    <timestamp>2011-01-15T04:43:02Z</timestamp>
    <contributor>
      <username>Natex</username>
      <id>157</id>
    </contributor>
    <comment>/* Using Samba */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20558" xml:space="preserve">[[Category:Tutorials]]
... this is a W.I.P ... will write more the next days, hope this is ok :)

comments, suggestions, etc. are welcome!

== Introduction ==
This Tutorial shows you how to configure Samba 3.0.x on Slackware 12.x.

It should later act as simple and secure as it can be in a heterogen network with Windows systems (a workstation with admin access, guest accounts for the rest [eg. your friends]), a media streaming client (eg. Xbox) and Linux / *nix (Solaris / Mac OS X).

I wanted to have all necessary parameters for home usage in my smb.conf so i can easily change them and have a mostly secure and stable system. Printing is disabled by default in my config, since i have no need to attach my printer to the server (the printer has its own print server: HP P2015). Also i really have no clue how to use a printer with linux. If someone wants to write something on printing then feel free to do so...

== Upgrade / Build Samba ==

If you are here you probably will know what Samba is good for and how it works.
Normally Samba is installed on your system and ready for action and doesn't need to be upgraded.

=== Upgrade Samba ===

All upgrades to Samba should be done via the patches directory on your favorite mirror. You should NOT NOT NOT mix -current packages with a non "-current" Slackware. 

=== Building Samba ===

Hey! Wanna build Samba? Get the source, get the slackbuild, make a package and install it!

I used the latest build from the 3.0.x fork since this comes with Slackware 12.x.

You can also try building Samba 3.2.x. If you want a optimized build with a better performance that suits your system, you should consider installing GCC &gt;4.2.4 since it supports better optimizing functions (''-march=native'' - specifying ''-march=native'' implies ''-mtune=native''. This will enable all instruction subsets supported by the local machine (hence the result might not run on different machines).) and use Samba 3.2.x cause it has a better overall performance. Only do this if you know what you are doing!

* Get the source + SlackBuild, edit it and build the package...
&lt;pre&gt;$ mkdir /tmp/samba
$ cd /tmp/samba
$ wget http://us3.samba.org/samba/ftp/stable/samba-3.0.31.tar.gz
  ...
$ wget -r -nH ftp://slackware.osuosl.org/pub/slackware/slackware-current/source/n/samba
$ jed samba.SlackBuild
  &gt;  VERSION=3.0.30
  &gt;&gt; VERSION=3.0.31

  &gt;  tar xjvf $CWD/samba-$VERSION.tar.bz2
  &gt;&gt; tar xfvz $CWD/samba-$VERSION.tar.gz
$ chmod +x samba.SlackBuild
$ ./samba.SlackBuild
$ upgradepkg /tmp/samba-3.0.31-i486-1.tgz&lt;/pre&gt;

== Configure Samba ==

There are a few requirments i had for this config.
* Guest access from Windows without the need for a password
* Guests are only allowed to read and have no ''home directory'' (eg. /home/guest)
* Guests are only allowed to put new files in a given directory
* Make everything secure as it can get with this config
* Users on the system have access to their ''home directory''
* No Printing at all
* Disable NetBios, we only have Windows XP or higher / *nix
* Maybe more?

=== /etc/samba/smb.conf ===
This is my own ''smb.conf'' as i use it on my system.

The config file itself should be selfexplaining. 

==== '''smb.conf /w comments''' ====
&lt;pre&gt;#smb.conf - v1.1
#
# Samba-3.0.30 - Slackware 12.x
# e.v.o ( e.v.o [A-T] gmx.net )
#
# ; COMMENT
# #PARAMETER ( name = default value )
# Normally every parameter should have its default value.
# If the parameter is commented out then it is the default value,
# otherwise you should have a look at "man smb.conf"
#
# This config is based on the smb.conf manual page
# and "Using Samba, 3rd Edition" from O'Reilly
#

# VARIABLE SUBSTITUTIONS
; %U	session username
; %G	primary group name of %U
; %h	the Internet hostname that Samba is running on
; %m	the NetBIOS name of the client machine (very useful)
; %L	the NetBIOS name of the server
; %M	the Internet name of the client machine
; %R	the selected protocol level after protocol negotiation
; %d	the process id of the current server process
; %a	the architecture of the remote machine
; %I	the IP address of the client machine
; %i	the local IP address to which a client connected
; %T	the current date and time
; %D	name of the domain or workgroup of the current user
; %w	the winbind separator
; %v	Samba version number
;
; The following substitutes apply only to some configuration options
; Only those that are used when a connection has been established
;
; %S	the name of the current service, if any
; %P	the root directory of the current service, if any
; %u	username of the current service, if any
; %g	primary group name of %u
; %H	the home directory of the user given by %u
; %N	the name of your NIS home directory server
; %p	the path of the service's home directory

[global]
; Parameters in this section apply to the server as a whole

; ###  USERSHARES  ### # Capability for non-root users to 
; ==================== # add/modify/delete own share definitions 
;
; Controls if usershares can permit guest access
#usershare allow guests      =
; Maximum number of user defined shares allowed
#usershare max shares        =
; If set only directories owned by the sharing user can be shared
#usershare owner only        =
; Directory containing the user defined share definitions
#usershare path              =
; Comma-separated list restricting what directories can be shared
#usershare prefix allow list =
; Comma-separated list restricting what directories can be shared
#usershare prefix deny list  =
; Pre-existing share used as a template for creating new usershares
#usershare template share    =

; ###  NAME MANGLING  ### # By default, Samba has the same
; ======================= # semantics as a Windows NT server
;
; Filenames are case sensitive
#case sensitive      = auto
; Default case for new filenames
#default case        = lower
; New files are created with the case that the client passes
#preserve case       = yes
; New files which conform to 8.3 syntax are created upper case
#short preserve case = yes

; ###  PRINTING  ###
; ==================
;
; All printers in the printcap will be loaded for browsing by default
load printers           = no
; Only applicable if printing is set to cups.
#cups server            = ""
; Show the "Add Printer Wizard" Dialog
show add printer wizard = no
; Yes = open, write to and submit spool files on the specified directory
printable               = no

; ===============================
; #   -   S E T T I N G S   -   #
; ===============================

; \-= USER SCRIPTS =-/    # These scripts are used on a PDC or stand-alone 
; ====================    # machine to add or delete corresponding unix accounts

; Script that will be run when a new group is requested
#add group script               = /usr/sbin/groupadd %g
; Script that will be run when a machine is added to Samba's domain
#add machine script             = /usr/sbin/adduser -s /bin/false -d /dev/null %u -n -g machines -c Machine 
; Script which will add a new service definition to smb.conf
#add share command              =
; Script which will add a new user
#add user script                = /usr/sbin/useradd -m %u
; Script that will be called when a user is added to a group
#add user to group script       = /usr/sbin/usermod -G %g %u
; Script which will modify an existing service definition in smb.conf
#change share command           =
; Script when a group is requested to be deleted
#delete group script            = /usr/sbin/groupdel %g
; Script when a user is removed from a group using the Windows NT domain administration tools
#delete user from group script  = /usr/sbin/deluser %u %g
; Script that will be run when managing users with remote RPC (NT) tools
#delete user script             = /usr/sbin/userdel -r %u
; Script that will be run under special circumstances
#rename user script             = no
; This script sets the primary group in the unix userdatase when an administrator sets the 
; primary group from the windows user manager or when fetching a SAM with net rpc vampire
#set primary group script       = /usr/sbin/usermod -g '%g' '%u'
; Program that can be used to set UNIX user passwords
#passwd program = /usr/bin/passwd %u
; Controls the "chat" conversation between smbd and the local password changing program
#passwd chat = "*New password:*" %n\r "*New password (again):*" %n\r \ "*Password changed*"

; \-= PERMISSION MASKS =-/
; ========================

#inherit owner                 = no
#inherit permissions           = no

#directory mask                = 0755
#directory security mask       = 0777
#force create mode             = 000
#force directory mode          = 000
#force directory security mode = 0
#force security mode           = 0
#security mask                 = 0777

; \-= USER PARAMETER =-/
; ======================

; List of users who will be granted administrative privileges on the share
admin users     = evo
; This is a list of users that should be allowed to login to this service
valid users     = evo guest
; This is a list of users that should not be allowed to login to this service
invalid users   = root nobody ftp adm apache bin daemon games gdm haldaemon halt lp mail messagebus mysql news operator pop rpc shutdown smmsp sshd sync uucp
; This is a list of users that are given read-only access to a service
read list       = evo guest
; This is a list of users that are given read-write access to a service
write list      = evo

; -= Guest Settings =-
; Username which will be used for access to services which are specified as guest ok
guest account   = guest
; Yes for a service, then no password is required to connect to the service
guest ok        = no
; Yes for a service, then only guest connections to the service are permitted
guest only      = no

; -= Forced User/Group Settings =-
; UNIX user name that will be assigned as the default user for all users
;force user = guest
; UNIX group name that will be assigned as the default primary group for all users
force group = users

; -= Map Settings =-
; Specify a file containing a mapping of usernames from the clients to the server
#username map = 
;
#map acl inherit  = no
#map archive      = yes
#map hidden       = 
#map read only    = yes
#map system       = no
map to guest     = Bad User

; \-= SHARE PARAMETER =-/
; =======================

; Lets you "turn off" a service. If available = no, then ALL attempts to connect to the service will fail
available       = yes
; Controls whether this share is seen in the list of available shares in a net view and in the browse list
browseable      = yes
; Allow or disallow client access to accounts that have null passwords 
#null password  = no
; If this parameter is yes, then users of a service may not create or modify files in the service's directory
read only       = yes
; Setting this parameter to no prevents any file or directory that is a symbolic link from being followed
follow symlinks = no
; This parameter controls whether or not links in the UNIX file system may be followed by the server
wide links      = no

; This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found
#default service = 
; This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty
dont descend     = /bin,/boot,/dev,/etc,/lib,/opt,/proc,/sbin,/srv,/sys,/tmp,/usr,/var

; -= Hide Files =-
; This is a boolean parameter that controls whether files starting with a dot appear as hidden files
#hide dot files         = yes
; This is a list of files or directories that are not visible but are accessible
#hide files             = 
; This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings
#hide special files     = no
; This parameter prevents clients from seeing the existance of files that cannot be read
#hide unreadable        = no
; This parameter prevents clients from seeing the existance of files that cannot be written to
#hide unwriteable files = no

; \-= WINDOWS PARAMETER =-/
; =========================

; Specifies the charset that samba will use to print messages to stdout and stderr
#display charset = "LOCALE" or "ASCII" (depending on the system)
; This option specifies which charset Samba should talk to DOS clients
#dos charset = # No default
; Enabling this parameter allows a user who has write access to the file (by whatever means) to modify the permissions
#dos filemode = no

; \-= NETWORK/CONNECTION PARAMETER =-/
; ====================================

; This controls what workgroup your server will appear to be in when queried by clients
workgroup = KlingKlang
; This controls what string will show up in the printer comment box in print manager and next to the IPC connection in net view
server string = FileDealer
; This sets the NetBIOS name by which a Samba server is known
netbios name = FileDealer
#netbios aliases = 

; -= Interface Settings =-
; This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service
hosts allow = 127.0.0.1 192.168.
hosts deny  = ALL

; -= Connection Options =-
; Represents the number of minutes of inactivity before a connection is considered dead and disconnected
#deadtime        = 0 
; The value of the parameter (an integer) represents the number of seconds between keepalive packets
#keepalive       = 300
; This option allows the number of simultaneous connections to a service
#max connections = 0
; This option allows you to set socket options to be used when talking with the client
socket options   = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536

; \-= OTHER PARAMETER =-/
; =======================

security = user

; Enabling this parameter will disable netbios support in Samba
disable netbios = yes
; Do a lookup with the DNS server
dns proxy = no

; -= SMBpasswd Settings =-
; This option allows the administrator to chose which backend will be used for storing user and possibly group information
#passdb backend = smbpasswd:/etc/samba/private/smbpasswd
; This option sets the path to the encrypted smbpasswd file
#smb passwd file = /etc/samba/private/smbpasswd

; -= Directory Settings =-
; This option specifies the directory where lock files will be placed
#lock directory = /var/lock
; This parameters defines the directory smbd will use for storing such files as smbpasswd and secrets.tdb
#private dir = /etc/samba/private

; -= Logging Settings =-
; This option allows you to override the name of the Samba log file
log file = /var/log/samba/samba.%m
; This option (an integer in kilobytes) specifies the max size the log file should grow to
max log size = 5000
; Parameter maps how Samba debug messages are logged onto the system
#syslog = 1
; Parameter is set then Samba debug messages are logged into the system syslog only
#syslog only = no

; Using the following line enables you to customise your configuration on a per machine
; basis. The %m gets replaced with the netbios name of the machine that is connecting.
; Note: Consider carefully the location in the configuration file of
;       this line.  The included file is read at that point.
#include = /etc/samba/smb.conf.%m

; ===========================
; #   -   S H A R E S   -   #
; ===========================

[homes]
comment    = Eigene Dateien

guest ok   = yes
read only  = no
browseable = no

[printers]
comment    = Drucker
path       = /var/spool/samba

browseable = no
available  = no
guest ok   = no
printable  = yes

[BitHalde]
comment   = 3TB
path      = /mnt/raid

guest ok  = yes
read only = yes
&lt;/pre&gt;

==== smb.conf w/o comments ====
&lt;pre&gt;[global]
        workgroup = KLINGKLANG
        server string = FileDealer
        map to guest = Bad User
        guest account = guest
        log file = /var/log/samba/samba.%m
        disable netbios = Yes
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
        load printers = No
        show add printer wizard = No
        dns proxy = No
        invalid users = root, nobody, ftp, adm, apache, bin, daemon, games, gdm, haldaemon, halt, lp, mail, messagebus, mysql, news, operator, pop, rpc, shutdown, smmsp, sshd, sync, uucp
        valid users = evo, guest
        admin users = evo
        read list = evo, guest
        write list = evo
        force group = users
        hosts allow = 127.0.0.1, 192.168.
        hosts deny = ALL
        wide links = No
        follow symlinks = No
        dont descend = /bin,/boot,/dev,/etc,/lib,/opt,/proc,/sbin,/srv,/sys,/tmp,/usr,/var

[homes]
        comment = Eigene Dateien
        read only = No
        guest ok = Yes
        browseable = No

[printers]
        comment = Drucker
        path = /var/spool/samba
        printable = Yes
        browseable = No
        available = No

[BitHalde]
        comment = 3TB
        path = /mnt/raid
        guest ok = Yes
&lt;/pre&gt;

== Using Samba ==

In this section we will have a look on how to restart, stop, and start the samba server.

=== Starting and Stopping Samba ===

In Slackware, the script /etc/rc.d/rc.samba controls the state of the samba server. Below are the three commands you can use (as root).

To restart samba use:
&lt;code&gt;/etc/rc.d/rc.samba restart &lt;/code&gt;

To stop samba use:
&lt;code&gt;/etc/rc.d/rc.samba stop &lt;/code&gt;

To start samba from a stopped state use:
&lt;code&gt;/etc/rc.d/rc.samba start &lt;/code&gt;

The rc.samba script described above is merely a convenient wrapper for the /usr/sbin/smbd and /usr/sbin/nmdb commands. For example, you could also start the samba server by using these two commands together:
&lt;pre&gt;#/usr/sbin/smbd -D
#/usr/sbin/nmbd -D
&lt;/pre&gt;

See the man pages for smbd and nmbd for details.
=== Optimizing Samba ===

== Testing and Troubleshooting ==

In this section we will have a look on how we test our configuration and what to do if we ran into problems.

=== Using ''testparm'' ===

&lt;blockquote&gt;testparm — check an smb.conf configuration file for internal correctness&lt;/blockquote&gt;

*: If your done with the setup of your ''smb.conf'' you should run ''testparm''. Do this by simply typing it ;)
&lt;pre&gt;$ testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
NOTE: Service printers is flagged unavailable.
Processing section "[BitHalde]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions&lt;/pre&gt;
:: Normally this is what the output should look like. By pressing enter you will get a list of all used parameters in smb.conf.

*: If you wish to have a complete list of all options and how they are set:
&lt;pre&gt;$ testparm -v&lt;/pre&gt;

==== Using ''smbclient'' ====

&lt;blockquote&gt;smbclient — ftp-like client to access SMB/CIFS resources on servers&lt;/blockquote&gt;

* Connecting as a guest and list all shares
&lt;pre&gt;$ smbclient -L localhost -N
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Sharename       Type      Comment
        ---------       ----      -------
        BitHalde        Disk      3TB
        IPC$            IPC       IPC Service (FileDealer)
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        KLINGKLANG           FILEDEALER&lt;/pre&gt;
&lt;blockquote&gt;-L ''host'' This option allows you to look at what services are available on a server.&lt;br/&gt;
-N Suppresses the normal password prompt. Useful when accessing a service that does not require a password.&lt;/blockquote&gt;

* Connecting with a specified username and list all shares
&lt;pre&gt;$ smbclient -L localhost -U evo
Password:
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Sharename       Type      Comment
        ---------       ----      -------
        BitHalde        Disk      3TB
        IPC$            IPC       IPC Service (FileDealer)
        evo             Disk      Eigene Dateien
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        KLINGKLANG           FILEDEALER&lt;/pre&gt;
&lt;blockquote&gt;-U Sets the SMB username or username and password.&lt;/blockquote&gt;


== To Do ==
* alle user eintragen (cat /etc/passwd | cut -d':' -f1 | sort)
* user scripte vervollständigen
* masken richten + upload beim gast/evo gehört root? warum das?
* was ist mit umlauten?
* --&gt; wie starten? rc.samba
* Testmethoden aus dem samba buch einfügen</text>
    <sha1>7f2aad2acc17370099c7c98d720f67da334b1396</sha1>
  </revision>
  <revision>
    <id>446</id>
    <parentid>445</parentid>
    <timestamp>2011-01-15T04:47:45Z</timestamp>
    <contributor>
      <username>Natex</username>
      <id>157</id>
    </contributor>
    <minor/>
    <comment>/* Optimizing Samba */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20532" xml:space="preserve">[[Category:Tutorials]]
... this is a W.I.P ... will write more the next days, hope this is ok :)

comments, suggestions, etc. are welcome!

== Introduction ==
This Tutorial shows you how to configure Samba 3.0.x on Slackware 12.x.

It should later act as simple and secure as it can be in a heterogen network with Windows systems (a workstation with admin access, guest accounts for the rest [eg. your friends]), a media streaming client (eg. Xbox) and Linux / *nix (Solaris / Mac OS X).

I wanted to have all necessary parameters for home usage in my smb.conf so i can easily change them and have a mostly secure and stable system. Printing is disabled by default in my config, since i have no need to attach my printer to the server (the printer has its own print server: HP P2015). Also i really have no clue how to use a printer with linux. If someone wants to write something on printing then feel free to do so...

== Upgrade / Build Samba ==

If you are here you probably will know what Samba is good for and how it works.
Normally Samba is installed on your system and ready for action and doesn't need to be upgraded.

=== Upgrade Samba ===

All upgrades to Samba should be done via the patches directory on your favorite mirror. You should NOT NOT NOT mix -current packages with a non "-current" Slackware. 

=== Building Samba ===

Hey! Wanna build Samba? Get the source, get the slackbuild, make a package and install it!

I used the latest build from the 3.0.x fork since this comes with Slackware 12.x.

You can also try building Samba 3.2.x. If you want a optimized build with a better performance that suits your system, you should consider installing GCC &gt;4.2.4 since it supports better optimizing functions (''-march=native'' - specifying ''-march=native'' implies ''-mtune=native''. This will enable all instruction subsets supported by the local machine (hence the result might not run on different machines).) and use Samba 3.2.x cause it has a better overall performance. Only do this if you know what you are doing!

* Get the source + SlackBuild, edit it and build the package...
&lt;pre&gt;$ mkdir /tmp/samba
$ cd /tmp/samba
$ wget http://us3.samba.org/samba/ftp/stable/samba-3.0.31.tar.gz
  ...
$ wget -r -nH ftp://slackware.osuosl.org/pub/slackware/slackware-current/source/n/samba
$ jed samba.SlackBuild
  &gt;  VERSION=3.0.30
  &gt;&gt; VERSION=3.0.31

  &gt;  tar xjvf $CWD/samba-$VERSION.tar.bz2
  &gt;&gt; tar xfvz $CWD/samba-$VERSION.tar.gz
$ chmod +x samba.SlackBuild
$ ./samba.SlackBuild
$ upgradepkg /tmp/samba-3.0.31-i486-1.tgz&lt;/pre&gt;

== Configure Samba ==

There are a few requirments i had for this config.
* Guest access from Windows without the need for a password
* Guests are only allowed to read and have no ''home directory'' (eg. /home/guest)
* Guests are only allowed to put new files in a given directory
* Make everything secure as it can get with this config
* Users on the system have access to their ''home directory''
* No Printing at all
* Disable NetBios, we only have Windows XP or higher / *nix
* Maybe more?

=== /etc/samba/smb.conf ===
This is my own ''smb.conf'' as i use it on my system.

The config file itself should be selfexplaining. 

==== '''smb.conf /w comments''' ====
&lt;pre&gt;#smb.conf - v1.1
#
# Samba-3.0.30 - Slackware 12.x
# e.v.o ( e.v.o [A-T] gmx.net )
#
# ; COMMENT
# #PARAMETER ( name = default value )
# Normally every parameter should have its default value.
# If the parameter is commented out then it is the default value,
# otherwise you should have a look at "man smb.conf"
#
# This config is based on the smb.conf manual page
# and "Using Samba, 3rd Edition" from O'Reilly
#

# VARIABLE SUBSTITUTIONS
; %U	session username
; %G	primary group name of %U
; %h	the Internet hostname that Samba is running on
; %m	the NetBIOS name of the client machine (very useful)
; %L	the NetBIOS name of the server
; %M	the Internet name of the client machine
; %R	the selected protocol level after protocol negotiation
; %d	the process id of the current server process
; %a	the architecture of the remote machine
; %I	the IP address of the client machine
; %i	the local IP address to which a client connected
; %T	the current date and time
; %D	name of the domain or workgroup of the current user
; %w	the winbind separator
; %v	Samba version number
;
; The following substitutes apply only to some configuration options
; Only those that are used when a connection has been established
;
; %S	the name of the current service, if any
; %P	the root directory of the current service, if any
; %u	username of the current service, if any
; %g	primary group name of %u
; %H	the home directory of the user given by %u
; %N	the name of your NIS home directory server
; %p	the path of the service's home directory

[global]
; Parameters in this section apply to the server as a whole

; ###  USERSHARES  ### # Capability for non-root users to 
; ==================== # add/modify/delete own share definitions 
;
; Controls if usershares can permit guest access
#usershare allow guests      =
; Maximum number of user defined shares allowed
#usershare max shares        =
; If set only directories owned by the sharing user can be shared
#usershare owner only        =
; Directory containing the user defined share definitions
#usershare path              =
; Comma-separated list restricting what directories can be shared
#usershare prefix allow list =
; Comma-separated list restricting what directories can be shared
#usershare prefix deny list  =
; Pre-existing share used as a template for creating new usershares
#usershare template share    =

; ###  NAME MANGLING  ### # By default, Samba has the same
; ======================= # semantics as a Windows NT server
;
; Filenames are case sensitive
#case sensitive      = auto
; Default case for new filenames
#default case        = lower
; New files are created with the case that the client passes
#preserve case       = yes
; New files which conform to 8.3 syntax are created upper case
#short preserve case = yes

; ###  PRINTING  ###
; ==================
;
; All printers in the printcap will be loaded for browsing by default
load printers           = no
; Only applicable if printing is set to cups.
#cups server            = ""
; Show the "Add Printer Wizard" Dialog
show add printer wizard = no
; Yes = open, write to and submit spool files on the specified directory
printable               = no

; ===============================
; #   -   S E T T I N G S   -   #
; ===============================

; \-= USER SCRIPTS =-/    # These scripts are used on a PDC or stand-alone 
; ====================    # machine to add or delete corresponding unix accounts

; Script that will be run when a new group is requested
#add group script               = /usr/sbin/groupadd %g
; Script that will be run when a machine is added to Samba's domain
#add machine script             = /usr/sbin/adduser -s /bin/false -d /dev/null %u -n -g machines -c Machine 
; Script which will add a new service definition to smb.conf
#add share command              =
; Script which will add a new user
#add user script                = /usr/sbin/useradd -m %u
; Script that will be called when a user is added to a group
#add user to group script       = /usr/sbin/usermod -G %g %u
; Script which will modify an existing service definition in smb.conf
#change share command           =
; Script when a group is requested to be deleted
#delete group script            = /usr/sbin/groupdel %g
; Script when a user is removed from a group using the Windows NT domain administration tools
#delete user from group script  = /usr/sbin/deluser %u %g
; Script that will be run when managing users with remote RPC (NT) tools
#delete user script             = /usr/sbin/userdel -r %u
; Script that will be run under special circumstances
#rename user script             = no
; This script sets the primary group in the unix userdatase when an administrator sets the 
; primary group from the windows user manager or when fetching a SAM with net rpc vampire
#set primary group script       = /usr/sbin/usermod -g '%g' '%u'
; Program that can be used to set UNIX user passwords
#passwd program = /usr/bin/passwd %u
; Controls the "chat" conversation between smbd and the local password changing program
#passwd chat = "*New password:*" %n\r "*New password (again):*" %n\r \ "*Password changed*"

; \-= PERMISSION MASKS =-/
; ========================

#inherit owner                 = no
#inherit permissions           = no

#directory mask                = 0755
#directory security mask       = 0777
#force create mode             = 000
#force directory mode          = 000
#force directory security mode = 0
#force security mode           = 0
#security mask                 = 0777

; \-= USER PARAMETER =-/
; ======================

; List of users who will be granted administrative privileges on the share
admin users     = evo
; This is a list of users that should be allowed to login to this service
valid users     = evo guest
; This is a list of users that should not be allowed to login to this service
invalid users   = root nobody ftp adm apache bin daemon games gdm haldaemon halt lp mail messagebus mysql news operator pop rpc shutdown smmsp sshd sync uucp
; This is a list of users that are given read-only access to a service
read list       = evo guest
; This is a list of users that are given read-write access to a service
write list      = evo

; -= Guest Settings =-
; Username which will be used for access to services which are specified as guest ok
guest account   = guest
; Yes for a service, then no password is required to connect to the service
guest ok        = no
; Yes for a service, then only guest connections to the service are permitted
guest only      = no

; -= Forced User/Group Settings =-
; UNIX user name that will be assigned as the default user for all users
;force user = guest
; UNIX group name that will be assigned as the default primary group for all users
force group = users

; -= Map Settings =-
; Specify a file containing a mapping of usernames from the clients to the server
#username map = 
;
#map acl inherit  = no
#map archive      = yes
#map hidden       = 
#map read only    = yes
#map system       = no
map to guest     = Bad User

; \-= SHARE PARAMETER =-/
; =======================

; Lets you "turn off" a service. If available = no, then ALL attempts to connect to the service will fail
available       = yes
; Controls whether this share is seen in the list of available shares in a net view and in the browse list
browseable      = yes
; Allow or disallow client access to accounts that have null passwords 
#null password  = no
; If this parameter is yes, then users of a service may not create or modify files in the service's directory
read only       = yes
; Setting this parameter to no prevents any file or directory that is a symbolic link from being followed
follow symlinks = no
; This parameter controls whether or not links in the UNIX file system may be followed by the server
wide links      = no

; This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found
#default service = 
; This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty
dont descend     = /bin,/boot,/dev,/etc,/lib,/opt,/proc,/sbin,/srv,/sys,/tmp,/usr,/var

; -= Hide Files =-
; This is a boolean parameter that controls whether files starting with a dot appear as hidden files
#hide dot files         = yes
; This is a list of files or directories that are not visible but are accessible
#hide files             = 
; This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings
#hide special files     = no
; This parameter prevents clients from seeing the existance of files that cannot be read
#hide unreadable        = no
; This parameter prevents clients from seeing the existance of files that cannot be written to
#hide unwriteable files = no

; \-= WINDOWS PARAMETER =-/
; =========================

; Specifies the charset that samba will use to print messages to stdout and stderr
#display charset = "LOCALE" or "ASCII" (depending on the system)
; This option specifies which charset Samba should talk to DOS clients
#dos charset = # No default
; Enabling this parameter allows a user who has write access to the file (by whatever means) to modify the permissions
#dos filemode = no

; \-= NETWORK/CONNECTION PARAMETER =-/
; ====================================

; This controls what workgroup your server will appear to be in when queried by clients
workgroup = KlingKlang
; This controls what string will show up in the printer comment box in print manager and next to the IPC connection in net view
server string = FileDealer
; This sets the NetBIOS name by which a Samba server is known
netbios name = FileDealer
#netbios aliases = 

; -= Interface Settings =-
; This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service
hosts allow = 127.0.0.1 192.168.
hosts deny  = ALL

; -= Connection Options =-
; Represents the number of minutes of inactivity before a connection is considered dead and disconnected
#deadtime        = 0 
; The value of the parameter (an integer) represents the number of seconds between keepalive packets
#keepalive       = 300
; This option allows the number of simultaneous connections to a service
#max connections = 0
; This option allows you to set socket options to be used when talking with the client
socket options   = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536

; \-= OTHER PARAMETER =-/
; =======================

security = user

; Enabling this parameter will disable netbios support in Samba
disable netbios = yes
; Do a lookup with the DNS server
dns proxy = no

; -= SMBpasswd Settings =-
; This option allows the administrator to chose which backend will be used for storing user and possibly group information
#passdb backend = smbpasswd:/etc/samba/private/smbpasswd
; This option sets the path to the encrypted smbpasswd file
#smb passwd file = /etc/samba/private/smbpasswd

; -= Directory Settings =-
; This option specifies the directory where lock files will be placed
#lock directory = /var/lock
; This parameters defines the directory smbd will use for storing such files as smbpasswd and secrets.tdb
#private dir = /etc/samba/private

; -= Logging Settings =-
; This option allows you to override the name of the Samba log file
log file = /var/log/samba/samba.%m
; This option (an integer in kilobytes) specifies the max size the log file should grow to
max log size = 5000
; Parameter maps how Samba debug messages are logged onto the system
#syslog = 1
; Parameter is set then Samba debug messages are logged into the system syslog only
#syslog only = no

; Using the following line enables you to customise your configuration on a per machine
; basis. The %m gets replaced with the netbios name of the machine that is connecting.
; Note: Consider carefully the location in the configuration file of
;       this line.  The included file is read at that point.
#include = /etc/samba/smb.conf.%m

; ===========================
; #   -   S H A R E S   -   #
; ===========================

[homes]
comment    = Eigene Dateien

guest ok   = yes
read only  = no
browseable = no

[printers]
comment    = Drucker
path       = /var/spool/samba

browseable = no
available  = no
guest ok   = no
printable  = yes

[BitHalde]
comment   = 3TB
path      = /mnt/raid

guest ok  = yes
read only = yes
&lt;/pre&gt;

==== smb.conf w/o comments ====
&lt;pre&gt;[global]
        workgroup = KLINGKLANG
        server string = FileDealer
        map to guest = Bad User
        guest account = guest
        log file = /var/log/samba/samba.%m
        disable netbios = Yes
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
        load printers = No
        show add printer wizard = No
        dns proxy = No
        invalid users = root, nobody, ftp, adm, apache, bin, daemon, games, gdm, haldaemon, halt, lp, mail, messagebus, mysql, news, operator, pop, rpc, shutdown, smmsp, sshd, sync, uucp
        valid users = evo, guest
        admin users = evo
        read list = evo, guest
        write list = evo
        force group = users
        hosts allow = 127.0.0.1, 192.168.
        hosts deny = ALL
        wide links = No
        follow symlinks = No
        dont descend = /bin,/boot,/dev,/etc,/lib,/opt,/proc,/sbin,/srv,/sys,/tmp,/usr,/var

[homes]
        comment = Eigene Dateien
        read only = No
        guest ok = Yes
        browseable = No

[printers]
        comment = Drucker
        path = /var/spool/samba
        printable = Yes
        browseable = No
        available = No

[BitHalde]
        comment = 3TB
        path = /mnt/raid
        guest ok = Yes
&lt;/pre&gt;

== Using Samba ==

In this section we will have a look on how to restart, stop, and start the samba server.

=== Starting and Stopping Samba ===

In Slackware, the script /etc/rc.d/rc.samba controls the state of the samba server. Below are the three commands you can use (as root).

To restart samba use:
&lt;code&gt;/etc/rc.d/rc.samba restart &lt;/code&gt;

To stop samba use:
&lt;code&gt;/etc/rc.d/rc.samba stop &lt;/code&gt;

To start samba from a stopped state use:
&lt;code&gt;/etc/rc.d/rc.samba start &lt;/code&gt;

The rc.samba script described above is merely a convenient wrapper for the /usr/sbin/smbd and /usr/sbin/nmdb commands. For example, you could also start the samba server by using these two commands together:
&lt;pre&gt;#/usr/sbin/smbd -D
#/usr/sbin/nmbd -D
&lt;/pre&gt;

See the man pages for smbd and nmbd for details.
== Testing and Troubleshooting ==

In this section we will have a look on how we test our configuration and what to do if we ran into problems.

=== Using ''testparm'' ===

&lt;blockquote&gt;testparm — check an smb.conf configuration file for internal correctness&lt;/blockquote&gt;

*: If your done with the setup of your ''smb.conf'' you should run ''testparm''. Do this by simply typing it ;)
&lt;pre&gt;$ testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
NOTE: Service printers is flagged unavailable.
Processing section "[BitHalde]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions&lt;/pre&gt;
:: Normally this is what the output should look like. By pressing enter you will get a list of all used parameters in smb.conf.

*: If you wish to have a complete list of all options and how they are set:
&lt;pre&gt;$ testparm -v&lt;/pre&gt;

==== Using ''smbclient'' ====

&lt;blockquote&gt;smbclient — ftp-like client to access SMB/CIFS resources on servers&lt;/blockquote&gt;

* Connecting as a guest and list all shares
&lt;pre&gt;$ smbclient -L localhost -N
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Sharename       Type      Comment
        ---------       ----      -------
        BitHalde        Disk      3TB
        IPC$            IPC       IPC Service (FileDealer)
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        KLINGKLANG           FILEDEALER&lt;/pre&gt;
&lt;blockquote&gt;-L ''host'' This option allows you to look at what services are available on a server.&lt;br/&gt;
-N Suppresses the normal password prompt. Useful when accessing a service that does not require a password.&lt;/blockquote&gt;

* Connecting with a specified username and list all shares
&lt;pre&gt;$ smbclient -L localhost -U evo
Password:
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Sharename       Type      Comment
        ---------       ----      -------
        BitHalde        Disk      3TB
        IPC$            IPC       IPC Service (FileDealer)
        evo             Disk      Eigene Dateien
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        KLINGKLANG           FILEDEALER&lt;/pre&gt;
&lt;blockquote&gt;-U Sets the SMB username or username and password.&lt;/blockquote&gt;


== To Do ==
* alle user eintragen (cat /etc/passwd | cut -d':' -f1 | sort)
* user scripte vervollständigen
* masken richten + upload beim gast/evo gehört root? warum das?
* was ist mit umlauten?
* --&gt; wie starten? rc.samba
* Testmethoden aus dem samba buch einfügen</text>
    <sha1>93ec2038537adfd5e2dbd8cd46eca4c9eb0aeb2a</sha1>
  </revision>
  <revision>
    <id>447</id>
    <parentid>446</parentid>
    <timestamp>2011-01-15T04:52:39Z</timestamp>
    <contributor>
      <username>Natex</username>
      <id>157</id>
    </contributor>
    <comment>/* Using testparm */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20529" xml:space="preserve">[[Category:Tutorials]]
... this is a W.I.P ... will write more the next days, hope this is ok :)

comments, suggestions, etc. are welcome!

== Introduction ==
This Tutorial shows you how to configure Samba 3.0.x on Slackware 12.x.

It should later act as simple and secure as it can be in a heterogen network with Windows systems (a workstation with admin access, guest accounts for the rest [eg. your friends]), a media streaming client (eg. Xbox) and Linux / *nix (Solaris / Mac OS X).

I wanted to have all necessary parameters for home usage in my smb.conf so i can easily change them and have a mostly secure and stable system. Printing is disabled by default in my config, since i have no need to attach my printer to the server (the printer has its own print server: HP P2015). Also i really have no clue how to use a printer with linux. If someone wants to write something on printing then feel free to do so...

== Upgrade / Build Samba ==

If you are here you probably will know what Samba is good for and how it works.
Normally Samba is installed on your system and ready for action and doesn't need to be upgraded.

=== Upgrade Samba ===

All upgrades to Samba should be done via the patches directory on your favorite mirror. You should NOT NOT NOT mix -current packages with a non "-current" Slackware. 

=== Building Samba ===

Hey! Wanna build Samba? Get the source, get the slackbuild, make a package and install it!

I used the latest build from the 3.0.x fork since this comes with Slackware 12.x.

You can also try building Samba 3.2.x. If you want a optimized build with a better performance that suits your system, you should consider installing GCC &gt;4.2.4 since it supports better optimizing functions (''-march=native'' - specifying ''-march=native'' implies ''-mtune=native''. This will enable all instruction subsets supported by the local machine (hence the result might not run on different machines).) and use Samba 3.2.x cause it has a better overall performance. Only do this if you know what you are doing!

* Get the source + SlackBuild, edit it and build the package...
&lt;pre&gt;$ mkdir /tmp/samba
$ cd /tmp/samba
$ wget http://us3.samba.org/samba/ftp/stable/samba-3.0.31.tar.gz
  ...
$ wget -r -nH ftp://slackware.osuosl.org/pub/slackware/slackware-current/source/n/samba
$ jed samba.SlackBuild
  &gt;  VERSION=3.0.30
  &gt;&gt; VERSION=3.0.31

  &gt;  tar xjvf $CWD/samba-$VERSION.tar.bz2
  &gt;&gt; tar xfvz $CWD/samba-$VERSION.tar.gz
$ chmod +x samba.SlackBuild
$ ./samba.SlackBuild
$ upgradepkg /tmp/samba-3.0.31-i486-1.tgz&lt;/pre&gt;

== Configure Samba ==

There are a few requirments i had for this config.
* Guest access from Windows without the need for a password
* Guests are only allowed to read and have no ''home directory'' (eg. /home/guest)
* Guests are only allowed to put new files in a given directory
* Make everything secure as it can get with this config
* Users on the system have access to their ''home directory''
* No Printing at all
* Disable NetBios, we only have Windows XP or higher / *nix
* Maybe more?

=== /etc/samba/smb.conf ===
This is my own ''smb.conf'' as i use it on my system.

The config file itself should be selfexplaining. 

==== '''smb.conf /w comments''' ====
&lt;pre&gt;#smb.conf - v1.1
#
# Samba-3.0.30 - Slackware 12.x
# e.v.o ( e.v.o [A-T] gmx.net )
#
# ; COMMENT
# #PARAMETER ( name = default value )
# Normally every parameter should have its default value.
# If the parameter is commented out then it is the default value,
# otherwise you should have a look at "man smb.conf"
#
# This config is based on the smb.conf manual page
# and "Using Samba, 3rd Edition" from O'Reilly
#

# VARIABLE SUBSTITUTIONS
; %U	session username
; %G	primary group name of %U
; %h	the Internet hostname that Samba is running on
; %m	the NetBIOS name of the client machine (very useful)
; %L	the NetBIOS name of the server
; %M	the Internet name of the client machine
; %R	the selected protocol level after protocol negotiation
; %d	the process id of the current server process
; %a	the architecture of the remote machine
; %I	the IP address of the client machine
; %i	the local IP address to which a client connected
; %T	the current date and time
; %D	name of the domain or workgroup of the current user
; %w	the winbind separator
; %v	Samba version number
;
; The following substitutes apply only to some configuration options
; Only those that are used when a connection has been established
;
; %S	the name of the current service, if any
; %P	the root directory of the current service, if any
; %u	username of the current service, if any
; %g	primary group name of %u
; %H	the home directory of the user given by %u
; %N	the name of your NIS home directory server
; %p	the path of the service's home directory

[global]
; Parameters in this section apply to the server as a whole

; ###  USERSHARES  ### # Capability for non-root users to 
; ==================== # add/modify/delete own share definitions 
;
; Controls if usershares can permit guest access
#usershare allow guests      =
; Maximum number of user defined shares allowed
#usershare max shares        =
; If set only directories owned by the sharing user can be shared
#usershare owner only        =
; Directory containing the user defined share definitions
#usershare path              =
; Comma-separated list restricting what directories can be shared
#usershare prefix allow list =
; Comma-separated list restricting what directories can be shared
#usershare prefix deny list  =
; Pre-existing share used as a template for creating new usershares
#usershare template share    =

; ###  NAME MANGLING  ### # By default, Samba has the same
; ======================= # semantics as a Windows NT server
;
; Filenames are case sensitive
#case sensitive      = auto
; Default case for new filenames
#default case        = lower
; New files are created with the case that the client passes
#preserve case       = yes
; New files which conform to 8.3 syntax are created upper case
#short preserve case = yes

; ###  PRINTING  ###
; ==================
;
; All printers in the printcap will be loaded for browsing by default
load printers           = no
; Only applicable if printing is set to cups.
#cups server            = ""
; Show the "Add Printer Wizard" Dialog
show add printer wizard = no
; Yes = open, write to and submit spool files on the specified directory
printable               = no

; ===============================
; #   -   S E T T I N G S   -   #
; ===============================

; \-= USER SCRIPTS =-/    # These scripts are used on a PDC or stand-alone 
; ====================    # machine to add or delete corresponding unix accounts

; Script that will be run when a new group is requested
#add group script               = /usr/sbin/groupadd %g
; Script that will be run when a machine is added to Samba's domain
#add machine script             = /usr/sbin/adduser -s /bin/false -d /dev/null %u -n -g machines -c Machine 
; Script which will add a new service definition to smb.conf
#add share command              =
; Script which will add a new user
#add user script                = /usr/sbin/useradd -m %u
; Script that will be called when a user is added to a group
#add user to group script       = /usr/sbin/usermod -G %g %u
; Script which will modify an existing service definition in smb.conf
#change share command           =
; Script when a group is requested to be deleted
#delete group script            = /usr/sbin/groupdel %g
; Script when a user is removed from a group using the Windows NT domain administration tools
#delete user from group script  = /usr/sbin/deluser %u %g
; Script that will be run when managing users with remote RPC (NT) tools
#delete user script             = /usr/sbin/userdel -r %u
; Script that will be run under special circumstances
#rename user script             = no
; This script sets the primary group in the unix userdatase when an administrator sets the 
; primary group from the windows user manager or when fetching a SAM with net rpc vampire
#set primary group script       = /usr/sbin/usermod -g '%g' '%u'
; Program that can be used to set UNIX user passwords
#passwd program = /usr/bin/passwd %u
; Controls the "chat" conversation between smbd and the local password changing program
#passwd chat = "*New password:*" %n\r "*New password (again):*" %n\r \ "*Password changed*"

; \-= PERMISSION MASKS =-/
; ========================

#inherit owner                 = no
#inherit permissions           = no

#directory mask                = 0755
#directory security mask       = 0777
#force create mode             = 000
#force directory mode          = 000
#force directory security mode = 0
#force security mode           = 0
#security mask                 = 0777

; \-= USER PARAMETER =-/
; ======================

; List of users who will be granted administrative privileges on the share
admin users     = evo
; This is a list of users that should be allowed to login to this service
valid users     = evo guest
; This is a list of users that should not be allowed to login to this service
invalid users   = root nobody ftp adm apache bin daemon games gdm haldaemon halt lp mail messagebus mysql news operator pop rpc shutdown smmsp sshd sync uucp
; This is a list of users that are given read-only access to a service
read list       = evo guest
; This is a list of users that are given read-write access to a service
write list      = evo

; -= Guest Settings =-
; Username which will be used for access to services which are specified as guest ok
guest account   = guest
; Yes for a service, then no password is required to connect to the service
guest ok        = no
; Yes for a service, then only guest connections to the service are permitted
guest only      = no

; -= Forced User/Group Settings =-
; UNIX user name that will be assigned as the default user for all users
;force user = guest
; UNIX group name that will be assigned as the default primary group for all users
force group = users

; -= Map Settings =-
; Specify a file containing a mapping of usernames from the clients to the server
#username map = 
;
#map acl inherit  = no
#map archive      = yes
#map hidden       = 
#map read only    = yes
#map system       = no
map to guest     = Bad User

; \-= SHARE PARAMETER =-/
; =======================

; Lets you "turn off" a service. If available = no, then ALL attempts to connect to the service will fail
available       = yes
; Controls whether this share is seen in the list of available shares in a net view and in the browse list
browseable      = yes
; Allow or disallow client access to accounts that have null passwords 
#null password  = no
; If this parameter is yes, then users of a service may not create or modify files in the service's directory
read only       = yes
; Setting this parameter to no prevents any file or directory that is a symbolic link from being followed
follow symlinks = no
; This parameter controls whether or not links in the UNIX file system may be followed by the server
wide links      = no

; This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found
#default service = 
; This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty
dont descend     = /bin,/boot,/dev,/etc,/lib,/opt,/proc,/sbin,/srv,/sys,/tmp,/usr,/var

; -= Hide Files =-
; This is a boolean parameter that controls whether files starting with a dot appear as hidden files
#hide dot files         = yes
; This is a list of files or directories that are not visible but are accessible
#hide files             = 
; This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings
#hide special files     = no
; This parameter prevents clients from seeing the existance of files that cannot be read
#hide unreadable        = no
; This parameter prevents clients from seeing the existance of files that cannot be written to
#hide unwriteable files = no

; \-= WINDOWS PARAMETER =-/
; =========================

; Specifies the charset that samba will use to print messages to stdout and stderr
#display charset = "LOCALE" or "ASCII" (depending on the system)
; This option specifies which charset Samba should talk to DOS clients
#dos charset = # No default
; Enabling this parameter allows a user who has write access to the file (by whatever means) to modify the permissions
#dos filemode = no

; \-= NETWORK/CONNECTION PARAMETER =-/
; ====================================

; This controls what workgroup your server will appear to be in when queried by clients
workgroup = KlingKlang
; This controls what string will show up in the printer comment box in print manager and next to the IPC connection in net view
server string = FileDealer
; This sets the NetBIOS name by which a Samba server is known
netbios name = FileDealer
#netbios aliases = 

; -= Interface Settings =-
; This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service
hosts allow = 127.0.0.1 192.168.
hosts deny  = ALL

; -= Connection Options =-
; Represents the number of minutes of inactivity before a connection is considered dead and disconnected
#deadtime        = 0 
; The value of the parameter (an integer) represents the number of seconds between keepalive packets
#keepalive       = 300
; This option allows the number of simultaneous connections to a service
#max connections = 0
; This option allows you to set socket options to be used when talking with the client
socket options   = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536

; \-= OTHER PARAMETER =-/
; =======================

security = user

; Enabling this parameter will disable netbios support in Samba
disable netbios = yes
; Do a lookup with the DNS server
dns proxy = no

; -= SMBpasswd Settings =-
; This option allows the administrator to chose which backend will be used for storing user and possibly group information
#passdb backend = smbpasswd:/etc/samba/private/smbpasswd
; This option sets the path to the encrypted smbpasswd file
#smb passwd file = /etc/samba/private/smbpasswd

; -= Directory Settings =-
; This option specifies the directory where lock files will be placed
#lock directory = /var/lock
; This parameters defines the directory smbd will use for storing such files as smbpasswd and secrets.tdb
#private dir = /etc/samba/private

; -= Logging Settings =-
; This option allows you to override the name of the Samba log file
log file = /var/log/samba/samba.%m
; This option (an integer in kilobytes) specifies the max size the log file should grow to
max log size = 5000
; Parameter maps how Samba debug messages are logged onto the system
#syslog = 1
; Parameter is set then Samba debug messages are logged into the system syslog only
#syslog only = no

; Using the following line enables you to customise your configuration on a per machine
; basis. The %m gets replaced with the netbios name of the machine that is connecting.
; Note: Consider carefully the location in the configuration file of
;       this line.  The included file is read at that point.
#include = /etc/samba/smb.conf.%m

; ===========================
; #   -   S H A R E S   -   #
; ===========================

[homes]
comment    = Eigene Dateien

guest ok   = yes
read only  = no
browseable = no

[printers]
comment    = Drucker
path       = /var/spool/samba

browseable = no
available  = no
guest ok   = no
printable  = yes

[BitHalde]
comment   = 3TB
path      = /mnt/raid

guest ok  = yes
read only = yes
&lt;/pre&gt;

==== smb.conf w/o comments ====
&lt;pre&gt;[global]
        workgroup = KLINGKLANG
        server string = FileDealer
        map to guest = Bad User
        guest account = guest
        log file = /var/log/samba/samba.%m
        disable netbios = Yes
        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536
        load printers = No
        show add printer wizard = No
        dns proxy = No
        invalid users = root, nobody, ftp, adm, apache, bin, daemon, games, gdm, haldaemon, halt, lp, mail, messagebus, mysql, news, operator, pop, rpc, shutdown, smmsp, sshd, sync, uucp
        valid users = evo, guest
        admin users = evo
        read list = evo, guest
        write list = evo
        force group = users
        hosts allow = 127.0.0.1, 192.168.
        hosts deny = ALL
        wide links = No
        follow symlinks = No
        dont descend = /bin,/boot,/dev,/etc,/lib,/opt,/proc,/sbin,/srv,/sys,/tmp,/usr,/var

[homes]
        comment = Eigene Dateien
        read only = No
        guest ok = Yes
        browseable = No

[printers]
        comment = Drucker
        path = /var/spool/samba
        printable = Yes
        browseable = No
        available = No

[BitHalde]
        comment = 3TB
        path = /mnt/raid
        guest ok = Yes
&lt;/pre&gt;

== Using Samba ==

In this section we will have a look on how to restart, stop, and start the samba server.

=== Starting and Stopping Samba ===

In Slackware, the script /etc/rc.d/rc.samba controls the state of the samba server. Below are the three commands you can use (as root).

To restart samba use:
&lt;code&gt;/etc/rc.d/rc.samba restart &lt;/code&gt;

To stop samba use:
&lt;code&gt;/etc/rc.d/rc.samba stop &lt;/code&gt;

To start samba from a stopped state use:
&lt;code&gt;/etc/rc.d/rc.samba start &lt;/code&gt;

The rc.samba script described above is merely a convenient wrapper for the /usr/sbin/smbd and /usr/sbin/nmdb commands. For example, you could also start the samba server by using these two commands together:
&lt;pre&gt;#/usr/sbin/smbd -D
#/usr/sbin/nmbd -D
&lt;/pre&gt;

See the man pages for smbd and nmbd for details.
== Testing and Troubleshooting ==

In this section we will have a look on how we test our configuration and what to do if we ran into problems.

=== Using ''testparm'' ===

&lt;blockquote&gt;testparm — check an smb.conf configuration file for internal correctness&lt;/blockquote&gt;

*: If your done with the setup of your ''smb.conf'' you should run ''testparm''. Do this by simply typing it ;)
&lt;pre&gt;$ testparm
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
NOTE: Service printers is flagged unavailable.
Processing section "[BitHalde]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions&lt;/pre&gt;
:: Normally this is what the output should look like. By pressing enter you will get a list of all used parameters in smb.conf.

*: If you wish to have a complete list of all options and how they are set:
&lt;pre&gt;$ testparm -v&lt;/pre&gt;

=== Using ''smbclient'' ===

&lt;blockquote&gt;smbclient — ftp-like client to access SMB/CIFS resources on servers&lt;/blockquote&gt;

* Connecting as a guest and list all shares
&lt;pre&gt;$ smbclient -L localhost -N
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Sharename       Type      Comment
        ---------       ----      -------
        BitHalde        Disk      3TB
        IPC$            IPC       IPC Service (FileDealer)
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        KLINGKLANG           FILEDEALER&lt;/pre&gt;
&lt;blockquote&gt;-L ''host'' This option allows you to look at what services are available on a server.&lt;br/&gt;
-N Suppresses the normal password prompt. Useful when accessing a service that does not require a password.&lt;/blockquote&gt;

* Connecting with a specified username and list all shares
&lt;pre&gt;$ smbclient -L localhost -U evo
Password:
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Sharename       Type      Comment
        ---------       ----      -------
        BitHalde        Disk      3TB
        IPC$            IPC       IPC Service (FileDealer)
        evo             Disk      Eigene Dateien
Domain=[FILEDEALER] OS=[Unix] Server=[Samba 3.0.30]

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        KLINGKLANG           FILEDEALER&lt;/pre&gt;
&lt;blockquote&gt;-U Sets the SMB username or username and password.&lt;/blockquote&gt;

== To Do ==
* alle user eintragen (cat /etc/passwd | cut -d':' -f1 | sort)
* user scripte vervollständigen
* masken richten + upload beim gast/evo gehört root? warum das?
* was ist mit umlauten?
* --&gt; wie starten? rc.samba
* Testmethoden aus dem samba buch einfügen</text>
    <sha1>1804b150b44482aa3e18e419c452807b72f2c872</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>448</id>
    <parentid>305</parentid>
    <timestamp>2011-01-15T13:35:41Z</timestamp>
    <contributor>
      <username>Natex</username>
      <id>157</id>
    </contributor>
    <minor/>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1416" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]
* [[User:natex|natex]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>8d3f658def79fdf6f18d6127dfe54a96990817dc</sha1>
  </revision>
  <revision>
    <id>455</id>
    <parentid>448</parentid>
    <timestamp>2011-02-18T08:40:05Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1453" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]
* [[User:natex|natex]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>f3173df5d143c44b3c693fef3ec951bfb8f1dd73</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>User talk:Balsa</title>
  <ns>3</ns>
  <id>236</id>
  <revision>
    <id>450</id>
    <timestamp>2011-02-03T08:28:32Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <comment>Discussed arecord and got it to record some microphone audio.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2873" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


ALSA
/etc/asound.names
    Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf
    I do not know what this is currently.

/etc/asound.state
    Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;
    Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;
    Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  
                name 'hw:0,4'
                comment 'Physical Device - ALC268 Analog (Capture)'
--
                name 'plughw:0,4'
                comment 'Physical Device With Conversions - ALC268 Analog (Capture)'

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au
Hot dog it worked!
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3

sox test5.au -d  --&gt; Lots of clipping, noisy.
sox au: header size 24 is too small

Input File     : 'test5.au'
Channels       : 1
Sample Rate    : 8000
Precision      : 8-bit
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors
Sample Encoding: 8-bit Signed Integer PCM

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k
sox effects: rate clipped 120593 samples; decrease volume?
sox sox: alsa: output clipped 61507 samples; decrease volume?
Done.

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d
sox formats_i: `test5.au': overriding encoding type
Sample Encoding: 8-bit Unsigned Integer PCM
OK, it plays as unsigned 8bit.  Success.</text>
    <sha1>3df007c6d43cf94ad57e3c1dc0e78989a36bd33d</sha1>
  </revision>
  <revision>
    <id>451</id>
    <parentid>450</parentid>
    <timestamp>2011-02-04T03:36:51Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>some formatting cleanup</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3046" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
    Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
    I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
    Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
    Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
    Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
                name 'hw:0,4'&lt;br/&gt;
                comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
                name 'plughw:0,4'&lt;br/&gt;
                comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;</text>
    <sha1>386afcef9cc942ef98d54e3fb4fde0df800f5647</sha1>
  </revision>
  <revision>
    <id>452</id>
    <parentid>451</parentid>
    <timestamp>2011-02-04T03:46:40Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>more formatting cleanup</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2962" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;</text>
    <sha1>7b03d1d213fa91ba642f4ac855deb295299c2ae9</sha1>
  </revision>
  <revision>
    <id>457</id>
    <parentid>452</parentid>
    <timestamp>2011-02-20T21:15:06Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>/* Simple tests from command line */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3846" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)</text>
    <sha1>a4f907968d137e4dcdd5bfaacffc816dbb6f14e9</sha1>
  </revision>
  <revision>
    <id>458</id>
    <parentid>457</parentid>
    <timestamp>2011-02-20T22:24:21Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>/* Exim - local mail only - setup and testing */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5493" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.</text>
    <sha1>c97e3de5ae6a7bdb72b13b5ecc771c1303fe505e</sha1>
  </revision>
  <revision>
    <id>459</id>
    <parentid>458</parentid>
    <timestamp>2011-02-21T18:17:52Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>/* Octave: simple functions */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7040" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

== Octave: simple functions ==

Find the Octave tutorial by typing doc at the Octave command line.&lt;br&gt;
Navigate to * Introduction::                A brief introduction to Octave.&lt;br&gt;
Then go to * Simple Examples::&lt;br&gt;
The tutorial is quite brief, and gives few examples of functions.&lt;br&gt;
This page will demo how to make simple functions, and how to call one function from another.&lt;br&gt;

octave:11&gt; function fn = fn ( p )&lt;br&gt;
&gt; fn = p*20&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:10&gt; function sn = sn ( a )&lt;br&gt;
&gt; sn = a * (1/2)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:12&gt; function tn = tn( p, a )&lt;br&gt;
&gt; tn = sn(a)+fn(p)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:17&gt; function excess = excess( p, a, bs )&lt;br&gt;
&gt; excess = bs - tn(p,a)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:18&gt; excess(p,a,bs)&lt;br&gt;
sn =  517.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2657.5&lt;br&gt;
excess = -1452.5&lt;br&gt;
ans = -1452.5&lt;br&gt;

octave:28&gt; function trade = trade ( p, a, bs, lt )&lt;br&gt;
&gt; trade = excess(p,a,bs)/lt&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:26&gt; function newacres = newacres (p, a, bs, lt, na )&lt;br&gt;
&gt; newacres = a+trade(p,a,bs,lt)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:36&gt; p=107; a=1013; bs=3017; lt=25;&lt;br&gt;
octave:37&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  506.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2646.5&lt;br&gt;
excess =  370.50&lt;br&gt;
trade =  14.820&lt;br&gt;
newacres =  1027.8&lt;br&gt;
ans =  1027.8&lt;br&gt;
octave:38&gt; p=114; a=1027; bs=3095; lt=23;&lt;br&gt;
octave:39&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  513.50&lt;br&gt;
fn =  2280&lt;br&gt;
tn =  2793.5&lt;br&gt;
excess =  301.50&lt;br&gt;
trade =  13.109&lt;br&gt;
newacres =  1040.1&lt;br&gt;
ans =  1040.1&lt;br&gt;

--[[User:Balsa|Balsa]] 13:17, 21 February 2011 (EST)</text>
    <sha1>f2e51ca13cf5501c85f75a29dce6af8887873b4c</sha1>
  </revision>
  <revision>
    <id>460</id>
    <parentid>459</parentid>
    <timestamp>2011-02-21T18:23:27Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>/* Getmail */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7420" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

== Octave: simple functions ==

Find the Octave tutorial by typing doc at the Octave command line.&lt;br&gt;
Navigate to * Introduction::                A brief introduction to Octave.&lt;br&gt;
Then go to * Simple Examples::&lt;br&gt;
The tutorial is quite brief, and gives few examples of functions.&lt;br&gt;
This page will demo how to make simple functions, and how to call one function from another.&lt;br&gt;

octave:11&gt; function fn = fn ( p )&lt;br&gt;
&gt; fn = p*20&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:10&gt; function sn = sn ( a )&lt;br&gt;
&gt; sn = a * (1/2)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:12&gt; function tn = tn( p, a )&lt;br&gt;
&gt; tn = sn(a)+fn(p)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:17&gt; function excess = excess( p, a, bs )&lt;br&gt;
&gt; excess = bs - tn(p,a)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:18&gt; excess(p,a,bs)&lt;br&gt;
sn =  517.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2657.5&lt;br&gt;
excess = -1452.5&lt;br&gt;
ans = -1452.5&lt;br&gt;

octave:28&gt; function trade = trade ( p, a, bs, lt )&lt;br&gt;
&gt; trade = excess(p,a,bs)/lt&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:26&gt; function newacres = newacres (p, a, bs, lt, na )&lt;br&gt;
&gt; newacres = a+trade(p,a,bs,lt)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:36&gt; p=107; a=1013; bs=3017; lt=25;&lt;br&gt;
octave:37&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  506.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2646.5&lt;br&gt;
excess =  370.50&lt;br&gt;
trade =  14.820&lt;br&gt;
newacres =  1027.8&lt;br&gt;
ans =  1027.8&lt;br&gt;
octave:38&gt; p=114; a=1027; bs=3095; lt=23;&lt;br&gt;
octave:39&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  513.50&lt;br&gt;
fn =  2280&lt;br&gt;
tn =  2793.5&lt;br&gt;
excess =  301.50&lt;br&gt;
trade =  13.109&lt;br&gt;
newacres =  1040.1&lt;br&gt;
ans =  1040.1&lt;br&gt;

--[[User:Balsa|Balsa]] 13:17, 21 February 2011 (EST)

== Getmail ==

One of getmail's biggest features is writing directly to Maildir.  This obviates the need for a Mail Transport Agent (MTA).&lt;br&gt;

In a getmail configuration file:

[destination]&lt;br&gt;
type = Maildir&lt;br&gt;
path = ~/Maildir/&lt;br&gt;

This will write your email directly to the ~/Maildir/ directory in Maildir format.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:23, 21 February 2011 (EST)</text>
    <sha1>8bc5f6d507703f50ce370dc2aaffed39558086b8</sha1>
  </revision>
  <revision>
    <id>461</id>
    <parentid>460</parentid>
    <timestamp>2011-02-21T18:34:55Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>/* Redirecting stderr and stdout to a file */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7611" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

== Octave: simple functions ==

Find the Octave tutorial by typing doc at the Octave command line.&lt;br&gt;
Navigate to * Introduction::                A brief introduction to Octave.&lt;br&gt;
Then go to * Simple Examples::&lt;br&gt;
The tutorial is quite brief, and gives few examples of functions.&lt;br&gt;
This page will demo how to make simple functions, and how to call one function from another.&lt;br&gt;

octave:11&gt; function fn = fn ( p )&lt;br&gt;
&gt; fn = p*20&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:10&gt; function sn = sn ( a )&lt;br&gt;
&gt; sn = a * (1/2)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:12&gt; function tn = tn( p, a )&lt;br&gt;
&gt; tn = sn(a)+fn(p)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:17&gt; function excess = excess( p, a, bs )&lt;br&gt;
&gt; excess = bs - tn(p,a)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:18&gt; excess(p,a,bs)&lt;br&gt;
sn =  517.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2657.5&lt;br&gt;
excess = -1452.5&lt;br&gt;
ans = -1452.5&lt;br&gt;

octave:28&gt; function trade = trade ( p, a, bs, lt )&lt;br&gt;
&gt; trade = excess(p,a,bs)/lt&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:26&gt; function newacres = newacres (p, a, bs, lt, na )&lt;br&gt;
&gt; newacres = a+trade(p,a,bs,lt)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:36&gt; p=107; a=1013; bs=3017; lt=25;&lt;br&gt;
octave:37&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  506.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2646.5&lt;br&gt;
excess =  370.50&lt;br&gt;
trade =  14.820&lt;br&gt;
newacres =  1027.8&lt;br&gt;
ans =  1027.8&lt;br&gt;
octave:38&gt; p=114; a=1027; bs=3095; lt=23;&lt;br&gt;
octave:39&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  513.50&lt;br&gt;
fn =  2280&lt;br&gt;
tn =  2793.5&lt;br&gt;
excess =  301.50&lt;br&gt;
trade =  13.109&lt;br&gt;
newacres =  1040.1&lt;br&gt;
ans =  1040.1&lt;br&gt;

--[[User:Balsa|Balsa]] 13:17, 21 February 2011 (EST)

== Getmail ==

One of getmail's biggest features is writing directly to Maildir.  This obviates the need for a Mail Transport Agent (MTA).&lt;br&gt;

In a getmail configuration file:

[destination]&lt;br&gt;
type = Maildir&lt;br&gt;
path = ~/Maildir/&lt;br&gt;

This will write your email directly to the ~/Maildir/ directory in Maildir format.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:23, 21 February 2011 (EST)

== Redirecting stderr and stdout to a file ==

/bin/true &amp;&gt; foo&lt;br&gt;

This may be helpful in the "Piping" section here on slackwiki.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:34, 21 February 2011 (EST)</text>
    <sha1>9fb8531e1b1c5ee5465c6387e08e14260705218b</sha1>
  </revision>
  <revision>
    <id>462</id>
    <parentid>461</parentid>
    <timestamp>2011-02-21T18:38:57Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>/* Sandbox and/or Editing Help pages on slackwiki? */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7887" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

== Octave: simple functions ==

Find the Octave tutorial by typing doc at the Octave command line.&lt;br&gt;
Navigate to * Introduction::                A brief introduction to Octave.&lt;br&gt;
Then go to * Simple Examples::&lt;br&gt;
The tutorial is quite brief, and gives few examples of functions.&lt;br&gt;
This page will demo how to make simple functions, and how to call one function from another.&lt;br&gt;

octave:11&gt; function fn = fn ( p )&lt;br&gt;
&gt; fn = p*20&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:10&gt; function sn = sn ( a )&lt;br&gt;
&gt; sn = a * (1/2)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:12&gt; function tn = tn( p, a )&lt;br&gt;
&gt; tn = sn(a)+fn(p)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:17&gt; function excess = excess( p, a, bs )&lt;br&gt;
&gt; excess = bs - tn(p,a)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:18&gt; excess(p,a,bs)&lt;br&gt;
sn =  517.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2657.5&lt;br&gt;
excess = -1452.5&lt;br&gt;
ans = -1452.5&lt;br&gt;

octave:28&gt; function trade = trade ( p, a, bs, lt )&lt;br&gt;
&gt; trade = excess(p,a,bs)/lt&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:26&gt; function newacres = newacres (p, a, bs, lt, na )&lt;br&gt;
&gt; newacres = a+trade(p,a,bs,lt)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:36&gt; p=107; a=1013; bs=3017; lt=25;&lt;br&gt;
octave:37&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  506.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2646.5&lt;br&gt;
excess =  370.50&lt;br&gt;
trade =  14.820&lt;br&gt;
newacres =  1027.8&lt;br&gt;
ans =  1027.8&lt;br&gt;
octave:38&gt; p=114; a=1027; bs=3095; lt=23;&lt;br&gt;
octave:39&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  513.50&lt;br&gt;
fn =  2280&lt;br&gt;
tn =  2793.5&lt;br&gt;
excess =  301.50&lt;br&gt;
trade =  13.109&lt;br&gt;
newacres =  1040.1&lt;br&gt;
ans =  1040.1&lt;br&gt;

--[[User:Balsa|Balsa]] 13:17, 21 February 2011 (EST)

== Getmail ==

One of getmail's biggest features is writing directly to Maildir.  This obviates the need for a Mail Transport Agent (MTA).&lt;br&gt;

In a getmail configuration file:

[destination]&lt;br&gt;
type = Maildir&lt;br&gt;
path = ~/Maildir/&lt;br&gt;

This will write your email directly to the ~/Maildir/ directory in Maildir format.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:23, 21 February 2011 (EST)

== Redirecting stderr and stdout to a file ==

/bin/true &amp;&gt; foo&lt;br&gt;

This may be helpful in the "Piping" section here on slackwiki.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:34, 21 February 2011 (EST)

== Sandbox and/or Editing Help pages on slackwiki? ==

If anyone knows if there exists a sandbox or an Help:Editing page here on slackwiki.org, please let me know.  If not, I might try to create one.  Advice welcome.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:38, 21 February 2011 (EST)</text>
    <sha1>b4ccf609c9d65d14a47cbbbfbe4152887fbefb66</sha1>
  </revision>
  <revision>
    <id>463</id>
    <parentid>462</parentid>
    <timestamp>2011-02-23T07:26:21Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>/* NTP log file configuration documentation */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8356" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

== Octave: simple functions ==

Find the Octave tutorial by typing doc at the Octave command line.&lt;br&gt;
Navigate to * Introduction::                A brief introduction to Octave.&lt;br&gt;
Then go to * Simple Examples::&lt;br&gt;
The tutorial is quite brief, and gives few examples of functions.&lt;br&gt;
This page will demo how to make simple functions, and how to call one function from another.&lt;br&gt;

octave:11&gt; function fn = fn ( p )&lt;br&gt;
&gt; fn = p*20&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:10&gt; function sn = sn ( a )&lt;br&gt;
&gt; sn = a * (1/2)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:12&gt; function tn = tn( p, a )&lt;br&gt;
&gt; tn = sn(a)+fn(p)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:17&gt; function excess = excess( p, a, bs )&lt;br&gt;
&gt; excess = bs - tn(p,a)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:18&gt; excess(p,a,bs)&lt;br&gt;
sn =  517.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2657.5&lt;br&gt;
excess = -1452.5&lt;br&gt;
ans = -1452.5&lt;br&gt;

octave:28&gt; function trade = trade ( p, a, bs, lt )&lt;br&gt;
&gt; trade = excess(p,a,bs)/lt&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:26&gt; function newacres = newacres (p, a, bs, lt, na )&lt;br&gt;
&gt; newacres = a+trade(p,a,bs,lt)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:36&gt; p=107; a=1013; bs=3017; lt=25;&lt;br&gt;
octave:37&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  506.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2646.5&lt;br&gt;
excess =  370.50&lt;br&gt;
trade =  14.820&lt;br&gt;
newacres =  1027.8&lt;br&gt;
ans =  1027.8&lt;br&gt;
octave:38&gt; p=114; a=1027; bs=3095; lt=23;&lt;br&gt;
octave:39&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  513.50&lt;br&gt;
fn =  2280&lt;br&gt;
tn =  2793.5&lt;br&gt;
excess =  301.50&lt;br&gt;
trade =  13.109&lt;br&gt;
newacres =  1040.1&lt;br&gt;
ans =  1040.1&lt;br&gt;

--[[User:Balsa|Balsa]] 13:17, 21 February 2011 (EST)

== Getmail ==

One of getmail's biggest features is writing directly to Maildir.  This obviates the need for a Mail Transport Agent (MTA).&lt;br&gt;

In a getmail configuration file:

[destination]&lt;br&gt;
type = Maildir&lt;br&gt;
path = ~/Maildir/&lt;br&gt;

This will write your email directly to the ~/Maildir/ directory in Maildir format.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:23, 21 February 2011 (EST)

== Redirecting stderr and stdout to a file ==

/bin/true &amp;&gt; foo&lt;br&gt;

This may be helpful in the "Piping" section here on slackwiki.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:34, 21 February 2011 (EST)

== Sandbox and/or Editing Help pages on slackwiki? ==

If anyone knows if there exists a sandbox or an Help:Editing page here on slackwiki.org, please let me know.  If not, I might try to create one.  Advice welcome.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:38, 21 February 2011 (EST)

== NTP log file configuration documentation ==

look for /usr/share/doc/ntp-doc/html/ntpd.html&lt;br&gt;
It may be in a different place.&lt;br&gt;
Use a http reader, like lynx to view it.&lt;br&gt;
Go to "The Configuration File", then "Miscellaneous Options".&lt;br&gt;

Scroll down to the "logconfig" and "logfile" headings.&lt;br&gt;

There you will find a way to eliminate the "kernel time sync status change 6001" messages from syslog.&lt;br&gt;

--[[User:Balsa|Balsa]] 02:26, 23 February 2011 (EST)</text>
    <sha1>6376f927de695bd63172e431ee45ac03982d4670</sha1>
  </revision>
  <revision>
    <id>466</id>
    <parentid>463</parentid>
    <timestamp>2011-03-20T05:47:30Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>/* ALSA */ jack UDP draft added</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9385" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;


== JACK network audio over UDP ==

On the end with the physical sound hardware (master):
jackd -r -T -d alsa -i1 -n 10 -o1 -p 4096 -r 8000 -S 
-i num input channels
-n nperiods 
-o num output channels
-p period, must be power of 2.
-r sample rate
-S prefer 16bit int over 32 bit.

Do last (third):
jack_netsource -h &lt;hostname&gt;
jack_netsource -h &lt;hostname&gt; -m 1400 -P 1 -C 1 -o 0 -i 0 -l 10 -b 16
-m set maximum transmit unit (MTU)
-P -C -o -i number of sound and midi in/out channels.
-l buffer in number of periods.
-b 16 bits per sample.
FIXME - how to set sample rate?


On the virtual end (remote):
jackd -r -d net
jackd -r -T -d net -i 1 -o 1 -I 0 -O 0 -r 8000 -p 4096 -n 10 -b 16
-r not realtime -c -a0
-T temporary, close when all clients gone.
-d net use device net.
-i -o -I -O num channels for sound/midi
-r sample rate
-p 4096 frames per period
-n 10 buffer size in num periods
-b 16 use 16 bits/sample
-c use CELT compression
-a 0 do not use autoconfig, just start
--[[User:Balsa|Balsa]] 01:47, 20 March 2011 (EDT)

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

== Octave: simple functions ==

Find the Octave tutorial by typing doc at the Octave command line.&lt;br&gt;
Navigate to * Introduction::                A brief introduction to Octave.&lt;br&gt;
Then go to * Simple Examples::&lt;br&gt;
The tutorial is quite brief, and gives few examples of functions.&lt;br&gt;
This page will demo how to make simple functions, and how to call one function from another.&lt;br&gt;

octave:11&gt; function fn = fn ( p )&lt;br&gt;
&gt; fn = p*20&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:10&gt; function sn = sn ( a )&lt;br&gt;
&gt; sn = a * (1/2)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:12&gt; function tn = tn( p, a )&lt;br&gt;
&gt; tn = sn(a)+fn(p)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:17&gt; function excess = excess( p, a, bs )&lt;br&gt;
&gt; excess = bs - tn(p,a)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:18&gt; excess(p,a,bs)&lt;br&gt;
sn =  517.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2657.5&lt;br&gt;
excess = -1452.5&lt;br&gt;
ans = -1452.5&lt;br&gt;

octave:28&gt; function trade = trade ( p, a, bs, lt )&lt;br&gt;
&gt; trade = excess(p,a,bs)/lt&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:26&gt; function newacres = newacres (p, a, bs, lt, na )&lt;br&gt;
&gt; newacres = a+trade(p,a,bs,lt)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:36&gt; p=107; a=1013; bs=3017; lt=25;&lt;br&gt;
octave:37&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  506.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2646.5&lt;br&gt;
excess =  370.50&lt;br&gt;
trade =  14.820&lt;br&gt;
newacres =  1027.8&lt;br&gt;
ans =  1027.8&lt;br&gt;
octave:38&gt; p=114; a=1027; bs=3095; lt=23;&lt;br&gt;
octave:39&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  513.50&lt;br&gt;
fn =  2280&lt;br&gt;
tn =  2793.5&lt;br&gt;
excess =  301.50&lt;br&gt;
trade =  13.109&lt;br&gt;
newacres =  1040.1&lt;br&gt;
ans =  1040.1&lt;br&gt;

--[[User:Balsa|Balsa]] 13:17, 21 February 2011 (EST)

== Getmail ==

One of getmail's biggest features is writing directly to Maildir.  This obviates the need for a Mail Transport Agent (MTA).&lt;br&gt;

In a getmail configuration file:

[destination]&lt;br&gt;
type = Maildir&lt;br&gt;
path = ~/Maildir/&lt;br&gt;

This will write your email directly to the ~/Maildir/ directory in Maildir format.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:23, 21 February 2011 (EST)

== Redirecting stderr and stdout to a file ==

/bin/true &amp;&gt; foo&lt;br&gt;

This may be helpful in the "Piping" section here on slackwiki.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:34, 21 February 2011 (EST)

== Sandbox and/or Editing Help pages on slackwiki? ==

If anyone knows if there exists a sandbox or an Help:Editing page here on slackwiki.org, please let me know.  If not, I might try to create one.  Advice welcome.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:38, 21 February 2011 (EST)

== NTP log file configuration documentation ==

look for /usr/share/doc/ntp-doc/html/ntpd.html&lt;br&gt;
It may be in a different place.&lt;br&gt;
Use a http reader, like lynx to view it.&lt;br&gt;
Go to "The Configuration File", then "Miscellaneous Options".&lt;br&gt;

Scroll down to the "logconfig" and "logfile" headings.&lt;br&gt;

There you will find a way to eliminate the "kernel time sync status change 6001" messages from syslog.&lt;br&gt;

--[[User:Balsa|Balsa]] 02:26, 23 February 2011 (EST)</text>
    <sha1>8253ae984890298c853d90c34c91dba9a7d84236</sha1>
  </revision>
  <revision>
    <id>468</id>
    <parentid>466</parentid>
    <timestamp>2011-04-08T09:02:03Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>Added link to sandbox.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9495" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;


== JACK network audio over UDP ==

On the end with the physical sound hardware (master):
jackd -r -T -d alsa -i1 -n 10 -o1 -p 4096 -r 8000 -S 
-i num input channels
-n nperiods 
-o num output channels
-p period, must be power of 2.
-r sample rate
-S prefer 16bit int over 32 bit.

Do last (third):
jack_netsource -h &lt;hostname&gt;
jack_netsource -h &lt;hostname&gt; -m 1400 -P 1 -C 1 -o 0 -i 0 -l 10 -b 16
-m set maximum transmit unit (MTU)
-P -C -o -i number of sound and midi in/out channels.
-l buffer in number of periods.
-b 16 bits per sample.
FIXME - how to set sample rate?


On the virtual end (remote):
jackd -r -d net
jackd -r -T -d net -i 1 -o 1 -I 0 -O 0 -r 8000 -p 4096 -n 10 -b 16
-r not realtime -c -a0
-T temporary, close when all clients gone.
-d net use device net.
-i -o -I -O num channels for sound/midi
-r sample rate
-p 4096 frames per period
-n 10 buffer size in num periods
-b 16 use 16 bits/sample
-c use CELT compression
-a 0 do not use autoconfig, just start
--[[User:Balsa|Balsa]] 01:47, 20 March 2011 (EDT)

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

== Octave: simple functions ==

Find the Octave tutorial by typing doc at the Octave command line.&lt;br&gt;
Navigate to * Introduction::                A brief introduction to Octave.&lt;br&gt;
Then go to * Simple Examples::&lt;br&gt;
The tutorial is quite brief, and gives few examples of functions.&lt;br&gt;
This page will demo how to make simple functions, and how to call one function from another.&lt;br&gt;

octave:11&gt; function fn = fn ( p )&lt;br&gt;
&gt; fn = p*20&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:10&gt; function sn = sn ( a )&lt;br&gt;
&gt; sn = a * (1/2)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:12&gt; function tn = tn( p, a )&lt;br&gt;
&gt; tn = sn(a)+fn(p)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:17&gt; function excess = excess( p, a, bs )&lt;br&gt;
&gt; excess = bs - tn(p,a)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:18&gt; excess(p,a,bs)&lt;br&gt;
sn =  517.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2657.5&lt;br&gt;
excess = -1452.5&lt;br&gt;
ans = -1452.5&lt;br&gt;

octave:28&gt; function trade = trade ( p, a, bs, lt )&lt;br&gt;
&gt; trade = excess(p,a,bs)/lt&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:26&gt; function newacres = newacres (p, a, bs, lt, na )&lt;br&gt;
&gt; newacres = a+trade(p,a,bs,lt)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:36&gt; p=107; a=1013; bs=3017; lt=25;&lt;br&gt;
octave:37&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  506.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2646.5&lt;br&gt;
excess =  370.50&lt;br&gt;
trade =  14.820&lt;br&gt;
newacres =  1027.8&lt;br&gt;
ans =  1027.8&lt;br&gt;
octave:38&gt; p=114; a=1027; bs=3095; lt=23;&lt;br&gt;
octave:39&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  513.50&lt;br&gt;
fn =  2280&lt;br&gt;
tn =  2793.5&lt;br&gt;
excess =  301.50&lt;br&gt;
trade =  13.109&lt;br&gt;
newacres =  1040.1&lt;br&gt;
ans =  1040.1&lt;br&gt;

--[[User:Balsa|Balsa]] 13:17, 21 February 2011 (EST)

== Getmail ==

One of getmail's biggest features is writing directly to Maildir.  This obviates the need for a Mail Transport Agent (MTA).&lt;br&gt;

In a getmail configuration file:

[destination]&lt;br&gt;
type = Maildir&lt;br&gt;
path = ~/Maildir/&lt;br&gt;

This will write your email directly to the ~/Maildir/ directory in Maildir format.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:23, 21 February 2011 (EST)

== Redirecting stderr and stdout to a file ==

/bin/true &amp;&gt; foo&lt;br&gt;

This may be helpful in the "Piping" section here on slackwiki.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:34, 21 February 2011 (EST)

== Sandbox and/or Editing Help pages on slackwiki? ==

If anyone knows if there exists a sandbox or an Help:Editing page here on slackwiki.org, please let me know.  If not, I might try to create one.  Advice welcome.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:38, 21 February 2011 (EST)

A [[User:Balsa/Sandbox|sand-filled box]] labelled "Testing"
--[[User:Balsa|Balsa]] 05:02, 8 April 2011 (EDT)

== NTP log file configuration documentation ==

look for /usr/share/doc/ntp-doc/html/ntpd.html&lt;br&gt;
It may be in a different place.&lt;br&gt;
Use a http reader, like lynx to view it.&lt;br&gt;
Go to "The Configuration File", then "Miscellaneous Options".&lt;br&gt;

Scroll down to the "logconfig" and "logfile" headings.&lt;br&gt;

There you will find a way to eliminate the "kernel time sync status change 6001" messages from syslog.&lt;br&gt;

--[[User:Balsa|Balsa]] 02:26, 23 February 2011 (EST)</text>
    <sha1>9758cf230d495f1c24840c2028a4fd25a29487ae</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>VirtualBox Compilation</title>
  <ns>0</ns>
  <id>237</id>
  <revision>
    <id>453</id>
    <timestamp>2011-02-09T03:11:01Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Created page with "[[category:tutorials]] '''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions * Open Sour..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3086" xml:space="preserve">[[category:tutorials]]
'''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions
* Open Source Edition (OSE) - open-source licensed under GPLv2 
* Personal Use and Evaluation License (PUEL) - closed-source with additional features (USB support, Remote desktop support, ...)

== Disclaimer ==
This tutorial applies to slackware-''current'' (-current after stable versions 13.1) and VirtualBox 4.0.x OSE

== Prerequisites ==
See this [http://www.virtualbox.org/wiki/Linux%20build%20instructions list]

Below lies additional, not obvious or not mentioned prerequisites. 

=== Source packages ===
* VirtualBox - get it here: [http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-4.0.2.tar.bz2 http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-x.y.z.tar.bz2] where x.y.z stands for version numbers (eg. 4.0.2)
* PulseAudio - no SlackBuild available (note: applies to 09-01-2010); download sources from [http://www.pulseaudio.org http://www.pulseaudio.org]
* makeself - get it here: [http://megastep.org/makeself/ http://megastep.org/makeself/]

=== Slackware packages ===
* jdk
* gcc-java

=== SlackBuilds ===
* iasl - contained in SlackBuild [http://slackbuilds.org/repository/13.1/development/acpica/ acpica]

== Compilation ==
Unpack sources somewhere
&lt;pre&gt;
tar xjvf VirtualBox-x.y.z.tar.bz2 -C build/
cd build/VirtualBox-x.y.z_OSE/
&lt;/pre&gt;

Run configure script which will generate Makefile.kmk and env.sh scripts
&lt;pre&gt;
$ ./configure --nofatal --disable-hardening --disable-docs
&lt;/pre&gt;
&lt;code&gt;--nofatal&lt;/code&gt; configure won't stop on non-fatal errors; it usually fails on &lt;code&gt;makeself variable&lt;/code&gt; 

&lt;code&gt;--disable-hardening&lt;/code&gt; - set some environment variable; use when you don't want to build package

&lt;code&gt;--disable-docs&lt;/code&gt; - for some reason, build fails when building documentation. If you don't mind using online documentation it's safe to disable building it

Update build environment variables with auto-generated script
&lt;pre&gt;
$ source ./env.sh
&lt;/pre&gt;

Now it's time to compile sources, but there are few pitfalls
==== PAM ====
Slackware doesn't ship PAM, so you have to change one line in Config.kmk to disable it
&lt;pre&gt;
if1of ($(KBUILD_TARGET), linux solaris)
 # VBOX_WITH_PAM = 1
 VBOX_WITH_PAM = 
endif
&lt;/pre&gt;

Note: It's really blank space, 0 doesn't work as logical False

==== Java path ====
Inside Config.kmk there is block with few possible locations of JDK binaries. Unfortunately, JDK in Slackware has different path, so you have to add right path.  
&lt;pre&gt;
ifeq ($(KBUILD_TARGET),linux)
  ifeq ($(origin VBOX_JAVA_HOME),undefined)
   # Add correct detection for you distro after the /usr/../java-6-sun line.
   # Slackware JDK resides in /usr/lib/jdk1.6.0_23 (JDK 1.6 update 23; type what version suits you) 
   VBOX_JAVA_HOME := $(firstword $(wildcard \
	$(PATH_DEVTOOLS)/linux.x86/jdk1.6.0_21 \
	/usr/lib/jvm/java-6-sun  \
	/usr/lib/jvm/java-6-openjdk \
	/usr/lib/jdk1.6.0_23 \
	/usr/lib/jvm/sun-jdk-1.6 \
	) /usr/lib/jvm/java-6-sun)
  endif
 endif
&lt;/pre&gt;</text>
    <sha1>0827be8f254126d14b8b6a3ec5b23e15cf3d624b</sha1>
  </revision>
  <revision>
    <id>454</id>
    <parentid>453</parentid>
    <timestamp>2011-02-09T03:16:01Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>add missing step + few minor changes</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3237" xml:space="preserve">[[category:tutorials]]
'''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions
* Open Source Edition (OSE) - open-source licensed under GPLv2 
* Personal Use and Evaluation License (PUEL) - closed-source with additional features (USB support, Remote desktop support, ...)

== Disclaimer ==
This tutorial applies to slackware-''current'' (-current after stable versions 13.1) and VirtualBox 4.0.x OSE

== Prerequisites ==
See this [http://www.virtualbox.org/wiki/Linux%20build%20instructions list]

Below lies additional, not obvious or not mentioned prerequisites. 

=== Source packages ===
* VirtualBox - get it here: [http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-4.0.2.tar.bz2 http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-x.y.z.tar.bz2] where x.y.z stands for version numbers (eg. 4.0.2)
* PulseAudio - no SlackBuild available (note: applies to 09-01-2010); download sources from [http://www.pulseaudio.org http://www.pulseaudio.org]
* makeself - get it here: [http://megastep.org/makeself/ http://megastep.org/makeself/]

=== Slackware packages ===
* jdk
* gcc-java

=== SlackBuilds ===
* iasl - contained in SlackBuild [http://slackbuilds.org/repository/13.1/development/acpica/ acpica]

== Compilation ==
Unpack sources somewhere
&lt;pre&gt;
tar xjvf VirtualBox-x.y.z.tar.bz2 -C build/
cd build/VirtualBox-x.y.z_OSE/
&lt;/pre&gt;

Run configure script which will generate Makefile.kmk and env.sh scripts
&lt;pre&gt;
$ ./configure --nofatal --disable-hardening --disable-docs
&lt;/pre&gt;
&lt;code&gt;--nofatal&lt;/code&gt; configure won't stop on non-fatal errors; it usually fails on &lt;code&gt;makeself variable&lt;/code&gt; 

&lt;code&gt;--disable-hardening&lt;/code&gt; - set some environment variable; use when you don't want to build package

&lt;code&gt;--disable-docs&lt;/code&gt; - for some reason, build fails when building documentation. If you don't mind using online documentation it's safe to disable building it

Update build environment variables with auto-generated script
&lt;pre&gt;
$ source ./env.sh
&lt;/pre&gt;

Now it's time to compile sources, but there are few pitfalls

=== Troubleshooting &amp; Pitfalls ===
==== PAM ====
Slackware doesn't ship PAM, so you have to change one line in Config.kmk to disable it
&lt;pre&gt;
if1of ($(KBUILD_TARGET), linux solaris)
 # VBOX_WITH_PAM = 1
 VBOX_WITH_PAM = 
endif
&lt;/pre&gt;

Note: It's really blank space, 0 doesn't work as logical False

==== Java path ====
Inside Config.kmk there is block with few possible locations of JDK binaries. Unfortunately, JDK in Slackware has different path, so you have to add right path.  
&lt;pre&gt;
ifeq ($(KBUILD_TARGET),linux)
  ifeq ($(origin VBOX_JAVA_HOME),undefined)
   # Add correct detection for you distro after the /usr/../java-6-sun line.
   # Slackware JDK resides in /usr/lib/jdk1.6.0_23 (JDK 1.6 update 23; type what version suits you) 
   VBOX_JAVA_HOME := $(firstword $(wildcard \
	$(PATH_DEVTOOLS)/linux.x86/jdk1.6.0_21 \
	/usr/lib/jvm/java-6-sun  \
	/usr/lib/jvm/java-6-openjdk \
	/usr/lib/jdk1.6.0_23 \
	/usr/lib/jvm/sun-jdk-1.6 \
	) /usr/lib/jvm/java-6-sun)
  endif
 endif
&lt;/pre&gt;

=== Build ===
Everything should be prepared by now. Type following command to build VirtualBox
&lt;pre&gt;
$ kmk
&lt;/pre&gt;</text>
    <sha1>c4d8f6e15a463bfddf127cd71a9d44e1751f4014</sha1>
  </revision>
  <revision>
    <id>464</id>
    <parentid>454</parentid>
    <timestamp>2011-02-27T01:15:12Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>little update; not complete yet</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3643" xml:space="preserve">[[category:tutorials]]
'''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions
* Open Source Edition (OSE) - open-source licensed under GPLv2 
* Personal Use and Evaluation License (PUEL) - closed-source with additional features (USB support, Remote desktop support, ...)

== Disclaimer ==
This tutorial applies to slackware-''current'' (-current after stable versions 13.1) and VirtualBox 4.0.x OSE

== Prerequisites ==
See this [http://www.virtualbox.org/wiki/Linux%20build%20instructions list]

Below lies additional, not obvious or not mentioned prerequisites. 

=== Source packages ===
* VirtualBox - get it here: [http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-4.0.2.tar.bz2 http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-x.y.z.tar.bz2] where x.y.z stands for version numbers (eg. 4.0.2)
* PulseAudio - no SlackBuild available (note: applies to 09-01-2010); download sources from [http://www.pulseaudio.org http://www.pulseaudio.org]
* makeself - get it here: [http://megastep.org/makeself/ http://megastep.org/makeself/]

=== Slackware packages ===
* jdk
* gcc-java

=== SlackBuilds ===
* iasl - contained in SlackBuild [http://slackbuilds.org/repository/13.1/development/acpica/ acpica]

== Compilation ==
Unpack sources somewhere
&lt;pre&gt;
tar xjvf VirtualBox-x.y.z.tar.bz2 -C build/
cd build/VirtualBox-x.y.z_OSE/
&lt;/pre&gt;

Run configure script which will generate Makefile.kmk and env.sh scripts
&lt;pre&gt;
$ ./configure --nofatal --disable-hardening --disable-docs
&lt;/pre&gt;
&lt;code&gt;--nofatal&lt;/code&gt; configure won't stop on non-fatal errors; it usually fails on &lt;code&gt;makeself&lt;/code&gt; variable 

&lt;code&gt;--disable-hardening&lt;/code&gt; - automatically set few symbolic links so you can run VirtualBox binaries from bin/ directory of your build environment; '''don't''' use this switch if you're building package for redistribution

&lt;code&gt;--disable-docs&lt;/code&gt; - for some reason, build fails when building documentation. If you don't mind using online documentation it's safe to disable building it

Update build environment variables with auto-generated script
&lt;pre&gt;
$ source ./env.sh
&lt;/pre&gt;

Now it's time to compile sources, but there are few pitfalls

=== Troubleshooting &amp; Pitfalls ===
==== PAM ====
Slackware doesn't ship PAM, so you have to change one line in Config.kmk to disable it
&lt;pre&gt;
if1of ($(KBUILD_TARGET), linux solaris)
 # VBOX_WITH_PAM = 1
 VBOX_WITH_PAM = 
endif
&lt;/pre&gt;

Note: It's really blank space, 0 doesn't work as logical False

==== Java path ====
Inside Config.kmk there is block with few possible locations of JDK binaries. Unfortunately, JDK in Slackware has different path, so you have to add right path.  
&lt;pre&gt;
ifeq ($(KBUILD_TARGET),linux)
  ifeq ($(origin VBOX_JAVA_HOME),undefined)
   # Add correct detection for you distro after the /usr/../java-6-sun line.
   # Slackware JDK resides in /usr/lib/jdk1.6.0_23 (JDK 1.6 update 23; type what version suits you) 
   VBOX_JAVA_HOME := $(firstword $(wildcard \
	$(PATH_DEVTOOLS)/linux.x86/jdk1.6.0_21 \
	/usr/lib/jvm/java-6-sun  \
	/usr/lib/jvm/java-6-openjdk \
	/usr/lib/jdk1.6.0_23 \
	/usr/lib/jvm/sun-jdk-1.6 \
	) /usr/lib/jvm/java-6-sun)
  endif
 endif
&lt;/pre&gt;

=== Build ===
Everything should be prepared by now. Type following command to build VirtualBox
&lt;pre&gt;
$ kmk
&lt;/pre&gt;

Build VirtualBox kernel module
&lt;pre&gt;
$ cd out/linux.x86/release/bin/src
$ make
$ su
&lt;password&gt;
$ make install
$ cd ..
&lt;/pre&gt;

Load kernel module (as root)
&lt;pre&gt;
$ modprobe vboxdrv
&lt;/pre&gt;

Now you can start VirtualBox front-end from local bin/ directory
&lt;pre&gt;
$ ./VirtualBox
&lt;/pre&gt;</text>
    <sha1>f9aa19a84c606f2d4ab862a4a779a12c51b7057e</sha1>
  </revision>
  <revision>
    <id>470</id>
    <parentid>464</parentid>
    <timestamp>2011-04-10T13:33:04Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>/* Source packages */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3643" xml:space="preserve">[[category:tutorials]]
'''VirtualBox''' is a general-purpose full virtualizer for x86 hardware, targeted at server, desktop and embedded use. It comes in two editions
* Open Source Edition (OSE) - open-source licensed under GPLv2 
* Personal Use and Evaluation License (PUEL) - closed-source with additional features (USB support, Remote desktop support, ...)

== Disclaimer ==
This tutorial applies to slackware-''current'' (-current after stable versions 13.1) and VirtualBox 4.0.x OSE

== Prerequisites ==
See this [http://www.virtualbox.org/wiki/Linux%20build%20instructions list]

Below lies additional, not obvious or not mentioned prerequisites. 

=== Source packages ===
* VirtualBox - get it here: [http://download.virtualbox.org/virtualbox/4.0.2/VirtualBox-4.0.2.tar.bz2 http://download.virtualbox.org/virtualbox/x.y.z/VirtualBox-x.y.z.tar.bz2] where x.y.z stands for version numbers (eg. 4.0.2)
* PulseAudio - no SlackBuild available (note: applies to 09-01-2010); download sources from [http://www.pulseaudio.org http://www.pulseaudio.org]
* makeself - get it here: [http://megastep.org/makeself/ http://megastep.org/makeself/]

=== Slackware packages ===
* jdk
* gcc-java

=== SlackBuilds ===
* iasl - contained in SlackBuild [http://slackbuilds.org/repository/13.1/development/acpica/ acpica]

== Compilation ==
Unpack sources somewhere
&lt;pre&gt;
tar xjvf VirtualBox-x.y.z.tar.bz2 -C build/
cd build/VirtualBox-x.y.z_OSE/
&lt;/pre&gt;

Run configure script which will generate Makefile.kmk and env.sh scripts
&lt;pre&gt;
$ ./configure --nofatal --disable-hardening --disable-docs
&lt;/pre&gt;
&lt;code&gt;--nofatal&lt;/code&gt; configure won't stop on non-fatal errors; it usually fails on &lt;code&gt;makeself&lt;/code&gt; variable 

&lt;code&gt;--disable-hardening&lt;/code&gt; - automatically set few symbolic links so you can run VirtualBox binaries from bin/ directory of your build environment; '''don't''' use this switch if you're building package for redistribution

&lt;code&gt;--disable-docs&lt;/code&gt; - for some reason, build fails when building documentation. If you don't mind using online documentation it's safe to disable building it

Update build environment variables with auto-generated script
&lt;pre&gt;
$ source ./env.sh
&lt;/pre&gt;

Now it's time to compile sources, but there are few pitfalls

=== Troubleshooting &amp; Pitfalls ===
==== PAM ====
Slackware doesn't ship PAM, so you have to change one line in Config.kmk to disable it
&lt;pre&gt;
if1of ($(KBUILD_TARGET), linux solaris)
 # VBOX_WITH_PAM = 1
 VBOX_WITH_PAM = 
endif
&lt;/pre&gt;

Note: It's really blank space, 0 doesn't work as logical False

==== Java path ====
Inside Config.kmk there is block with few possible locations of JDK binaries. Unfortunately, JDK in Slackware has different path, so you have to add right path.  
&lt;pre&gt;
ifeq ($(KBUILD_TARGET),linux)
  ifeq ($(origin VBOX_JAVA_HOME),undefined)
   # Add correct detection for you distro after the /usr/../java-6-sun line.
   # Slackware JDK resides in /usr/lib/jdk1.6.0_23 (JDK 1.6 update 23; type what version suits you) 
   VBOX_JAVA_HOME := $(firstword $(wildcard \
	$(PATH_DEVTOOLS)/linux.x86/jdk1.6.0_21 \
	/usr/lib/jvm/java-6-sun  \
	/usr/lib/jvm/java-6-openjdk \
	/usr/lib/jdk1.6.0_23 \
	/usr/lib/jvm/sun-jdk-1.6 \
	) /usr/lib/jvm/java-6-sun)
  endif
 endif
&lt;/pre&gt;

=== Build ===
Everything should be prepared by now. Type following command to build VirtualBox
&lt;pre&gt;
$ kmk
&lt;/pre&gt;

Build VirtualBox kernel module
&lt;pre&gt;
$ cd out/linux.x86/release/bin/src
$ make
$ su
&lt;password&gt;
$ make install
$ cd ..
&lt;/pre&gt;

Load kernel module (as root)
&lt;pre&gt;
$ modprobe vboxdrv
&lt;/pre&gt;

Now you can start VirtualBox front-end from local bin/ directory
&lt;pre&gt;
$ ./VirtualBox
&lt;/pre&gt;</text>
    <sha1>58aa6df952022ccd419799467d4ce3e4baf7414a</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>Slack-desc</title>
  <ns>0</ns>
  <id>17</id>
  <revision>
    <id>465</id>
    <parentid>252</parentid>
    <timestamp>2011-03-19T12:51:24Z</timestamp>
    <contributor>
      <username>Alienbob</username>
      <id>9</id>
    </contributor>
    <comment>Define the layout of the slack-desc's first line.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1857" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: appname (Short description of the application)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname:
 appname: It's a good idea to include a link to the application's homepage too.
 appname:

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 2,9 &amp; 11 should not have a space after the :

=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>e88c3e7826710ad58f73b854e50f86d611e1ddd7</sha1>
  </revision>
  <revision>
    <id>472</id>
    <parentid>465</parentid>
    <timestamp>2011-04-16T10:49:51Z</timestamp>
    <contributor>
      <username>John Harris</username>
      <id>170</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1855" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: appname (Short description of the application)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname:
 appname: It's a good idea to include a link to the application's homepage too.
 appname:

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 &amp; 11 should not have a space after the :

=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>faf2f112bca2d0053c023fadeb6dbdceaa94e906</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>User:Balsa/Sandbox</title>
  <ns>2</ns>
  <id>239</id>
  <revision>
    <id>467</id>
    <timestamp>2011-04-08T08:56:58Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <minor/>
    <comment>A prototype sandbox.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="510" xml:space="preserve">'''Some bold text'''  
''Some italicised text''  
'''''Some bold and italicised text '''''  
&lt;s&gt;Strike-through&lt;/s&gt;&lt;br&gt;
An internal link: [[User_talk:Balsa]]&lt;br&gt;
Math:  &lt;math&gt;2+2=4&lt;/math&gt;
*A really short list&lt;br&gt;
 A space at the beginning of the line.
&lt;p&gt;A paragraph tag.  
&lt;font color="blue"&gt;  Font tag colour test. &lt;/font&gt;
{| 
| style="background:green; color:blue" | Test
|  of
| style="background:black; color:green" | Colours.
|}
A signature with timestamp: --[[User:Balsa|Balsa]] 04:56, 8 April 2011 (EDT)</text>
    <sha1>2c79fbc6b8aa028c8d67f732ba75e17e329d1297</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>Hibernate</title>
  <ns>0</ns>
  <id>223</id>
  <revision>
    <id>469</id>
    <parentid>368</parentid>
    <timestamp>2011-04-10T13:20:31Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1358" xml:space="preserve">In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

 append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''.

If you're using generic or your own kernel, you need to adjust initrd image as well. Append 

  -h /dev/sdx

to mkinitrd command so it may look like this:
 
  mkinitrd -c -k 2.6.33.4 -r /dev/sdx -f &lt;fs_type&gt; -m &lt;fs_type&gt; -h /dev/sdy

Replace ''/dev/sdx'' with your actual root partition and ''/dev/sdy'' with your actual swap space.
 
Afterwards, run lilo.

----

The above is everything I needed to do with my Slackware64 13.1 on a new laptop. I hope that works for you as well, but there are many requirements and intricacies not mentioned above. Google might help you. Please edit this document accordingly if you find out more.

Some more info at [http://www.linuxquestions.org/linux/answers/Hardware/Mini_HOW_TO_Hibernate_and_resume_0]

[[Category:Tutorials]]</text>
    <sha1>bae31355a75c9790a0b525c5e2b5ab0b61fabaf8</sha1>
  </revision>
  <revision>
    <id>471</id>
    <parentid>469</parentid>
    <timestamp>2011-04-13T11:39:54Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1451" xml:space="preserve">In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

== Huge kernel ==

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

 append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''.

== Generic kernel + initrd ==

If you're using generic or your own kernel, you need to adjust initrd image as well. Append 

  -h /dev/sdx

to mkinitrd command so it may look like this:
 
  mkinitrd -c -k 2.6.33.4 -f &lt;fs_type&gt; -m &lt;fs_type&gt; -r /dev/sdx -h /dev/sdy

Replace ''/dev/sdx'' with your actual root partition and ''/dev/sdy'' with your actual swap space.

If you're using LVM, don't forget to append '''-L''' to mkinitrd command

  mkinitrd -c -k 2.6.33.4 -f &lt;fs_type&gt; -m &lt;fs_type&gt; -r /dev/sdx -h /dev/volumegroup/swap -L

Afterwards, run lilo.

== Further reading ==

* [http://www.linuxquestions.org/linux/answers/Hardware/Mini_HOW_TO_Hibernate_and_resume_0 Mini_HOW_TO_Hibernate_and_resume_0]
* Hibernate to encrypted swap - [http://slackware.osuosl.org/slackware-13.1/README_CRYPT.TXT REAME_CRYPT.TXT]

[[Category:Tutorials]]</text>
    <sha1>a6898d54a798f54bf51a06d439975fbf20bacd73</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>Fstab</title>
  <ns>0</ns>
  <id>94</id>
  <revision>
    <id>473</id>
    <parentid>116</parentid>
    <timestamp>2011-04-19T23:08:37Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>/* Useful Examples */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3916" xml:space="preserve">The /etc/fstab file tells the system how and where to mount filesystems by default.

==Syntax==
The syntax of the file is this:

&lt;table cellspacing="10"&gt;
&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;MAN PAGE-ese:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;FS_SPEC&lt;/td&gt;
&lt;td align="center"&gt;FS_FILE&lt;/td&gt;
&lt;td align="center"&gt;FS_VFSTYPE&lt;/td&gt;
&lt;td align="center"&gt;FS_MNTOPS&lt;/td&gt;
&lt;td align="center"&gt;FS_FREQ&lt;/td&gt;
&lt;td align="center"&gt;FS_PASSNO&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;IN ENGLISH:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;DEVICE&lt;/td&gt;
&lt;td align="center"&gt;MOUNT_POINT&lt;/td&gt;
&lt;td align="center"&gt;FILESYSTEM&lt;/td&gt;
&lt;td align="center"&gt;OPTIONS&lt;/td&gt;
&lt;td align="center"&gt;DUMP&lt;/td&gt;
&lt;td align="center"&gt;FSCK_ORDER&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;EXAMPLE:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;/dev/hdb1&lt;/td&gt;
&lt;td align="center"&gt;/mnt/windows&lt;/td&gt;
&lt;td align="center"&gt;vfat&lt;/td&gt;
&lt;td align="center"&gt;default&lt;/td&gt;
&lt;td align="center"&gt;0&lt;/td&gt;
&lt;td align="center"&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;

==Field Descriptions==
FS_SPEC (DEVICE) - the device or remote filesystem to be mounted.

FS_FILE (MOUNT_POINT) - the mount point for the filesystem. &lt;i&gt;NOTE: For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces these can be escaped as `\040'.&lt;/i&gt;

FS_VFSTYPE (FILESYSTEM)-  the type of the filesystem. As of Slackware 10.2, the FILE_SYSTEM choices are:
:auto, adfs, affs, autofs, coda, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xfs, xiafs and possibly others.
&lt;i&gt;NOTE: for swap-able and portable devices (e.g. memory sticks and CDROMs), &lt;code&gt;auto&lt;/code&gt; is the best choice because it allows the computer to determine the correct filesystem.&lt;/i&gt;

FS_MNTOPS (OPTION) - the (comma seperated) mount options. See the MOUNT command's MAN PAGE for the options because there are MANY!
The most commonly used options are:&lt;br&gt;
:noauto - do not mount this device/partition automatically on boot-up.
:ro - mount this device/partition READ-ONLY (e.g. CDROM).
:owner - Only allow the owner to mount and un-mount this device/partition.
:users - Allow any user to mount or unmount this device/partition.


FS_FREQ (DUMP) - used for these filesystems by the dump command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. For the most part, this should be "0" (zero).

FS_PASSNO (FSCK_ORDER) - used by the fsck program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

==Benefits Of fstab Entries==
Once you have a device in the fstab, mounting become VERY easy.  Instead of having to:
:&lt;code&gt;mount -t iso9660 /dev/hdb1 /mnt/cdrom&lt;/code&gt;
every time you want to use the CDROM, you can just type:
:&lt;code&gt;mount /mnt/cdrom&lt;/code&gt;
IF you have the entry in your fstab.


==Useful Examples==
CDROM:&lt;br&gt;
:/dev/hdc1 /mnt/cdrom auto noauto,ro,owner,users 0 0

[[USB Memory Stick]]:&lt;br&gt;
:/dev/sda1 /mnt/memstick auto noauto,owner,users 0 0&lt;br&gt;
(make sure to &lt;code&gt;mkdir /mnt/memstick&lt;/code&gt; after changing your /etc/fstab).

[[External USB Drive / NTFS partition]]
:/dev/sdd1        /media/1T        ntfs-3g     defaults  2   0
(/dev/sdd1 is your external USB hard drive and /media/1T is destination folder)


Note: For changing who can access the filesystem on NON-Native linux formats see [[Permissions and Umasks]] and [[Windows Partitions]]

[[Category:Tutorials]]</text>
    <sha1>4f8b9a74914041582acae1aea1665adb5422ef4a</sha1>
  </revision>
  <revision>
    <id>474</id>
    <parentid>473</parentid>
    <timestamp>2011-04-19T23:16:06Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>/* Useful Examples */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3912" xml:space="preserve">The /etc/fstab file tells the system how and where to mount filesystems by default.

==Syntax==
The syntax of the file is this:

&lt;table cellspacing="10"&gt;
&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;MAN PAGE-ese:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;FS_SPEC&lt;/td&gt;
&lt;td align="center"&gt;FS_FILE&lt;/td&gt;
&lt;td align="center"&gt;FS_VFSTYPE&lt;/td&gt;
&lt;td align="center"&gt;FS_MNTOPS&lt;/td&gt;
&lt;td align="center"&gt;FS_FREQ&lt;/td&gt;
&lt;td align="center"&gt;FS_PASSNO&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;IN ENGLISH:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;DEVICE&lt;/td&gt;
&lt;td align="center"&gt;MOUNT_POINT&lt;/td&gt;
&lt;td align="center"&gt;FILESYSTEM&lt;/td&gt;
&lt;td align="center"&gt;OPTIONS&lt;/td&gt;
&lt;td align="center"&gt;DUMP&lt;/td&gt;
&lt;td align="center"&gt;FSCK_ORDER&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;EXAMPLE:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;/dev/hdb1&lt;/td&gt;
&lt;td align="center"&gt;/mnt/windows&lt;/td&gt;
&lt;td align="center"&gt;vfat&lt;/td&gt;
&lt;td align="center"&gt;default&lt;/td&gt;
&lt;td align="center"&gt;0&lt;/td&gt;
&lt;td align="center"&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;

==Field Descriptions==
FS_SPEC (DEVICE) - the device or remote filesystem to be mounted.

FS_FILE (MOUNT_POINT) - the mount point for the filesystem. &lt;i&gt;NOTE: For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces these can be escaped as `\040'.&lt;/i&gt;

FS_VFSTYPE (FILESYSTEM)-  the type of the filesystem. As of Slackware 10.2, the FILE_SYSTEM choices are:
:auto, adfs, affs, autofs, coda, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xfs, xiafs and possibly others.
&lt;i&gt;NOTE: for swap-able and portable devices (e.g. memory sticks and CDROMs), &lt;code&gt;auto&lt;/code&gt; is the best choice because it allows the computer to determine the correct filesystem.&lt;/i&gt;

FS_MNTOPS (OPTION) - the (comma seperated) mount options. See the MOUNT command's MAN PAGE for the options because there are MANY!
The most commonly used options are:&lt;br&gt;
:noauto - do not mount this device/partition automatically on boot-up.
:ro - mount this device/partition READ-ONLY (e.g. CDROM).
:owner - Only allow the owner to mount and un-mount this device/partition.
:users - Allow any user to mount or unmount this device/partition.


FS_FREQ (DUMP) - used for these filesystems by the dump command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. For the most part, this should be "0" (zero).

FS_PASSNO (FSCK_ORDER) - used by the fsck program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

==Benefits Of fstab Entries==
Once you have a device in the fstab, mounting become VERY easy.  Instead of having to:
:&lt;code&gt;mount -t iso9660 /dev/hdb1 /mnt/cdrom&lt;/code&gt;
every time you want to use the CDROM, you can just type:
:&lt;code&gt;mount /mnt/cdrom&lt;/code&gt;
IF you have the entry in your fstab.


==Useful Examples==
CDROM:&lt;br&gt;
:/dev/hdc1 /mnt/cdrom auto noauto,ro,owner,users 0 0

[[USB Memory Stick]]:&lt;br&gt;
:/dev/sda1 /mnt/memstick auto noauto,owner,users 0 0&lt;br&gt;
(make sure to &lt;code&gt;mkdir /mnt/memstick&lt;/code&gt; after changing your /etc/fstab).

[[External USB Drive / NTFS partition]]
:/dev/sdd1        /media/1T        ntfs-3g     auto  0   0
(/dev/sdd1 is your external USB hard drive and /media/1T is destination folder)


Note: For changing who can access the filesystem on NON-Native linux formats see [[Permissions and Umasks]] and [[Windows Partitions]]

[[Category:Tutorials]]</text>
    <sha1>c69a8885981e743863cca0c15caf6135bb4cfa07</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>NVIDIA-comercial-drivers-13.37</title>
  <ns>0</ns>
  <id>240</id>
  <revision>
    <id>475</id>
    <timestamp>2011-04-28T21:36:54Z</timestamp>
    <contributor>
      <username>Toymachine</username>
      <id>172</id>
    </contributor>
    <comment>Initial tutorial on how to install commercial Nvidia drivers in Slackware 13.37 x86_64</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1685" xml:space="preserve">== Installing commercial Nvidia drivers in 64-bit Slackware 13.37 ==
This tutorial assumes you have a fresh '''full''' install of Slackware 13.37 '''x86_64'''.

What you'll need:

*'''NVIDIA-Linux-x86_64-270.41.06.run''' [Version from official nvidia website as of 4-28-11]
*'''xf86-video-nouveau-blacklist-noarch-1.txz''' [This package can be found on the slackware 13.37 DVD in /extra]
*A reboot

Once you've obtained these files, stick them somewhere (for example, /tmp).

To get the Commercial Nvidia driver working you'll need to remove the nouveau driver, and for good measure, make sure it is blacklisted.

Do the following as root:

 '''removepkg xf86-video-nouveau'''
 '''installpkg /tmp/xf86-video-nouveau-blacklist-noarch-1.txz'''
 '''chmod a+x /tmp/NVIDIA-Linux-x86_64-270.41.06.run'''

Now it's time to install the NVIDIA Driver:

 '''cd /tmp &amp;&amp; ./NVIDIA-Linux-x86_64-270.41.06.run'''

Follow the on-screen prompts to complete the install.  Also be sure to include the 32-bit gl content. (Sorry for lack of detail here, I'll try and add more detail later)

If the driver builds successfully without error then proceed.

Invoke the following:
 '''nvidia-xconfig'''

Allow it to make the change to /etc/X11/xorg.conf

Now reboot:

 '''reboot'''

Once your system has rebooted ensure that the 'nouveau' driver is NOT present and that the 'nvidia' driver is.

The following command should return nothing:
 lsmod | grep nouveau

Now check for the nvidia driver:
 lsmod | grep nvidia

You should see something like:
 root@slackbox:~# lsmod | grep nvidia
 nvidia              10486926  40 
 agpgart                28874  1 nvidia
 i2c_core               19769  2 nvidia,i2c_piix4</text>
    <sha1>aa5bd84cbd194184aeb42c4aad291e7ce536fb2e</sha1>
  </revision>
  <revision>
    <id>476</id>
    <parentid>475</parentid>
    <timestamp>2011-04-28T21:38:27Z</timestamp>
    <contributor>
      <username>Toymachine</username>
      <id>172</id>
    </contributor>
    <comment>moving this to a more appropriate title</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20101117235039|426">
  <title>NVIDIA-Commercial-Drivers</title>
  <ns>0</ns>
  <id>241</id>
  <revision>
    <id>477</id>
    <timestamp>2011-04-28T21:39:37Z</timestamp>
    <contributor>
      <username>Toymachine</username>
      <id>172</id>
    </contributor>
    <comment>Initial page for commercial nvidia drivers on Slackware 13.37 x86_64</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1685" xml:space="preserve">== Installing commercial Nvidia drivers in 64-bit Slackware 13.37 ==
This tutorial assumes you have a fresh '''full''' install of Slackware 13.37 '''x86_64'''.

What you'll need:

*'''NVIDIA-Linux-x86_64-270.41.06.run''' [Version from official nvidia website as of 4-28-11]
*'''xf86-video-nouveau-blacklist-noarch-1.txz''' [This package can be found on the slackware 13.37 DVD in /extra]
*A reboot

Once you've obtained these files, stick them somewhere (for example, /tmp).

To get the Commercial Nvidia driver working you'll need to remove the nouveau driver, and for good measure, make sure it is blacklisted.

Do the following as root:

 '''removepkg xf86-video-nouveau'''
 '''installpkg /tmp/xf86-video-nouveau-blacklist-noarch-1.txz'''
 '''chmod a+x /tmp/NVIDIA-Linux-x86_64-270.41.06.run'''

Now it's time to install the NVIDIA Driver:

 '''cd /tmp &amp;&amp; ./NVIDIA-Linux-x86_64-270.41.06.run'''

Follow the on-screen prompts to complete the install.  Also be sure to include the 32-bit gl content. (Sorry for lack of detail here, I'll try and add more detail later)

If the driver builds successfully without error then proceed.

Invoke the following:
 '''nvidia-xconfig'''

Allow it to make the change to /etc/X11/xorg.conf

Now reboot:

 '''reboot'''

Once your system has rebooted ensure that the 'nouveau' driver is NOT present and that the 'nvidia' driver is.

The following command should return nothing:
 lsmod | grep nouveau

Now check for the nvidia driver:
 lsmod | grep nvidia

You should see something like:
 root@slackbox:~# lsmod | grep nvidia
 nvidia              10486926  40 
 agpgart                28874  1 nvidia
 i2c_core               19769  2 nvidia,i2c_piix4</text>
    <sha1>aa5bd84cbd194184aeb42c4aad291e7ce536fb2e</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>NVIDIA-Commercial-Drivers</title>
  <ns>0</ns>
  <id>241</id>
  <revision>
    <id>478</id>
    <parentid>477</parentid>
    <timestamp>2011-04-28T21:41:56Z</timestamp>
    <contributor>
      <username>Toymachine</username>
      <id>172</id>
    </contributor>
    <comment>Made the last to lsmod commands bold now.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1697" xml:space="preserve">== Installing commercial Nvidia drivers in 64-bit Slackware 13.37 ==
This tutorial assumes you have a fresh '''full''' install of Slackware 13.37 '''x86_64'''.

What you'll need:

*'''NVIDIA-Linux-x86_64-270.41.06.run''' [Version from official nvidia website as of 4-28-11]
*'''xf86-video-nouveau-blacklist-noarch-1.txz''' [This package can be found on the slackware 13.37 DVD in /extra]
*A reboot

Once you've obtained these files, stick them somewhere (for example, /tmp).

To get the Commercial Nvidia driver working you'll need to remove the nouveau driver, and for good measure, make sure it is blacklisted.

Do the following as root:

 '''removepkg xf86-video-nouveau'''
 '''installpkg /tmp/xf86-video-nouveau-blacklist-noarch-1.txz'''
 '''chmod a+x /tmp/NVIDIA-Linux-x86_64-270.41.06.run'''

Now it's time to install the NVIDIA Driver:

 '''cd /tmp &amp;&amp; ./NVIDIA-Linux-x86_64-270.41.06.run'''

Follow the on-screen prompts to complete the install.  Also be sure to include the 32-bit gl content. (Sorry for lack of detail here, I'll try and add more detail later)

If the driver builds successfully without error then proceed.

Invoke the following:
 '''nvidia-xconfig'''

Allow it to make the change to /etc/X11/xorg.conf

Now reboot:

 '''reboot'''

Once your system has rebooted ensure that the 'nouveau' driver is NOT present and that the 'nvidia' driver is.

The following command should return nothing:
 '''lsmod | grep nouveau'''

Now check for the nvidia driver:
 '''lsmod | grep nvidia
'''
You should see something like:
 root@slackbox:~# lsmod | grep nvidia
 nvidia              10486926  40 
 agpgart                28874  1 nvidia
 i2c_core               19769  2 nvidia,i2c_piix4</text>
    <sha1>9b655cb4b1efd3cad4edd359355969d8900c2dbd</sha1>
  </revision>
  <revision>
    <id>479</id>
    <parentid>478</parentid>
    <timestamp>2011-04-28T21:44:00Z</timestamp>
    <contributor>
      <username>Toymachine</username>
      <id>172</id>
    </contributor>
    <comment>Added conclusion.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1793" xml:space="preserve">== Installing commercial Nvidia drivers in 64-bit Slackware 13.37 ==
This tutorial assumes you have a fresh '''full''' install of Slackware 13.37 '''x86_64'''.

What you'll need:

*'''NVIDIA-Linux-x86_64-270.41.06.run''' [Version from official nvidia website as of 4-28-11]
*'''xf86-video-nouveau-blacklist-noarch-1.txz''' [This package can be found on the slackware 13.37 DVD in /extra]
*A reboot

Once you've obtained these files, stick them somewhere (for example, /tmp).

To get the Commercial Nvidia driver working you'll need to remove the nouveau driver, and for good measure, make sure it is blacklisted.

Do the following as root:

 '''removepkg xf86-video-nouveau'''
 '''installpkg /tmp/xf86-video-nouveau-blacklist-noarch-1.txz'''
 '''chmod a+x /tmp/NVIDIA-Linux-x86_64-270.41.06.run'''

Now it's time to install the NVIDIA Driver:

 '''cd /tmp &amp;&amp; ./NVIDIA-Linux-x86_64-270.41.06.run'''

Follow the on-screen prompts to complete the install.  Also be sure to include the 32-bit gl content. (Sorry for lack of detail here, I'll try and add more detail later)

If the driver builds successfully without error then proceed.

Invoke the following:
 '''nvidia-xconfig'''

Allow it to make the change to /etc/X11/xorg.conf

Now reboot:

 '''reboot'''

Once your system has rebooted ensure that the 'nouveau' driver is NOT present and that the 'nvidia' driver is.

The following command should return nothing:
 '''lsmod | grep nouveau'''

Now check for the nvidia driver:
 '''lsmod | grep nvidia
'''
You should see something like:
 root@slackbox:~# lsmod | grep nvidia
 nvidia              10486926  40 
 agpgart                28874  1 nvidia
 i2c_core               19769  2 nvidia,i2c_piix4

You should now have a working commercial Nvidia driver and be able to start X11 without issue.</text>
    <sha1>a09c573f688627ab3a29587cfec355ee52c918f6</sha1>
  </revision>
  <revision>
    <id>480</id>
    <parentid>479</parentid>
    <timestamp>2011-04-28T21:46:26Z</timestamp>
    <contributor>
      <username>Toymachine</username>
      <id>172</id>
    </contributor>
    <comment>Added Tutorials category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1816" xml:space="preserve">[[Category:Tutorials]]
== Installing commercial Nvidia drivers in 64-bit Slackware 13.37 ==
This tutorial assumes you have a fresh '''full''' install of Slackware 13.37 '''x86_64'''.

What you'll need:

*'''NVIDIA-Linux-x86_64-270.41.06.run''' [Version from official nvidia website as of 4-28-11]
*'''xf86-video-nouveau-blacklist-noarch-1.txz''' [This package can be found on the slackware 13.37 DVD in /extra]
*A reboot

Once you've obtained these files, stick them somewhere (for example, /tmp).

To get the Commercial Nvidia driver working you'll need to remove the nouveau driver, and for good measure, make sure it is blacklisted.

Do the following as root:

 '''removepkg xf86-video-nouveau'''
 '''installpkg /tmp/xf86-video-nouveau-blacklist-noarch-1.txz'''
 '''chmod a+x /tmp/NVIDIA-Linux-x86_64-270.41.06.run'''

Now it's time to install the NVIDIA Driver:

 '''cd /tmp &amp;&amp; ./NVIDIA-Linux-x86_64-270.41.06.run'''

Follow the on-screen prompts to complete the install.  Also be sure to include the 32-bit gl content. (Sorry for lack of detail here, I'll try and add more detail later)

If the driver builds successfully without error then proceed.

Invoke the following:
 '''nvidia-xconfig'''

Allow it to make the change to /etc/X11/xorg.conf

Now reboot:

 '''reboot'''

Once your system has rebooted ensure that the 'nouveau' driver is NOT present and that the 'nvidia' driver is.

The following command should return nothing:
 '''lsmod | grep nouveau'''

Now check for the nvidia driver:
 '''lsmod | grep nvidia
'''
You should see something like:
 root@slackbox:~# lsmod | grep nvidia
 nvidia              10486926  40 
 agpgart                28874  1 nvidia
 i2c_core               19769  2 nvidia,i2c_piix4

You should now have a working commercial Nvidia driver and be able to start X11 without issue.</text>
    <sha1>969a5bc82fcbe847bb57278f13e19ad1e5f1143c</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Bootsplash</title>
  <ns>0</ns>
  <id>192</id>
  <revision>
    <id>481</id>
    <parentid>259</parentid>
    <timestamp>2011-05-11T01:30:50Z</timestamp>
    <contributor>
      <username>Netrixtardis</username>
      <id>146</id>
    </contributor>
    <minor/>
    <comment>/* Prerequisites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12297" xml:space="preserve">[[Category:Tutorials]]

== Prerequisites ==
* kernel source
* a bootsplash patch for your kernel version [http://www.mcbeister.de/bootsplash/index.html] bootsplash patch.
* A bootsplash theme [http://kde-look.org/index.php?xcontentmode=61 kde-look themes]
* Bootsplash utilites [http://www.yzzerdd.net/slackware/files/bootsplash/bootsplash-3.1.tar.bz2 download]

== Setup ==
Start by patching and building a new kernel.

Assuming Stock kernel configuration/source. And all your downloads are in /home/username/Downloads.

  &lt;sub&gt; cd /usr/src/linux
        patch -p1&lt;/home/username/Downloads/bootsplash*.diff
        rm .config
        zcat /proc/config.gz &gt; .config
        make menuconfig&lt;/sub&gt;

   *Note: If you insist on using the generic kernel. And are currently using it.
        Check to see if the .config in your /usr/src/linux directory matches /proc/config.gz
          &lt;sub&gt; zdiff /proc/config.gz /usr/src/linux/.config &lt;/sub&gt;
        If they match, skip the "rm .config &amp;&amp; zcat ..." part above
        You'll also want to converge your initrd.gz and bootsplash's initrd. More on that below.

Edit these 2 options:

  &lt;sub&gt;  Device Drivers ---&gt;
             Graphics support ---&gt;
                  Logo configuration ---&gt;
                      [ ] Bootup logo
                  Bootsplash configuration ---&gt;
                      [*] Bootup splash screen&lt;/sub&gt;
* If you aren't using a stock kernel configuration, or on another distro check these settings whileyou are still in the kernel configuration dialog:
  &lt;sub&gt;&lt;nowiki&gt;  Device Drivers ---&gt;
            Block devices ---&gt;
                   &lt;*&gt; RAM disk support
            Graphics support ---&gt;
                   &lt;*&gt; Support for frame buffer devices&lt;/nowiki&gt;&lt;/sub&gt;
Now to make the patched kernel and install it

  &lt;sub&gt; make ; cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;
For slamd64, thats:
  &lt;sub&gt; make ; cp /usr/src/linux/arch/x86_64/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;

On to making a new bootsplash initrd.
Compile and install the splash utility.
  &lt;sub&gt; cd /home/username/Downloads
        tar xf bootsplash-3.0.7.tar.bz2
        cd bootsplash-3.0.7/Utilities/
        make splash
        cp splash /usr/bin/ &lt;/sub&gt;
And use it to build your new initrd.
Untar the theme file you downloaded, and check to see if it has a config directory and an image/s directory.
Look in the config directory for an appropriately sized config file (usually bootsplash-1024x768.cfg).
Edit this file, changing the directory it looks for images in (jpeg= option and silentjpeg= option) to point to the correct directory of the images for that theme. Example: /home/username/Downloads/bootsplashtheme/images/foo-bar.jpg
Finish by making the initrd with splash:
  &lt;sub&gt; splash -s -f /home/username/Downloads/bootsplashtheme/config/bootsplash-1024x768.cfg &gt;&gt; /boot/initrd.splash &lt;/sub&gt;
    For generic kernel users, you'll have to converge your stock initrd.gz and the bootsplash initrds.
For example:
      &lt;sub&gt;mkinitrd -c -m reiserfs&lt;/sub&gt;
      &lt;sub&gt;
            cp /boot/initrd.splash /boot/initrd-tree/bootsplash
      &lt;/sub&gt;
After putting the initrd-splash into the mkinitrd's initrd-tree you'll need to run mkinitrd again.

Remember to do this every time you make a new initrd.splash.
Now edit /etc/lilo.conf with your favorite editor, adding the new kernel and bootsplash options.
Sample:
  &lt;sub&gt; boot = /dev/hda
        message = /boot/boot_message.txt
        prompt
        timeout = 300
        change-rules
         reset
        vga = 791
        image = /boot/vmlinuz
          root = /dev/hda1
          label = Linux
          read-only
        image = /boot/vmlinuz-bootsplash
          root = /dev/hda1
          label = Bootsplash
          initrd=/boot/initrd.splash
          append="splash=silent" &lt;/sub&gt;
Substitue "initrd=/boot/initrd.gz" if you had to run mkinitrd for a generic kernel, then run lilo to update and you're set.
  &lt;sub&gt;root@slackware:~# lilo
       Added Linux
       Added Bootsplash &lt;/sub&gt;
Now you can Reboot to test everything. If boot fails for some reason. You still have your stock kernel and entry in lilo to boot into without worries.

== Progressbar - rc.progress ==
Theres no set way to do this, you just need init to update /proc/splash correctly.
The way I do it (with help from LinuxQuestiosn forums):
create a new file in /etc/rc.d/ named rc.progress
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.progress &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
#rc.progress  This file has a common subroutine used to update a
#             bootsplash progress bar.
#

# Count the number of times the progress bar is likely to gbe increased
numu=$((`cat /etc/rc.d/rc.* | grep -c "^progressup"`));
numd=$((`cat /etc/rc.d/rc.* | grep -c "^progressdown"`));

function progressup(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress+1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numu ))" &gt; /proc/splash
}

function progressdown(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress-1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numd ))" &gt; /proc/splash
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.progress &lt;/sub&gt;
The . tells your system to include the functionality described in /etc/rc.d/rc.progress.
Now scroll through and add "progressup" (the defined trigger in rc.progress) on a new line
at the end of every subroutine where you want the progressbar to incriment up.
Example section of my rc.S:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.S:  System initialization script.
#
# Mostly written by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.progress
PATH=/sbin:/usr/sbin:/bin:/usr/bin

# Mount /proc right away: 
  &lt;/nowiki&gt;&lt;/sub&gt;
Don't add progressup till after your partition is mounted read/write
it'll be at the end of a long segment of echo .. echo.. echo like this.
  &lt;sub&gt;&lt;nowiki&gt;  echo -n "Press ENTER to continue. "
  read junk;
fi # Done checking root filesystem
progressup
  &lt;/nowiki&gt;&lt;/sub&gt;
Do the same for /etc/rc.d/rc.6 adding progressdown instead of progressup.
After you've finished that, you need to delete your temporary progressbar output cache.
Since rc.local is run last during startup, it's best to accomplish this here.
Edit rc.local:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

rm -fr /var/run/progressbar &lt;/nowiki&gt;&lt;/sub&gt;

== Progressbar - rc.bootsplash ==
An alternate script can also be used if you should have problems implementing the rc.progress script.
In my case the prior script was not able to delete its progressbar file, and adding progressdown entries to rc.6 resulted in odd behaviors even during bootup when rc.6 should not of been a factor. 
Create a new file in /etc/rc.d/ named rc.bootsplash
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.bootsplash &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# /etc/rc.d/rc.bootsplash: bootsplash functions.
# This file does nothing if run, and is called by other rc.
# files in order to make the progress bar and animations works.

function progressbar()
{
        if [ $# != 1 ]
                then
                echo "Usage: progressbar {progress}"
                exit 1
        fi
        if [ -a /proc/splash ] ; then
                echo "show $(( 65534 * $1 / 100 ))" &gt; /proc/splash
        fi
}
#
function animate()
{
        if [ $# = 0 ]
                then
                echo "Usage: animate {hook}"
                exit 1
        fi
        splash "$*"
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.bootsplash &lt;/sub&gt;
Now scroll through and add "progressbar X" (where X is a number representing the percent to incriment to) on a new line
at the end of every subroutine where you want the progressbar to incriment up. 0 is not a valid incriment. Only 1 - 100 are valid. 

Example rc.S
  &lt;sub&gt;&lt;nowiki&gt;
# Scan for new volume groups:
  /sbin/vgscan --mknodes --ignorelockingfailure 2&gt; /dev/null
  if [ $? = 0 ]; then
    # Make volume groups available to the kernel.
    # This should also make logical volumes available.
    /sbin/vgchange -ay --ignorelockingfailure
  fi
fi
progressbar 5

# Open any volumes created by cryptsetup:
if [ -f /etc/crypttab -a -x /sbin/cryptsetup.static ]; then
  # First, check for device-mapper support.
  if ! grep -wq device-mapper /proc/devices ; then
    # If device-mapper exists as a module, try to load it.
    # Try to load a device-mapper kernel module:
    /sbin/modprobe -q dm-mod
  fi
  cat /etc/crypttab | grep -v "^#" | grep -v "^$" | while read line; do
    LUKS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f1 -d' ')
    DEV=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f2 -d' ')
    PASS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f3 -d' ')
    OPTS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f4 -d' ')
    LUKSOPTS=""
    if echo $OPTS | grep -wq ro ; then LUKSOPTS="${LUKSOPTS} --readonly" ; fi

    # NOTE: we only support LUKS formatted volumes (except for swap)!
    if /sbin/cryptsetup.static isLuks $DEV 2&gt;/dev/null ; then
      echo "Unlocking LUKS crypt volume '${LUKS}' on device '$DEV':"
      if [ -n "${PASS}" ]; then
        if [ -f ${PASS} ]; then
          /sbin/cryptsetup.static ${LUKSOPTS} --key-file=${PASS} luksOpen $DEV $LUKS
        elif [ "${PASS}" != "none" ]; then
          echo "${PASS}" | /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS
        fi
      else
        for i in seq 1 3 ; do
          /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS &lt;/dev/tty0 &gt;/dev/tty0 2&gt;&amp;1
          [ $? -eq 0 ] &amp;&amp; break
        done
      fi
    elif echo $OPTS | grep -wq swap ; then
      # If any of the volumes is to be used as encrypted swap,
      # then encrypt it using a random key and run mkswap:
      echo "Creating encrypted swap on device '$DEV' mapped to '${LUKS}':"
      /sbin/cryptsetup.static --cipher=aes --key-file=/dev/urandom --key-size=256 create $LUKS $DEV
      mkswap /dev/mapper/$LUKS
    fi
  done
fi

# Enable swapping:
/sbin/swapon -a
progressbar 10
&lt;/nowiki&gt;&lt;/sub&gt;

Continue adding "progressbar X" entries in both rc.S and rc.M

Do the same for rc.6 but instead incrimenting down 'X'. 

Example rc.6
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# rc.6          This file is executed by init when it goes into runlevel
#               0 (halt) or runlevel 6 (reboot). It kills all processes,
#               unmounts file systems and then either halts or reboots.
#
# Version:      @(#)/etc/rc.d/rc.6      2.47 Sat Jan 13 13:37:26 PST 2001
#
# Author:       Miquel van Smoorenburg &lt;miquels@drinkel.nl.mugnet.org&gt;
# Modified by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.bootsplash

# Set the path.
PATH=/sbin:/etc:/bin:/usr/bin
progressbar 100

# If there are SystemV init scripts for this runlevel, run them.
if [ -x /etc/rc.d/rc.sysvinit ]; then
  . /etc/rc.d/rc.sysvinit
fi
progressbar 90

# Set linefeed mode to avoid staircase effect.
/bin/stty onlcr

echo "Running shutdown script $0:"

# Find out how we were called.
case "$0" in
        *0)
                command="halt"
                ;;
        *6)
                command=reboot
                ;;
        *)
                echo "$0: call me as \"rc.0\" or \"rc.6\" please!"
                exit 1
                ;;
esac

# Save the system time to the hardware clock using hwclock --systohc.
if [ -x /sbin/hwclock ]; then
  # Check for a broken motherboard RTC clock (where ioports for rtc are
  # unknown) to prevent hwclock causing a hang:
  if ! grep -q -w rtc /proc/ioports ; then
    CLOCK_OPT="--directisa"
  fi
  if grep -q "^UTC" /etc/hardwareclock 2&gt; /dev/null ; then
    echo "Saving system time to the hardware clock (UTC)."
    /sbin/hwclock $CLOCK_OPT --utc --systohc
  else
    echo "Saving system time to the hardware clock (localtime)."
    /sbin/hwclock  $CLOCK_OPT --localtime --systohc
  fi
fi
progressbar 80
&lt;/nowiki&gt;&lt;/sub&gt;</text>
    <sha1>469af6549d2c3b04e94ab848706350e7046801bc</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Bootsplash (old)</title>
  <ns>0</ns>
  <id>55</id>
  <revision>
    <id>482</id>
    <parentid>257</parentid>
    <timestamp>2011-05-11T01:31:32Z</timestamp>
    <contributor>
      <username>Netrixtardis</username>
      <id>146</id>
    </contributor>
    <minor/>
    <comment>/* Prerequisites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12328" xml:space="preserve">[[Category:Tutorials]]

== Prerequisites ==
* kernel source
* a bootsplash patch for your kernel version [http://www.mcbeister.de/bootsplash/index.html] bootsplash patch.
* A bootsplash theme [http://kde-look.org/index.php?xcontentmode=61 kde-look themes]
* Bootsplash utilites [http://www.yzzerdd.net/slackware/files/bootsplash/bootsplash-3.1.tar.bz2 download]

== Setup ==
Start by patching and building a new kernel.

Assuming Stock kernel configuration/source. And all your downloads are in /home/username/Downloads.

  &lt;sub&gt; cd /usr/src/linux
        patch -p1&lt;/home/username/Downloads/bootsplash*.diff
        rm .config
        zcat /proc/config.gz &gt; .config
        make menuconfig&lt;/sub&gt;

   *Note: If you insist on using the generic kernel. And are currently using it.
        Check to see if the .config in your /usr/src/linux directory matches /proc/config.gz
          &lt;sub&gt; zdiff /proc/config.gz /usr/src/linux/.config &lt;/sub&gt;
        If they match, skip the "rm .config &amp;&amp; zcat ..." part above
        You'll also want to converge your initrd.gz and bootsplash's initrd. More on that below.

Edit these 2 options:

  &lt;sub&gt;  Device Drivers ---&gt;
             Graphics support ---&gt;
                  Logo configuration ---&gt;
                      [ ] Bootup logo
                  Bootsplash configuration ---&gt;
                      [*] Bootup splash screen&lt;/sub&gt;
* If you aren't using a stock kernel configuration, or on another distro check these settings whileyou are still in the kernel configuration dialog:
  &lt;sub&gt;&lt;nowiki&gt;  Device Drivers ---&gt;
            Block devices ---&gt;
                   &lt;*&gt; RAM disk support
            Graphics support ---&gt;
                   &lt;*&gt; Support for frame buffer devices&lt;/nowiki&gt;&lt;/sub&gt;
Now to make the patched kernel and install it

  &lt;sub&gt; make ; cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;
For slamd64, thats:
  &lt;sub&gt; make ; cp /usr/src/linux/arch/x86_64/boot/bzImage /boot/vmlinuz-bootsplash&lt;/sub&gt;

On to making a new bootsplash initrd.
Compile and install the splash utility.
  &lt;sub&gt; cd /home/username/Downloads
        tar xf bootsplash-3.0.7.tar.bz2
        cd bootsplash-3.0.7/Utilities/
        make splash
        cp splash /usr/bin/ &lt;/sub&gt;
And use it to build your new initrd.
Untar the theme file you downloaded, and check to see if it has a config directory and an image/s directory.
Look in the config directory for an appropriately sized config file (usually bootsplash-1024x768.cfg).
Edit this file, changing the directory it looks for images in (jpeg= option and silentjpeg= option) to point to the correct directory of the images for that theme. Example: /home/username/Downloads/bootsplashtheme/images/foo-bar.jpg
Finish by making the initrd with splash:
  &lt;sub&gt; splash -s -f /home/username/Downloads/bootsplashtheme/config/bootsplash-1024x768.cfg &gt;&gt; /boot/initrd.splash &lt;/sub&gt;
    For generic kernel users, you'll have to converge your stock initrd.gz and the bootsplash initrds.
       &lt;sub&gt;mkinitrd
            cp /boot/initrd.splash /boot/initrd-tree/
       &lt;/sub&gt;
After putting the initrd-splash into the mkinitrd's initrd-tree you'll need to run mkinitrd again with some computer specific options. Example:
      &lt;sub&gt;mkinitrd -c -m reiserfs&lt;/sub&gt;
Remember to do this every time you make a new initrd.splash.
Now edit /etc/lilo.conf with your favorite editor, adding the new kernel and bootsplash options.
Sample:
  &lt;sub&gt; boot = /dev/hda
        message = /boot/boot_message.txt
        prompt
        timeout = 300
        change-rules
         reset
        vga = 791
        image = /boot/vmlinuz
          root = /dev/hda1
          label = Linux
          read-only
        image = /boot/vmlinuz-bootsplash
          root = /dev/hda1
          label = Bootsplash
          initrd=/boot/initrd.splash
          append="splash=silent" &lt;/sub&gt;
Substitue "initrd=/boot/initrd.gz" if you had to run mkinitrd for a generic kernel, then run lilo to update and you're set.
  &lt;sub&gt;root@slackware:~# lilo
       Added Linux
       Added Bootsplash &lt;/sub&gt;
Now you can Reboot to test everything. If boot fails for some reason. You still have your stock kernel and entry in lilo to boot into without worries.

== Progressbar - rc.progress ==
Theres no set way to do this, you just need init to update /proc/splash correctly.
The way I do it (with help from LinuxQuestiosn forums):
create a new file in /etc/rc.d/ named rc.progress
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.progress &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
#rc.progress  This file has a common subroutine used to update a
#             bootsplash progress bar.
#

# Count the number of times the progress bar is likely to gbe increased
numu=$((`cat /etc/rc.d/rc.* | grep -c "^progressup"`));
numd=$((`cat /etc/rc.d/rc.* | grep -c "^progressdown"`));

function progressup(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress+1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numu ))" &gt; /proc/splash
}

function progressdown(){
 progress=$((`cat /var/run/progressbar`));
 progress=$(($progress-1));
 echo $progress &gt; /var/run/progressbar
 echo "show $(( 65523 * $progress / $numd ))" &gt; /proc/splash
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.progress &lt;/sub&gt;
The . tells your system to include the functionality described in /etc/rc.d/rc.progress.
Now scroll through and add "progressup" (the defined trigger in rc.progress) on a new line
at the end of every subroutine where you want the progressbar to incriment up.
Example section of my rc.S:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.S:  System initialization script.
#
# Mostly written by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.progress
PATH=/sbin:/usr/sbin:/bin:/usr/bin

# Mount /proc right away: 
  &lt;/nowiki&gt;&lt;/sub&gt;
Don't add progressup till after your partition is mounted read/write
it'll be at the end of a long segment of echo .. echo.. echo like this.
  &lt;sub&gt;&lt;nowiki&gt;  echo -n "Press ENTER to continue. "
  read junk;
fi # Done checking root filesystem
progressup
  &lt;/nowiki&gt;&lt;/sub&gt;
Do the same for /etc/rc.d/rc.6 adding progressdown instead of progressup.
After you've finished that, you need to delete your temporary progressbar output cache.
Since rc.local is run last during startup, it's best to accomplish this here.
Edit rc.local:
  &lt;sub&gt;&lt;nowiki&gt; 
#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.

rm -fr /var/run/progressbar &lt;/nowiki&gt;&lt;/sub&gt;

== Progressbar - rc.bootsplash ==
An alternate script can also be used if you should have problems implementing the rc.progress script.
In my case the prior script was not able to delete its progressbar file, and adding progressdown entries to rc.6 resulted in odd behaviors even during bootup when rc.6 should not of been a factor. 
Create a new file in /etc/rc.d/ named rc.bootsplash
  &lt;sub&gt; cd /etc/rc.d/ ; touch rc.bootsplash &lt;/sub&gt;
edit it, and add this script:
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# /etc/rc.d/rc.bootsplash: bootsplash functions.
# This file does nothing if run, and is called by other rc.
# files in order to make the progress bar and animations works.

function progressbar()
{
        if [ $# != 1 ]
                then
                echo "Usage: progressbar {progress}"
                exit 1
        fi
        if [ -a /proc/splash ] ; then
                echo "show $(( 65534 * $1 / 100 ))" &gt; /proc/splash
        fi
}
#
function animate()
{
        if [ $# = 0 ]
                then
                echo "Usage: animate {hook}"
                exit 1
        fi
        splash "$*"
}

&lt;/nowiki&gt;&lt;/sub&gt;

Now *CAREFULLY* edit /etc/rc.d/rc.S
at the top add the line (a new line by itself)
&lt;sub&gt; . /etc/rc.d/rc.bootsplash &lt;/sub&gt;
Now scroll through and add "progressbar X" (where X is a number representing the percent to incriment to) on a new line
at the end of every subroutine where you want the progressbar to incriment up. 0 is not a valid incriment. Only 1 - 100 are valid. 

Example rc.S
  &lt;sub&gt;&lt;nowiki&gt;
# Scan for new volume groups:
  /sbin/vgscan --mknodes --ignorelockingfailure 2&gt; /dev/null
  if [ $? = 0 ]; then
    # Make volume groups available to the kernel.
    # This should also make logical volumes available.
    /sbin/vgchange -ay --ignorelockingfailure
  fi
fi
progressbar 5

# Open any volumes created by cryptsetup:
if [ -f /etc/crypttab -a -x /sbin/cryptsetup.static ]; then
  # First, check for device-mapper support.
  if ! grep -wq device-mapper /proc/devices ; then
    # If device-mapper exists as a module, try to load it.
    # Try to load a device-mapper kernel module:
    /sbin/modprobe -q dm-mod
  fi
  cat /etc/crypttab | grep -v "^#" | grep -v "^$" | while read line; do
    LUKS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f1 -d' ')
    DEV=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f2 -d' ')
    PASS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f3 -d' ')
    OPTS=$(echo $line | tr '\t' ' ' | tr -s ' ' | cut -f4 -d' ')
    LUKSOPTS=""
    if echo $OPTS | grep -wq ro ; then LUKSOPTS="${LUKSOPTS} --readonly" ; fi

    # NOTE: we only support LUKS formatted volumes (except for swap)!
    if /sbin/cryptsetup.static isLuks $DEV 2&gt;/dev/null ; then
      echo "Unlocking LUKS crypt volume '${LUKS}' on device '$DEV':"
      if [ -n "${PASS}" ]; then
        if [ -f ${PASS} ]; then
          /sbin/cryptsetup.static ${LUKSOPTS} --key-file=${PASS} luksOpen $DEV $LUKS
        elif [ "${PASS}" != "none" ]; then
          echo "${PASS}" | /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS
        fi
      else
        for i in seq 1 3 ; do
          /sbin/cryptsetup.static ${LUKSOPTS} luksOpen $DEV $LUKS &lt;/dev/tty0 &gt;/dev/tty0 2&gt;&amp;1
          [ $? -eq 0 ] &amp;&amp; break
        done
      fi
    elif echo $OPTS | grep -wq swap ; then
      # If any of the volumes is to be used as encrypted swap,
      # then encrypt it using a random key and run mkswap:
      echo "Creating encrypted swap on device '$DEV' mapped to '${LUKS}':"
      /sbin/cryptsetup.static --cipher=aes --key-file=/dev/urandom --key-size=256 create $LUKS $DEV
      mkswap /dev/mapper/$LUKS
    fi
  done
fi

# Enable swapping:
/sbin/swapon -a
progressbar 10
&lt;/nowiki&gt;&lt;/sub&gt;

Continue adding "progressbar X" entries in both rc.S and rc.M

Do the same for rc.6 but instead incrimenting down 'X'. 

Example rc.6
  &lt;sub&gt;&lt;nowiki&gt;
#! /bin/sh
#
# rc.6          This file is executed by init when it goes into runlevel
#               0 (halt) or runlevel 6 (reboot). It kills all processes,
#               unmounts file systems and then either halts or reboots.
#
# Version:      @(#)/etc/rc.d/rc.6      2.47 Sat Jan 13 13:37:26 PST 2001
#
# Author:       Miquel van Smoorenburg &lt;miquels@drinkel.nl.mugnet.org&gt;
# Modified by:  Patrick J. Volkerding, &lt;volkerdi@slackware.com&gt;
#
. /etc/rc.d/rc.bootsplash

# Set the path.
PATH=/sbin:/etc:/bin:/usr/bin
progressbar 100

# If there are SystemV init scripts for this runlevel, run them.
if [ -x /etc/rc.d/rc.sysvinit ]; then
  . /etc/rc.d/rc.sysvinit
fi
progressbar 90

# Set linefeed mode to avoid staircase effect.
/bin/stty onlcr

echo "Running shutdown script $0:"

# Find out how we were called.
case "$0" in
        *0)
                command="halt"
                ;;
        *6)
                command=reboot
                ;;
        *)
                echo "$0: call me as \"rc.0\" or \"rc.6\" please!"
                exit 1
                ;;
esac

# Save the system time to the hardware clock using hwclock --systohc.
if [ -x /sbin/hwclock ]; then
  # Check for a broken motherboard RTC clock (where ioports for rtc are
  # unknown) to prevent hwclock causing a hang:
  if ! grep -q -w rtc /proc/ioports ; then
    CLOCK_OPT="--directisa"
  fi
  if grep -q "^UTC" /etc/hardwareclock 2&gt; /dev/null ; then
    echo "Saving system time to the hardware clock (UTC)."
    /sbin/hwclock $CLOCK_OPT --utc --systohc
  else
    echo "Saving system time to the hardware clock (localtime)."
    /sbin/hwclock  $CLOCK_OPT --localtime --systohc
  fi
fi
progressbar 80
&lt;/nowiki&gt;&lt;/sub&gt;</text>
    <sha1>9d811d340b6a1aa9238315f236c1d8e9c271a30e</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Slack-desc</title>
  <ns>0</ns>
  <id>17</id>
  <revision>
    <id>483</id>
    <parentid>472</parentid>
    <timestamp>2011-05-12T19:37:41Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Added Tools section, with links to tools that generate slack-desc files</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2134" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: appname (Short description of the application)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname:
 appname: It's a good idea to include a link to the application's homepage too.
 appname:

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 &amp; 11 should not have a space after the :

=Tools=
1. There is a command-line tool that automates the creation of slack-desc files and helps you generate legal slack-desc files with minimal effort:
http://slack-desc.sourceforge.net/

2. A web-based tool is also available at: http://www.linuxpackages.net/slackcreator.php
=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>242781af77d76a443f16591f75a566dad0467aa2</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Building A Package</title>
  <ns>0</ns>
  <id>23</id>
  <revision>
    <id>484</id>
    <parentid>358</parentid>
    <timestamp>2011-05-12T20:39:39Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Added link to slack-desc section and link to slack-desc generation tool</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2971" xml:space="preserve">[[Category:Tutorials]]

= Intro =

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

== The good and decent way ==

Configure and compile the source as you usually do:
 ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
 make

Make a temporary destination directory available:
 mkdir /tmp/build

Install into the temporary directory:
 make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
 strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in &lt;tt&gt;/usr/man&lt;/tt&gt; is gzipped before you make the package:
 gzip -9 /tmp/build/usr/man/man?/*.?

Create the &lt;tt&gt;install&lt;/tt&gt; directory, this is where the description and install script will be stored:
 cd /tmp/build
 mkdir install
 cd install

Using a text editor (or a [http://slack-desc.sourceforge.net/ tool]]), create a file called [[slack-desc]] and fill it with the following contents:

    |-----handy-ruler------------------------------------------------------|
 app: Application Name (Short/Brief description)
 app:
 app: Enter a description of the package you are building.
 app: All 11 "app:" lines must be present
 app: "app" needs to be your application name.
 app: The handy-ruler is there to help you, these lines should not exceed
 app: 79 characters.
 app:
 app:
 app:
 app:

Create the actual package:
 cd /tmp/build
 makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc.  Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say &lt;tt&gt;yes&lt;/tt&gt;&lt;br&gt;
When prompted to reset permissions, say &lt;tt&gt;no&lt;/tt&gt;

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
 cd ..
 installpkg app-version-arch-tag.tgz


== The "i don't have time" way ==

Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this: 
 ./configure --prefix=/usr
 make install DESTDIR=$(pwd)/PACKAGE
 cd $(pwd)/PACKAGE
 makepkg -l y -c n ../app-version-arch-tag.tgz
 installpkg ../app-version-arch-tag.tgz

Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.

----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----</text>
    <sha1>e243a2544503cedcd63bcf8a9d895edfb2280bb1</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>SLiM</title>
  <ns>0</ns>
  <id>212</id>
  <revision>
    <id>486</id>
    <parentid>311</parentid>
    <timestamp>2011-05-27T05:05:25Z</timestamp>
    <contributor>
      <username>Netrixtardis</username>
      <id>146</id>
    </contributor>
    <minor/>
    <comment>use '-nodaemon' for rc.4</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3311" xml:space="preserve">[[category:tutorials]]
'''SLiM (Simple Login Manager)''' is a Desktop-independent graphical login manager for X11, derived from [http://largo.windowmaker.org/Login.app/ Login.app]. 
It aims to be light and simple, although completely configurable through themes and an option file; is suitable for machines on which remote login functionalities are not needed.

== Features ==
* PNG and XFT support for alpha transparency and antialiased fonts
* External themes support
* Configurable runtime options: X server, login / shutdown / reboot commands
* Single (GDM-like) or double (XDM-like) input control
* Can load predefined user at startup
* Configurable welcome / shutdown messages
* Random theme selection

== Requirements ==
* X11
* libpng
* libjpeg
* freetype
== Instalation ==
Use package, SlackBuild or compile it from source.

== Configuration ==
=== Themes ===
Themes are located in /usr/share/slim/themes. If you want more themes, try themepack or standalone theme from [http://developer.berlios.de/project/showfiles.php?group_id=2663 project download page]. Unpack file there
&lt;pre&gt;
$ tar xvzf themefile.tar.gz -C /usr/share/slim/themes
&lt;/pre&gt;
 
By default SLiM use ''default'' theme. You can change it in it's configuration file /etc/slim.conf by rewriting ''current_theme'' line
&lt;pre&gt;
# current theme, use comma separated list to specify a set to 
# randomly choose from
#current_theme       default
current_theme       theme_you_like
&lt;/pre&gt;
If you use SlackBuild (at least for 13.0) it comes with nice Slackware theme. Rewrite ''current_theme'' line to 
&lt;pre&gt;
current_theme       slackware-black
&lt;/pre&gt; 

=== Startup ===
Edit run level 4 init script - /etc/rc.d/rc.4 - to try start SLiM as default graphical login manager. You have to add these lines '''before''' GDM (or whatever graphical login manager you have as default; GDM is set as first to start by default)
&lt;pre&gt;
#! /bin/sh
#
# rc.4		This file is executed by init(8) when the system is being
#		initialized for run level 4 (XDM)
#
# Version:	@(#)/etc/rc.d/rc.4	2.00	02/17/93
#
# Author:	Fred N. van Kempen, &lt;waltje@uwalt.nl.mugnet.org&gt;
# At least 47% rewritten by:  Patrick J. Volkerding &lt;volkerdi@slackware.com&gt;
#

# Tell the viewers what's going to happen...
echo "Starting up X11 session manager..."

# Add this if statement to the top
# If you have SliM, it goes first
#---------------------------------

if [ -x /usr/bin/slim ]; then
  exec /usr/bin/slim -nodaemon 
fi

#---------------------------------
# end of new if statement

# Try to use GNOME's gdm session manager.  This comes first because if
# gdm is on the machine then the user probably installed it and wants
# to use it by default:
if [ -x /usr/bin/gdm ]; then
  exec /usr/bin/gdm -nodaemon
fi
&lt;/pre&gt; 

If you aren't already using this, set run level to 4 in /etc/inittab
&lt;pre&gt;
# These are the default runlevels in Slackware:
#   0 = halt
#   1 = single user mode
#   2 = unused (but configured the same as runlevel 3)
#   3 = multiuser mode (default Slackware runlevel)
#   4 = X11 with KDM/GDM/XDM (session managers)
#   5 = unused (but configured the same as runlevel 3)
#   6 = reboot

# Default runlevel. (Do not set to 0 or 6)
id:4:initdefault:
&lt;/pre&gt;
Reboot and you have nice simple login manager running :~)
== Links ==
[http://slim.berlios.de Project homepage]</text>
    <sha1>21af03cd3620a8ad884e51029b1fe799a1a1dcd4</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>User:Erik</title>
  <ns>2</ns>
  <id>2</id>
  <revision>
    <id>488</id>
    <parentid>301</parentid>
    <timestamp>2011-06-07T09:21:29Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="217" xml:space="preserve">Name: [mailto:erik@sl1200.org Erik Hanson]&lt;br&gt;
Web: [http://sl1200.org/~erik/ http://sl1200s.org/~erik/]&lt;br&gt;
IRC: erik @ [irc://frop.taphouse.org/ Taphouse Cabal] and [irc://chat.freenode.net The Freenode Network]&lt;br&gt;</text>
    <sha1>6945a61c62172eecffa218ed6621095b7653f6ad</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Links</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>489</id>
    <parentid>418</parentid>
    <timestamp>2011-06-07T09:22:29Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3680" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ - Slackware FAQ by [[User:juhl|juhl]] (Jesper Juhl)
* http://www.slackbook.org - updated version of the slackware book
* http://www.slackware.com/getslack - Extensive listing of Slackware mirrors
* http://www.linuxquestions.org/questions/slackware-14/ - Slackware forum
* http://slackbuilds.org/ - Build scripts for additional software
* http://sbopkg.org - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* http://www.kde-look.org/content/show.php?content=23384 - Slack-Track - a superkaramba theme to track the slackware-current changelog on your desktop, created by [[User:omal|omal]]
* http://jtgzmanager.sf.net/ - A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://slackware.linux.or.id - Indonesian Slackware Community - by [[User:Willysr|Willysr]]
* http://open-eslack.org/ - Spanish Slackware community
* http://www.slack-world.com - Iranian Slackware Community

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Free packages==


* [http://slackware.com/~alien/ http://slackware.com/~alien/] Eric Hameleers' packages
* [http://rlworkman.net/pkgs/ http://rlworkman.net/pkgs/] rworkman's packages
* http://www.linuxpackages.net/
* [http://www.slacky.eu/repository/slackware-11.0/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware
* [http://scxd.info/en/ Slackware Current eXtended Desktop] Packages for Slackware Current

==.SlackBuild Repositories==
* http://slackbuilds.org - The SlackBuilds.org Project
* http://slackbuilds.net - The French SlackBuilds Repository
* http://www.slackware.com/~alien/slackbuilds/ - Eric "Alien" Hameleer's SlackBuilds
* http://slackbuild.strangeworlds.co.uk - cathectic's SlackBuilds
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.
* http://scxd.info/pub/slackbuilds/ - Slackware Current eXtended Desktop's SlackBuilds

==Live CD's based on Slackware==
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* http://open-eslack.org/wiki/ - Wiki of the Slackware spanish community
* http://slackware.linux.or.id/wiki/ - Indonesian Slackware Wiki

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for stable and current</text>
    <sha1>0aba648d3f75ab0d38e426c5a7c21a0407e257a6</sha1>
  </revision>
  <revision>
    <id>516</id>
    <parentid>489</parentid>
    <timestamp>2011-09-09T12:32:09Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <comment>Added new links, Improved formatting, and removed obsolete links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3900" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* [http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ Slackware FAQ by] [[User:juhl|juhl]] (Jesper Juhl)
* [http://www.nielshorn.net/slackware/slack_versions.php A complete overview of all Slackware versions] by Niels Horn
* [http://www.slackbook.org Updated version of the slackware book]
* [http://www.slackware.com/getslack Extensive listing of Slackware mirrors]
* [http://www.linuxquestions.org/questions/slackware-14/ Slackware forum] on LinuxQuestions.org
* [http://slackbuilds.org/ slackbuilds.org - Build scripts for additional software]
* [http://sbopkg.org sbopkg.org] - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* [http://gitorious.org/sbopkg-slackware-queues Build queues for all Slackware packages from SlackBuilds.org]
* [http://slackworld.berlios.de/ The Slack World page on berlios]
* [http://slacky.eu European Slackware community]
* [http://slackware.linux.or.id Indonesian Slackware Community] - by [[User:Willysr|Willysr]]
* [http://open-eslack.org/ Spanish Slackware community]
* [http://www.slack-world.com Iranian Slackware Community]
* http://jtgzmanager.sf.net/  A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.

==Free packages==
* [http://connie.slackware.com/~alien/slackbuilds/ Eric Hameleers' packages] [http://slackware.org.uk/people/alien/slackbuilds/ mirror] 
* [http://rlworkman.net/pkgs/ rworkman's packages] [http://slackware.org.uk/people/rlworkman/ mirror] 
* [http://www.nielshorn.net/slackware/slack_pkg.php Niels Horn's packages]
* http://www.linuxpackages.net/
* [http://repository.slacky.eu/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware

==SlackBuild Repositories==
* [http://slackbuilds.org The SlackBuilds.org Project]
* [http://www.slackware.com/~alien/slackbuilds/ Eric "Alien" Hameleer's SlackBuilds]
* [http://slackware.org.uk/people/rlworkman/sources/ rworkman's SlackBuilds]

==Live CD's based on Slackware==
* [http://porteus.org/ Porteus] - A fast, portable and modular live CD/USB, originally started as a community remix of Slax
* [http://www.imagineos.com.br/ ImagineOS] (formerly GoblinX)
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://open-eslack.org/wiki/ A Spanish Slackware Wiki]

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for stable and current

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs</text>
    <sha1>96e64aefdbf0a3842352843fd95b2c61044005ba</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Install Slackware Using A USB Flash Drive</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>490</id>
    <parentid>439</parentid>
    <timestamp>2011-06-07T11:08:05Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Installation quirks</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2860" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is, and mount the device to some location:

 mkdir flash &amp;&amp; mount /dev/sdX1 flash

When installing, choose "Install from a hard drive partition", with the USB drive as source partition.

Other than that, installation process should be no different than when installing from a DVD.</text>
    <sha1>b2496012dc8976cf5aa9abd4bea7454bcceeae11</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>492</id>
    <parentid>449</parentid>
    <timestamp>2011-06-13T22:55:35Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Upgraded Mediawiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3942" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. [[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>e5c6152fa1fae19926f4ca8f6569dc15cebcb2fb</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>ALSA</title>
  <ns>0</ns>
  <id>35</id>
  <revision>
    <id>493</id>
    <parentid>420</parentid>
    <timestamp>2011-06-13T23:00:14Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Added sepaker-test</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1032" xml:space="preserve">[[Category:Tutorials]]

Sound problems *should* be rare these days, and of the ones that still exist, they are likely related to suspend/resume.  Those are driver issues which are largely out of your control, but see the documentation with the pm-utils package for details on handling those issues.

: &lt;code&gt;alsaconf&lt;/code&gt; used to be needed to set up sound cards in linux, but even that shouldn't be needed in recent linux distributions - everything should be handled automatically.

: &lt;code&gt;alsamixer&lt;/code&gt; can be used to change the volume.

: &lt;code&gt;alsactl store&lt;/code&gt; is used to save the volume settings.

: &lt;code&gt;alsactl restore&lt;/code&gt; is used to restore the volume settings.  This is automatically run on boot, so you usually won't need to run this command.

: &lt;code&gt;speaker-test&lt;/code&gt; is used to test speaker output.

There is one tip for the Sound Baster 5.1 cards: sometimes you want to MUTE digital out so you can hear on all the speakers; in alsamixer, you just press M on the &lt;tt&gt;Analog/Digital Output Jack&lt;/tt&gt; item.</text>
    <sha1>c8426a3bd290171f0e6312a45822c49ebfa153a4</sha1>
  </revision>
  <revision>
    <id>494</id>
    <parentid>493</parentid>
    <timestamp>2011-06-13T23:04:09Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Added aplay</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1084" xml:space="preserve">[[Category:Tutorials]]

Sound problems *should* be rare these days, and of the ones that still exist, they are likely related to suspend/resume.  Those are driver issues which are largely out of your control, but see the documentation with the pm-utils package for details on handling those issues.

: &lt;code&gt;alsaconf&lt;/code&gt; used to be needed to set up sound cards in linux, but even that shouldn't be needed in recent linux distributions - everything should be handled automatically.

: &lt;code&gt;alsamixer&lt;/code&gt; can be used to change the volume.

: &lt;code&gt;alsactl store&lt;/code&gt; is used to save the volume settings.

: &lt;code&gt;alsactl restore&lt;/code&gt; is used to restore the volume settings.  This is automatically run on boot, so you usually won't need to run this command.

: &lt;code&gt;aplay&lt;/code&gt; a command-line sound player. 

: &lt;code&gt;speaker-test&lt;/code&gt; is used to test speaker output.

There is one tip for the Sound Baster 5.1 cards: sometimes you want to MUTE digital out so you can hear on all the speakers; in alsamixer, you just press M on the &lt;tt&gt;Analog/Digital Output Jack&lt;/tt&gt; item.</text>
    <sha1>8f0b882893fcba71080a7162dc2be988833aebcf</sha1>
  </revision>
  <revision>
    <id>495</id>
    <parentid>494</parentid>
    <timestamp>2011-06-13T23:27:45Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Checking ConfirmEdit extension</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="971" xml:space="preserve">[[Category:Tutorials]]

Sound problems *should* be rare these days, and of the ones that still exist, they are likely related to suspend/resume.  Those are driver issues which are largely out of your control, but see the documentation with the pm-utils package for details on handling those issues.

: &lt;code&gt;alsaconf&lt;/code&gt; used to be needed to set up sound cards in linux, but even that shouldn't be needed in recent linux distributions - everything should be handled automatically.

: &lt;code&gt;alsamixer&lt;/code&gt; can be used to change the volume.

: &lt;code&gt;alsactl store&lt;/code&gt; is used to save the volume settings.

: &lt;code&gt;alsactl restore&lt;/code&gt; is used to restore the volume settings.  This is automatically run on boot, so you usually won't need to run this command.

There is one tip for the Sound Baster 5.1 cards: sometimes you want to MUTE digital out so you can hear on all the speakers; in alsamixer, you just press M on the &lt;tt&gt;Analog/Digital Output Jack&lt;/tt&gt; item.</text>
    <sha1>ccf2823bf01fa3c8f6a7ea8413679d96cbcfe20c</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>496</id>
    <parentid>455</parentid>
    <timestamp>2011-06-24T22:02:36Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1486" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Alisonken1[Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]
* [[User:natex|natex]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>9512faa000cd4d66f9acbe5e5ac2dc9652a51ac2</sha1>
  </revision>
  <revision>
    <id>497</id>
    <parentid>496</parentid>
    <timestamp>2011-06-24T22:03:26Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1486" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]
* [[User:natex|natex]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>e5853917ce5c345599ba8784e314c0f4ce79e7cb</sha1>
  </revision>
  <revision>
    <id>517</id>
    <parentid>497</parentid>
    <timestamp>2011-09-09T13:05:46Z</timestamp>
    <contributor>
      <username>Adioe3</username>
      <id>199</id>
    </contributor>
    <minor/>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1511" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Adioe3|adioe3]]
* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]
* [[User:natex|natex]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>d9e481250835d2428c0c318d6b0a3c8b70ab9079</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>User:Alisonken1</title>
  <ns>2</ns>
  <id>242</id>
  <revision>
    <id>498</id>
    <timestamp>2011-06-24T22:05:15Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <comment>Created page with "Real name: Ken Roberts IRC Nickname: alisonken1 Slackware mirror that I maintain: http://slackware.dreamhost.com/slackware"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="122" xml:space="preserve">Real name: Ken Roberts
IRC Nickname: alisonken1
Slackware mirror that I maintain: http://slackware.dreamhost.com/slackware</text>
    <sha1>fb1b30215caa521c33a510c99773cf52c6d13b87</sha1>
  </revision>
  <revision>
    <id>499</id>
    <parentid>498</parentid>
    <timestamp>2011-06-24T22:06:02Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="128" xml:space="preserve">* Real name: Ken Roberts
* IRC Nickname: alisonken1
* Slackware mirror that I maintain: http://slackware.dreamhost.com/slackware</text>
    <sha1>03f96b3ce662091c29ffa3d5048f2220743361b7</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Slapt-get</title>
  <ns>0</ns>
  <id>161</id>
  <revision>
    <id>500</id>
    <parentid>189</parentid>
    <timestamp>2011-06-25T17:03:12Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>/* Distributions */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8697" xml:space="preserve">'''slapt-get''' is an [[APT]]-like system for [http://en.wikipedia.org/wiki/Slackware Slackware] [[package management]].

It tries to emulate the features of [[Debian]]'s [[apt-get]] as closely as possible.

==Features==

* uses native [http://en.wikipedia.org/wiki/Slackware Slackware] tools (installpkg, upgradepkg, and removepkg)
* supports multiple package sources (including http://linuxpackages.net)
* cache data concerning packages and updates from package sources
* supports sources from ftp, ftps, http, https, file:/// and more (libcurl)
* resumes broken downloads and will verify package integrity with [http://en.wikipedia.org/wiki/Md5 MD5] checksum
* show packages that are available (from cached data) and installed
* search package listing using [http://en.wikipedia.org/wiki/POSIX POSIX] and extended [http://en.wikipedia.org/wiki/Regular_expressions regular expressions] by package name, location, and description
* retrieve, install, and remove packages by name or by specific version
* retrieve and apply updates
* upgrade from one Slackware release to another in a few simple steps - see [[Upgrade_Using_Slapt-get]]
* show description of packages, including mirror location, version, size, dependencies (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ10 FAQ]), conflicts (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ31 FAQ]), suggestions (where available, see [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ44 FAQ]), description, and installation status
* exclude (hold) packages from upgrades, by name or by regular expression
* transaction engine for install, remove, and upgrades, reporting concise information on what is to be done, ensuring each step happens correctly
* "compare package version" algorithm to prevent downgrades
* recursive dependency resolution using slack-required meta-data ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ10 see FAQ]) supporting hard, soft, and conditional dependencies
* package conflict resolution using slack-conflicts meta-data ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ31 see FAQ])
* package suggestion support for complimentary packages ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ44 see FAQ])
* Package data download robustness, only writing changes if all sources download successfully as well as only downloading those sources that have changed since the last download
* [http://en.wikipedia.org/wiki/I18n i18n] support via [http://en.wikipedia.org/wiki/GNU GNU] gettext with over 20 language translations
* extremely fast and easy to script with

==Dependencies==

slapt-get does not provide dependency resolution for packages included within the Slackware distribution. It does, however, provide a framework for dependency resolution in Slackware compatible packages similar in fashion to the hand-tuned method [http://en.wikipedia.org/wiki/Advanced_Packaging_Tool Advanced Packaging Tool|APT] utilizes. Several package sources and Slackware based distributions take advantage of this functionality.

Adding dependency information requires no modification to the packages themselves.  Rather, the package listing file, PACKAGES.TXT, is used to specify these relationships.  This file is provided by  [http://en.wikipedia.org/wiki/Patrick_Volkerding Patrick Volkerding] and is similar to the Packages.gz file in use by [http://en.wikipedia.org/wiki/Debian Debian].  Several scripts are available to generate the PACKAGES.TXT file from a group of packages (See [http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ17 FAQ #17]).  The file format used by  [http://en.wikipedia.org/wiki/Patrick_Volkerding Patrick Volkerding] is extended by adding a few extra lines per package.  slapt-get then parses this file during source downloads.  Typically, third party packages store the dependency information within the package itself for later extraction into the PACKAGES.TXT ([http://software.jaos.org/BUILD/slapt-get/FAQ.html#slgFAQ19 See FAQ #19]).  The inclusion of this information within the Slackware package format does not inhibit the ability for Slackware pkgtools to install these packages.  This information is silently ignored and discarded after the package is installed.

[http://www.stabellini.net/depslack.html Other methods] exist for adding dependency information for official Slackware packages without altering the packages themselves.

==Package Sources==

slapt-get works with official Slackware mirrors and third party package repositories.  slapt-get looks for support files, PACKAGES.TXT and CHECKSUMS.md5, in the repository for package information.  These files provide package names, versions, sizes (both compressed and uncompressed), checksums, as well as a package description.  These files can be extended, as discussed in the previous section, to add dependency listings, conflict information, and package suggestions.  These files can also proxy for other remote sources by specifying a MIRROR declaration for each package.  

==libslapt==

slapt-get exports a [http://en.wikipedia.org/wiki/C_programming_language C] [http://en.wikipedia.org/wiki/Library_(computer_science) library] that is used by [http://en.wikipedia.org/wiki/gslapt gslapt] to provide similar functionality through a [http://en.wikipedia.org/wiki/GTK+ GTK+] frontend. 

==Distributions==

Besides Slackware, slapt-get may be used with or included by the following distributions:

 * [http://www.vectorlinux.com Vector Linux]
 * [http://www.mutagenix.org Mutagenix]
 * [http://slax.linux-live.org SLAX]
 * [http://www.slamd64.com/ Slamd64]
 * [http://gsb.sourceforge.net/ Freerock GNOME]
 * [http://www.gware.org/ GWARE GNOME]
 * [http://slampp.abangadek.com/ SLAMPP]
 * [http://getopenlab.com/ OpenLab GNU/Linux]
 * [http://ocsid.spaghettilinux.org/ Open Community Slackware Install DVD]
 * [http://floyd-linux.pappapc.com/ Floyd GNU/Linux]
 * [http://www.stibs.cc/stx/ STX GNU/Linux]
 * [http://www.nnlinux.com/ Nonux GNU/Linux]
 * [http://wolvix.org/ Wolvix LiveCD]
 * [http://www.collegelinux.org College Linux]
 * [http://www.zenwalk.org/ Zenwalk Linux]
 * [http://www.truvalinux.org.tr Truva Linux]
 * [http://sms.it-ccs.com SMS(Superb Mini Server)]

==Examples==

  $ slapt-get --update
  Retrieving package data http://www.slackware.at/data/slackware-10.0/ ...Done
  Retrieving patch list http://www.slackware.at/data/slackware-10.0/ ...Done
  Retrieving checksum list http://www.slackware.at/data/slackware-10.0/ ...Done
  Reading Package Lists...Done
  Retrieving package data http://software.jaos.org/slackpacks/10.0/ ...Cached
  Retrieving patch list http://software.jaos.org/slackpacks/10.0/ ...Cached
  Retrieving checksum list http://software.jaos.org/slackpacks/10.0/ ...Cached
  Reading Package Lists...Done

  $ slapt-get --upgrade
  Reading Package Lists... Done
  The following packages have been EXCLUDED:
    devs kernel-headers
  The following packages will be upgraded:
    binutils bash bin bind cdrtools bzip2 kbd cups cxxlibs e2fsprogs etc gawk gcc gdb inetd infozip less links
    logrotate lynx man man-pages openssh openssl openssl-solibs pidentd pkgtools procps sed shadow slocate
    sysklogd sysvinit tar tcpip util-linux vim wget zlib
  39 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  Need to get 36710K of archives.
  After unpacking 17880K of additional disk space will be used.
  Do you want to continue? [y/N]

  $ slapt-get --show slapt-get
  Package Name: slapt-get
  Package Mirror: http://software.jaos.org/slackpacks/10.0/
  Package Location: .
  Package Version: 0.9.9f-i386-1
  Package Size: 147 K
  Package Installed Size: 530 K
  Package Required:   curl &gt;= 7.12.0-i486-1,glibc-solibs &gt;= 2.3.2-i486-7,binutils,openssl &gt;= 0.9.7d-i486-1,pkgtools,zlib
  Package Conflicts:
  Package Suggests:
  Package MD5 Sum:  cb4b44cbb4efee4e993109231b107828
  Package Description:
  slapt-get: slapt-get (APT like system for Slackware)
  slapt-get: slapt-get is an APT like system for Slackware package management.
  slapt-get:
  slapt-get:  * See /usr/doc/slapt-get-0.9.9f/ for complete documentation.
  slapt-get:  * You will also want to customize /etc/slapt-get/slapt-getrc,
  slapt-get:    using a local mirror.  www.slackware.com may be very busy.
  slapt-get:  * Support:
  slapt-get:    http://software.jaos.org/cgi-bin/mailman/listinfo/slapt-get-user
  slapt-get:  * Please translate
  slapt-get:    http://software.jaos.org/BUILD/slapt-get/po/slapt-get.pot
  slapt-get:    then send to slapt-get-devel@software.jaos.org
  slapt-get:
  Package Installed: yes

==External links==
*[http://software.jaos.org/#slapt-get Homepage]

[[Category:Information]]</text>
    <sha1>fa97bc4ad0e9d8c334d8edb2b1e551172ef82772</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Upgrade Using Slapt-get</title>
  <ns>0</ns>
  <id>174</id>
  <revision>
    <id>501</id>
    <parentid>202</parentid>
    <timestamp>2011-06-26T10:37:24Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10553" xml:space="preserve">[[Category:Tutorials]]
= Introduction =

See the [[Slapt-get]] page for an introduction to slapt-get and its functionality.

Prior to using slapt-get, you should really be familiar with proper usage of the native Slackware package management tools:
 man pkgtool
 man installpkg
 man upgradepkg
 man removepkg
As indicated in the link above, slapt-get is *not* a replacement for those utilities - it *uses* those utilities.  As such, any inherent "limitations" (yes, I use that term loosely) in the pkgtool suite will also apply to slapt-get.

= Installation and Configuration =

Get the [[slapt-get]] package for your version of Slackware.

Once it's installed, configure it to point to your favourite
mirror (edit '''/etc/slapt-get/slaptgetrc''')

    # See /usr/doc/slapt-get-0.10.1/example.slapt-getrc 
    # for example source entries and configuration hints.
    WORKINGDIR=/var/slapt-get
    EXCLUDE=^kernel-.*,^alsa-.*,^glibc.*,.*-[0-9]dl$,^devs$,^udev$,aaa_elflibs,x86_64
    SOURCE=http://slackware.osuosl.org/slackware-12.2/:OFFICIAL
    SOURCE=http://software.jaos.org/slackpacks/12.2/:OFFICIAL

= Usage Hints =

Depending upon your individual goals of using slapt-get, the usage hints will vary.  An individual wishing to upgrade  from one release of Slackware to another will have more issues with which to contend than another individual who simply wants to keep up-to-date with official security/stability patches.

The biggest piece of advice I can give to *anyone* regardless of how/why you're using slapt-get is this: READ THE CHANGELOG!  The pertinent portions of the changelog are also viewable for each package using --show option.  You'll be okay most of the time if you ignore this advice, but don't come crying to ##slackware if you do... :)  

From '''man slapt-get''':
 UPGRADE.TXT and ChangeLog.txt is still required reading, the latter is especially true  when running -current.

By the way, don't even consider trying to follow the Slackware -current development using slapt-get; that's just *asking* for a problem (for reasons which will hopefully be clear later).  
 Official ChangeLog is at ftp://ftp.slackware.com/pub/slackware/slackware-12.2/ChangeLog.txt
 Replace the "12.2" with the release version you're using.
Rather than using the official ChangeLog (and Slackware.com bandwidth), it's better to use one of the official Slackware mirrors (you'll notice faster connections with the mirrors):
 &lt;SlackwareMirror&gt;/slackware-&lt;version&gt;/ChangeLog.txt
See the Slackware site [[http://slackware.com/getslack/]] to find an official mirror site.

== Usage Hint #1: Security and Stability Patches ==

If your only goal is to stay up-to-date with official security and stability patches for your version of Slackware, then the default configuration of slapt-get should work fine for you.  While I'm not the author of slapt-get (Jason, feel free to jump in here), it seems to me that this was the original intent of slapt-get (and it works *extremely* well for that task, might I add).

The only exception of which I can think is kernel upgrades; thankfully, those haven't happened *too* often in official releases in recent memory, but they do occur frequently enough to be worth considering.  The default configuration of slapt-get will ignore kernel upgrades, so the only way you'll know about those is by reading the official ChangeLog.  Anyway, every time you upgrade your kernel, you'll need to make sure the paths in '''/etc/lilo.conf''' point to a valid kernel, and then run '''/sbin/lilo''' to reinstall LILO.  If you use some other boot loader, then I'm going to assume you know enough about its usage to perform the corresponding operation (if required) after upgrading your kernel.

I would recommend that you keep your old kernel around when installing a new one; it's always good to have a known-good kernel lying around just in case the new one doesn't boot.  However, you'll notice that by default, running this command: 
 slapt-get --install kernel-$VERSION
will *upgrade* the kernel; in other words, it will *remove* the old kernel package and *install* the new one.  This is not desirable if you wanted to keep your old kernel, so you can run this command instead:
 slapt-get --install --no-upgrade kernel-$VERSION
From '''man slapt-get''':
  --no-upgrade
         Install the package rather than  attempting  to  detect  if  a  previous  version  is
         installed  and  upgrading  it.   This is useful for installing kernel packages.  This
         option is only valid for --install targets.
You might also find this option useful for installing multiple versions of the alsa-* packages; if you're running both 2.4.x and 2.6.x kernels, you'll need the alsa-driver packages for both kernels, so an *upgrade* of the 2.4.x version to 2.6.x will remove the 2.4.x version.

== Usage Hint #2: Upgrade From One Release To Another ==

Every Slackware release includes a file named UPGRADE.TXT - it was included for a reason, so READ IT!  Once you are familiar with its contents, the rationale behind the information below will make more sense.  

=== Step 1: Edit your /etc/slapt-get/slaptgetrc ===

Edit your '''/etc/slapt-get/slaptgetrc''' file to reflect the new Slackware version

This:
    SOURCE=http://slackware.osuosl.org/slackware-12.1/
    SOURCE=http://software.jaos.org/slackpacks/12.1/
becomes this:
    SOURCE=http://slackware.osuosl.org/slackware-12.2/:OFFICIAL
    SOURCE=http://software.jaos.org/slackpacks/12.2/:OFFICIAL

=== Step 2: Download all updated packages === 

Download all updated packages to slapt-get's working directory; by default, this is '''/var/slapt-get'''
 slapt-get --dist-upgrade --ignore-excludes --download-only

=== Step 3: Put your machine in single-user mode ===

Make sure you have already performed step 2, because the network will not be available in runlevel 1.
 telinit 1

=== Step 4: Upgrade main packages ===

Versions &gt;= 0.9.11 upgrade glibc-solibs, pkgtools, and sed first , and then upgrade the remainder of the packages.  If you have read the UPGRADE.TXT file, you already know why this is needed. (hint, hint)

* '''Step 4a:''' If you are using slapt-get version earlier than 0.9.11, do:
 slapt-get --install kernel --no-upgrade
 slapt-get --install glibc-solibs pkgtools sed
 slapt-get --dist-upgrade

* '''Step 4b:''' If you are using slapt-get version 0.9.11 or later, do:
 slapt-get --install kernel --no-upgrade
 slapt-get --dist-upgrade --ignore-excludes

The '''--dist-upgrade''' option will prompt you to install all *new* packages in the ./a series, and you should say "yes" to ensure that you have a working system after the upgrade.  See step 8 below for more information on installing new packages.

=== Step 5: Update LILO and config files ===
* Make sure the paths in '''/etc/lilo.conf''' point to a valid kernel image, and then run '''/sbin/lilo'''
* Fix your config files in '''/etc'''; the new ones are named with a *.new suffix.  You should be able to use '''diff -u file file.new''' to show the differences between file and file.new.  You'll have to decide whether to completely replace the old files with the new ones or merge your changes into the new ones first, but you *must* use the new files.

=== Step 6: Go back to multi-user mode ===

Sometimes the screen stays blank when you return to runlevel 3, and you might be worried that something went wrong.  Before you panic, type '''clear''' and press Enter - you'll probably get your root prompt back :)
 telinit 3

=== Step 7: Remove obsolete packages ===

There is an option to do this automatically with slapt-get:
 slapt-get [--remove|--dist-upgrade] --remove-obsolete
From '''man slapt-get'''
   --remove-obsolete
         Remove  installed packages that are no longer available.  This works for dist-upgrade
         only.  This removes packages that are no longer available from  any  current  package
         sources,  but  are  currently  installed.  Be careful as this will also remove custom
         built packages.
As you see, this option will be fine ''if you don't have any custom-compiled packages'' installed (such as with [[checkinstall]] or using [[SlackBuild_Scripts]]).  Read through the official ChangeLog to find all packages that were removed from Slackware during the development phase; you might be able use something like this to make the process go a bit more quickly:
 grep -i removed ChangeLog.txt  OR  grep Removed ChangeLog.txt

=== Step 8: Add new packages ===

Similar to removing obsolete packages, there is an option to do this automatically with slapt-get using the '''--install-set''' option:
 slapt-get --upgrade --install-set a ap d f k kde l n t tcl x xap y

From '''man slapt-get''':
   --install-set [disk set(s)]
          Install specified disk set(s).  example: --install-set xap n l

This option will upgrade (or install, if not already installed) every package in every disk set.  For reasons already detailed (kernel/alsa versions), this may not be desirable; additionally, if you don't have a full installation of Slackware for whatever reason, this will not be desirable. 

The safest option is to read through the official ChangeLog.txt, make a note of new packages added during the release cycle, and install them now with this command:
 slapt-get --install &lt;newpackage1&gt; &lt;newpackage2&gt; &lt;...&gt;
You might be able to use something like this to make the process go a bit more quickly, but it will return quite a few extraneous results.
 grep -i added ChangeLog.txt

=== Step 9: Admire the Results :) ===
At this point, you should be running the latest version of Slackware.  

== Usage Hint #3: Keep Up With Slackware -current Development ==

After modifying your &lt;code&gt;/etc/slapt-get/slaptgetrc&lt;/code&gt; file to reflect -current sources, the most important advice you should hear is: &lt;b&gt;READ THE CHANGELOG&lt;/b&gt;

Seriously, always read the ChangeLog.txt file associated with the -current tree; so long as you read it prior to running the &lt;code&gt;slapt-get --upgrade&lt;/code&gt; command, you should be familiar with any issues that might be encountered.

One idea you might consider is to use slapt-get as a "double checking" tool to ensure you haven't accidentally overlooked any packages.  While the concerns detailed earlier in this article apply here (you won't be informed of any new packages added to -current), you can use the following lines to see if you missed anything that needed to be upgraded:

 slapt-get --update
 slapt-get --upgrade --simulate

= Related Links =

* [[Release_Changes|Changes in Slackware Release Versions]]</text>
    <sha1>df3bf55267bb730328f7c4bfd1cbafb979c1c770</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Fluxbox Newbie</title>
  <ns>0</ns>
  <id>243</id>
  <revision>
    <id>503</id>
    <timestamp>2011-07-31T13:20:08Z</timestamp>
    <contributor>
      <username>Kevcortez</username>
      <id>194</id>
    </contributor>
    <comment>basic fluxbox configuration and installing openoffice</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13719" xml:space="preserve">[[Category:Tutorials]] 
== Fluxbox Desktop -- basic configuration ==
This is my attempt to contribute to Slackware documentation with a newbie oriented how-to for initially setting up a usable Fluxbox desktop. There is also a section on installing OpenOffice, since many desktop users will want that program. &lt;br /&gt;


'''Use at your own risk!''' &lt;br /&gt;


I assume a default Slackware install.&lt;br /&gt;


Reference:&lt;br /&gt;
http://www.fluxbox.org &lt;br /&gt;
http://fluxbox-wiki.org&lt;br /&gt;

Fluxbox is a very nice desktop window manager that has most everything you need.  It is minimal, which allows good desktop performance on older or moderate hardware.  Plus, it can be configured to really simplify things so you don't have to deal with lots of programs you don't understand or ever use.  Besides simplification, the right configuration of Fluxbox can add quite a bit to your computing productivity.

Note: One time fluxbox refused to start for me.  As I recall, the problem was fixed by removing the .Xauthority and .ICEauthority files from my home folder and trying again.

Note: the ''' [user@host] ~/ $ ''' represents the command prompt with '''~''' being a shortcut for your /home/username folder.

&lt;blockquote&gt;
Tip: Use "bash completion" when working with directories and files from the command prompt.
Type the first few letters of the directory or file you want and the "tab" key.  If the text completes, then ''you are on the right path.''  Pressing "tab" twice will give a list of possible matches.
&lt;/blockquote&gt;
&lt;blockquote&gt;
Tip2: use the command "pwd" to show your present working directory and "whoami" to show your username.
&lt;/blockquote&gt;

== Choosing Fluxbox ==


* &lt;big&gt;Choose Fluxbox as the the default window manager&lt;/big&gt;
After you log in, from the console or a terminal screen in X: &lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ xwmconfig 
&lt;/code&gt;
: ( select fluxbox and OK )


If you are in X, close the current X session, log out, close, exit, or end.

Start up the (new) default fluxbox &lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ startx 
&lt;/code&gt;

== Fluxbox Configuration ==
Now, let us get fluxbox configured.
You will need to look into your ''' ~/.fluxbox ''' directory

Right-click on the desktop to display the menu and select rxvt or xterm
which will open a terminal window.&lt;br /&gt;


The Fluxbox configuration is kept in a hidden folder (dotfile) which may or may not be visible in an ordinary file browser, but won't be shown with a plain "ls" command, unless it is specified. &lt;br /&gt;
 
&lt;code&gt;
 [user@host] ~/ $ ls .fluxbox
    apps    keys           menu    init    slitlist
    init    windowmenu     overlay startup backgrounds  styles
&lt;/code&gt;

You should see something resembling this. &lt;br /&gt; 
Fluxbox should be started once before you modify it because it writes initial configurations in your .fluxbox folder.&lt;br /&gt;

* &lt;big&gt;Format the clock&lt;/big&gt;
From the menu, select '''Fluxbox-menu | Configure | Toolbar | Edit clock format''' &lt;br /&gt;
A small edit box opens and you can modify the format string and then press "enter."  Here is a suggestion: &lt;br /&gt;
&lt;code&gt;
 %I:%M %a %b %e
&lt;/code&gt;

* &lt;big&gt;Add keyboard access to main menu&lt;/big&gt;
Use the command below or right-click on the desktop to display the menu and select an editor from the Editors section -- gvim is good, but kate or kwrite are easier and more intuitive to use.  In fact, with kate you have a built-in terminal, which might make things easier. &lt;br /&gt;
&lt;code&gt;
 [user@host] ~/ $ kate .fluxbox/keys &amp;
&lt;/code&gt;

Edit the keys file by inserting the following at the very beginning, so it is easy to find if you want to change it later. (I assume you have a US pc105 keyboard, with two "windows" keys and one "menu" key on the bottom row.)

&lt;code&gt;
 # keyboard access to main menu
 # Menu key is next to right Control key
 None Menu     :RootMenu
 Shift Menu    :HideMenus
 # optional, Super_L is the left windows key
 None Super_L  :RootMenu
 Shift Super_L :HideMenus
&lt;/code&gt;

You can use the "xev" command to see the names and keycodes of your keyboard keys. &lt;br /&gt;
&lt;code&gt;
 [user@host] ~/ $ xev
&lt;/code&gt;

When done, save the keys file. &lt;br /&gt;

Test it by pressing the Menu key and the Shift-Menu to show/hide the Fluxbox menu.  &lt;br /&gt;

You may reload the configuration by using the menu ''' Fluxbox-menu | Reload config ''' 
Right click on the desktop to get this from the Fluxbox menu.

* Create a simple menu.
&lt;code&gt;
 [user@host] ~/ $ kate .fluxbox/menu.simple &amp;
&lt;/code&gt;
kate may say it cannot read the file, but continue on.  It will give you a blank file.&lt;br /&gt;

Copy/paste the following menu: &lt;br /&gt;
&lt;code&gt;
 # My Fluxbox menu
 [begin] (Fluxbox menu.simple) {} &lt; &gt;
 [encoding] {UTF-8}
    [exec] (Terminal) {konsole} &lt; &gt;
    [exec] (Browser) {firefox} &lt; &gt;
    [exec] (Editor) {kate} &lt; &gt;
    [exec] (Reader) {okular} &lt; &gt;
    [exec] (Audio) {audacious} &lt; &gt;
    [separator]
    [submenu] (Net) {} &lt;&gt;
        [exec] (Browser) {seamonkey} &lt; &gt;
        [exec] (Mail) {thunderbird} &lt; &gt;
        [exec] (IM) {pidgin} &lt; &gt;
        [exec] (Chat) {xchat} &lt; &gt;
        [exec] (FTP) {gftp} &lt; &gt;
    [end]
    [submenu] (Media) {} &lt; &gt;
        [exec] (Graphics) {gimp} &lt; &gt;
        [exec] (Photos) {gqview} &lt; &gt;
        [exec] (Media Player) {xine} &lt; &gt;
        [exec] (Scanner) {xsane} &lt; &gt;
        [exec] (CD Copy) {k3b} &lt; &gt;
    [end]
    [submenu] (Office) {} &lt;&gt;
        # openoffice and acrobat are not included in Slackware
        [submenu] (OpenOffice) {} &lt;&gt;
                [exec] (Writer) {swriter} &lt;&gt;
                [exec] (Spreadsheet) {scalc} &lt;&gt;
                [exec] (Presentation) {simpress} &lt;&gt;
                [exec] (Draw) {sdraw} &lt;&gt; 
        [end]
        [exec] (OfficeSuite) {soffice} &lt; &gt;
        [exec] (PIM kde) {kontact} &lt; &gt;
        [exec] (Acrobat) {acroread} &lt; &gt;
        [exec] (Accounts) {kmymoney} &lt; &gt;
    [end]
    [submenu] (Tools) {} &lt; &gt;
        [exec] (Kill) {xkill} &lt; &gt;
        [exec] (Xterm) {xterm} &lt; &gt;
        [exec] (Files) {dolphin} &lt; &gt;
        [exec] (Calculator) {kcalc} &lt; &gt;
        [exec] (System) {ksysguard} &lt; &gt;
        [exec] (Manual) {xman} &lt; &gt;
        [exec] (Help) {khelpcenter} &lt; &gt;
        [exec] (Lock) {xlock} &lt; &gt;
    [end]
    [separator]
    [submenu] (Fluxbox-menu) {} &lt;&gt;
        [config] (Configure) {} &lt;&gt;
        [submenu] (Styles) {Choose a style...} &lt;&gt;
            [stylesdir] (/usr/X11R6/share/fluxbox/styles) {} &lt;&gt;
            [stylesdir] (~/.fluxbox/styles) {} &lt;&gt;
        [end]
        [workspaces] (Workspace List) {} &lt;&gt;
        [submenu] (Tools) {} &lt;&gt;
            [exec] (Windowname) {xprop|grep WM_CLASS|cut -d \" -f 2|xmessage -file - -center} &lt;&gt;
            [exec] (Screenshot - JPG) {import screenshot.jpg &amp;&amp; display -resize 50% screenshot.jpg}
            [exec] (Screenshot - PNG) {import screenshot.png &amp;&amp; display -resize 50% screenshot.png}
            [exec] (Run) {fbrun }
            [exec] (Regen Menu) {fluxbox-generate_menu }
        [end]
        [reconfig] (Reload config) {} &lt;&gt;
        [restart] (Restart) {} &lt;&gt; 
        [exec] (Shutdown) {/usr/bin/sudo /sbin/shutdown -h now} &lt;&gt;
        [separator]
        [exit] (Exit) {} &lt;&gt;
    [end]
    [separator]
    [exit] (Exit) {} &lt;&gt;
 [endencoding]
 [end]
&lt;/code&gt;

To add a program, the syntax is:
&lt;code&gt;
 [exec] (Label) {command} &lt; optional path to .xpm icon &gt;
&lt;/code&gt;
Also, every  '''[submenu]''' tag must have a matching ''' [end] ''' tag.

Save this file as .fluxbox/menu.simple (kate '''File | Save''') &lt;br /&gt;

'''Do not overwrite your .fluxbox/menu file.''' You may want it later.&lt;br /&gt;


Open the file .fluxbox/init &lt;br /&gt;
&lt;code&gt;
 kate .fluxbox/init &amp;
&lt;/code&gt;
Or just use kate's '''File | Open.'''  Since .fluxbox should be the current directory, the file dialog should show the file, or you can enter .fluxbox/init in the Name box at the bottom of the dialog.&lt;br /&gt;

&lt;code&gt;
Find the following line (near the bottom)&lt;br /&gt;
 session.menuFile:	~/.fluxbox/menu
&lt;/code&gt;
Change "menu" to "menu.simple" and save/close the init file.&lt;br /&gt;


* &lt;big&gt;Now for the desktop background.&lt;/big&gt;  
Copy your favorite background .jpeg file to .fluxbox/backgrounds/my_favorite_background.jpg

&lt;code&gt;
 [user@host] ~/ $ cp path-to/my_favorite_background.jpg .fluxbox/backgrounds/
 [user@host] ~/ $ chmod 644 .fluxbox/backgrounds/*
&lt;/code&gt;

Now open the overlay file .fluxbox/overlay and add these lines:
&lt;code&gt;
 background: fullscreen
 background.pixmap: ~/.fluxbox/backgrounds/my_favorite_background.jpg
&lt;/code&gt;

Your overlay file should look like this:
&lt;code&gt;
 ! The following line will prevent styles from setting the background.
 ! background: none
 background: fullscreen
 background.pixmap: ~/.fluxbox/backgrounds/my_favorite_background.jpg
&lt;/code&gt;
Save/close the overlay file.&lt;br /&gt;


See what it looks like with the fbsetbg command&lt;br /&gt;
&lt;code&gt;
 [user@host] ~/ $ fbsetbg ~/.fluxbox/backgrounds/my_favorite_background.jpg
&lt;/code&gt;
Now, make sure all your modified files are saved and select Restart from the Fluxbox menu --select '''Fluxbox-menu | Restart'''&lt;br /&gt;


* &lt;big&gt;Learn more from the man pages:&lt;/big&gt;
&lt;code&gt;
 [user@host] ~/ $ man fluxbox | less
 [user@host] ~/ $ man fluxstyle | less
&lt;/code&gt;
(press "q" to quit the less pager or man page)

Or use the Help --&gt; khelpcenter; select Unix Manuals, section 1, fluxbox; or even xman.

I also suggest doing a web search for .Xdefaults or .Xresources files.

Hopefully, you will like the look and feel of Fluxbox. Of course, there are more things you can do with your configuration, but hopefully this introduction has shown you some possibilities and got you off to a good start.

== Installing Open Office ==
Since OpenOffice is probably wanted by many desktop users, but not included in Slackware, I have these directions for getting it installed. &lt;br /&gt;

* Uninstalling OpenOffice for Upgrade

See if you have OpenOffice packages installed.  The packages have names containing ooobasis or openoffice.&lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ ls /var/log/packages | grep ooo
 [user@host] ~/ $ ls /var/log/packages | grep openoffice
&lt;/code&gt;

If you are going to upgrade, first uninstall your existing packages.
If you did not use Slackware compatible packages, then you can probably simply delete the openoffice.org directories under /opt.  Otherwise, use pkgtool.&lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ su
  password
 [root@host] ~/ # pkgtool
&lt;/code&gt;
: Choose Remove Packages and scroll down to the openoffice packages.
: Select them with the space bar and then tab to OK and press enter.

'''Be careful with pkgtool or you will remove the wrong packages.'''

Or, to just remove the directories (this does not update Slackware's package tracking). &lt;br /&gt;

&lt;code&gt;
 [root@host] ~/ # cd /opt
 [root@host] opt/ # rm -f openoffice3.org
 [root@host] opt/ # rm -f openoffice3.org3
&lt;/code&gt;
&lt;br /&gt;

* &lt;big&gt;Downloading OpenOffice.org&lt;/big&gt;

Point your browser to http://www.openoffice.org

Click on "I want to download OpenOffice.org"

Choose "Searching for another version"
: This takes you to the alternate downloads page

'''Uncheck''' the box [] "include the JRE to the download"&lt;br /&gt;

Slackware includes the java JRE and it is usable by OpenOffice.&lt;br /&gt;

Choose the "Linux Intel RPM" for your language (2nd column). &lt;br /&gt;

Save the '''OOo_3.3.0_Linux_x86_install-rpm_en-US.tar.gz''' to your downloads or Downloads directory (wherever you put tarballs) (version may vary).

Open a terminal and untar the tarball.&lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ cd &lt;path-to-download-folder&gt;
 [user@host] downloads/ $ tar -xzf OOo_3.3.0_Linux_x86_install-rpm_en-US.tar.gz
&lt;/code&gt;
This creates a folder named OOO330_m20_native_packed-1_en-US.9567, with an RPMS subdirectory and other things.&lt;br /&gt;


Change to the OOO... /RPMS folder and see what you have&lt;br /&gt;

&lt;code&gt;
 [user@host] downloads/ $ cd OOO330_m20_native_packed-1_en-US.9567/RPMS
 [user@host] RPMS/ $ ls
&lt;/code&gt;

There should be quite a few .rpm files.  We will change these to .tgz files with '''rpm2tgz'''.&lt;br /&gt;

&lt;code&gt;
 [user@host] RPMS/ $ rpm2tgz *.rpm
&lt;/code&gt;
This takes a little while.  When done there should be a matching .tgz file for each .rpm file.

* &lt;big&gt;Installing OpenOffice.org&lt;/big&gt;

Now change to root and install the packages.&lt;br /&gt;

&lt;code&gt;
 [user@host] RPMS/ $ su 
 password
 [root@host] RPMS/ # installpkg *.tgz
&lt;/code&gt;
This also takes a little while.

Now create symbolic links to put the OpenOffice executables in your path.
Note: OpenOffice creates two directories in /opt, 
''/opt/openoffice3.org''  and  ''/opt/openoffice3.org3''&lt;br /&gt;

The /opt/openoffice3.org3 is the directory that contains the executables.&lt;br /&gt;

&lt;code&gt;
 [root@host] RPMS/ # cd /usr/bin
&lt;/code&gt;
: (The '''ln -s TARGET [LINK_NAME]''' command creates symbolic links)&lt;br /&gt;
: Use the bash completion with these commands ln -s /opt/openo[tab] ... /program/s[tab] to be sure you are correctly referencing the executable programs. &lt;br /&gt;


&lt;code&gt;
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/soffice
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/sbase
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/scalc
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/sdraw
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/simpress
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/swriter

 [root@host] bin/ # exit
&lt;/code&gt;

* &lt;big&gt;Try it out&lt;/big&gt;

Just select OpenOffice or OfficeSuite in your fluxbox menu.simple.

* &lt;big&gt;I hope this all worked for you.&lt;/big&gt;
Check out http://slackbuilds.org for more packages. The accounting program '''kmymoney''' is found there.
As far as installing Adobe Acrobat goes, there is also a package at slackbuilds.org, but you may have better luck just downloading it from Adobe and running their AdbeRdr9...sh installation program.  Same for Adobe flashplayer.  IMHO, flashplayer is the more necessary program.&lt;br /&gt;
Have fun!</text>
    <sha1>563f763bda4c54a6d32aad3daedbd296d2cc7aff</sha1>
  </revision>
  <revision>
    <id>504</id>
    <parentid>503</parentid>
    <timestamp>2011-07-31T14:18:11Z</timestamp>
    <contributor>
      <username>Kevcortez</username>
      <id>194</id>
    </contributor>
    <minor/>
    <comment>format edit</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13730" xml:space="preserve">[[Category:Tutorials]] 
== Fluxbox Desktop -- basic configuration ==
This is my attempt to contribute to Slackware documentation with a newbie oriented how-to for initially setting up a usable Fluxbox desktop. There is also a section on installing OpenOffice, since many desktop users will want that program. &lt;br /&gt;


'''Use at your own risk!''' &lt;br /&gt;


I assume a default Slackware install.&lt;br /&gt;


Reference:&lt;br /&gt;
http://www.fluxbox.org &lt;br /&gt;
http://fluxbox-wiki.org&lt;br /&gt;

Fluxbox is a very nice desktop window manager that has most everything you need.  It is minimal, which allows good desktop performance on older or moderate hardware.  Plus, it can be configured to really simplify things so you don't have to deal with lots of programs you don't understand or ever use.  Besides simplification, the right configuration of Fluxbox can add quite a bit to your computing productivity.

Note: One time fluxbox refused to start for me.  As I recall, the problem was fixed by removing the .Xauthority and .ICEauthority files from my home folder and trying again.

Note: the ''' [user@host] ~/ $ ''' represents the command prompt with '''~''' being a shortcut for your /home/username folder.

&lt;blockquote&gt;
Tip: Use "bash completion" when working with directories and files from the command prompt.
Type the first few letters of the directory or file you want and the "tab" key.  If the text completes, then ''you are on the right path.''  Pressing "tab" twice will give a list of possible matches.
&lt;/blockquote&gt;
&lt;blockquote&gt;
Tip2: use the command "pwd" to show your present working directory and "whoami" to show your username.
&lt;/blockquote&gt;

== Choosing Fluxbox ==


* &lt;big&gt;Choose Fluxbox as the the default window manager&lt;/big&gt;
After you log in, from the console or a terminal screen in X: &lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ xwmconfig 
&lt;/code&gt;
: ( select fluxbox and OK )


If you are in X, close the current X session, log out, close, exit, or end.

Start up the (new) default fluxbox &lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ startx 
&lt;/code&gt;

== Fluxbox Configuration ==
Now, let us get fluxbox configured.
You will need to look into your ''' ~/.fluxbox ''' directory

Right-click on the desktop to display the menu and select rxvt or xterm
which will open a terminal window.&lt;br /&gt;


The Fluxbox configuration is kept in a hidden folder (dotfile) which may or may not be visible in an ordinary file browser, but won't be shown with a plain "ls" command, unless it is specified. &lt;br /&gt;
 
&lt;code&gt;
 [user@host] ~/ $ ls .fluxbox
    apps    keys           menu    init    slitlist
    init    windowmenu     overlay startup backgrounds  styles
&lt;/code&gt;

You should see something resembling this. &lt;br /&gt; 
Fluxbox should be started once before you modify it because it writes initial configurations in your .fluxbox folder.&lt;br /&gt;

* &lt;big&gt;Format the clock&lt;/big&gt;
From the menu, select '''Fluxbox-menu | Configure | Toolbar | Edit clock format''' &lt;br /&gt;
A small edit box opens and you can modify the format string and then press "enter."  Here is a suggestion: &lt;br /&gt;
&lt;code&gt;
 %I:%M %a %b %e
&lt;/code&gt;

* &lt;big&gt;Add keyboard access to main menu&lt;/big&gt;
Use the command below or right-click on the desktop to display the menu and select an editor from the Editors section -- gvim is good, but kate or kwrite are easier and more intuitive to use.  In fact, with kate you have a built-in terminal, which might make things easier. &lt;br /&gt;
&lt;code&gt;
 [user@host] ~/ $ kate .fluxbox/keys &amp;
&lt;/code&gt;

Edit the keys file by inserting the following at the very beginning, so it is easy to find if you want to change it later. (I assume you have a US pc105 keyboard, with two "windows" keys and one "menu" key on the bottom row.)

&lt;code&gt;
 # keyboard access to main menu
 # Menu key is next to right Control key
 None Menu     :RootMenu
 Shift Menu    :HideMenus
 # optional, Super_L is the left windows key
 None Super_L  :RootMenu
 Shift Super_L :HideMenus
&lt;/code&gt;

You can use the "xev" command to see the names and keycodes of your keyboard keys. &lt;br /&gt;
&lt;code&gt;
 [user@host] ~/ $ xev
&lt;/code&gt;

When done, save the keys file. &lt;br /&gt;

Test it by pressing the Menu key and the Shift-Menu to show/hide the Fluxbox menu.  &lt;br /&gt;

You may reload the configuration by using the menu ''' Fluxbox-menu | Reload config ''' 
Right click on the desktop to get this from the Fluxbox menu.

* &lt;big&gt;Create a simple menu.&lt;/big&gt;
&lt;code&gt;
 [user@host] ~/ $ kate .fluxbox/menu.simple &amp;
&lt;/code&gt;
kate may say it cannot read the file, but continue on.  It will give you a blank file.&lt;br /&gt;

Copy/paste the following menu: &lt;br /&gt;
&lt;code&gt;
 # My Fluxbox menu
 [begin] (Fluxbox menu.simple) {} &lt; &gt;
 [encoding] {UTF-8}
    [exec] (Terminal) {konsole} &lt; &gt;
    [exec] (Browser) {firefox} &lt; &gt;
    [exec] (Editor) {kate} &lt; &gt;
    [exec] (Reader) {okular} &lt; &gt;
    [exec] (Audio) {audacious} &lt; &gt;
    [separator]
    [submenu] (Net) {} &lt;&gt;
        [exec] (Browser) {seamonkey} &lt; &gt;
        [exec] (Mail) {thunderbird} &lt; &gt;
        [exec] (IM) {pidgin} &lt; &gt;
        [exec] (Chat) {xchat} &lt; &gt;
        [exec] (FTP) {gftp} &lt; &gt;
    [end]
    [submenu] (Media) {} &lt; &gt;
        [exec] (Graphics) {gimp} &lt; &gt;
        [exec] (Photos) {gqview} &lt; &gt;
        [exec] (Media Player) {xine} &lt; &gt;
        [exec] (Scanner) {xsane} &lt; &gt;
        [exec] (CD Copy) {k3b} &lt; &gt;
    [end]
    [submenu] (Office) {} &lt;&gt;
        # openoffice and acrobat are not included in Slackware
        [submenu] (OpenOffice) {} &lt;&gt;
                [exec] (Writer) {swriter} &lt;&gt;
                [exec] (Spreadsheet) {scalc} &lt;&gt;
                [exec] (Presentation) {simpress} &lt;&gt;
                [exec] (Draw) {sdraw} &lt;&gt; 
        [end]
        [exec] (OfficeSuite) {soffice} &lt; &gt;
        [exec] (PIM kde) {kontact} &lt; &gt;
        [exec] (Acrobat) {acroread} &lt; &gt;
        [exec] (Accounts) {kmymoney} &lt; &gt;
    [end]
    [submenu] (Tools) {} &lt; &gt;
        [exec] (Kill) {xkill} &lt; &gt;
        [exec] (Xterm) {xterm} &lt; &gt;
        [exec] (Files) {dolphin} &lt; &gt;
        [exec] (Calculator) {kcalc} &lt; &gt;
        [exec] (System) {ksysguard} &lt; &gt;
        [exec] (Manual) {xman} &lt; &gt;
        [exec] (Help) {khelpcenter} &lt; &gt;
        [exec] (Lock) {xlock} &lt; &gt;
    [end]
    [separator]
    [submenu] (Fluxbox-menu) {} &lt;&gt;
        [config] (Configure) {} &lt;&gt;
        [submenu] (Styles) {Choose a style...} &lt;&gt;
            [stylesdir] (/usr/X11R6/share/fluxbox/styles) {} &lt;&gt;
            [stylesdir] (~/.fluxbox/styles) {} &lt;&gt;
        [end]
        [workspaces] (Workspace List) {} &lt;&gt;
        [submenu] (Tools) {} &lt;&gt;
            [exec] (Windowname) {xprop|grep WM_CLASS|cut -d \" -f 2|xmessage -file - -center} &lt;&gt;
            [exec] (Screenshot - JPG) {import screenshot.jpg &amp;&amp; display -resize 50% screenshot.jpg}
            [exec] (Screenshot - PNG) {import screenshot.png &amp;&amp; display -resize 50% screenshot.png}
            [exec] (Run) {fbrun }
            [exec] (Regen Menu) {fluxbox-generate_menu }
        [end]
        [reconfig] (Reload config) {} &lt;&gt;
        [restart] (Restart) {} &lt;&gt; 
        [exec] (Shutdown) {/usr/bin/sudo /sbin/shutdown -h now} &lt;&gt;
        [separator]
        [exit] (Exit) {} &lt;&gt;
    [end]
    [separator]
    [exit] (Exit) {} &lt;&gt;
 [endencoding]
 [end]
&lt;/code&gt;

To add a program, the syntax is:
&lt;code&gt;
 [exec] (Label) {command} &lt; optional path to .xpm icon &gt;
&lt;/code&gt;
Also, every  '''[submenu]''' tag must have a matching ''' [end] ''' tag.

Save this file as .fluxbox/menu.simple (kate '''File | Save''') &lt;br /&gt;

'''Do not overwrite your .fluxbox/menu file.''' You may want it later.&lt;br /&gt;


Open the file .fluxbox/init &lt;br /&gt;
&lt;code&gt;
 kate .fluxbox/init &amp;
&lt;/code&gt;
Or just use kate's '''File | Open.'''  Since .fluxbox should be the current directory, the file dialog should show the file, or you can enter .fluxbox/init in the Name box at the bottom of the dialog.&lt;br /&gt;

&lt;code&gt;
Find the following line (near the bottom)&lt;br /&gt;
 session.menuFile:	~/.fluxbox/menu
&lt;/code&gt;
Change "menu" to "menu.simple" and save/close the init file.&lt;br /&gt;


* &lt;big&gt;Now for the desktop background.&lt;/big&gt;  
Copy your favorite background .jpeg file to .fluxbox/backgrounds/my_favorite_background.jpg

&lt;code&gt;
 [user@host] ~/ $ cp path-to/my_favorite_background.jpg .fluxbox/backgrounds/
 [user@host] ~/ $ chmod 644 .fluxbox/backgrounds/*
&lt;/code&gt;

Now open the overlay file .fluxbox/overlay and add these lines:
&lt;code&gt;
 background: fullscreen
 background.pixmap: ~/.fluxbox/backgrounds/my_favorite_background.jpg
&lt;/code&gt;

Your overlay file should look like this:
&lt;code&gt;
 ! The following line will prevent styles from setting the background.
 ! background: none
 background: fullscreen
 background.pixmap: ~/.fluxbox/backgrounds/my_favorite_background.jpg
&lt;/code&gt;
Save/close the overlay file.&lt;br /&gt;


See what it looks like with the fbsetbg command&lt;br /&gt;
&lt;code&gt;
 [user@host] ~/ $ fbsetbg ~/.fluxbox/backgrounds/my_favorite_background.jpg
&lt;/code&gt;
Now, make sure all your modified files are saved and select Restart from the Fluxbox menu --select '''Fluxbox-menu | Restart'''&lt;br /&gt;


* &lt;big&gt;Learn more from the man pages:&lt;/big&gt;
&lt;code&gt;
 [user@host] ~/ $ man fluxbox | less
 [user@host] ~/ $ man fluxstyle | less
&lt;/code&gt;
(press "q" to quit the less pager or man page)

Or use the Help --&gt; khelpcenter; select Unix Manuals, section 1, fluxbox; or even xman.

I also suggest doing a web search for .Xdefaults or .Xresources files.

Hopefully, you will like the look and feel of Fluxbox. Of course, there are more things you can do with your configuration, but hopefully this introduction has shown you some possibilities and got you off to a good start.

== Installing Open Office ==
Since OpenOffice is probably wanted by many desktop users, but not included in Slackware, I have these directions for getting it installed. &lt;br /&gt;

* Uninstalling OpenOffice for Upgrade

See if you have OpenOffice packages installed.  The packages have names containing ooobasis or openoffice.&lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ ls /var/log/packages | grep ooo
 [user@host] ~/ $ ls /var/log/packages | grep openoffice
&lt;/code&gt;

If you are going to upgrade, first uninstall your existing packages.
If you did not use Slackware compatible packages, then you can probably simply delete the openoffice.org directories under /opt.  Otherwise, use pkgtool.&lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ su
  password
 [root@host] ~/ # pkgtool
&lt;/code&gt;
: Choose Remove Packages and scroll down to the openoffice packages.
: Select them with the space bar and then tab to OK and press enter.

'''Be careful with pkgtool or you will remove the wrong packages.'''

Or, to just remove the directories (this does not update Slackware's package tracking). &lt;br /&gt;

&lt;code&gt;
 [root@host] ~/ # cd /opt
 [root@host] opt/ # rm -f openoffice3.org
 [root@host] opt/ # rm -f openoffice3.org3
&lt;/code&gt;
&lt;br /&gt;

* &lt;big&gt;Downloading OpenOffice.org&lt;/big&gt;

Point your browser to http://www.openoffice.org

Click on "I want to download OpenOffice.org"

Choose "Searching for another version"
: This takes you to the alternate downloads page

'''Uncheck''' the box [] "include the JRE to the download"&lt;br /&gt;

Slackware includes the java JRE and it is usable by OpenOffice.&lt;br /&gt;

Choose the "Linux Intel RPM" for your language (2nd column). &lt;br /&gt;

Save the '''OOo_3.3.0_Linux_x86_install-rpm_en-US.tar.gz''' to your downloads or Downloads directory (wherever you put tarballs) (version may vary).

Open a terminal and untar the tarball.&lt;br /&gt;

&lt;code&gt;
 [user@host] ~/ $ cd &lt;path-to-download-folder&gt;
 [user@host] downloads/ $ tar -xzf OOo_3.3.0_Linux_x86_install-rpm_en-US.tar.gz
&lt;/code&gt;
This creates a folder named OOO330_m20_native_packed-1_en-US.9567, with an RPMS subdirectory and other things.&lt;br /&gt;


Change to the OOO... /RPMS folder and see what you have&lt;br /&gt;

&lt;code&gt;
 [user@host] downloads/ $ cd OOO330_m20_native_packed-1_en-US.9567/RPMS
 [user@host] RPMS/ $ ls
&lt;/code&gt;

There should be quite a few .rpm files.  We will change these to .tgz files with '''rpm2tgz'''.&lt;br /&gt;

&lt;code&gt;
 [user@host] RPMS/ $ rpm2tgz *.rpm
&lt;/code&gt;
This takes a little while.  When done there should be a matching .tgz file for each .rpm file.

* &lt;big&gt;Installing OpenOffice.org&lt;/big&gt;

Now change to root and install the packages.&lt;br /&gt;

&lt;code&gt;
 [user@host] RPMS/ $ su 
 password
 [root@host] RPMS/ # installpkg *.tgz
&lt;/code&gt;
This also takes a little while.

Now create symbolic links to put the OpenOffice executables in your path.
Note: OpenOffice creates two directories in /opt, 
''/opt/openoffice3.org''  and  ''/opt/openoffice3.org3''&lt;br /&gt;

The /opt/openoffice3.org3 is the directory that contains the executables.&lt;br /&gt;

&lt;code&gt;
 [root@host] RPMS/ # cd /usr/bin
&lt;/code&gt;
: (The '''ln -s TARGET [LINK_NAME]''' command creates symbolic links)&lt;br /&gt;
: Use the bash completion with these commands ln -s /opt/openo[tab] ... /program/s[tab] to be sure you are correctly referencing the executable programs. &lt;br /&gt;


&lt;code&gt;
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/soffice
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/sbase
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/scalc
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/sdraw
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/simpress
 [root@host] bin/ # ln -s /opt/openoffice3.org3/program/swriter

 [root@host] bin/ # exit
&lt;/code&gt;

* &lt;big&gt;Try it out&lt;/big&gt;

Just select OpenOffice or OfficeSuite in your fluxbox menu.simple.

* &lt;big&gt;I hope this all worked for you.&lt;/big&gt;
Check out http://slackbuilds.org for more packages. The accounting program '''kmymoney''' is found there.
As far as installing Adobe Acrobat goes, there is also a package at slackbuilds.org, but you may have better luck just downloading it from Adobe and running their AdbeRdr9...sh installation program.  Same for Adobe flashplayer.  IMHO, flashplayer is the more necessary program.&lt;br /&gt;
Have fun!</text>
    <sha1>dbd1ab1cc596a6a7c409ed8e340216cf0f307975</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Customizing Bash Prompt</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>505</id>
    <parentid>99</parentid>
    <timestamp>2011-08-01T11:33:56Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4805" xml:space="preserve">[[Category:Tips]]
There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying, or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one, or just want some more in it.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@yahoo.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[su_pyrow@yahoo.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes. Try it out, and see if it grows on you!</text>
    <sha1>7c82e582fd230bbd86f3cd1b8dad0dda4ba0f1c6</sha1>
  </revision>
  <revision>
    <id>506</id>
    <parentid>505</parentid>
    <timestamp>2011-08-01T11:42:51Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4903" xml:space="preserve">[[Category:Tips]]
# Originally posted by SU_PyRoW 
# &lt;a href="http://compelitepc.host56.com"&gt;CompElitePC, Inc.&lt;/a&gt;

There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying, or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one, or just want some more in it.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@yahoo.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[su_pyrow@yahoo.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes. Try it out, and see if it grows on you!</text>
    <sha1>1eed9626997929c47450b28fddcfc02f257bde22</sha1>
  </revision>
  <revision>
    <id>507</id>
    <parentid>506</parentid>
    <timestamp>2011-08-01T11:44:13Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4868" xml:space="preserve">[[Category:Tips]]

Originally posted by SU_PyRoW 
http://compelitepc.host56.com

There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying, or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one, or just want some more in it.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@yahoo.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[su_pyrow@yahoo.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes. Try it out, and see if it grows on you!</text>
    <sha1>092c7642162dff0d2261eb8a8cb8f91450be7d08</sha1>
  </revision>
  <revision>
    <id>508</id>
    <parentid>507</parentid>
    <timestamp>2011-08-01T11:50:09Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <comment>moved [[Customizing Bash Prompt]] to [[Customising Bash Prompt]]: spelling</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4868" xml:space="preserve">[[Category:Tips]]

Originally posted by SU_PyRoW 
http://compelitepc.host56.com

There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying, or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one, or just want some more in it.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@yahoo.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[su_pyrow@yahoo.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes. Try it out, and see if it grows on you!</text>
    <sha1>092c7642162dff0d2261eb8a8cb8f91450be7d08</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>User talk:Balsa</title>
  <ns>3</ns>
  <id>236</id>
  <revision>
    <id>510</id>
    <parentid>468</parentid>
    <timestamp>2011-08-17T00:05:34Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <comment>/* Editing Resource Limits page */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10864" xml:space="preserve">Hi.  

[[User:Balsa|Balsa]] 03:28, 3 February 2011 (EST)


== ALSA ==

/etc/asound.names&lt;br/&gt;
Gives names and descriptions for ALSA hardware devices.  Very useful when using arecord and its '-D, --device=NAME' command line options.

/etc/asound.conf&lt;br/&gt;
I do not know what this is currently.

/etc/asound.state&lt;br/&gt;
Ditto.

strace - handy utility to see what programs are doing.
strace -e file [some program and its args if relevant] - only shows file related stuff.

arecord - ALSA utility to record sound.  It's what I'm having trouble with, and is the subject of most of this page.

sox - "Sound eXchange, the Swiss Army knife of audio manipulation" - (man sox; GNU General Public License)

strace -e file arecord -v -d 5 -t au   test4.au   ----&gt;  &lt;snip&gt;&lt;br/&gt;
Recording Sparc Audio 'test4.au' : Unsigned 8 bit, Rate 8000 Hz, Mono &lt;snip&gt;&lt;br/&gt;
Very interesting, indeed.  This gives us the default ALSA device used by arecord, in my case it was /dev/snd/pcmC0D0c.  Cross referencing with /etc/asound.names doesn't get us far, because I still don't know the mappings between that file and the stuff in /dev/snd.  Some speculation may be in order.

grep -i capture -B 1  /etc/asound.names  --&gt;  &lt;br/&gt;
name 'hw:0,4'&lt;br/&gt;
comment 'Physical Device - ALC268 Analog (Capture)'&lt;br/&gt;
--&lt;br/&gt;
name 'plughw:0,4'&lt;br/&gt;
comment 'Physical Device With Conversions - ALC268 Analog (Capture)'&lt;br/&gt;

Hmm.

Lets try: strace -e file arecord -v -d 5 -t au  -D hw:0,4  test5.au&lt;br/&gt;
This opens /dev/snd/pcmC0D4c, and says "Recording Sparc Audio 'test5.au' : Unsigned 8 bit, Rate 8000 Hz, Mono" but exits with "arecord: set_params:954: Sample format non available".

strace -e file arecord -v -d 5 -t au  -D hw:0,0  test5.au&lt;br/&gt;
Same deal, but opens /dev/snd/pcmC0D0c instead.  Strange, since that is the same as the default.

TODO:  Look at source code.  Edit: nevermind.

Let's try one more thing - that /etc/asound.names gave me an idea...&lt;br/&gt;
strace -e file arecord -v -d 5 -t au  -D plughw:0,0  test5.au&lt;br/&gt;
Hot dog it worked!&lt;br/&gt;
open("/dev/snd/pcmC0D0c", O_RDWR|O_NONBLOCK) = 4&lt;br/&gt;
open("test5.au", O_WRONLY|O_CREAT|O_LARGEFILE, 0644) = 3&lt;br/&gt;

sox test5.au -d  --&gt; Lots of clipping, noisy.&lt;br/&gt;
sox au: header size 24 is too small

Input File     : 'test5.au'&lt;br/&gt;
Channels       : 1&lt;br/&gt;
Sample Rate    : 8000&lt;br/&gt;
Precision      : 8-bit&lt;br/&gt;
Duration       : 00:05.00 = 40000 samples ~ 375 CDDA sectors&lt;br/&gt;
Sample Encoding: 8-bit Signed Integer PCM&lt;br/&gt;

100%  00:05.00 [00:00.00] of 00:05.00 Out:240k  [!=====|=====!]Hd:0.0 Clip:182k&lt;br/&gt;
sox effects: rate clipped 120593 samples; decrease volume?&lt;br/&gt;
sox sox: alsa: output clipped 61507 samples; decrease volume?&lt;br/&gt;
Done.&lt;br/&gt;

Aha!  The recording is unsigned 8bit, but the playback was signed 8bit.  How does one change this?

man sox

sox -u test5.au  -d&lt;br/&gt;
sox formats_i: `test5.au': overriding encoding type&lt;br/&gt;
Sample Encoding: 8-bit Unsigned Integer PCM&lt;br/&gt;
OK, it plays as unsigned 8bit.  Success.&lt;br/&gt;


== JACK network audio over UDP ==

On the end with the physical sound hardware (master):
jackd -r -T -d alsa -i1 -n 10 -o1 -p 4096 -r 8000 -S 
-i num input channels
-n nperiods 
-o num output channels
-p period, must be power of 2.
-r sample rate
-S prefer 16bit int over 32 bit.

Do last (third):
jack_netsource -h &lt;hostname&gt;
jack_netsource -h &lt;hostname&gt; -m 1400 -P 1 -C 1 -o 0 -i 0 -l 10 -b 16
-m set maximum transmit unit (MTU)
-P -C -o -i number of sound and midi in/out channels.
-l buffer in number of periods.
-b 16 bits per sample.
FIXME - how to set sample rate?


On the virtual end (remote):
jackd -r -d net
jackd -r -T -d net -i 1 -o 1 -I 0 -O 0 -r 8000 -p 4096 -n 10 -b 16
-r not realtime -c -a0
-T temporary, close when all clients gone.
-d net use device net.
-i -o -I -O num channels for sound/midi
-r sample rate
-p 4096 frames per period
-n 10 buffer size in num periods
-b 16 use 16 bits/sample
-c use CELT compression
-a 0 do not use autoconfig, just start
--[[User:Balsa|Balsa]] 01:47, 20 March 2011 (EDT)

== Simple tests from command line ==

netstat - man netstat

look for services that you don't know, read their manual pages.  See if the service would be better listening to fewer interfaces [like localhost].  Use the ps command to figure out what's running.  Try the netstat flags "--inet -anp" and read what they mean in the netstat manual.

look at /etc/fstab

man fstab
man mount

Read a security article [fixme] about this file and the options.  Skim the LVM and partitions pages here on slackwiki.  Read about the noexec option (don't use this without understanding the consequences)

Try "hostname --fqdn" and see what it does.  Check the exim page or qmail page to see about local mail delivery.  Some security tools (and other stuff too) will email you when important events occur.

Read about the sudo and su commands.

--[[User:Balsa|Balsa]] 16:15, 20 February 2011 (EST)

== Exim - local mail only - setup and testing ==

Setup: not written yet.


Testing / Debugging:

The following are draft quality only.
ps -efw | grep -i -e exim | grep -v grep
#Lists running exim processes.
netstat --inet -anp | grep -i -e exim -e 25 -e mail
#See if anything is listening on port 25.


ls -l /var/log
look for mail or exim4 directory, and mail.??? and mail.???? files.

ls -l /var/
look for mail, queue, or spool.
Do a ls -l in any directories found above.

Mail might be in ~/Mail

Read the Mutt HOWTO on slackwiki.org.

Read the qmail HOWTO as well.

tail -f /var/log/exim4/mainlog (if it exists)
The -f flag makes tail follow the file, so its best used on another virtual console or with screen.
There are numerous guides for screen.  My suggestion is to printout the most common commands on paper and keep it near your monitor.


Try the mail command out.
man mail

echo "Testing local mail, sent on `date` to the local system" \
| mail -s "Test of Local Mail" username@localhost.localdomain

Note that username@localhost.localdomain may not work.

Try hostname --fqdn

look in /etc/hosts


Testing the MTA with telnet on a certain port:

telnet localhost 25

HELO localhost

MAIL FROM: username@localhost.localdomain

RCPT TO: username@localhost.localdomain

DATA

SUBJECT: Testing mail via telnet

This is the message body.

Check if it worked with your favorite mail reader or by
looking in the files listed above.
End message body with a "." on a line by itself.
.

QUIT


Once local mail delivery works, you can setup cron jobs (see cron page on slackwiki, and man cron) and the output (if any) will be mailed to you.

== Octave: simple functions ==

Find the Octave tutorial by typing doc at the Octave command line.&lt;br&gt;
Navigate to * Introduction::                A brief introduction to Octave.&lt;br&gt;
Then go to * Simple Examples::&lt;br&gt;
The tutorial is quite brief, and gives few examples of functions.&lt;br&gt;
This page will demo how to make simple functions, and how to call one function from another.&lt;br&gt;

octave:11&gt; function fn = fn ( p )&lt;br&gt;
&gt; fn = p*20&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:10&gt; function sn = sn ( a )&lt;br&gt;
&gt; sn = a * (1/2)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:12&gt; function tn = tn( p, a )&lt;br&gt;
&gt; tn = sn(a)+fn(p)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:17&gt; function excess = excess( p, a, bs )&lt;br&gt;
&gt; excess = bs - tn(p,a)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:18&gt; excess(p,a,bs)&lt;br&gt;
sn =  517.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2657.5&lt;br&gt;
excess = -1452.5&lt;br&gt;
ans = -1452.5&lt;br&gt;

octave:28&gt; function trade = trade ( p, a, bs, lt )&lt;br&gt;
&gt; trade = excess(p,a,bs)/lt&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:26&gt; function newacres = newacres (p, a, bs, lt, na )&lt;br&gt;
&gt; newacres = a+trade(p,a,bs,lt)&lt;br&gt;
&gt; endfunction&lt;br&gt;

octave:36&gt; p=107; a=1013; bs=3017; lt=25;&lt;br&gt;
octave:37&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  506.50&lt;br&gt;
fn =  2140&lt;br&gt;
tn =  2646.5&lt;br&gt;
excess =  370.50&lt;br&gt;
trade =  14.820&lt;br&gt;
newacres =  1027.8&lt;br&gt;
ans =  1027.8&lt;br&gt;
octave:38&gt; p=114; a=1027; bs=3095; lt=23;&lt;br&gt;
octave:39&gt; newacres(p,a,bs,lt,na)&lt;br&gt;
sn =  513.50&lt;br&gt;
fn =  2280&lt;br&gt;
tn =  2793.5&lt;br&gt;
excess =  301.50&lt;br&gt;
trade =  13.109&lt;br&gt;
newacres =  1040.1&lt;br&gt;
ans =  1040.1&lt;br&gt;

--[[User:Balsa|Balsa]] 13:17, 21 February 2011 (EST)

== Getmail ==

One of getmail's biggest features is writing directly to Maildir.  This obviates the need for a Mail Transport Agent (MTA).&lt;br&gt;

In a getmail configuration file:

[destination]&lt;br&gt;
type = Maildir&lt;br&gt;
path = ~/Maildir/&lt;br&gt;

This will write your email directly to the ~/Maildir/ directory in Maildir format.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:23, 21 February 2011 (EST)

== Redirecting stderr and stdout to a file ==

/bin/true &amp;&gt; foo&lt;br&gt;

This may be helpful in the "Piping" section here on slackwiki.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:34, 21 February 2011 (EST)

== Sandbox and/or Editing Help pages on slackwiki? ==

If anyone knows if there exists a sandbox or an Help:Editing page here on slackwiki.org, please let me know.  If not, I might try to create one.  Advice welcome.&lt;br&gt;

--[[User:Balsa|Balsa]] 13:38, 21 February 2011 (EST)

A [[User:Balsa/Sandbox|sand-filled box]] labelled "Testing"
--[[User:Balsa|Balsa]] 05:02, 8 April 2011 (EDT)

== NTP log file configuration documentation ==

look for /usr/share/doc/ntp-doc/html/ntpd.html&lt;br&gt;
It may be in a different place.&lt;br&gt;
Use a http reader, like lynx to view it.&lt;br&gt;
Go to "The Configuration File", then "Miscellaneous Options".&lt;br&gt;

Scroll down to the "logconfig" and "logfile" headings.&lt;br&gt;

There you will find a way to eliminate the "kernel time sync status change 6001" messages from syslog.&lt;br&gt;

--[[User:Balsa|Balsa]] 02:26, 23 February 2011 (EST)

== Editing Resource Limits page ==

Having recently run into some limits issues myself (and spending an hour or two learning about them), I am going to revise and extend the original [[Resource_Limits]] page. &lt;br&gt;
Current goals:
&lt;ul&gt;
&lt;li&gt;Clarify where the ulimit documentation is.  Slackware 12.2.0 (at least) has only a programmer's man page for ulimit.  The shell builtin is documented in the shell's own man page.&lt;/li&gt;
&lt;li&gt;Steer users away from any programming manual pages.  The above man page [ULIMIT(3)] says, "POSIX.1-2008 marks ulimit() as obsolete."  This is potentially confusing; users may try to use non-existent getrlimit commands.&lt;/li&gt;
&lt;li&gt;ULIMIT(3) also says: "Warning:  This routine is obsolete.  Use getrlimit(2), setrlimit(2), and sysconf(3) instead.  For the shell command ulimit(), see bash(1)."  Same issue as above." &lt;/li&gt;
&lt;li&gt;Clarify whether or not ulimit is a shell builtin by letting the user test for it; if it is builtin, then matters become somewhat shell-specific.&lt;/li&gt;
&lt;li&gt;Expand the scope of the original article beyond increasing the limit for open files.&lt;/li&gt;
&lt;li&gt;Add a new section pointing to the README.limits file (as provided by the shadow package) as an alternate way of dealing with limits.&lt;/li&gt;
&lt;/ul&gt;

[[User:Balsa/Resource_Limits_Working_Draft|Resource Limits Working Draft]]
--[[User:Balsa|Balsa]] 19:05, 16 August 2011 (CDT)</text>
    <sha1>0484a411a8035af64333135e74f2b7ed05945e53</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>User:Balsa/Resource Limits Working Draft</title>
  <ns>2</ns>
  <id>245</id>
  <revision>
    <id>511</id>
    <timestamp>2011-08-17T00:08:16Z</timestamp>
    <contributor>
      <username>Balsa</username>
      <id>156</id>
    </contributor>
    <comment>Resource Limits page working draft</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7550" xml:space="preserve">= Purpose =

This page does not attempt to explain the different types of system resource limits or when it is (or is not) appropriate to change them; see '''man ulimit''' and [[http://google.com Google]] for that discussion.

However, some users run into problems with the linux kernel's default limit settings, so we'll attempt to explain how to modify them to suit their special needs.&lt;br&gt;

Also covered:
&lt;ul&gt;
&lt;li&gt;How to display the system resource limits.&lt;/li&gt;
&lt;/ul&gt;


= Overview =


The default settings provided by the kernel are sane values for most multi-user machines.&lt;br&gt;
However, the defaults may be different depending on your FIXME[distribution/kernel?].&lt;br&gt;
The examples that follow may have different limits than your system.  The limits in the examples are not necessarily better.  This page does not endorse or recommend any particular limits.&lt;br&gt;
Depending on your shell, the examples may be different, and the commands may need to be modified.&lt;br&gt;

Issuing the command '''ulimit -Ha''' should show all the ''Hard'' limits.
Example:
 user@host:~$ ulimit -Ha
 core file size          (blocks, -c) unlimited
 data seg size           (kbytes, -d) unlimited
 file size               (blocks, -f) unlimited
 pending signals                 (-i) 8118
 max locked memory       (kbytes, -l) 32
 max memory size         (kbytes, -m) unlimited
 open files                      (-n) 1024
 pipe size            (512 bytes, -p) 8
 POSIX message queues     (bytes, -q) 819200
 stack size              (kbytes, -s) unlimited
 cpu time               (seconds, -t) unlimited
 max user processes              (-u) 8118
 virtual memory          (kbytes, -v) unlimited
 file locks                      (-x) unlimited

and '''ulimit -Sa''' should show all the ''Soft'' limits:
 user@host:~$ ulimit -Sa
 core file size          (blocks, -c) 0
 data seg size           (kbytes, -d) unlimited
 file size               (blocks, -f) unlimited
 pending signals                 (-i) 8118
 max locked memory       (kbytes, -l) 32
 max memory size         (kbytes, -m) unlimited
 open files                      (-n) 1024
 pipe size            (512 bytes, -p) 8
 POSIX message queues     (bytes, -q) 819200
 stack size              (kbytes, -s) 8192
 cpu time               (seconds, -t) unlimited
 max user processes              (-u) 8118
 virtual memory          (kbytes, -v) unlimited
 file locks                      (-x) unlimited


The first command shows the hard limits set by the kernel, and the second command shows the soft limits set by the user(Verify?).  An unprivileged user can increase the soft limit (up to the hard limit value), and he is also able to lower the hard limit (but then is unable to increase it, as an unprivileged user cannot raise the hard limit at all).

There are some situations which might require a larger hard limit for users, and the obvious "solution" is to add a line in /etc/profile to increase it.  However, this will not work, because normal users cannot increase their hard limits (as indicated above).


= Solution #1: ''/sbin/initscript'' =

To increase the hard limits for users, you will need to create '''/sbin/initscript''' and place appropriate commands inside it.  The easiest way is to copy the file '''/sbin/initscript.sample''' to '''/sbin/initscript''' and edit the copy, but you are certainly free to "roll your own."  If you decide to create your own, make sure it is executable or it will not work.&lt;br&gt;
Note:  If /sbin/initscript.sample does not exist, you may find reading the initscript manual page helpful.&lt;br&gt;
Using the following '''/sbin/initscript''' file:

 PATH=/bin:/sbin:/usr/bin:/usr/sbin
 export PATH
 
 # Increase the hardlimit for open files
 ulimit -Hn 4096
 
 # Execute the program.
 eval exec "$4"

You should get the following after a reboot:
 user@host:~$ ulimit -Hn
 4096
 
 user@host:~$ ulimit -n
 1024

Notice that the hardlimit is now 4096 (as specified in /sbin/initscript), but the softlimit is still 1024.  In other words, you will still need to use /etc/profile (or some other shell init file - see below for recommendation) to raise the desired users' softlimits.  With some creative scripting, you can be more selective about which users have what limits.

Rather than editing the system /etc/profile, it's recommended to create a custom file in /etc/profile.d and make it executable.  This way, you don't have to worry about trying to merge your changes to /etc/profile when doing Slackware upgrades to new versions.


= Solution #2: README.limits and the ''shadow'' package =

To increase the hard limits for users, you should read the README.limits file provided by the shadow package which is very likely already installed.  See the "''Other Resources''" section to find its location.

Here is an example /etc/limits file.
 # /etc/limits contains user resource limits.
 # See limits(5).
 #
 # Format:
 # &lt;username&gt; &lt;limits-string&gt;
 #
 # default entry is '*' for username
 #
 # Valid flags are:
 # A: max address space (KB)
 # C: max core file size (KB)
 # D: max data size (KB)
 # F: maximum filesize (KB)
 # M: max locked-in-memory address space (KB) [only for root on Linux 2.0.x]
 # N: max number of open files
 # R: max resident set size (KB) [no effect on Linux 2.0.x]
 # S: max stack size (KB)
 # T: max CPU time (MIN)
 # U: max number of processes
 # L: max number of logins for this user
 # I: max nice value (0..39 translates to 20..-19)
 # O: max real time priority (0..MAX_RT_PRIO)
 #
 # Examples:
 # the default entry
 #* L2 D6144 R2048 S2048 U32 N32 F16384 T5 C0 I20 O0
 # another way of suspending a user login
 #guest   L0
 # this account has no limits
 #sysadm  -

Following the example in Solution #1 above, to increase the hardlimit for open files you would need to add the following line to /etc/limits:
 user N4096

You do ''not'' need to reboot.  Simply log off [Fixme: all instances?] and then log back on again.&lt;br&gt;
Apparently, [Verify?] this will set the hard and soft limits equal.

Results:
 user@host:~$ ulimit -Hn
 4096
 
 user@host:~$ ulimit -Sn
 4096

= Other Resources =

Find out if ulimit is a '''''shell builtin''''' or not.
If ''which'' finds an ulimit executable, then it is not a shell builtin.
* '''which ulimit'''

Example of a shell builtin (which returns no results):
 user@host: ~ $ which ulimit
 which: no ulimit in (/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib/java/bin:/usr/lib/java/jre/bin:/usr/lib/qt/bin:/usr/share/texmf/bin:.:/sbin:/sbin)

The ulimit man page may not be useful if ulimit is a shell builtin.  If it is a shell builtin, read your shell's man page and search for the string "ulimit".  (without the quotes)
* '''man bash'''   
* '''man ash'''
* '''man dash'''
* '''man sh'''
* '''man ksh'''
* '''man csh'''
* '''man tcsh'''
Otherwise,
* '''man ulimit'''


Read the other manual pages:
* '''man initscript'''
* '''man limits'''

== Finding the README.limits file ==

Find the package that installed the limits (5) man page:  (should be shadow)
* '''grep -i "limits.5.gz" /var/log/packages/*'''

Find the README.limits file, replacing x.y.z.-march-n with whatever version of shadow you found above:
* '''grep -i "README.limits" /var/log/packages/shadow-x.y.z.-march-n'''

Alternatively, if you have slocate installed:
* '''slocate README.limits'''
(or the really easy way):
* '''less `slocate README.limits`'''&lt;br&gt;
&lt;br&gt;
Finally, read the README.limits file, replacing x.y.z with whatever version of shadow you have installed:
* '''less /usr/doc/shadow-x.y.z/README.limits'''


[[Category:Tutorials]]</text>
    <sha1>0cbbeac0206dc8645dc52cc3a59961720c85c2a7</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Broadcom Wireless</title>
  <ns>0</ns>
  <id>246</id>
  <revision>
    <id>512</id>
    <timestamp>2011-09-09T11:14:47Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <comment>A HowTo for installing and configuring Broadcom wireless cards on Slackware</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3758" xml:space="preserve">[[Category:Tutorials]]
= Introduction =

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

= Prerequisites =

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

= Getting Started =

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

= Installing the driver =

Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

= Blacklisting the b43 and ssb modules =

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/etc/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
&lt;/pre&gt;

= Final steps =

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

= Installing Wicd =

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If you already have a working internet connection on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;. For example, on a 32-bit system, as root :
&lt;pre&gt;
 wget http://slackware.osuosl.org/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

= Wicd usage =
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.</text>
    <sha1>fcffcde727148ec782ec9ff76f2117da8d111993</sha1>
  </revision>
  <revision>
    <id>514</id>
    <parentid>512</parentid>
    <timestamp>2011-09-09T11:26:49Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3772" xml:space="preserve">[[Category:Tutorials]]
= Introduction =

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/etc/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If you already have a working internet connection on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;. For example, on a 32-bit system, as root :
&lt;pre&gt;
 wget http://slackware.osuosl.org/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.</text>
    <sha1>404358f7f06d2819eb23439d89246126aa4f6c65</sha1>
  </revision>
  <revision>
    <id>515</id>
    <parentid>514</parentid>
    <timestamp>2011-09-09T11:27:27Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <minor/>
    <comment>Fixed formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3774" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/etc/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If you already have a working internet connection on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;. For example, on a 32-bit system, as root :
&lt;pre&gt;
 wget http://slackware.osuosl.org/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.</text>
    <sha1>39cfd24cc107ec02175d84ea1476bf9b80409718</sha1>
  </revision>
  <revision>
    <id>518</id>
    <parentid>515</parentid>
    <timestamp>2011-09-09T14:50:09Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <comment>Added sbopkg instructions</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3991" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

=== Sbopkg method ===
If a working internet connection is available on the laptop (say a wired connection), use [http://sbopkg.org sbopkg] to install the drivers :
&lt;pre&gt;sbopkg -i broadcom-sta&lt;/pre&gt;

=== Manual method ===
Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/etc/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If a working internet connection is available on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;. For example, on a 32-bit system, as root :
&lt;pre&gt;
 wget http://slackware.osuosl.org/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.</text>
    <sha1>e296fee9d34e91ddf6d9824ad82dadddcc4581c2</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>User:Klickback</title>
  <ns>2</ns>
  <id>247</id>
  <revision>
    <id>513</id>
    <timestamp>2011-09-09T11:17:24Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <comment>User page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41" xml:space="preserve">User klickback on ##slackware at freenode</text>
    <sha1>6e169349e93bd8a974f23b38aefd349c9ec0de51</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Chromium browser</title>
  <ns>0</ns>
  <id>249</id>
  <revision>
    <id>520</id>
    <timestamp>2011-09-23T15:54:53Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <comment>Created page with "== Introduction ==  Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Bro..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4870" xml:space="preserve">== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. A single user system is assumed, however, modifying it for a multi-user system should be simple enough.

== Getting started ==

Chromium depends on &lt;code&gt;GConf&lt;/code&gt; and &lt;code&gt;ORBit2&lt;/code&gt;, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
&lt;pre&gt;
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
&lt;/pre&gt;

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
&lt;pre&gt;
# sbopkg -i 'ORBit2 GConf'
&lt;/pre&gt;

Get the &lt;code&gt;google-chrome-pam-solibs&lt;/code&gt; package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bi] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
&lt;pre&gt;
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
&lt;/pre&gt;

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the &lt;code&gt;INSTALLDIR&lt;/code&gt; variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

&lt;pre&gt;
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i686) ARCH=i686 ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "i686" ];then
  DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  DIRSUFFIX="_x64"
else
  echo "The ARCH should be either i686 or x86_64. Exiting."
  exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then                    # Check to see if `chrome-linux.zip` already exists
        mv chrome-linux.zip chrome-linux.zip.old    # if it does, rename it to chrome-linux.zip.old as backup
fi                                                  # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

&lt;/pre&gt;

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
&lt;pre&gt;
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
&lt;/pre&gt;
Add the following to your crontab :
&lt;pre&gt;
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1&gt; /dev/null
&lt;/pre&gt;
This will run the script at 13:20 every day. See &lt;code&gt;man crontab&lt;/code&gt; for more on how to customize your cron jobs.


== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]</text>
    <sha1>b439593fbfe6aa6712a6b26fe3fd620f19c7945e</sha1>
  </revision>
  <revision>
    <id>521</id>
    <parentid>520</parentid>
    <timestamp>2011-09-23T16:07:02Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5163" xml:space="preserve">== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. A single user system is assumed. However, adapting this tutorial for a multi-user system should be simple enough. Also keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

== Getting started ==

Chromium depends on &lt;code&gt;GConf&lt;/code&gt; and &lt;code&gt;ORBit2&lt;/code&gt;, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
&lt;pre&gt;
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
&lt;/pre&gt;

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
&lt;pre&gt;
# sbopkg -i 'ORBit2 GConf'
&lt;/pre&gt;

Get the &lt;code&gt;google-chrome-pam-solibs&lt;/code&gt; package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
&lt;pre&gt;
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
&lt;/pre&gt;

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the &lt;code&gt;INSTALLDIR&lt;/code&gt; variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

&lt;pre&gt;
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i686) ARCH=i686 ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "i686" ];then
  DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  DIRSUFFIX="_x64"
else
  echo "The ARCH should be either i686 or x86_64. Exiting."
  exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then                    # Check to see if `chrome-linux.zip` already exists
        mv chrome-linux.zip chrome-linux.zip.old    # if it does, rename it to chrome-linux.zip.old as backup
fi                                                  # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

&lt;/pre&gt;

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
&lt;pre&gt;
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
&lt;/pre&gt;
Add the following to your crontab :
&lt;pre&gt;
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1&gt; /dev/null
&lt;/pre&gt;
This will run the script at 13:20 every day. See &lt;code&gt;man crontab&lt;/code&gt; for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]</text>
    <sha1>d606bcc2e17420c24971d449f21676355205652a</sha1>
  </revision>
  <revision>
    <id>522</id>
    <parentid>521</parentid>
    <timestamp>2011-09-23T17:16:18Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <comment>added use case</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5794" xml:space="preserve">== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading a 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops or slower computers. Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process; helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on &lt;code&gt;GConf&lt;/code&gt; and &lt;code&gt;ORBit2&lt;/code&gt;, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
&lt;pre&gt;
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
&lt;/pre&gt;

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
&lt;pre&gt;
# sbopkg -i 'ORBit2 GConf'
&lt;/pre&gt;

Get the &lt;code&gt;google-chrome-pam-solibs&lt;/code&gt; package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
&lt;pre&gt;
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
&lt;/pre&gt;

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the &lt;code&gt;INSTALLDIR&lt;/code&gt; variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

&lt;pre&gt;
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i686) ARCH=i686 ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "i686" ];then
  DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  DIRSUFFIX="_x64"
else
  echo "The ARCH should be either i686 or x86_64. Exiting."
  exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then                    # Check to see if `chrome-linux.zip` already exists
        mv chrome-linux.zip chrome-linux.zip.old    # if it does, rename it to chrome-linux.zip.old as backup
fi                                                  # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

&lt;/pre&gt;

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
&lt;pre&gt;
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
&lt;/pre&gt;
Add the following to your crontab :
&lt;pre&gt;
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1&gt; /dev/null
&lt;/pre&gt;
This will run the script at 13:20 every day. See &lt;code&gt;man crontab&lt;/code&gt; for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]</text>
    <sha1>e370c14e6b955a97c61adb1890dbf9f57dacf052</sha1>
  </revision>
  <revision>
    <id>523</id>
    <parentid>522</parentid>
    <timestamp>2011-09-23T17:18:33Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <minor/>
    <comment>/* Use Case */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5825" xml:space="preserve">== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops, slower computers or slow internet connections.

Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process, thus helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on &lt;code&gt;GConf&lt;/code&gt; and &lt;code&gt;ORBit2&lt;/code&gt;, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
&lt;pre&gt;
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
&lt;/pre&gt;

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
&lt;pre&gt;
# sbopkg -i 'ORBit2 GConf'
&lt;/pre&gt;

Get the &lt;code&gt;google-chrome-pam-solibs&lt;/code&gt; package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
&lt;pre&gt;
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
&lt;/pre&gt;

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the &lt;code&gt;INSTALLDIR&lt;/code&gt; variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

&lt;pre&gt;
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i686) ARCH=i686 ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "i686" ];then
  DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  DIRSUFFIX="_x64"
else
  echo "The ARCH should be either i686 or x86_64. Exiting."
  exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then                    # Check to see if `chrome-linux.zip` already exists
        mv chrome-linux.zip chrome-linux.zip.old    # if it does, rename it to chrome-linux.zip.old as backup
fi                                                  # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

&lt;/pre&gt;

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
&lt;pre&gt;
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
&lt;/pre&gt;
Add the following to your crontab :
&lt;pre&gt;
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1&gt; /dev/null
&lt;/pre&gt;
This will run the script at 13:20 every day. See &lt;code&gt;man crontab&lt;/code&gt; for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]</text>
    <sha1>51ae02a055c4433ae701a024c808f7e7139b92f4</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Acer Aspire 502x(WLMi)</title>
  <ns>0</ns>
  <id>37</id>
  <revision>
    <id>524</id>
    <parentid>58</parentid>
    <timestamp>2011-10-16T11:19:00Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Remove out of date information and some of the references to pre-historic kernels</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12034" xml:space="preserve">[[Category:Hardware]]
==Slackware on an Acer Aspire 5020 series==

This article is based on an Aspire 5021WLMi. The 5021WLMi is an an AMD Turion 64 based laptop - it mainly differs from other laptops of the 5020 series only in the specific processor model and some other models come with built in bluetooth - the 5021 has an ML-28 and no bluetooth, I believe the 5024 uses an ML-34 and does have built in bluetooth, so most of this should apply to the 502x series as well. (This is a work in progress, and therefore far from finished).

I have installed my own bluetooth module into the 5021 - this is not very difficult to do (just rather fiddly), but the instructions for operating the bluetooth apply to any 5020 series laptop with bluetooth installed.

==Hardware==
Output of lspci:&lt;pre&gt;
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
00:02.0 PCI bridge: ATI Technologies Inc RS480 PCI-X Root Port
00:07.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)
00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev 02)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700 (PCIE)
06:05.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
06:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
06:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
06:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
06:06.4 Class 0805: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
&lt;/pre&gt;

===Overview===

* AMD Turion 64 ML-28 at 1.6 GHz with 128 KB L1 cache and 512 KB L2 cache
* 512 MB of DDR333 memory
* 15.4" Samsung LTN154X3-L01 WXGA LCD panel (1280 x 800)
* ATi Mobility Radeon X700 (128MB dedicated memory)
* 80GB (4200 RPM) (P)ATA Hard Drive ([http://www.seagate.com/cda/products/discsales/marketing/detail/0,1081,638,00.html Seagate Momentus 4200.2 - ST9808210A])
* Slot DVD Writer (DVD-R/RW, DVD+R/RW, DVD+R Dual Layer)
* Texas Instruments (TI7421) 6-in-1 card reader
* Gigabit Ethernet (Realtek RTL-8169 chipset?)
* 802.11 b/g Wireless LAN (Broadcom AirForce One 54g (BCM4318))
* ATi SB400 AC'97 Soundcard + Modem
* 1 x IR port
* 1 x IEEE-1394 (Firewire) port
* 4 x USB ports
* 1 x S-Video port
* 1 x VGA port
* 1 x PCMCIA slot

===Working===

* Video Card: ATI Mobility X700 (1280x800 - fglrx and radeon &amp; r300)
* Broadcom Wireless LAN Card (acer_acpi + ndiswrapper with bcmwl564.sys driver, available as 80211g.zip from Acer driver download area. Slamd64 - need Windows XP 64 driver).
* Soundcard (snd-atiixp as of alsa-driver-1.0.9b or kernel)
* Function/Hot Keys (have not tried all though; extra configuration required for 'multimedia' keys)
* Touchpad (Doesn't need a driver for basic functions)
* USB
* CD/RW, DVD+/-RW
* Ethernet card (works with Realtek 8169 driver)
* Battery Status
* PCMCIA
* 6-in-1 card reader (SD/ MMC &amp; MemoryStick/ Pro only at the moment - [http://tifmxx.berlios.de/ driver in progress])
* Bluetooth

===Not Tested, but probably works===

* Firewire
* Infra Red
* VGA out

==Kernel Configuration==

You will need to use a 2.6.19 or newer kernel to get this laptop to work properly in Linux without any extra kernel patching (see Troubleshooting for more information).

I would *strongly* recommend you always use the latest stable 2.6.x kernel with this laptop, since there are a lot of fixes going in that relate to this laptop (ATI chipset, apic, yenta socket, wireless drivers (b43), etc).

This should be very similar to any other AMD64 laptop with an ATi chipset (like the Acer Ferrari 4000 series- enable anything with 'ATI IXP', plus the relevant ACPI options. I'll put up more here about any necessary specific options later. However, I have *disabled* the framebuffer, as it doesn't play well with the X video drivers.

When building a new kernel make sure that you use the following options, if you want to use the ATI/fglrx driver:&lt;br&gt;
use '/dev/agpgart' as module&lt;br&gt;
turn off, the 'Direct Render Manager'&lt;br&gt;
(so you dont select 'radeon'..)&lt;br&gt;

==Hardware Package and Software Dependencies==
===Graphics===

Follow the instructions here [http://slackwiki.org/ATI_Graphics] to install and set up your video driver, using the radeon &amp; r300 Mesa drivers. fglrx is no longer supported on this hardware.

===Mouse===

To get advanced features, you will need to install the [http://web.telia.com/~u89404340/touchpad/ Synaptics Mousepad driver for X] and change your mouse driver in xorg.conf to use 'synaptics'. (I use the Synaptics driver mostly to disable 'Tap-to-Click')

To ensure the touchpad always has the same device name, create /etc/udev/rules.d/local.rules (if it doesn't exist) and add the following:

 BUS=="serio", SYSFS{description}=="i8042 Aux-3 Port", KERNEL=="mouse*", NAME="input/%k",SYMLINK+="input/touchpad"

You can now point xorg.conf towards /dev/input/touchpad for the touchpad (/dev/input/touchpad will always be a symlink to whichever device the touchpad is - this can vary depending on whether you plug another mouse into the system before or after booting).

===Modem===
          
This is a Conexant HSF modem - it is incompatible with slmodemd (you therefore do _not_ need snd-atiixp-modem). The only drivers available for this modem are from [http://www.linuxant.com Linuxant] (the free-of-charge drivers are limited to 14.4K, you will need to pay if you want full 56.6K speeds and fax).

===Wireless===

To use the built in wireless, you need to firstly switch on the wireless, then load the b43 driver. You will also need to obtain the firmware for this card - see [http://linuxwireless.org/en/users/Drivers/b43#devicefirmware Linux Wireless] on where to get it from.

1. Enable Wireless

'''2.6.24:'''

* Download, build and install [http://code.google.com/p/aceracpi acer_acpi]
* Load acer_acpi: modprobe acer_acpi wireless=1

'''2.6.25 or newer:'''

* echo 1 &gt; /sys/devices/platform/acer-wmi/wireless
* Or create /etc/modprobe.d/acer-wmi and add "options acer-wmi wireless=1" to do this at boot time

2. Install b43 firmware

* Download, build and install b43-fwcutter - use the [http://www.slackbuilds.org SlackBuilds.org] Slackbuild for thos
* Follow the instructions on [http://linuxwireless.org/en/users/Drivers/b43#devicefirmware Linux Wireless] for your kernel version to extract the firmware and install it to /lib/firmware

(The orange light for the wireless at the front should turn on now)

3. Configure the wireless in /etc/rc.d/rc.inet1.conf

Note: I deleted rc.wireless.conf as it is unecessary and keeps trying to override rc.inet1.conf (besides, configuring wireless in rc.inet1.conf is the future).

===Bluetooth===

The bluetooth is an internal USB dongle. To turn it on:

* echo 1 &gt; /sys/devices/platform/acer-wmi/bluetooth
* Or create /etc/modprobe.d/acer-wmi and add "options acer-wmi bluetooth=1" to do this at boot time

The bluetooth device can now be seen with lsusb (it is not visible when bluetooth if you don't enable it through acer_acpi/ acer-wmi).

===Special Keys===

There is a keymap for the special keys available [http://www.fwconsult.com/acer-install/index.html here].

However, I have had problems with it on my UK layout keyboard so would not recommend using it at the moment.

===Special Keys with X===

====HAL====

You will need, at a minimum, HAL 0.5.10 and hal-info 20070725. The Aspire 5020 has been submitted to HAL as part of their keyboard quirk project, so the extra keys which generated dmesg messages, will now generate proper keycodes.

====X====

There is now a generic acer_laptop keyboard layout in upstream xkeyboard-config (which works in tandem with HAL to map the extra keys). This will be in the next xkeyboard-config release after 1.0 (it is therefore unlikely to make the next X.Org release).

You can also use the evdev layout instead.

===Hardware Monitoring===

Unfortunately, the extent of 'hardware monitoring' on this system comes through 3 thermal zones provided by ACPI.

You can play around with using I2C to access the SMBus, but the hardware on the other end of it appears to be a National Semiconductors chip of sorts that is not supported under Linux (and based on comments on the lm_sensors mailing list, due to various problems, is not very likely to be either).

===Suspend===

Suspend does work on this laptop (assuming you don't have any funny PCMCIA, USB or Firewire devices attached that will break it).

'''In a terminal'''

You will need either vbetool or a 2.6.17-rc (or newer) kernel with s2ram (found in [http://suspend.sourceforge.net suspend]).

Using s2ram:
 s2ram -f -p

Using swusp (run this command after resuming):
  vbetool post

'''In X'''

Works with either radeon or fglrx (you don't need to run s2ram if you suspend from X).

===Card Reader===

This card reader is not fully supported in Linux yet. There is an in development driver, [http://tifmxx.berlios.de tifmxx], that currently supports MMC/ SD, and Memory Stick/ Pro. If you want to help out the project, hardware donations are welcome for unsupported hardware (be aware that the developer's card reader can not physically support SmartMedia cards).

==Troubleshooting==

===HPET===

Not available on this laptop - locks hard with hpet=force (I suspect HPET's are only available on the newer SB480 chipsets).

===DVDs will not play back===

You need to set the DVD region before you can play any DVDs. The 'regionset' tool for Linux will let you do this (otherwise you will have lots of strange error messages in dmesg).

===Suspend/ Resume does not work===

Please be aware that kernel updates can break this. If that's the case, I will try and update this page to reflect that.

Otherwise, go back and make sure you have applied the necessary patch specified earlier in "Suspend" to your kernel. Also, try unplugging any devices attached to the laptop, rebooting (some drivers can be a bit funny otherwise) and then try suspend/ resume. If it now works, then one of your devices or a driver somewhere is breaking suspend - in which case, you should report the bug to the relevant person/ place.

==Contributors==

*[http://slackwiki.org/User:Ccorbacho Carlos Corbacho (aka cathectic)]
*[http://slackwiki.org/User:Funmain Funmain]

==External Links/ References==
* [http://forums.slamd64.com/viewtopic.php?t=27 fglrx on Slamd64]
* [http://www.fwconsult.com/acer-install/index.html Installing Gentoo (2005.0) on an Acer 5021NWLCi]
* [http://gentoo-wiki.com/HARDWARE_Gentoo_Acer_Ferrari_4005WLMi_Manual Gentoo Acer Ferrari 4005WLMi Manual]
* [http://website.lineone.net/~bryanrpoole/atiixp-modem.html ATI-IXP MC97 Modem Development / Configuration Information]
* [http://bugzilla.kernel.org/show_bug.cgi?id=3927 Kernel Bugzilla entry for AMD64/ ATi timer running fast problem]
* [http://doube.net/3023wlmi.html Linux and Windows on an Acer Aspire 3023WLMi]</text>
    <sha1>f20d44203161d01c62c4c939c9cb0385279bd334</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Hibernate</title>
  <ns>0</ns>
  <id>223</id>
  <revision>
    <id>525</id>
    <parentid>471</parentid>
    <timestamp>2011-10-18T13:12:49Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <minor/>
    <comment>/* Generic kernel + initrd */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1467" xml:space="preserve">In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

== Huge kernel ==

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

 append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''.

== Generic kernel + initrd ==

If you're using generic or your own kernel, you need to adjust initrd image as well. Append 

  -h /dev/sdx

to mkinitrd command so it may look like this:
 
  mkinitrd -c -k &lt;kernel-version&gt; -f &lt;fs_type&gt; -m &lt;fs_type&gt; -r /dev/sdx -h /dev/sdy

Replace ''/dev/sdx'' with your actual root partition and ''/dev/sdy'' with your actual swap space.

If you're using LVM, don't forget to append '''-L''' to mkinitrd command

  mkinitrd -c -k &lt;kernel-version&gt; -f &lt;fs_type&gt; -m &lt;fs_type&gt; -r /dev/sdx -h /dev/volumegroup/swap -L

Afterwards, run lilo.

== Further reading ==

* [http://www.linuxquestions.org/linux/answers/Hardware/Mini_HOW_TO_Hibernate_and_resume_0 Mini_HOW_TO_Hibernate_and_resume_0]
* Hibernate to encrypted swap - [http://slackware.osuosl.org/slackware-13.1/README_CRYPT.TXT REAME_CRYPT.TXT]

[[Category:Tutorials]]</text>
    <sha1>36855b4c154cb2bb355481fa74d9c51f5e7c8c9f</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>NoMachine NX Server Installation</title>
  <ns>0</ns>
  <id>250</id>
  <revision>
    <id>526</id>
    <timestamp>2011-10-20T00:29:44Z</timestamp>
    <contributor>
      <username>Natex</username>
      <id>157</id>
    </contributor>
    <comment>Created page with "[[Category:Tutorials]]   == Introduction == The purpose of this article is help the user quickly get an NX server up and running on a Slackware machine. The instructions only app..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="486" xml:space="preserve">[[Category:Tutorials]]


== Introduction ==
The purpose of this article is help the user quickly get an NX server up and running on a Slackware machine. The instructions only apply to NoMachine's NX server implementation and does not apply to Freenx server. Instructions for installing a Freenx server can be found here.

== What is NX? ==
An introduction to NX can be found at http://www.nomachine.com/documents/getting-started.php


NX
Requirements
Obtain
Extract
Installation
Connect</text>
    <sha1>4b813ebd315554aa190e889e3d284fed2961e8f6</sha1>
  </revision>
  <revision>
    <id>527</id>
    <parentid>526</parentid>
    <timestamp>2011-10-20T02:42:11Z</timestamp>
    <contributor>
      <username>Natex</username>
      <id>157</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1401" xml:space="preserve">[[Category:Tutorials]]


== Introduction ==
The purpose of this article is help the user quickly get NX Server installed on a Slackware machine. The installation will use the compressed tar packages (version 3.5.X.TAR.GZ) from http://www.nomachine.com. The tutorial only applies to NoMachine's NX server implementation (free edition) and does not apply to Freenx. Instructions for installing Freenx can be found here.

== What is NX? ==
An introduction to NX can be found at http://www.nomachine.com/documents/getting-started.php

== Slackware Requirements ==
According to NoMachine, there are three required packages for a working installation on Linux.
* nxclient
* nxnode
* nxserver

No other dependencies are required to install NX Server. However, sshd must already be running on the server and configured properly. ''The client machine must be able to connect to the server via ssh.''

== NX Installation ==
The following steps must be performed with root priviledges.
# Obtain the nxserver, nxnode, and nxclient (compressed tar) packages from http://www.nomachine.com/select-package.php?os=linux&amp;id=1.
# Change to the /usr directory.&lt;blockquote&gt;# cd /usr&lt;/blockquote&gt;
# Extract each of the three packages.&lt;blockquote&gt;# tar zxvf nxclient-3.5.X.tar.gz&lt;/blockquote&gt;&lt;blockquote&gt;# tar zxvf nxnode-3.5.X.tar.gz&lt;/blockquote&gt;&lt;blockquote&gt;#tar zxvf nxserver-3.5.X.tar.gz&lt;/blockquote&gt;
Installation
Connect</text>
    <sha1>9553e45a64251d6a5698a8fca53b2b1377519c04</sha1>
  </revision>
  <revision>
    <id>528</id>
    <parentid>527</parentid>
    <timestamp>2011-10-20T02:59:06Z</timestamp>
    <contributor>
      <username>Natex</username>
      <id>157</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1701" xml:space="preserve">[[Category:Tutorials]]


== Introduction ==
The purpose of this article is help the user quickly get NX Server installed on a Slackware machine. The installation will use the compressed tar packages (version 3.5.X.TAR.GZ) from http://www.nomachine.com. The tutorial only applies to NoMachine's NX server implementation (free edition) and does not apply to Freenx. Instructions for installing Freenx can be found here.

== What is NX? ==
An introduction to NX can be found at http://www.nomachine.com/documents/getting-started.php

== Slackware Requirements ==
According to NoMachine, there are three required packages for a working installation on Linux.
* nxclient
* nxnode
* nxserver

No other dependencies are required to install NX Server. However, to connect to NX Server, sshd must already be running on the server and configured properly. ''The client machine must be able to connect to the server via ssh.''

== NX Installation ==
The following steps must be performed with root priviledges.
# Obtain the nxserver, nxnode, and nxclient (compressed tar) packages from http://www.nomachine.com/select-package.php?os=linux&amp;id=1.
# Change to the /usr directory.&lt;blockquote&gt;# cd /usr&lt;/blockquote&gt;
# Extract each of the three packages.&lt;blockquote&gt;# tar zxvf nxclient-3.5.X.tar.gz&lt;/blockquote&gt;&lt;blockquote&gt;# tar zxvf nxnode-3.5.X.tar.gz&lt;/blockquote&gt;&lt;blockquote&gt;# tar zxvf nxserver-3.5.X.tar.gz&lt;/blockquote&gt;
# Create some required directories in /etc/init.d/&lt;blockquote&gt;# mkdir /etc/init.d/rc{0,2,3,5,6}.d&lt;/blockquote&gt;
# Run the installation scripts &lt;blockquote&gt;# /usr/NX/scripts/setup/nxnode --install suse&lt;/blockquote&gt;&lt;blockquote&gt;# /usr/NX/scripts/setup/nxserver --install suse&lt;/blockquote&gt;
 
Connect</text>
    <sha1>8f024506e05a8ac5aaea73f4c9886ff0de3849ea</sha1>
  </revision>
  <revision>
    <id>529</id>
    <parentid>528</parentid>
    <timestamp>2011-10-20T04:34:28Z</timestamp>
    <contributor>
      <username>Natex</username>
      <id>157</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1860" xml:space="preserve">[[Category:Tutorials]]


== Introduction ==
The purpose of this article is help the user quickly get NX Server installed on a Slackware machine. The installation will use the compressed tar packages (version 3.5.X.TAR.GZ) from http://www.nomachine.com. The tutorial only applies to NoMachine's NX server implementation (free edition) and does not apply to Freenx. Instructions for installing Freenx can be found here.

== What is NX? ==
An introduction to NX can be found at http://www.nomachine.com/documents/getting-started.php

== Slackware Requirements ==
According to NoMachine, there are three required packages for a working installation on Linux.
* nxclient
* nxnode
* nxserver

A working sshd installation must already be running on the server and configured properly. ''The client machine must be able to connect to the server via ssh.''

== Changes to /etc/ssh/sshd_config === 
Comment out #AuthorizedKeysFile .ssh/authorized_keys so that the sshd daemon configuration is configured to look for an authorized key file named .ssh/authorized_keys and .ssh/authorized_keys2. 


== NX Installation ==
The following steps must be performed with root priviledges.
# Obtain the nxserver, nxnode, and nxclient (compressed tar) packages from http://www.nomachine.com/select-package.php?os=linux&amp;id=1.
# Change to the /usr directory.&lt;blockquote&gt;# cd /usr&lt;/blockquote&gt;
# Extract each of the three packages.&lt;blockquote&gt;# tar zxvf nxclient-3.5.X.tar.gz&lt;/blockquote&gt;&lt;blockquote&gt;# tar zxvf nxnode-3.5.X.tar.gz&lt;/blockquote&gt;&lt;blockquote&gt;# tar zxvf nxserver-3.5.X.tar.gz&lt;/blockquote&gt;
# Create some required directories in /etc/init.d/&lt;blockquote&gt;# mkdir /etc/init.d/rc{0,2,3,5,6}.d&lt;/blockquote&gt;
# Run the installation scripts &lt;blockquote&gt;# /usr/NX/scripts/setup/nxnode --install suse&lt;/blockquote&gt;&lt;blockquote&gt;# /usr/NX/scripts/setup/nxserver --install suse&lt;/blockquote&gt;</text>
    <sha1>62641159edc407eafd60900e6f79721c13e8e290</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Dual Booting With FreeBSD 9</title>
  <ns>0</ns>
  <id>253</id>
  <revision>
    <id>533</id>
    <timestamp>2011-10-25T09:57:59Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>Created page with "=Introduction=  FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however do..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3107" xml:space="preserve">=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

    # grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

    # make install &amp;&amp; rm -rf work
    # grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

    #!/bin/sh
      exec tail -n +3 $0
      # This file provides an easy way to add custom menu entries.  Simply type the
      # menu entries you want to add after this comment.  Be careful not to change
      # the 'exec tail' line above.
    
      menuentry 'Slackware' --class slackware --class gnu-linux --class os {
          insmod gzio
          insmod part_msdos
          insmod ext2
          set root='(hd0,2)'
          linux   /boot/vmlinuz root=/dev/sdb2 ro
      }
    
      menuentry "FreeBSD /boot/loader" --class freebsd --class bsd --class os {
              insmod ufs2
              set root='(hd1,2)'
              kfreebsd                /boot/loader
      }

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

My Slackware uses ext4 and a custom kernel with no initrd. For, say, xfs you should use 'insmod xfs'.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]</text>
    <sha1>0513ad76fb5cc03fd28577a6c856ee8878eaaae5</sha1>
  </revision>
  <revision>
    <id>534</id>
    <parentid>533</parentid>
    <timestamp>2011-10-25T09:59:02Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>moved [[Dual Booting With FreeBSD 9+]] to [[Dual Booting With FreeBSD 9]]: + messes up the link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3107" xml:space="preserve">=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

    # grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

    # make install &amp;&amp; rm -rf work
    # grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

    #!/bin/sh
      exec tail -n +3 $0
      # This file provides an easy way to add custom menu entries.  Simply type the
      # menu entries you want to add after this comment.  Be careful not to change
      # the 'exec tail' line above.
    
      menuentry 'Slackware' --class slackware --class gnu-linux --class os {
          insmod gzio
          insmod part_msdos
          insmod ext2
          set root='(hd0,2)'
          linux   /boot/vmlinuz root=/dev/sdb2 ro
      }
    
      menuentry "FreeBSD /boot/loader" --class freebsd --class bsd --class os {
              insmod ufs2
              set root='(hd1,2)'
              kfreebsd                /boot/loader
      }

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

My Slackware uses ext4 and a custom kernel with no initrd. For, say, xfs you should use 'insmod xfs'.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]</text>
    <sha1>0513ad76fb5cc03fd28577a6c856ee8878eaaae5</sha1>
  </revision>
  <revision>
    <id>536</id>
    <parentid>534</parentid>
    <timestamp>2011-10-25T10:55:53Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3174" xml:space="preserve">=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

    # grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

    # make install &amp;&amp; rm -rf work
    # grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

    #!/bin/sh
      exec tail -n +3 $0
      # This file provides an easy way to add custom menu entries.  Simply type the
      # menu entries you want to add after this comment.  Be careful not to change
      # the 'exec tail' line above.
    
      menuentry 'Slackware' --class slackware --class gnu-linux --class os {
          insmod gzio
          insmod part_msdos
          insmod ext2
          set root='(hd0,2)'
          linux   /boot/vmlinuz root=/dev/sdb2 ro
      }
    
      menuentry "FreeBSD /boot/loader" --class freebsd --class bsd --class os {
              insmod ufs2
              set root='(hd1,2)'
              kfreebsd                /boot/loader
      }

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

The Slackware partition uses ext4 and the huge kernel with no initrd. For, say, xfs you should use 'insmod xfs'. For an initrd you need to look up the appropriate docs.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]</text>
    <sha1>356a1e7bea3b087b1d2110805386cec5f5e8b213</sha1>
  </revision>
</page>
<page arvcontinue="20110428214156|478">
  <title>Dual Booting With FreeBSD 9+</title>
  <ns>0</ns>
  <id>254</id>
  <revision>
    <id>535</id>
    <timestamp>2011-10-25T09:59:02Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <comment>moved [[Dual Booting With FreeBSD 9+]] to [[Dual Booting With FreeBSD 9]]: + messes up the link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41" xml:space="preserve">#REDIRECT [[Dual Booting With FreeBSD 9]]</text>
    <sha1>d72b2b389374323983ab0bceb17fa099505b7f30</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Dual Booting With FreeBSD 9</title>
  <ns>0</ns>
  <id>253</id>
  <revision>
    <id>537</id>
    <parentid>536</parentid>
    <timestamp>2011-10-25T11:07:51Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Custom Rule */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3148" xml:space="preserve">=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

    # grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

    # make install &amp;&amp; rm -rf work
    # grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

    #!/bin/sh
      exec tail -n +3 $0
      # This file provides an easy way to add custom menu entries.  Simply type the
      # menu entries you want to add after this comment.  Be careful not to change
      # the 'exec tail' line above.
    
      menuentry 'Slackware' --class slackware --class gnu-linux --class os {
          insmod gzio
          insmod part_msdos
          insmod ext2
          set root='(hd0,2)'
          linux   /boot/vmlinuz root=/dev/sdb2 ro
      }
    
      menuentry "FreeBSD --class freebsd --class bsd --class os {
          insmod ufs2
          set root='(hd1,2)'
          kfreebsd                /boot/loader
      }

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

The Slackware partition uses ext4 and the huge kernel with no initrd. For, say, xfs you should use 'insmod xfs'. For an initrd you need to look up the appropriate docs.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]</text>
    <sha1>853c89f5362b0c9234dd7193f5d7eaf747acb9eb</sha1>
  </revision>
  <revision>
    <id>538</id>
    <parentid>537</parentid>
    <timestamp>2011-10-25T11:08:23Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Custom Rule */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3149" xml:space="preserve">=Introduction=

FreeBSD 9+ differs from older releases by using GPT (GUID Partition Table). This means that lilo and grub version 1 will no longer work. Grub version 2 however does work.

There are two way of doings this - either install grub2 in Slackware, or install it in FreeBSD. Grub2 in Slackware does not seem to be able to pick up the FreeBSD partition and Grub2 in FreeBSD doesn't seem to pick up the Linux partitions. You will need to manually add these to /usr/local/etc/grub.d/40_custom.

To pick up all your Slackware kernels it's probably best to install grub2 in Slackware and add the FreeBSD partition manually. I've shown both methods here though, for completeness.

For this howto we'll assume that Slackware / is on /dev/sda2 (with no separate /boot partition), and that FreeBSD is on /dev/sdb2 (/dev/ada1p2 in FreeBSD-speak). These correspond to (hd0,2) and (hd1,2) in Grub2.

=To install Grub2 in Slackware=

To install Grub2 in Slackware, you can use the slackbuild script here:
http://slackbuilds.org/repository/13.37/system/grub2/ and its dependencies. Once installed, issue:

    # grub-install --modules=part_gpt /dev/sda

Edit /etc/grub.d/40_custom to add your FreeBSD partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pickup all your Linux partitions and all kernels (hopefully).

=To install in FreeBSD=

To install Grub2 in FreeBSD, you need to use ports.

I won't give an extended howto on using ports but these are the steps:

Fire up your FreeBSD system and navigate your way to /usr/ports/sysutils/grub2 as root

    # make install &amp;&amp; rm -rf work
    # grub-install --modules=part_gpt /dev/ad0

Edit /usr/local/etc/grub.d/40_custom to add your Slackware partition (see mine below for an example). Once done:

    # grub-mkconfig -o /boot/grub/grub.cfg

grub-mkconfig will pick up FreeBSD automatically.
/usr/local/etc/grub.d/40_custom will contain the extra OS's and FreeBSD boot loader if req'd.

=Custom Rule=
This is my 40_custom:

    #!/bin/sh
      exec tail -n +3 $0
      # This file provides an easy way to add custom menu entries.  Simply type the
      # menu entries you want to add after this comment.  Be careful not to change
      # the 'exec tail' line above.
    
      menuentry 'Slackware' --class slackware --class gnu-linux --class os {
          insmod gzio
          insmod part_msdos
          insmod ext2
          set root='(hd0,2)'
          linux   /boot/vmlinuz root=/dev/sdb2 ro
      }
    
      menuentry "FreeBSD" --class freebsd --class bsd --class os {
          insmod ufs2
          set root='(hd1,2)'
          kfreebsd                /boot/loader
      }

(You choose which section you want to add - FreeBSD or Slackware - depending on where you installed Grub2.)

That's pretty much it.

=Notes=

The Slackware partition uses ext4 and the huge kernel with no initrd. For, say, xfs you should use 'insmod xfs'. For an initrd you need to look up the appropriate docs.

Caveat: This was tested on FreeBSD 9.0Beta3. I can't see that it wouldn't work when release is out but you never know.

[[User:Dive|Dive]]</text>
    <sha1>384ea90a80e56f24d0b45c74d645fae087eb79b0</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>User talk:Merge-delete</title>
  <ns>3</ns>
  <id>255</id>
  <revision>
    <id>539</id>
    <timestamp>2011-11-27T13:14:08Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <comment>Planning a trip to lonavala?Visit our site for more information on hotels in lonavala.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2344" xml:space="preserve">Boutique Hotels In India

Indulge yourself in sheer luxury throughout your remain in boutique hotels in India.[http://hotelslonavala.net/ hotels in lonavala] These are the places where one can live like rajas and maharajas. They're simply unique within their architecture and hang up where one can get highly personalized services inside a distinctive manner. They are heritage hotels that supply you with a unique connection with living existence.[http://hotelslonavala.net/ hotels in lonavala] Just opposite to western style hotels, these places permit you to know and have the wealthy culture and history of India.

 On a trip from the beaten tracks in India, you might find several boutique hotels where one can unwind yourself and also have home-cooked food. With enchanting folk music, amazing architecture, peace and exceptional hospitality, these hotels can bring alive the times of rajas and maharajas of older occasions. Their architecture, gardens, food and luxuries echo from the glorious past of India. Although you will find several hotels in India but when youre searching for best hotels, then certainly Rajasthan may be the condition that you need to visit whenever you arrived at India.

 You will find several havelis-converted-hotels in Rajasthan where you can unwind yourself and dip your senses in luxury. Remaining during these hotels is definitely an entirely different experience. Youll feel like you aren't nowadays. For experience a completely different lifestyle, you have to visit these hotels and spend your trip. Trust, youll possess a lifetime experience. The deserted great thing about Rajasthan and wealthy tradition enables you to definitely go through the luxury in simplicity. You no more have to pretend as possible be genuine and do what youve always loved.

 The best hotels in Rajasthan are Rawla Narlai, Raas Hotel, The Serai, Udai Kothi, Bhainsrorgarh and Devigarh. From the sights of those hotels, regal inside and grass to authentic antiques, lodging and fooding may be worth admiring. You seem like wandering within the deserts, going through the wonder, studying wealthy tradition, listening folk music and gorging on local meals. Several companies offer vacation packages to Rajasthan. Whenever you arrived at India, you just cant manage to miss these places. They feature glorious past of India.</text>
    <sha1>41ee596bca7edd95e7e87a4ae8e86d225025fc69</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Different Approach To Buildscripts</title>
  <ns>0</ns>
  <id>22</id>
  <revision>
    <id>540</id>
    <parentid>30</parentid>
    <timestamp>2011-12-09T10:18:39Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7035" xml:space="preserve">[[Category:Tutorials]]
Pretty much everyone can hanve their own way of writing Slackware buildscripts. I also have mine, which just makes it easier for me to package software.

In here, I'm going to explain mine. To start, let's look at one I wrote this morning while drinking coffee cup #1:

    #!/bin/bash
    
    #############################################################################
    ## Name: jpilot                                                            ##
    ## Version: 0.99.8                                                         ##
    ## Packager: Martin Lefebvre (dadexter@gmail.com)                          ##
    ## Homepage: http://www.jpilot.org                                         ##
    #############################################################################
    
    PKGNAME=jpilot
    VERSION=0.99.8
    LOC="http://jpilot.org/$PKGNAME-$VERSION.tar.gz"
    ARCH=`uname -m`
    
    START=`pwd`
    PKG=$START/pkg
    SRC=$START/work
    
    build() {
            mkdir -p $PKG $SRC
            cd $SRC
            wget $LOC
            tar -zxvf $PKGNAME-$VERSION.tar.gz
            cd $PKGNAME-$VERSION
            ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
            --enable-gtk2 --enable-prometheon
            
            patch -p0 &lt; patch.0.99.8-memory
            patch -p0 &lt; patch.jpilot-sync
            make
            make DESTDIR=$PKG install
            mkdir -p $PKG/usr/doc/$PKGNAME-$VERSION
            cp -r ABOUT-NLS AUTHORS BUGS COPYING ChangeLog ChangeLog.cvs INSTALL \
            NEWS README TODO UPGRADING docs $PKG/usr/doc/$PKGNAME-$VERSION
            
            cp KeyRing/README.txt $PKG/usr/doc/$PKGNAME-$VERSION/README.keyring
            cp dialer/README $PKG/usr/doc/$PKGNAME-$VERSION/README.dialer
            cp icons/README $PKG/usr/doc/$PKGNAME-$VERSION/README.icons
    }
    
    package() {
            cd $PKG
            find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "current ar archive" | cut -f 1 -d : | \
            xargs strip --strip-debug 2&gt; /dev/null
            chown -R root:root usr/bin
            gzip -p $PKG/usr/man/man*/*
            mkdir $PKG/install
            cp $START/slack-desc $PKG/install/slack-desc
            cd $PKG
            makepkg -l y -c n $START/$PKGNAME-$VERSION-$ARCH-1.tgz
    }
    
    build
    package


The top section is just comments identifying the piece of software we're going to build, and the name of the script's author. Then we have the following lines:

    PKGNAME=jpilot
    VERSION=0.99.8
    LOC="http://jpilot.org/$PKGNAME-$VERSION.tar.gz"
    ARCH=`uname -m`
    
    START=`pwd`
    PKG=$START/pkg
    SRC=$START/work

They set the program's name, version, download URL, build and package directories. Since I usually don't specify anything related to the cpu or architecture, it auto detects the architecture. So, the $ARCH variable *should be* accurate.

    build() {
            mkdir -p $PKG $SRC
            cd $SRC
            wget $LOC
            tar -zxvf $PKGNAME-$VERSION.tar.gz
            cd $PKGNAME-$VERSION
            ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
            --enable-gtk2 --enable-prometheon
            
            patch -p0 &lt; patch.0.99.8-memory
            patch -p0 &lt; patch.jpilot-sync
            make
            make DESTDIR=$PKG install
            mkdir -p $PKG/usr/doc/$PKGNAME-$VERSION
            cp -r ABOUT-NLS AUTHORS BUGS COPYING ChangeLog ChangeLog.cvs INSTALL \
            NEWS README TODO UPGRADING docs $PKG/usr/doc/$PKGNAME-$VERSION
            
            cp KeyRing/README.txt $PKG/usr/doc/$PKGNAME-$VERSION/README.keyring
            cp dialer/README $PKG/usr/doc/$PKGNAME-$VERSION/README.dialer
            cp icons/README $PKG/usr/doc/$PKGNAME-$VERSION/README.icons
    }

The is the main build function. This contains the code required to build the software. First, we create the build and package directories. The next 3 lines change to the building diirectory, uses wget to fetch the source file and extracts it.

The lines after that are what you would normally type at your command line to build the software:

* Change to the source directory.
* Run ./configure with all the options you want.
* Apply two patches required (in this case) to fix bugs with the software.
* Run make
* Install the software in the package directory defined by $PKG
* Create the standard Slackware Software Documentation directory in the package
* Copy the standard documentation.


The next section is the packaging part:

    package() {
            cd $PKG
            find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "current ar archive" | cut -f 1 -d : | \
            xargs strip --strip-debug 2&gt; /dev/null
            chown -R root:root usr/bin
            gzip -p $PKG/usr/man/man*/*
            mkdir $PKG/install
            cp $START/slack-desc $PKG/install/slack-desc
            cd $PKG
            makepkg -l y -c n $START/$PKGNAME-$VERSION-$ARCH-1.tgz
    }

* We change to the package directory
* Strip executables and libraries in order to decrease size.
* As a Slackware standard, we change the ownership of the executables to root:root (to be done for every bin/ and sbin/ directory)
* We compress the manpages
* Create install/ and copy the slack-desc file from the start directory
* Finally, change back to the package folder and create the package tarball.


In this example, the slack-desc and some patch files are distributed with the SlackBuild. This also makes it easier to ship the build script with patches that might be required for the software to work on Slackware (patch to remove PAM stuff).

The slack-desc file format is described here: [http://www.linuxpackages.net/howto.php?page=slack-desc&amp;title=Slackware+Desc+Files LinuxPackages.net]


Additional files:

Some people use slapt-get (like me). slapt-get supports additional features such as
* Dependencies
* Conflicts
* Suggestions

Not everyone wants those features, so building a package with those files will not interfere with the normal pkgtools process. For more info on these optional files, go here: [http://www.linuxpackages.net/howto.php?page=perfect-package&amp;title=Perfect+Package#Optional LinuxPackages.net]

If you decide to use those files, you will then have to repeat these lines:

    cp $START/slack-desc $PKG/install/slack-desc

for slack-required, slack-conflicts, and slack-suggests.


----
See also [[SlackBuild_Scripts]] and [[Writing A SlackBuild Script]]
----</text>
    <sha1>a2b8fad2796c3cf8c3f3871605463b424a4d4a9f</sha1>
  </revision>
  <revision>
    <id>567</id>
    <parentid>540</parentid>
    <timestamp>2011-12-09T14:11:17Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Dugan|Dugan]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7034" xml:space="preserve">[[Category:Tutorials]]
Pretty much everyone can have their own way of writing Slackware buildscripts. I also have mine, which just makes it easier for me to package software.

In here, I'm going to explain mine. To start, let's look at one I wrote this morning while drinking coffee cup #1:

    #!/bin/bash
    
    #############################################################################
    ## Name: jpilot                                                            ##
    ## Version: 0.99.8                                                         ##
    ## Packager: Martin Lefebvre (dadexter@gmail.com)                          ##
    ## Homepage: http://www.jpilot.org                                         ##
    #############################################################################
    
    PKGNAME=jpilot
    VERSION=0.99.8
    LOC="http://jpilot.org/$PKGNAME-$VERSION.tar.gz"
    ARCH=`uname -m`
    
    START=`pwd`
    PKG=$START/pkg
    SRC=$START/work
    
    build() {
            mkdir -p $PKG $SRC
            cd $SRC
            wget $LOC
            tar -zxvf $PKGNAME-$VERSION.tar.gz
            cd $PKGNAME-$VERSION
            ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
            --enable-gtk2 --enable-prometheon
            
            patch -p0 &lt; patch.0.99.8-memory
            patch -p0 &lt; patch.jpilot-sync
            make
            make DESTDIR=$PKG install
            mkdir -p $PKG/usr/doc/$PKGNAME-$VERSION
            cp -r ABOUT-NLS AUTHORS BUGS COPYING ChangeLog ChangeLog.cvs INSTALL \
            NEWS README TODO UPGRADING docs $PKG/usr/doc/$PKGNAME-$VERSION
            
            cp KeyRing/README.txt $PKG/usr/doc/$PKGNAME-$VERSION/README.keyring
            cp dialer/README $PKG/usr/doc/$PKGNAME-$VERSION/README.dialer
            cp icons/README $PKG/usr/doc/$PKGNAME-$VERSION/README.icons
    }
    
    package() {
            cd $PKG
            find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "current ar archive" | cut -f 1 -d : | \
            xargs strip --strip-debug 2&gt; /dev/null
            chown -R root:root usr/bin
            gzip -p $PKG/usr/man/man*/*
            mkdir $PKG/install
            cp $START/slack-desc $PKG/install/slack-desc
            cd $PKG
            makepkg -l y -c n $START/$PKGNAME-$VERSION-$ARCH-1.tgz
    }
    
    build
    package


The top section is just comments identifying the piece of software we're going to build, and the name of the script's author. Then we have the following lines:

    PKGNAME=jpilot
    VERSION=0.99.8
    LOC="http://jpilot.org/$PKGNAME-$VERSION.tar.gz"
    ARCH=`uname -m`
    
    START=`pwd`
    PKG=$START/pkg
    SRC=$START/work

They set the program's name, version, download URL, build and package directories. Since I usually don't specify anything related to the cpu or architecture, it auto detects the architecture. So, the $ARCH variable *should be* accurate.

    build() {
            mkdir -p $PKG $SRC
            cd $SRC
            wget $LOC
            tar -zxvf $PKGNAME-$VERSION.tar.gz
            cd $PKGNAME-$VERSION
            ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var \
            --enable-gtk2 --enable-prometheon
            
            patch -p0 &lt; patch.0.99.8-memory
            patch -p0 &lt; patch.jpilot-sync
            make
            make DESTDIR=$PKG install
            mkdir -p $PKG/usr/doc/$PKGNAME-$VERSION
            cp -r ABOUT-NLS AUTHORS BUGS COPYING ChangeLog ChangeLog.cvs INSTALL \
            NEWS README TODO UPGRADING docs $PKG/usr/doc/$PKGNAME-$VERSION
            
            cp KeyRing/README.txt $PKG/usr/doc/$PKGNAME-$VERSION/README.keyring
            cp dialer/README $PKG/usr/doc/$PKGNAME-$VERSION/README.dialer
            cp icons/README $PKG/usr/doc/$PKGNAME-$VERSION/README.icons
    }

The is the main build function. This contains the code required to build the software. First, we create the build and package directories. The next 3 lines change to the building diirectory, uses wget to fetch the source file and extracts it.

The lines after that are what you would normally type at your command line to build the software:

* Change to the source directory.
* Run ./configure with all the options you want.
* Apply two patches required (in this case) to fix bugs with the software.
* Run make
* Install the software in the package directory defined by $PKG
* Create the standard Slackware Software Documentation directory in the package
* Copy the standard documentation.


The next section is the packaging part:

    package() {
            cd $PKG
            find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : \
            | xargs strip --strip-unneeded 2&gt; /dev/null
            find . | xargs file | grep "current ar archive" | cut -f 1 -d : | \
            xargs strip --strip-debug 2&gt; /dev/null
            chown -R root:root usr/bin
            gzip -p $PKG/usr/man/man*/*
            mkdir $PKG/install
            cp $START/slack-desc $PKG/install/slack-desc
            cd $PKG
            makepkg -l y -c n $START/$PKGNAME-$VERSION-$ARCH-1.tgz
    }

* We change to the package directory
* Strip executables and libraries in order to decrease size.
* As a Slackware standard, we change the ownership of the executables to root:root (to be done for every bin/ and sbin/ directory)
* We compress the manpages
* Create install/ and copy the slack-desc file from the start directory
* Finally, change back to the package folder and create the package tarball.


In this example, the slack-desc and some patch files are distributed with the SlackBuild. This also makes it easier to ship the build script with patches that might be required for the software to work on Slackware (patch to remove PAM stuff).

The slack-desc file format is described here: [http://www.linuxpackages.net/howto.php?page=slack-desc&amp;title=Slackware+Desc+Files LinuxPackages.net]


Additional files:

Some people use slapt-get (like me). slapt-get supports additional features such as
* Dependencies
* Conflicts
* Suggestions

Not everyone wants those features, so building a package with those files will not interfere with the normal pkgtools process. For more info on these optional files, go here: [http://www.linuxpackages.net/howto.php?page=perfect-package&amp;title=Perfect+Package#Optional LinuxPackages.net]

If you decide to use those files, you will then have to repeat these lines:

    cp $START/slack-desc $PKG/install/slack-desc

for slack-required, slack-conflicts, and slack-suggests.


----
See also [[SlackBuild_Scripts]] and [[Writing A SlackBuild Script]]
----</text>
    <sha1>00c1d139fe473abbcd7fd5f55290127ea0189736</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Permissions and Umasks</title>
  <ns>0</ns>
  <id>30</id>
  <revision>
    <id>541</id>
    <parentid>39</parentid>
    <timestamp>2011-12-09T10:19:48Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3542" xml:space="preserve">==Normal Permissions==

On *nix-like systems, traditionally eery file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).

You can change the owner of a file with the "chown" command:

: &lt;code&gt;fred@linux:~&gt; chown someUser foo&lt;/code&gt;

You can change the group of a file with the "chgrp" command:

: &lt;code&gt;fred@linux:~&gt; chgrp someGroup foo&lt;/code&gt;

Alternatively, you can do both at once:

: fred@linux:~&gt; &lt;code&gt;chown someUser.someGroup foo&lt;/code&gt;

or:

: fred@linux:~&gt; &lt;code&gt;chown someUser:someGroup foo&lt;/code&gt;

For every file, you can set the following for the User, Group, and Others: r - can read w - can write x - can execute

These are set with the "chmod" command:

: fred@linux:~&gt; &lt;code&gt;chmod u=rwx,g=rx,o=r foo&lt;/code&gt;
: fred@linux:~&gt; &lt;code&gt;ls -l foo&lt;/code&gt;
: -rwxr-xr--  1 fred users 0 2004-10-26 11:38 foo

You don't need to set all the permissions - you can just modify them, for example, to make a file executable:

: fred@linux:~&gt; &lt;code&gt;chmod +x foo&lt;/code&gt;

You can also change the permissions just for either the User, Group, or Others:

: fred@linux:~&gt; &lt;code&gt;chmod o-x foo&lt;/code&gt;

==Octal Permissions==

You can also specify permissions with a number. To find out which numbers, add up the numbers from this table:

 r w x
 4 2 1

For example, rwxr-xr-- would be:

 U  G  O
 4  4  4
 +2 +0 +0
 +1 +1 +0
 =7 =5 =4

So to give a file rwxr-xr-- permissions:

: fred@linux:~&gt; &lt;code&gt;chmod 754 foo&lt;/code&gt;

==Umasks==

umasks define which permissions can not be set (in octal). For example, the default umask on slackware is 0022:

: fred@laptop:~$ &lt;code&gt;umask&lt;/code&gt;
: 0022

Ignoring the first digit, this means that the owner can do anything, but group and others are unable to write (2 == w). A more secure umask (possibly more suitable for your ~/) is 0077, meaning that group and others have no access to your files.

==More Umask==

The following is based on [[User:Sandman1|Sandman1]]'s Umask tutorial.

Well first this is a pretty boring topic to write about, So im going to get right to the point. When you set a umask you set what permission NOT to set. So when you create a file it uses the umask to set the file permissions. All of this might not make sense now but it will later. Now type:

: &lt;code&gt;umask&lt;/code&gt;

Now on slackware you will get "0022", First ignore the first 0. Now we have 022. The first 0 makes sure the owner has ALL the permissions of a file. You can tell that becuase you have no permissions you want to turn off. Now the next two numbers you have a 2 for. The 2 indicates that you NEVER want to set write permissions.

Now that method above of trying to find a umask is a bit confusing. All you do is set the number what you DON'T want the user to have. Now there is an easier way of finding out a umask. You can subtract the permission from 777. Example:

 777 - 750 = 027

That is the umask of the 750 permission. Now you may be asking yourself what is this usefull for. Well you can set the umask by typing "umask 027" in bash and when you create a file/directory it goes by umask 027 instead of the 0022.

Now another reason for setting a umask is becuase you want to access a filesystem such as NTFS,VFAT,Samba,etc as a regular user. You can set the umask and allow regular users to write to the filesytem. It is really easy, in the fstab all you add is "umask=027" and remount the filesystem.
See [[Windows_Partitions]] for more information (and a potentially better option than setting umask options).

[[Category:Tutorials]]</text>
    <sha1>ef0ef98cd3784fec7378d34ef36947f6034d57f9</sha1>
  </revision>
  <revision>
    <id>568</id>
    <parentid>541</parentid>
    <timestamp>2011-12-09T14:11:36Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3543" xml:space="preserve">==Normal Permissions==

On *nix-like systems, traditionally every file has an owner, an assigned group, and a list of permissions (although POSIX Access Control Lists are getting more popular).

You can change the owner of a file with the "chown" command:

: &lt;code&gt;fred@linux:~&gt; chown someUser foo&lt;/code&gt;

You can change the group of a file with the "chgrp" command:

: &lt;code&gt;fred@linux:~&gt; chgrp someGroup foo&lt;/code&gt;

Alternatively, you can do both at once:

: fred@linux:~&gt; &lt;code&gt;chown someUser.someGroup foo&lt;/code&gt;

or:

: fred@linux:~&gt; &lt;code&gt;chown someUser:someGroup foo&lt;/code&gt;

For every file, you can set the following for the User, Group, and Others: r - can read w - can write x - can execute

These are set with the "chmod" command:

: fred@linux:~&gt; &lt;code&gt;chmod u=rwx,g=rx,o=r foo&lt;/code&gt;
: fred@linux:~&gt; &lt;code&gt;ls -l foo&lt;/code&gt;
: -rwxr-xr--  1 fred users 0 2004-10-26 11:38 foo

You don't need to set all the permissions - you can just modify them, for example, to make a file executable:

: fred@linux:~&gt; &lt;code&gt;chmod +x foo&lt;/code&gt;

You can also change the permissions just for either the User, Group, or Others:

: fred@linux:~&gt; &lt;code&gt;chmod o-x foo&lt;/code&gt;

==Octal Permissions==

You can also specify permissions with a number. To find out which numbers, add up the numbers from this table:

 r w x
 4 2 1

For example, rwxr-xr-- would be:

 U  G  O
 4  4  4
 +2 +0 +0
 +1 +1 +0
 =7 =5 =4

So to give a file rwxr-xr-- permissions:

: fred@linux:~&gt; &lt;code&gt;chmod 754 foo&lt;/code&gt;

==Umasks==

umasks define which permissions can not be set (in octal). For example, the default umask on slackware is 0022:

: fred@laptop:~$ &lt;code&gt;umask&lt;/code&gt;
: 0022

Ignoring the first digit, this means that the owner can do anything, but group and others are unable to write (2 == w). A more secure umask (possibly more suitable for your ~/) is 0077, meaning that group and others have no access to your files.

==More Umask==

The following is based on [[User:Sandman1|Sandman1]]'s Umask tutorial.

Well first this is a pretty boring topic to write about, So im going to get right to the point. When you set a umask you set what permission NOT to set. So when you create a file it uses the umask to set the file permissions. All of this might not make sense now but it will later. Now type:

: &lt;code&gt;umask&lt;/code&gt;

Now on slackware you will get "0022", First ignore the first 0. Now we have 022. The first 0 makes sure the owner has ALL the permissions of a file. You can tell that becuase you have no permissions you want to turn off. Now the next two numbers you have a 2 for. The 2 indicates that you NEVER want to set write permissions.

Now that method above of trying to find a umask is a bit confusing. All you do is set the number what you DON'T want the user to have. Now there is an easier way of finding out a umask. You can subtract the permission from 777. Example:

 777 - 750 = 027

That is the umask of the 750 permission. Now you may be asking yourself what is this usefull for. Well you can set the umask by typing "umask 027" in bash and when you create a file/directory it goes by umask 027 instead of the 0022.

Now another reason for setting a umask is becuase you want to access a filesystem such as NTFS,VFAT,Samba,etc as a regular user. You can set the umask and allow regular users to write to the filesytem. It is really easy, in the fstab all you add is "umask=027" and remount the filesystem.
See [[Windows_Partitions]] for more information (and a potentially better option than setting umask options).

[[Category:Tutorials]]</text>
    <sha1>a733e385a9bde5877ec30fda985673302ca6c137</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Kernel26Compilation</title>
  <ns>0</ns>
  <id>100</id>
  <revision>
    <id>542</id>
    <parentid>122</parentid>
    <timestamp>2011-12-09T10:20:18Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3605" xml:space="preserve">How to build a 2.6.x Kernel on Slackware

Note: Maybe this replaces the 2.6 part of the kernel compile tutorial already here.

==Warning!==
If you work on your kernel and do something wrong you may destroy your system in a way you have to reinstall it. All actions on your own risk! Noone assures that all actions described here are 100% right and work in any case. We are not responsible for damages caused by following this tutorial!

==Prerequisites==

* Get the kernel sources you want from ftp://ftp.de.kernel.org or from a mirror (http://www.kernel.org/mirrors/).
* Make sure you are able toboot your Slackware original kernel after kernel update (You have to install 2.6.13 from "testing" to do this-slack12 uses 2.6.21.5 by default, no need to install it)

image = /boot/vmlinuz-generic-2.6.13&lt;br&gt;
root = /dev/ #Your root partition. Get this from another kernel entry or from original /etc/lilo.conf
label = Backup
read-only

Now run "lilo" once as root
* If you want to play safe you may now reboot and try if the kernel boots without errors.
* Uncompress your kernel sources below /usr/src
* The symlink /usr/src/linux has to point to the directory of the new kernel. For example: /usr/src/linux -&gt; /usr/src/linux-2.6.14.4

==Configure the kernel==

* Change to the kernel directory.
cd /usr/src/linux

* Configure your kernel:
** From scratch, then you may choose from

make config (You get prompted for all possible options)
make menuconfig (You get a nice menu where you may navigate with cursor keys. Needs curses-5.x)
make xconfig (You may configure in X, of course needs working X installation)
make gconfig
make qtconfig

:* From old configuration:
Copy the config file of the old kernel to ./.config. If you want to come from orignal Slackware kernel, then:

cp /boot/config .config

After that "make oldconfig" to configure new features (you may acceppt all questions with "Enter" to use the default values) and use "make menuconfig" (or any other of the above list) to change things if you like.

Important! Be sure to compile the alsa modules (or you won't have sound). You have also to do this if you used "make oldconfig" (for example using "make menuconfig") as the original kernel is compiled without alsa.

==Compile and install kernel==

* The real compiling can start:

make (Now, depending on your computer, you may go drinking some coffee, watch a movie or go on your balcony to smoke one ;-) )

If this finished without errors (we assume this) then your kernel and your kernel modules should be compiled.

* Remove symlinks. If you still run your original slackware kernel, then "vmlinuz" and "System.map" are Symlinks to the kernel files. To get sure that we don't override this files, we delete the symlinks

rm /boot/vmlinuz /boot/System.map

* Install the kernel

Install the kernel modules with:&lt;br&gt;
make modules_install

and the kernel with:&lt;br&gt;
make install

* If all steps have been done successful you may now use your new (self-made) kernel.

==Troubleshooting==

* Help, the kernel doesn't work!

Choose your backup kernel on lilo, check your kernel configuration and recompile.

* Choose your backup kernel sounds easy, but...

Now you know why you should keep a running kernel before you install a new one. Either your system is as usable as you are able to check the kernel configuration or you may boot from your slackware setup CD, mount your root partition to /mnt, chroot /mnt and recompile your kernel from there or install slackware packages of a running kernel.

[http://www.slackforum.de/wiki/Kernel26Kompilieren german version]

[[Category:Tutorials]]</text>
    <sha1>4201446b0d6e1c13738ea756b7691eeb593ad30a</sha1>
  </revision>
  <revision>
    <id>552</id>
    <parentid>542</parentid>
    <timestamp>2011-12-09T10:29:51Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3971" xml:space="preserve">How to build a 2.6.x Kernel on Slackware

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;
Note: Maybe this replaces the 2.6 part of the kernel compile tutorial already here.

==Warning!==
If you work on your kernel and do something wrong you may destroy your system in a way you have to reinstall it. All actions on your own risk! Noone assures that all actions described here are 100% right and work in any case. We are not responsible for damages caused by following this tutorial!

==Prerequisites==

* Get the kernel sources you want from ftp://ftp.de.kernel.org or from a mirror (http://www.kernel.org/mirrors/).
* Make sure you are able toboot your Slackware original kernel after kernel update (You have to install 2.6.13 from "testing" to do this-slack12 uses 2.6.21.5 by default, no need to install it)

image = /boot/vmlinuz-generic-2.6.13&lt;br&gt;
root = /dev/ #Your root partition. Get this from another kernel entry or from original /etc/lilo.conf
label = Backup
read-only

Now run "lilo" once as root
* If you want to play safe you may now reboot and try if the kernel boots without errors.
* Uncompress your kernel sources below /usr/src
* The symlink /usr/src/linux has to point to the directory of the new kernel. For example: /usr/src/linux -&gt; /usr/src/linux-2.6.14.4

==Configure the kernel==

* Change to the kernel directory.
cd /usr/src/linux

* Configure your kernel:
** From scratch, then you may choose from

make config (You get prompted for all possible options)
make menuconfig (You get a nice menu where you may navigate with cursor keys. Needs curses-5.x)
make xconfig (You may configure in X, of course needs working X installation)
make gconfig
make qtconfig

:* From old configuration:
Copy the config file of the old kernel to ./.config. If you want to come from orignal Slackware kernel, then:

cp /boot/config .config

After that "make oldconfig" to configure new features (you may acceppt all questions with "Enter" to use the default values) and use "make menuconfig" (or any other of the above list) to change things if you like.

Important! Be sure to compile the alsa modules (or you won't have sound). You have also to do this if you used "make oldconfig" (for example using "make menuconfig") as the original kernel is compiled without alsa.

==Compile and install kernel==

* The real compiling can start:

make (Now, depending on your computer, you may go drinking some coffee, watch a movie or go on your balcony to smoke one ;-) )

If this finished without errors (we assume this) then your kernel and your kernel modules should be compiled.

* Remove symlinks. If you still run your original slackware kernel, then "vmlinuz" and "System.map" are Symlinks to the kernel files. To get sure that we don't override this files, we delete the symlinks

rm /boot/vmlinuz /boot/System.map

* Install the kernel

Install the kernel modules with:&lt;br&gt;
make modules_install

and the kernel with:&lt;br&gt;
make install

* If all steps have been done successful you may now use your new (self-made) kernel.

==Troubleshooting==

* Help, the kernel doesn't work!

Choose your backup kernel on lilo, check your kernel configuration and recompile.

* Choose your backup kernel sounds easy, but...

Now you know why you should keep a running kernel before you install a new one. Either your system is as usable as you are able to check the kernel configuration or you may boot from your slackware setup CD, mount your root partition to /mnt, chroot /mnt and recompile your kernel from there or install slackware packages of a running kernel.

[http://www.slackforum.de/wiki/Kernel26Kompilieren german version]

[[Category:Tutorials]]</text>
    <sha1>bdaec4956d9d6134d9f24b26749c32f60c0e7aa0</sha1>
  </revision>
  <revision>
    <id>569</id>
    <parentid>552</parentid>
    <timestamp>2011-12-09T14:12:07Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3606" xml:space="preserve">How to build a 2.6.x Kernel on Slackware

Note: Maybe this replaces the 2.6 part of the kernel compile tutorial already here.

==Warning!==
If you work on your kernel and do something wrong you may destroy your system in a way you have to reinstall it. All actions on your own risk! Noone assures that all actions described here are 100% right and work in any case. We are not responsible for damages caused by following this tutorial!

==Prerequisites==

* Get the kernel sources you want from ftp://ftp.de.kernel.org or from a mirror (http://www.kernel.org/mirrors/).
* Make sure you are able to boot your Slackware original kernel after kernel update (You have to install 2.6.13 from "testing" to do this-slack12 uses 2.6.21.5 by default, no need to install it)

image = /boot/vmlinuz-generic-2.6.13&lt;br&gt;
root = /dev/ #Your root partition. Get this from another kernel entry or from original /etc/lilo.conf
label = Backup
read-only

Now run "lilo" once as root
* If you want to play safe you may now reboot and try if the kernel boots without errors.
* Uncompress your kernel sources below /usr/src
* The symlink /usr/src/linux has to point to the directory of the new kernel. For example: /usr/src/linux -&gt; /usr/src/linux-2.6.14.4

==Configure the kernel==

* Change to the kernel directory.
cd /usr/src/linux

* Configure your kernel:
** From scratch, then you may choose from

make config (You get prompted for all possible options)
make menuconfig (You get a nice menu where you may navigate with cursor keys. Needs curses-5.x)
make xconfig (You may configure in X, of course needs working X installation)
make gconfig
make qtconfig

:* From old configuration:
Copy the config file of the old kernel to ./.config. If you want to come from orignal Slackware kernel, then:

cp /boot/config .config

After that "make oldconfig" to configure new features (you may acceppt all questions with "Enter" to use the default values) and use "make menuconfig" (or any other of the above list) to change things if you like.

Important! Be sure to compile the alsa modules (or you won't have sound). You have also to do this if you used "make oldconfig" (for example using "make menuconfig") as the original kernel is compiled without alsa.

==Compile and install kernel==

* The real compiling can start:

make (Now, depending on your computer, you may go drinking some coffee, watch a movie or go on your balcony to smoke one ;-) )

If this finished without errors (we assume this) then your kernel and your kernel modules should be compiled.

* Remove symlinks. If you still run your original slackware kernel, then "vmlinuz" and "System.map" are Symlinks to the kernel files. To get sure that we don't override this files, we delete the symlinks

rm /boot/vmlinuz /boot/System.map

* Install the kernel

Install the kernel modules with:&lt;br&gt;
make modules_install

and the kernel with:&lt;br&gt;
make install

* If all steps have been done successful you may now use your new (self-made) kernel.

==Troubleshooting==

* Help, the kernel doesn't work!

Choose your backup kernel on lilo, check your kernel configuration and recompile.

* Choose your backup kernel sounds easy, but...

Now you know why you should keep a running kernel before you install a new one. Either your system is as usable as you are able to check the kernel configuration or you may boot from your slackware setup CD, mount your root partition to /mnt, chroot /mnt and recompile your kernel from there or install slackware packages of a running kernel.

[http://www.slackforum.de/wiki/Kernel26Kompilieren german version]

[[Category:Tutorials]]</text>
    <sha1>fc9ff4331ec429c4ad75c9cd1fb6a859a3a7abb6</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Writing A SlackBuild Script</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>543</id>
    <parentid>273</parentid>
    <timestamp>2011-12-09T10:24:32Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22173" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt &lt;span class="plainlinks"&gt;[http://buyphentermine.herbalweightlossaid.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;Phen375&lt;/span&gt;] applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the &lt;span class="plainlinks"&gt;[http://www.performer5pills.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;performer 5&lt;/span&gt;] developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move &lt;span class="plainlinks"&gt;[http://weightlossproductreviews.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slimming reviews&lt;/span&gt;] them to their correct location within the package directory &lt;span class="plainlinks"&gt;[http://www.hghadvancedreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;HGH Advanced&lt;/span&gt;] tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include &lt;span class="plainlinks"&gt;[http://www.clearskinmaxreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;clear skin max&lt;/span&gt;] instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit &lt;span class="plainlinks"&gt;[http://www.hoodiapill.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;unique hoodia&lt;/span&gt;] easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the &lt;span class="plainlinks"&gt;[http://weightlossproductreviews.info/?page_id=268 &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slim weight patch&lt;/span&gt;] command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one &lt;span class="plainlinks"&gt;[http://www.teethwhitenerguide.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;teeth whitener reviews&lt;/span&gt;] being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the &lt;span class="plainlinks"&gt;[http://www.phen375reviewed.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;phen375 fat burner&lt;/span&gt;] package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because &lt;span class="plainlinks"&gt;[http://www.herbalweightlossaid.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slimming pills&lt;/span&gt;] developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure &lt;span class="plainlinks"&gt;[http://www.capsiplexreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;capsiplex&lt;/span&gt;] script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the &lt;span class="plainlinks"&gt;[http://proactolpluspills.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;proactol plus&lt;/span&gt;] scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/</text>
    <sha1>0d6ebc1f06a3b35aa77cf613b0fb096651ff3e07</sha1>
  </revision>
  <revision>
    <id>553</id>
    <parentid>543</parentid>
    <timestamp>2011-12-09T10:31:03Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22172" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to instll the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt &lt;span class="plainlinks"&gt;[http://buyphentermine.herbalweightlossaid.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;Phen375&lt;/span&gt;] applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the &lt;span class="plainlinks"&gt;[http://www.performer5pills.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;performer 5&lt;/span&gt;] developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move &lt;span class="plainlinks"&gt;[http://weightlossproductreviews.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slimming reviews&lt;/span&gt;] them to their correct location within the package directory &lt;span class="plainlinks"&gt;[http://www.hghadvancedreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;HGH Advanced&lt;/span&gt;] tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include &lt;span class="plainlinks"&gt;[http://www.clearskinmaxreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;clear skin max&lt;/span&gt;] instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit &lt;span class="plainlinks"&gt;[http://www.hoodiapill.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;unique hoodia&lt;/span&gt;] easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the &lt;span class="plainlinks"&gt;[http://weightlossproductreviews.info/?page_id=268 &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slim weight patch&lt;/span&gt;] command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one &lt;span class="plainlinks"&gt;[http://www.teethwhitenerguide.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;teeth whitener reviews&lt;/span&gt;] being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the &lt;span class="plainlinks"&gt;[http://www.phen375reviewed.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;phen375 fat burner&lt;/span&gt;] package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because &lt;span class="plainlinks"&gt;[http://www.herbalweightlossaid.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slimming pills&lt;/span&gt;] developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure &lt;span class="plainlinks"&gt;[http://www.capsiplexreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;capsiplex&lt;/span&gt;] script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the &lt;span class="plainlinks"&gt;[http://proactolpluspills.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;proactol plus&lt;/span&gt;] scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/</text>
    <sha1>12c4fa324bfba7c9d5982a42183053ab55d44edc</sha1>
  </revision>
  <revision>
    <id>556</id>
    <parentid>553</parentid>
    <timestamp>2011-12-09T10:32:00Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22171" xml:space="preserve">[[Category:Tutorials]]

= Introduction =
 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to instll the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt &lt;span class="plainlinks"&gt;[http://buyphentermine.herbalweightlossaid.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;Phen375&lt;/span&gt;] applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the &lt;span class="plainlinks"&gt;[http://www.performer5pills.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;performer 5&lt;/span&gt;] developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move &lt;span class="plainlinks"&gt;[http://weightlossproductreviews.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slimming reviews&lt;/span&gt;] them to their correct location within the package directory &lt;span class="plainlinks"&gt;[http://www.hghadvancedreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;HGH Advanced&lt;/span&gt;] tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include &lt;span class="plainlinks"&gt;[http://www.clearskinmaxreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;clear skin max&lt;/span&gt;] instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit &lt;span class="plainlinks"&gt;[http://www.hoodiapill.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;unique hoodia&lt;/span&gt;] easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the &lt;span class="plainlinks"&gt;[http://weightlossproductreviews.info/?page_id=268 &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slim weight patch&lt;/span&gt;] command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one &lt;span class="plainlinks"&gt;[http://www.teethwhitenerguide.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;teeth whitener reviews&lt;/span&gt;] being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the &lt;span class="plainlinks"&gt;[http://www.phen375reviewed.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;phen375 fat burner&lt;/span&gt;] package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because &lt;span class="plainlinks"&gt;[http://www.herbalweightlossaid.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;slimming pills&lt;/span&gt;] developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure &lt;span class="plainlinks"&gt;[http://www.capsiplexreview.info/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;capsiplex&lt;/span&gt;] script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the &lt;span class="plainlinks"&gt;[http://proactolpluspills.com/ &lt;span style="color:#000000;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;"&gt;proactol plus&lt;/span&gt;] scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/</text>
    <sha1>fab0378eea24dc2ea55402294ce0d56e441b1fa3</sha1>
  </revision>
  <revision>
    <id>573</id>
    <parentid>556</parentid>
    <timestamp>2011-12-09T14:13:27Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:SiegeX|SiegeX]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19605" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/
;* http://www2.linuxpackages.net/packages/SlackBuilds/
;* http://www.selkfoster.com.ar/downloads/slackbuilds/
;* http://slack.sarava.org/slackbuilds/</text>
    <sha1>292b77163684b3b1836f33a1053ee77516b47303</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Windows Partitions</title>
  <ns>0</ns>
  <id>32</id>
  <revision>
    <id>544</id>
    <parentid>49</parentid>
    <timestamp>2011-12-09T10:25:36Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2710" xml:space="preserve">One of the frequent questions on ##slackware is something along the lines of "How can I allow normal users to access my Windows partition?"  There are *at least* two different ways of doing this.

For a FAT partition, you *could* add umask=0000 to /etc/fstab's options, but I personally don't recommend doing that.  It's *your* computer, so you make the call, but I would do something along these lines:

1. If you want *every* user to be able to read and write to the partition, then you can add dmask=0000 and fmask=0111 to /etc/fstab's options and be done with it - problem solved.

 /dev/hda1     /mnt/win98     vfat     rw,dmask=0000,fmask=0111     0   0

The reason for dmask/fmask as opposed to umask is quite obvious (though I hadn't thought about it until elohim on ##slackware pointed it out):  The FAT and NTFS file systems don't "understand" the executable (-x) bit, so it's automatically present on every file in such a filesystem.  There's no need for normal files to be executable (and it can indeed be a security risk), so we use fmask to turn off those permissions.

2. If you only want some users to be able to read and write to the partition, but you want *every* user to have read access, then you'll want something along these lines.  First, create a special group called "windows" (change the name if you wish) by adding it to /etc/group using your favorite editor and add to this group the users you want to have write access.  

 nogroup:x:99:
 users:x:100:
 console:x:101:
 windows:x:102:user1,user2,user3

Next, edit your /etc/fstab line for that partition and specify that it be mounted with group ownership of the "windows" group, and that write access be removed from others.

 /dev/hda1     /mnt/win98     vfat     rw,gid=102,dmask=0002,fmask=0113     0   0

An NTFS partition will be mounted read-only, so you won't have write access for anyone, but the central idea is the same.

If you don't want everyone else to even have read access to the partition, you can easily do that with the above fstab line modified a bit:

 /dev/hda1     /mnt/winXP     ntfs     ro,gid=102,dmask=0227,fmask=0337     0   0

If you prefer write access to the partition, then you can use ntfs-3g instead and something like this:
All users can read the partition; only members of gid 102 can write:
 /dev/hda1     /mnt/win98     ntfs-3g     rw,gid=102,dmask=0002,fmask=0113     0   0
Users of gid can read and write; nobody else can do anything:
 /dev/hda1     /mnt/winXP     ntfs-3g     rw,gid=102,dmask=0007,fmask=0117     0   0

For more information, see the [[Permissions and Umasks]] and [[Fstab]] pages.

--rworkman (thanks to Erik for the pointers about dmask and fmask)

[[Category:Tutorials]]</text>
    <sha1>58ec1677032f776070c038326b982fbb4f268dcd</sha1>
  </revision>
  <revision>
    <id>551</id>
    <parentid>544</parentid>
    <timestamp>2011-12-09T10:29:35Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3077" xml:space="preserve">One of the frequent questions on ##slackware is something along the lines of "How can I allow normal users to access my Windows partition?"  There are *at least* two different ways of doing this.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

For a FAT partition, you *could* add umask=0000 to /etc/fstab's options, but I personally don't recommend doing that.  It's *your* computer, so you make the call, but I would do something along these lines:

1. If you want *every* user to be able to read and write to the partition, then you can add dmask=0000 and fmask=0111 to /etc/fstab's options and be done with it - problem solved.

 /dev/hda1     /mnt/win98     vfat     rw,dmask=0000,fmask=0111     0   0

The reason for dmask/fmask as opposed to umask is quite obvious (though I hadn't thought about it until elohim on ##slackware pointed it out):  The FAT and NTFS file systems don't "understand" the executable (-x) bit, so it's automatically present on every file in such a filesystem.  There's no need for normal files to be executable (and it can indeed be a security risk), so we use fmask to turn off those permissions.

2. If you only want some users to be able to read and write to the partition, but you want *every* user to have read access, then you'll want something along these lines.  First, create a special group called "windows" (change the name if you wish) by adding it to /etc/group using your favorite editor and add to this group the users you want to have write access.  

 nogroup:x:99:
 users:x:100:
 console:x:101:
 windows:x:102:user1,user2,user3

Next, edit your /etc/fstab line for that partition and specify that it be mounted with group ownership of the "windows" group, and that write access be removed from others.

 /dev/hda1     /mnt/win98     vfat     rw,gid=102,dmask=0002,fmask=0113     0   0

An NTFS partition will be mounted read-only, so you won't have write access for anyone, but the central idea is the same.

If you don't want everyone else to even have read access to the partition, you can easily do that with the above fstab line modified a bit:

 /dev/hda1     /mnt/winXP     ntfs     ro,gid=102,dmask=0227,fmask=0337     0   0

If you prefer write access to the partition, then you can use ntfs-3g instead and something like this:
All users can read the partition; only members of gid 102 can write:
 /dev/hda1     /mnt/win98     ntfs-3g     rw,gid=102,dmask=0002,fmask=0113     0   0
Users of gid can read and write; nobody else can do anything:
 /dev/hda1     /mnt/winXP     ntfs-3g     rw,gid=102,dmask=0007,fmask=0117     0   0

For more information, see the [[Permissions and Umasks]] and [[Fstab]] pages.

--rworkman (thanks to Erik for the pointers about dmask and fmask)

[[Category:Tutorials]]</text>
    <sha1>d396b693150c808b09a4c8aa13bf654bdc3987a4</sha1>
  </revision>
  <revision>
    <id>565</id>
    <parentid>551</parentid>
    <timestamp>2011-12-09T14:06:35Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Rworkman|Rworkman]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2709" xml:space="preserve">One of the frequent questions on ##slackware is something along the lines of "How can I allow normal users to access my Windows partition?"  There are *at least* two different ways of doing this.

For a FAT partition, you *could* add umask=0000 to /etc/fstab's options, but I personally don't recommend doing that.  It's *your* computer, so you make the call, but I would do something along these lines:
1. If you want *every* user to be able to read and write to the partition, then you can add dmask=0000 and fmask=0111 to /etc/fstab's options and be done with it - problem solved.

 /dev/hda1     /mnt/win98     vfat     rw,dmask=0000,fmask=0111     0   0

The reason for dmask/fmask as opposed to umask is quite obvious (though I hadn't thought about it until elohim on ##slackware pointed it out):  The FAT and NTFS file systems don't "understand" the executable (-x) bit, so it's automatically present on every file in such a filesystem.  There's no need for normal files to be executable (and it can indeed be a security risk), so we use fmask to turn off those permissions.

2. If you only want some users to be able to read and write to the partition, but you want *every* user to have read access, then you'll want something along these lines.  First, create a special group called "windows" (change the name if you wish) by adding it to /etc/group using your favorite editor and add to this group the users you want to have write access.  

 nogroup:x:99:
 users:x:100:
 console:x:101:
 windows:x:102:user1,user2,user3

Next, edit your /etc/fstab line for that partition and specify that it be mounted with group ownership of the "windows" group, and that write access be removed from others.

 /dev/hda1     /mnt/win98     vfat     rw,gid=102,dmask=0002,fmask=0113     0   0

An NTFS partition will be mounted read-only, so you won't have write access for anyone, but the central idea is the same.

If you don't want everyone else to even have read access to the partition, you can easily do that with the above fstab line modified a bit:

 /dev/hda1     /mnt/winXP     ntfs     ro,gid=102,dmask=0227,fmask=0337     0   0

If you prefer write access to the partition, then you can use ntfs-3g instead and something like this:
All users can read the partition; only members of gid 102 can write:
 /dev/hda1     /mnt/win98     ntfs-3g     rw,gid=102,dmask=0002,fmask=0113     0   0
Users of gid can read and write; nobody else can do anything:
 /dev/hda1     /mnt/winXP     ntfs-3g     rw,gid=102,dmask=0007,fmask=0117     0   0

For more information, see the [[Permissions and Umasks]] and [[Fstab]] pages.

--rworkman (thanks to Erik for the pointers about dmask and fmask)

[[Category:Tutorials]]</text>
    <sha1>6e47018ae54c8b5bd08edc300568e012b97465bc</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>SlackBuild Scripts</title>
  <ns>0</ns>
  <id>15</id>
  <revision>
    <id>545</id>
    <parentid>21</parentid>
    <timestamp>2011-12-09T10:26:18Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2967" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.


== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>649f5b756f2e317ac7d3fae80af90798f469263d</sha1>
  </revision>
  <revision>
    <id>550</id>
    <parentid>545</parentid>
    <timestamp>2011-12-09T10:29:16Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3334" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.


== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>afbf10b93e33455d1f1aca5403f5aef68a81422a</sha1>
  </revision>
  <revision>
    <id>572</id>
    <parentid>550</parentid>
    <timestamp>2011-12-09T14:12:51Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Dugan|Dugan]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2966" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/
;* http://www.slackbuilds.net/slackbuilds/
;* http://slackbuild.strangeworlds.co.uk/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5790ce4393af0df4fbef5d93d3a01eb0177d0d87</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Building A Package</title>
  <ns>0</ns>
  <id>23</id>
  <revision>
    <id>546</id>
    <parentid>484</parentid>
    <timestamp>2011-12-09T10:26:22Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2972" xml:space="preserve">[[Category:Tutorials]]

= Intro =

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

== The good and decent way ==

Configure and compile the source as you usually do:
 ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
 make

Make a temporary destination directory available:
 mkdir /tmp/build

Install into the temporary directory:
 make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
 strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in &lt;tt&gt;/usr/man&lt;/tt&gt; is gzipped before you make the package:
 gzip -9 /tmp/build/usr/man/man?/*.?

Create the &lt;tt&gt;install&lt;/tt&gt; directory, this is where the description and install script will be stored:
 cd /tmp/build
 mkdir install
 cd install

Using a text editor (or a [http://slack-desc.sourceforge.net/ tool]]), create a file called [[slack-desc]] and fill it with the following contents:

    |-----handy-ruler------------------------------------------------------|
 app: Application Name
 (Short/Brief description)
 app:
 app: Enter a description of the package you are building.
 app: All 11 "app:" lines must be present
 app: "app" needs to be your application name.
 app: The handy-ruler is there to help you, these lines should not exceed
 app: 79 characters.
 app:
 app:
 app:
 app:

Create the actual package:
 cd /tmp/build
 makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc.  Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say &lt;tt&gt;yes&lt;/tt&gt;&lt;br&gt;
When prompted to reset permissions, say &lt;tt&gt;no&lt;/tt&gt;

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
 cd ..
 installpkg app-version-arch-tag.tgz


== The "i don't have time" way ==

Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this: 
 ./configure --prefix=/usr
 make install DESTDIR=$(pwd)/PACKAGE
 cd $(pwd)/PACKAGE
 makepkg -l y -c n ../app-version-arch-tag.tgz
 installpkg ../app-version-arch-tag.tgz

Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.

----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----</text>
    <sha1>39903d84b86cbd2e2bbc01386ae95dfc262007bf</sha1>
  </revision>
  <revision>
    <id>549</id>
    <parentid>546</parentid>
    <timestamp>2011-12-09T10:29:03Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3356" xml:space="preserve">[[Category:Tutorials]]

= Intro =

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

== The good and decent way ==

Configure and compile the source as you usually do:
 ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
 make

Make a temporary destination directory available:
 mkdir /tmp/build

Install into the temporary directory:
 make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
 strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in &lt;tt&gt;/usr/man&lt;/tt&gt; is gzipped before you make the package:
 gzip -9 /tmp/build/usr/man/man?/*.?

Create the &lt;tt&gt;install&lt;/tt&gt; directory, this is where the description and install script will be stored:
 cd /tmp/build
 mkdir install
 cd install

Using a text editor (or a [http://slack-desc.sourceforge.net/ tool]]), create a file called [[slack-desc]] and fill it with the following contents:

    |-----handy-ruler------------------------------------------------------|
 app: Application Name
 (Short/Brief description)
 app:
 app: Enter a description of the package you are building.
 app: All 11 "app:" lines must be present
 app: "app" needs to be your application name.
 app: The handy-ruler is there to help you, these lines should not exceed
 app: 79 characters.
 app:
 app:
 app:
 app:

Create the actual package:
 cd /tmp/build
 makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc.  Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say &lt;tt&gt;yes&lt;/tt&gt;&lt;br&gt;
When prompted to reset permissions, say &lt;tt&gt;no&lt;/tt&gt;

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
 cd ..
 installpkg app-version-arch-tag.tgz


 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's 
also customary to
 # leave one space after the ':'.
== The "i don't have time" way ==

Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this: 
 ./configure --prefix=/usr
 make install DESTDIR=$(pwd)/PACKAGE
 cd $(pwd)/PACKAGE
 makepkg -l y -c n ../app-version-arch-tag.tgz
 installpkg ../app-version-arch-tag.tgz

Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.

----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----</text>
    <sha1>cbe9192118233c27ab7ed67a4b168f68f2afc068</sha1>
  </revision>
  <revision>
    <id>571</id>
    <parentid>549</parentid>
    <timestamp>2011-12-09T14:12:49Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Vporpo|Vporpo]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2971" xml:space="preserve">[[Category:Tutorials]]

= Intro =

This is a rough outline for building Slackware packages. Some steps may not be neccessary, some steps might be missing. Use the discussion page for side-notes such as using slacktrack (when DESTDIR fails) and other utilities like checkinstall.

== The good and decent way ==

Configure and compile the source as you usually do:
 ./configure --prefix=/usr --localstatedir=/var --sysconfdir=/etc
 make

Make a temporary destination directory available:
 mkdir /tmp/build

Install into the temporary directory:
 make install DESTDIR=/tmp/build

Now strip libs/bins within the temporary directory:
 strip -s /tmp/build/usr/lib/* /tmp/build/usr/bin/*

You also want to make sure that anything in &lt;tt&gt;/usr/man&lt;/tt&gt; is gzipped before you make the package:
 gzip -9 /tmp/build/usr/man/man?/*.?

Create the &lt;tt&gt;install&lt;/tt&gt; directory, this is where the description and install script will be stored:
 cd /tmp/build
 mkdir install
 cd install

Using a text editor (or a [http://slack-desc.sourceforge.net/ tool]]), create a file called [[slack-desc]] and fill it with the following contents:

    |-----handy-ruler------------------------------------------------------|
 app: Application Name (Short/Brief description)
 app:
 app: Enter a description of the package you are building.
 app: All 11 "app:" lines must be present
 app: "app" needs to be your application name.
 app: The handy-ruler is there to help you, these lines should not exceed
 app: 79 characters.
 app:
 app:
 app:
 app:

Create the actual package:
 cd /tmp/build
 makepkg ../app-version-arch-tag.tgz

''(The dashes should appear as above, so if the version has a subversion like say "1.0 RC2" make sure you use 1.0_RC2 not 1.0-RC2. The arch should be something like "i486" for example. The tag should consist of the build number and your initals, e.g. 1zb for Zaphod Beeblebrox's first build, 2zb for his second build, etc.  Official slackware packages have only numbers as tags.)''

When prompted to recreate symbolic links, say &lt;tt&gt;yes&lt;/tt&gt;&lt;br&gt;
When prompted to reset permissions, say &lt;tt&gt;no&lt;/tt&gt;

''Note: Using '''makepkg -l y -c n''' will give you the same behaviour as answering yes to the symlinks question, and no to the permissions question.''

If all went well, you can now install the package.
 cd ..
 installpkg app-version-arch-tag.tgz


== The "i don't have time" way ==

Fortunately, Slackware are pretty flexible too. If you don't mind much about what is the source (beware!) that you're compiling you can burn some stages and do something like this: 
 ./configure --prefix=/usr
 make install DESTDIR=$(pwd)/PACKAGE
 cd $(pwd)/PACKAGE
 makepkg -l y -c n ../app-version-arch-tag.tgz
 installpkg ../app-version-arch-tag.tgz

Of course, you will have a package without description, (probably) uncompressed man pages and unstripped binaries.

----
For more information, also see the pages on [[SlackBuild_Scripts]] and [[Different_Approach_To_Buildscripts]].
----</text>
    <sha1>e243a2544503cedcd63bcf8a9d895edfb2280bb1</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Slack-desc</title>
  <ns>0</ns>
  <id>17</id>
  <revision>
    <id>547</id>
    <parentid>483</parentid>
    <timestamp>2011-12-09T10:26:34Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2135" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's 
also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: appname (Short description of the application)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname:
 appname: It's a good idea to include a link to the application's homepage too.
 appname:

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 &amp; 11 should not have a space after the :

=Tools=
1. There is a command-line tool that automates the creation of slack-desc files and helps you generate legal slack-desc files with minimal effort:
http://slack-desc.sourceforge.net/

2. A web-based tool is also available at: http://www.linuxpackages.net/slackcreator.php
=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>bb7ba0ff367e2392a8f47f503815f92f504ccee9</sha1>
  </revision>
  <revision>
    <id>548</id>
    <parentid>547</parentid>
    <timestamp>2011-12-09T10:28:05Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2519" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's 
also customary to
 # leave one space after the ':'.
 
 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's 
also customary to
 # leave one space after the ':'.
        |-----handy-ruler------------------------------------------------------|
 appname: appname (Short description of the application)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname:
 appname: It's a good idea to include a link to the application's homepage too.
 appname:

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 &amp; 11 should not have a space after the :

=Tools=
1. There is a command-line tool that automates the creation of slack-desc files and helps you generate legal slack-desc files with minimal effort:
http://slack-desc.sourceforge.net/

2. A web-based tool is also available at: http://www.linuxpackages.net/slackcreator.php
=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>3a997d65392725949e816851bbdc78469fa7819c</sha1>
  </revision>
  <revision>
    <id>570</id>
    <parentid>548</parentid>
    <timestamp>2011-12-09T14:12:47Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Vporpo|Vporpo]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2134" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: appname (Short description of the application)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname:
 appname: It's a good idea to include a link to the application's homepage too.
 appname:

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 &amp; 11 should not have a space after the :

=Tools=
1. There is a command-line tool that automates the creation of slack-desc files and helps you generate legal slack-desc files with minimal effort:
http://slack-desc.sourceforge.net/

2. A web-based tool is also available at: http://www.linuxpackages.net/slackcreator.php
=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>242781af77d76a443f16591f75a566dad0467aa2</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Packages</title>
  <ns>0</ns>
  <id>18</id>
  <revision>
    <id>557</id>
    <parentid>333</parentid>
    <timestamp>2011-12-09T10:33:23Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1986" xml:space="preserve">Slackware's package management system utilizes .tgz/.txz tarballs as its standard package format. These tarballs are  tar.gz/tar.xz archives which contain Slackware built binaries, support files, a description file and installation script. Although they can be unzipped and untarred like a normal archive, they are (usually) binary-only packages intended to be installed through Slackware's provided package management tools.


Information about a package is stored in two ways, in the filename of the package and a description file inside that package.

==Package Tools==
See the respective manual pages for more information on each of the following commands.

&lt;code&gt;pkgtool&lt;/code&gt;

&lt;code&gt;installpkg&lt;/code&gt;

&lt;code&gt;removepkg&lt;/code&gt;

&lt;code&gt;explodepkg&lt;/code&gt;

&lt;code&gt;makepkg&lt;/code&gt;

&lt;code&gt;upgradepkg&lt;/code&gt;

==Slackware Package Layout==
A typical Slackware package is laid out as such:
 ./
 ./install/doinst.sh
 ./install/slack-desc
 [./usr/bin]
 [./usr/lib]
 [...]

The install directory as well as the files within it will be deleted after the installation of the package to the root install directory (usually '/'). The install directory is not necessarily required for the most basic packages but allows additional functionality: [[slack-desc]] contains the package description, and [[doinst.sh]] contains post-installation instructions such as creating symbolic links.

Every other file within the package is simply untarred (extracted) to the root directory. Most of these files are in standard locations. 

There are other special files within packages: 

'''usr/doc/&lt;appname&gt;&lt;version&gt;'''
All documentation included with the package (such as README, INSTALL, ChangeLog, docs/, etcetera) should be placed in this directory. Some of the files in this directory should be manually copied from the source archive, since Makefiles usually don't copy these documentation files to the package build tree.

==Making Slackware Packages==
See [[Building A Package]]

[[Category: Information]]</text>
    <sha1>c81c6372de1c2ed4fb1f5fc1bdaa0e62a8c07eae</sha1>
  </revision>
  <revision>
    <id>577</id>
    <parentid>557</parentid>
    <timestamp>2011-12-09T14:13:34Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Grissiom|Grissiom]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1985" xml:space="preserve">Slackware's package management system utilizes .tgz/.txz tarballs as its standard package format. These tarballs are  tar.gz/tar.xz archives which contain Slackware built binaries, support files, a description file and installation script. Although they can be unzipped and untarred like a normal archive, they are (usually) binary-only packages intended to be installed through Slackware's provided package management tools.

Information about a package is stored in two ways, in the filename of the package and a description file inside that package.

==Package Tools==
See the respective manual pages for more information on each of the following commands.

&lt;code&gt;pkgtool&lt;/code&gt;

&lt;code&gt;installpkg&lt;/code&gt;

&lt;code&gt;removepkg&lt;/code&gt;

&lt;code&gt;explodepkg&lt;/code&gt;

&lt;code&gt;makepkg&lt;/code&gt;

&lt;code&gt;upgradepkg&lt;/code&gt;

==Slackware Package Layout==
A typical Slackware package is laid out as such:
 ./
 ./install/doinst.sh
 ./install/slack-desc
 [./usr/bin]
 [./usr/lib]
 [...]

The install directory as well as the files within it will be deleted after the installation of the package to the root install directory (usually '/'). The install directory is not necessarily required for the most basic packages but allows additional functionality: [[slack-desc]] contains the package description, and [[doinst.sh]] contains post-installation instructions such as creating symbolic links.

Every other file within the package is simply untarred (extracted) to the root directory. Most of these files are in standard locations. 

There are other special files within packages: 

'''usr/doc/&lt;appname&gt;&lt;version&gt;'''
All documentation included with the package (such as README, INSTALL, ChangeLog, docs/, etcetera) should be placed in this directory. Some of the files in this directory should be manually copied from the source archive, since Makefiles usually don't copy these documentation files to the package build tree.

==Making Slackware Packages==
See [[Building A Package]]

[[Category: Information]]</text>
    <sha1>29ecbc47c3624fd37e27efb0674fab3ddecae81e</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Mount Count</title>
  <ns>0</ns>
  <id>115</id>
  <revision>
    <id>558</id>
    <parentid>138</parentid>
    <timestamp>2011-12-09T10:33:27Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="336" xml:space="preserve">[[Category:Information]]
A count of how many times a filesystem has been mounted.  Used to determine whether a [[Forced Fuck]] should be executed.

After a successful fsck (filesystem check), the mount count is reset to zero.  When the mount count reaches (or exceeds) the [[Maximum Mount Count]], a Forced Fsck is executed during boot.</text>
    <sha1>712badad7fc3e4ac6765d2f611ec6324fd366803</sha1>
  </revision>
  <revision>
    <id>574</id>
    <parentid>558</parentid>
    <timestamp>2011-12-09T14:13:29Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="336" xml:space="preserve">[[Category:Information]]
A count of how many times a filesystem has been mounted.  Used to determine whether a [[Forced Fsck]] should be executed.

After a successful fsck (filesystem check), the mount count is reset to zero.  When the mount count reaches (or exceeds) the [[Maximum Mount Count]], a Forced Fsck is executed during boot.</text>
    <sha1>c1016fca1d75994c5e6b497417bdb52c0f774c4a</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Log Correlation</title>
  <ns>0</ns>
  <id>106</id>
  <revision>
    <id>559</id>
    <parentid>129</parentid>
    <timestamp>2011-12-09T10:34:43Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9340" xml:space="preserve">[[Category:Tutorials]]

'''Log Correlation'''
I thought I'd talk about the importance of log correlation. For instance, you've found that someone is continually pinging your server. You want to see if your box is responding to the pings. Usually, you'll know right off, since most people know if their firewall was configured to block pings...I'm just using pings as a quick example, though. Log correlation usually consists of checking, for instance, web server logs against firewall logs, or Snort logs against firewall and web server logs. This helps you understand what suspicious activity is actually doing and if your server/workstation responded (and how it responded, if it did).

I run Snort on a server, along with a web server, which is firewalled with IPTables. I have Snort report what it sees to a MySQL database, although it does record captures to a PCAP file locally. I also run Modsecurity, an application firewall that is designed to sniff and possibly block traffic going to/from web servers, mainly Apache. So, I've a ton of logs that I can correlate: Snort, Apache, IPTables, and Modsecurity logs.

We'll pick something easy. In fact, I'll fabricate some logs by generating some false alerts. I'll use 'wget', to visit my website. Keep in mind that what you see below gives you the advantage...you know what you're doing and looking for when we soon check the logs. This won't be the case when some stranger or worm hits your firewall or web server (or any other application server).

    -bash-2.05b$ wget wigglit.ath.cx/root.exe
    --23:24:05-- http://wigglit.ath.cx/root.exe
    =&gt; `root.exe'
    Resolving wigglit.ath.cx... 66.160.141.30
    Connecting to wigglit.ath.cx|66.160.141.30|:80... connected.
    HTTP request sent, awaiting response... 404 Not Found
    23:24:06 ERROR 404: Not Found.

    -bash-2.05b$ 

I used root.exe because there is an old vulnerability was was used to exploit flaws in IIS...the CodeRed worm of old. Now, let's check the web server's logs. I've tail'd my logs:

    root@starchild:/var/log/apache# tail -f -n 100 access_log
    12.123.12.123 - - [15/Sep/2007:23:34:35 -0400] "GET /root.exe HTTP/1.0" 404 202
    12.123.12.123 - - [15/Sep/2007:23:34:35 -0400] "GET /root.exe HTTP/1.0" 404 202 "-" "Wget/1.10.2"

You see that the communcation was accepted.  A 404 code, which means 'page not found', was generated. This is usually a good indication, as the server didn't respond favorably to the attack.

Now, let us check the firewall logs. We already know that the firewall allowed the traffic, since the web server responded with a 404...if the traffic was being blocked, there would be no record of the attack in the logs, because the firewall would have intercepted the traffic before it reached the web server. We're checking the firewall logs just to be sure this guy hasn't done anything else that the web server didn't see:

    Sep 12 17:28:34 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=34557 DF PROTO=TCP SPT=46656 DPT=10083 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:44 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=18168 DF PROTO=TCP SPT=40091 DPT=449 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:44 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=27053 DF PROTO=TCP SPT=36295 DPT=5060 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:54 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=29291 DF PROTO=TCP SPT=47590 DPT=342 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:54 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=11788 DF PROTO=TCP SPT=43604 DPT=1519 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:04 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=17600 DF PROTO=TCP SPT=32783 DPT=577 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:04 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=51338 DF PROTO=TCP SPT=47879 DPT=18187 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:14 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=58520 DF PROTO=TCP SPT=41983 DPT=517 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:14 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=20255 DF PROTO=TCP SPT=53355 DPT=1986 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:24 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=28213 DF PROTO=TCP SPT=38543 DPT=978 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:24 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=10244 DF PROTO=TCP SPT=45624 DPT=11371 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:37 starchild kernel: ICMP-request: IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=28 TOS=0x00 PREC=0x00 TTL=42 ID=53002 PROTO=ICMP TYPE=8 CODE=0 ID=10683 SEQ=16615
    Sep 15 23:21:08 starchild kernel: ICMP-request: IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=84 TOS=0x00 PREC=0x00 TTL=55 ID=40988 PROTO=ICMP TYPE=8 CODE=0 ID=614 SEQ=0

Quite a bit of stuff, huh? This looks to be a port scan! This is something that we didn't see in the Apache logs! Good thing we checked! Looks like this IP needs to be blocked with IPTables (which we won't do in this exercise).

Sadly, nothing shows in the Modsecurity logs, but we've enough information already. What about Snort? Because I've PCAP files, the search becomes a bit more involved. I'll spare the intimate details, but this is what we see:

    [**] [1:1256:9] WEB-IIS CodeRed v2 root.exe access [**]
    [Classification: Web Application Attack] [Priority: 1]
    09/15-23:34:35.708546 0:C:DB:F5:90:0 -&gt; FE:FD:40:3E:E7:DC type:0x800 len:0xB0
    12.123.12.123:52753 -&gt; 66.160.141.30:80 TCP TTL:56 TOS:0x0 ID:51589 IpLen:20 DgmLen:162 DF
    ***AP*** Seq: 0xAF32BB68 Ack: 0x3F319F7A Win: 0xFFFF TcpLen: 32
    TCP Options (3) =&gt; NOP NOP TS: 288652007 1521931210
    [Xref =&gt; http://www.cert.org/advisories/CA-2001-19.html]

    23:34:35.708546 00:0c:db:f5:90:00 &gt; fe:fd:40:3e:e7:dc, ethertype IPv4 (0x0800), length 176: IP (tos 0x0, ttl 56, id 51589, offset 0, flags [DF], length: 162) 12.123.12.123.52753 &gt; 66.160.141.30.80: P [tcp sum ok] 2939337576:2939337686(110) ack 1060216698 win 65535
    0x0000: fefd 403e e7dc 000c dbf5 9000 0800 4500 ..@&gt;..........E.
    0x0010: 00a2 c985 4000 3806 56c0 47b2 0aa0 42a0 ....@.8.V.G...B.
    0x0020: 8d1e ce11 0050 af32 bb68 3f31 9f7a 8018 .....P.2.h?1.z..
    0x0030: ffff e9c5 0000 0101 080a 1134 7ae7 5ab6 ...........4z.Z.
    0x0040: d3ca 4745 5420 2f72 6f6f 742e 6578 6520 ..GET./root.exe.
    0x0050: 4854 5450 2f31 2e30 0d0a 5573 6572 2d41 HTTP/1.0..User-A
    0x0060: 6765 6e74 3a20 5767 6574 2f31 2e31 302e gent:.Wget/1.10.
    0x0070: 320d 0a41 6363 6570 743a 202a 2f2a 0d0a 2..Accept:.*/*..
    0x0080: 486f 7374 3a20 7769 6767 6c69 742e 6174 Host:.wigglit.at
    0x0090: 682e 6378 0d0a 436f 6e6e 6563 7469 6f6e h.cx..Connection
    0x00a0: 3a20 4b65 6570 2d41 6c69 7665 0d0a 0d0a :.Keep-Alive....

The first is the Snort alert file...this is a fast alert, with minimal detail (no packet capture). The second section is the full alert, including packet capture. It is also garbled (due to the hex code and the fact that this blog has issues with formatting) Note that my logs show no response. Apparently, my Snort install doesn't have a 404 signature. Again, the fact that we can correlate helps me when my Snort install lacks the data that I may have needed. I was able to look at the Apache logs to see the 404 when my Snort logs didn't show the return traffic.

Well, this concludes our chat about correlating existing logs. Note that any log files can be correlated. Correlation can also assist in tracking down network issues or issues with, for instance, a faulty Snort install (ahem). Although this discussion focused more on security, hopefully this helps someone understand their network or software architecture also.

This page is also linked at [http://slackfiles.blogspot.com/2007/09/log-correlation.html my blog]

--[[User:Unixfool|Ron]] 00:35, 16 September 2007 (EDT)</text>
    <sha1>572db83e541280ceecf072b7e376f82d0cca81ac</sha1>
  </revision>
  <revision>
    <id>576</id>
    <parentid>559</parentid>
    <timestamp>2011-12-09T14:13:32Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9341" xml:space="preserve">[[Category:Tutorials]]

'''Log Correlation'''

I thought I'd talk about the importance of log correlation. For instance, you've found that someone is continually pinging your server. You want to see if your box is responding to the pings. Usually, you'll know right off, since most people know if their firewall was configured to block pings...I'm just using pings as a quick example, though. Log correlation usually consists of checking, for instance, web server logs against firewall logs, or Snort logs against firewall and web server logs. This helps you understand what suspicious activity is actually doing and if your server/workstation responded (and how it responded, if it did).

I run Snort on a server, along with a web server, which is firewalled with IPTables. I have Snort report what it sees to a MySQL database, although it does record captures to a PCAP file locally. I also run Modsecurity, an application firewall that is designed to sniff and possibly block traffic going to/from web servers, mainly Apache. So, I've a ton of logs that I can correlate: Snort, Apache, IPTables, and Modsecurity logs.

We'll pick something easy. In fact, I'll fabricate some logs by generating some false alerts. I'll use 'wget', to visit my website. Keep in mind that what you see below gives you the advantage...you know what you're doing and looking for when we soon check the logs. This won't be the case when some stranger or worm hits your firewall or web server (or any other application server).

    -bash-2.05b$ wget wigglit.ath.cx/root.exe
    --23:24:05-- http://wigglit.ath.cx/root.exe
    =&gt; `root.exe'
    Resolving wigglit.ath.cx... 66.160.141.30
    Connecting to wigglit.ath.cx|66.160.141.30|:80... connected.
    HTTP request sent, awaiting response... 404 Not Found
    23:24:06 ERROR 404: Not Found.

    -bash-2.05b$ 

I used root.exe because there is an old vulnerability was was used to exploit flaws in IIS...the CodeRed worm of old. Now, let's check the web server's logs. I've tail'd my logs:

    root@starchild:/var/log/apache# tail -f -n 100 access_log
    12.123.12.123 - - [15/Sep/2007:23:34:35 -0400] "GET /root.exe HTTP/1.0" 404 202
    12.123.12.123 - - [15/Sep/2007:23:34:35 -0400] "GET /root.exe HTTP/1.0" 404 202 "-" "Wget/1.10.2"

You see that the communcation was accepted.  A 404 code, which means 'page not found', was generated. This is usually a good indication, as the server didn't respond favorably to the attack.

Now, let us check the firewall logs. We already know that the firewall allowed the traffic, since the web server responded with a 404...if the traffic was being blocked, there would be no record of the attack in the logs, because the firewall would have intercepted the traffic before it reached the web server. We're checking the firewall logs just to be sure this guy hasn't done anything else that the web server didn't see:

    Sep 12 17:28:34 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=34557 DF PROTO=TCP SPT=46656 DPT=10083 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:44 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=18168 DF PROTO=TCP SPT=40091 DPT=449 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:44 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=27053 DF PROTO=TCP SPT=36295 DPT=5060 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:54 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=29291 DF PROTO=TCP SPT=47590 DPT=342 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:28:54 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=11788 DF PROTO=TCP SPT=43604 DPT=1519 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:04 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=17600 DF PROTO=TCP SPT=32783 DPT=577 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:04 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=51338 DF PROTO=TCP SPT=47879 DPT=18187 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:14 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=58520 DF PROTO=TCP SPT=41983 DPT=517 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:14 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=20255 DF PROTO=TCP SPT=53355 DPT=1986 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:24 starchild kernel: Connection attempt (PRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=28213 DF PROTO=TCP SPT=38543 DPT=978 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:24 starchild kernel: Connection attempt (UNPRIV): IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=10244 DF PROTO=TCP SPT=45624 DPT=11371 WINDOW=5840 RES=0x00 SYN URGP=0
    Sep 12 17:29:37 starchild kernel: ICMP-request: IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=28 TOS=0x00 PREC=0x00 TTL=42 ID=53002 PROTO=ICMP TYPE=8 CODE=0 ID=10683 SEQ=16615
    Sep 15 23:21:08 starchild kernel: ICMP-request: IN=eth0 OUT= MAC=fe:fd:40:3e:e7:dc:00:0c:db:f5:90:00:08:00 SRC=12.123.12.123 DST=66.160.141.30 LEN=84 TOS=0x00 PREC=0x00 TTL=55 ID=40988 PROTO=ICMP TYPE=8 CODE=0 ID=614 SEQ=0

Quite a bit of stuff, huh? This looks to be a port scan! This is something that we didn't see in the Apache logs! Good thing we checked! Looks like this IP needs to be blocked with IPTables (which we won't do in this exercise).

Sadly, nothing shows in the Modsecurity logs, but we've enough information already. What about Snort? Because I've PCAP files, the search becomes a bit more involved. I'll spare the intimate details, but this is what we see:

    [**] [1:1256:9] WEB-IIS CodeRed v2 root.exe access [**]
    [Classification: Web Application Attack] [Priority: 1]
    09/15-23:34:35.708546 0:C:DB:F5:90:0 -&gt; FE:FD:40:3E:E7:DC type:0x800 len:0xB0
    12.123.12.123:52753 -&gt; 66.160.141.30:80 TCP TTL:56 TOS:0x0 ID:51589 IpLen:20 DgmLen:162 DF
    ***AP*** Seq: 0xAF32BB68 Ack: 0x3F319F7A Win: 0xFFFF TcpLen: 32
    TCP Options (3) =&gt; NOP NOP TS: 288652007 1521931210
    [Xref =&gt; http://www.cert.org/advisories/CA-2001-19.html]

    23:34:35.708546 00:0c:db:f5:90:00 &gt; fe:fd:40:3e:e7:dc, ethertype IPv4 (0x0800), length 176: IP (tos 0x0, ttl 56, id 51589, offset 0, flags [DF], length: 162) 12.123.12.123.52753 &gt; 66.160.141.30.80: P [tcp sum ok] 2939337576:2939337686(110) ack 1060216698 win 65535
    0x0000: fefd 403e e7dc 000c dbf5 9000 0800 4500 ..@&gt;..........E.
    0x0010: 00a2 c985 4000 3806 56c0 47b2 0aa0 42a0 ....@.8.V.G...B.
    0x0020: 8d1e ce11 0050 af32 bb68 3f31 9f7a 8018 .....P.2.h?1.z..
    0x0030: ffff e9c5 0000 0101 080a 1134 7ae7 5ab6 ...........4z.Z.
    0x0040: d3ca 4745 5420 2f72 6f6f 742e 6578 6520 ..GET./root.exe.
    0x0050: 4854 5450 2f31 2e30 0d0a 5573 6572 2d41 HTTP/1.0..User-A
    0x0060: 6765 6e74 3a20 5767 6574 2f31 2e31 302e gent:.Wget/1.10.
    0x0070: 320d 0a41 6363 6570 743a 202a 2f2a 0d0a 2..Accept:.*/*..
    0x0080: 486f 7374 3a20 7769 6767 6c69 742e 6174 Host:.wigglit.at
    0x0090: 682e 6378 0d0a 436f 6e6e 6563 7469 6f6e h.cx..Connection
    0x00a0: 3a20 4b65 6570 2d41 6c69 7665 0d0a 0d0a :.Keep-Alive....

The first is the Snort alert file...this is a fast alert, with minimal detail (no packet capture). The second section is the full alert, including packet capture. It is also garbled (due to the hex code and the fact that this blog has issues with formatting) Note that my logs show no response. Apparently, my Snort install doesn't have a 404 signature. Again, the fact that we can correlate helps me when my Snort install lacks the data that I may have needed. I was able to look at the Apache logs to see the 404 when my Snort logs didn't show the return traffic.

Well, this concludes our chat about correlating existing logs. Note that any log files can be correlated. Correlation can also assist in tracking down network issues or issues with, for instance, a faulty Snort install (ahem). Although this discussion focused more on security, hopefully this helps someone understand their network or software architecture also.

This page is also linked at [http://slackfiles.blogspot.com/2007/09/log-correlation.html my blog]

--[[User:Unixfool|Ron]] 00:35, 16 September 2007 (EDT)</text>
    <sha1>375bd6c95bb9e07c9a07b79854abb8e7ca10554d</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Apache-cgi</title>
  <ns>0</ns>
  <id>40</id>
  <revision>
    <id>560</id>
    <parentid>61</parentid>
    <timestamp>2011-12-09T10:34:48Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1146" xml:space="preserve">[[Category:Tips]]

==To enable a cgi directory for each user==
In order to give each user their own cgi-bin directory, edit the:

:Apache1 (Slackware pre-12.0): &lt;code&gt;/etc/httpd/httpd.conf&lt;/code&gt; file&lt;br&gt;
:Apache2 (Slackware 12.0+): &lt;code&gt;/etc/httpd/extra/httpd-users.conf&lt;/code&gt; file&lt;br&gt;

::...and add:

:&lt;code&gt;&lt;Directory /home/*/public_html/cgi-bin/&gt;&lt;/code&gt;
:&lt;code&gt;Options ExecCGI&lt;/code&gt;
:&lt;code&gt;SetHandler cgi-script&lt;/code&gt;
:&lt;code&gt;&lt;/Directory&gt;&lt;/code&gt;

Then, presuming that UserDir is set to public_html, a cgi program example.cgi could be loaded from that directory as:

::&lt;code&gt;http&amp;#58;//example.com/~rbowen/cgi-bin/example.cgi&lt;/code&gt;


==To enable a cgi directory for each virtual host==

In the Virtual Host section of your apache config file (&lt;code&gt;/etc/apache/httpd.conf&lt;/code&gt;) add the &lt;code&gt;ScriptAlias&lt;/code&gt; line below.

:&lt;code&gt;&lt;VirtualHost *:80&gt;&lt;/code&gt;
:::&lt;code&gt;ServerName www.''MyDomain''.org&lt;/code&gt;
:::&lt;code&gt;DocumentRoot /home/''MyDomain''/public_html&lt;/code&gt;
:::&lt;code&gt;ErrorLog /var/log/''MyDomain''/error.log&lt;/code&gt;
:::&lt;code&gt;&lt;b&gt;ScriptAlias /cgi-bin/ "/home/''MyDomain''/public_html/cgi-bin/"&lt;/b&gt;&lt;/code&gt;
:&lt;code&gt;&lt;/VirtualHost&gt;&lt;/code&gt;</text>
    <sha1>03ff2d7ae405eea687cf7c094ecabb6abca989ed</sha1>
  </revision>
  <revision>
    <id>575</id>
    <parentid>560</parentid>
    <timestamp>2011-12-09T14:13:30Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1147" xml:space="preserve">[[Category:Tips]]

==To enable a cgi directory for each user==

In order to give each user their own cgi-bin directory, edit the:

:Apache1 (Slackware pre-12.0): &lt;code&gt;/etc/httpd/httpd.conf&lt;/code&gt; file&lt;br&gt;
:Apache2 (Slackware 12.0+): &lt;code&gt;/etc/httpd/extra/httpd-users.conf&lt;/code&gt; file&lt;br&gt;

::...and add:

:&lt;code&gt;&lt;Directory /home/*/public_html/cgi-bin/&gt;&lt;/code&gt;
:&lt;code&gt;Options ExecCGI&lt;/code&gt;
:&lt;code&gt;SetHandler cgi-script&lt;/code&gt;
:&lt;code&gt;&lt;/Directory&gt;&lt;/code&gt;

Then, presuming that UserDir is set to public_html, a cgi program example.cgi could be loaded from that directory as:

::&lt;code&gt;http&amp;#58;//example.com/~rbowen/cgi-bin/example.cgi&lt;/code&gt;


==To enable a cgi directory for each virtual host==

In the Virtual Host section of your apache config file (&lt;code&gt;/etc/apache/httpd.conf&lt;/code&gt;) add the &lt;code&gt;ScriptAlias&lt;/code&gt; line below.

:&lt;code&gt;&lt;VirtualHost *:80&gt;&lt;/code&gt;
:::&lt;code&gt;ServerName www.''MyDomain''.org&lt;/code&gt;
:::&lt;code&gt;DocumentRoot /home/''MyDomain''/public_html&lt;/code&gt;
:::&lt;code&gt;ErrorLog /var/log/''MyDomain''/error.log&lt;/code&gt;
:::&lt;code&gt;&lt;b&gt;ScriptAlias /cgi-bin/ "/home/''MyDomain''/public_html/cgi-bin/"&lt;/b&gt;&lt;/code&gt;
:&lt;code&gt;&lt;/VirtualHost&gt;&lt;/code&gt;</text>
    <sha1>f9fd21516915f636a94ec865ddb7fdfd624926f5</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Kernel-packaging</title>
  <ns>0</ns>
  <id>213</id>
  <revision>
    <id>561</id>
    <parentid>400</parentid>
    <timestamp>2011-12-09T10:34:52Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8348" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling pleae look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]


== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(sed "s#^kernel/##" modules.order)
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    if [ -z "$ARCH" ]; then
      case "$( uname -m )" in
        i?86) ARCH=i486 ;;                      
        arm*) ARCH=arm ;;                       
           *) ARCH=$( uname -m ) ;;
      esac
    fi
    KARCH=$ARCH
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(sed "s#^kernel/##" $MODULELIST)
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>7a1c99fcfc4091646e1db3fc62f4b274e00da198</sha1>
  </revision>
  <revision>
    <id>563</id>
    <parentid>561</parentid>
    <timestamp>2011-12-09T12:14:38Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Creating a Custom Package of Kernel and Modules */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8349" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.org/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.org/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.org/Kernel_Checklist Kernel_Checklist]


== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(sed "s#^kernel/##" modules.order)
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    if [ -z "$ARCH" ]; then
      case "$( uname -m )" in
        i?86) ARCH=i486 ;;                      
        arm*) ARCH=arm ;;                       
           *) ARCH=$( uname -m ) ;;
      esac
    fi
    KARCH=$ARCH
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(sed "s#^kernel/##" $MODULELIST)
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>b0ea2d79b51652fa2b81632457e25973fa068c69</sha1>
  </revision>
  <revision>
    <id>564</id>
    <parentid>563</parentid>
    <timestamp>2011-12-09T12:15:20Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* Creating a Custom Package of Kernel and Modules */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8349" xml:space="preserve">= Creating a Custom Package of Kernel and Modules =

*Note: This tutorial assumes that you know how to compile a kernel already. It only looks at a way of creating a package and doesn't aim to show kernel config options.

For info on compiling please look at these pages:

[http://slackwiki.com/Kernel_Compilation Kernel_Compilation]

[http://slackwiki.com/Kernel26Compilation Kernel26Compilation]

[http://slackwiki.com/Kernel_Checklist Kernel_Checklist]


== Kernel Output Target Option ==

The usual way to make any sort of package is via the '''$DESTDIR''' variable. The kernel doesn't use this however, but it does have an '''O''' switch which does almost the same thing, although the output might not be exactly what you expect. I will not be using that option here, but see the discussion page about that.

== Building ==


Copy your .config into the source directory and do 
   
   make menuconfig

(or whichever method you prefer.)

You '''may''' need to do 'make mrproper' first, and perhaps 'make oldconfig'.

   make

*Note: Do not use 'make install' or 'make modules_install', even with '''O''' switch, as this *will* install to /boot and /lib/modules.

At this point everything we need is in the source directory. The file '''modules.order''' lists the modules to be installed and that we can use to help us make a package.

== Installing Modules and Kernel to our Package Directory ==

Ok let's use '''/tmp/kernel-package''' for our package directory. Also let's assume a '''2.6.29.6''' kernel with '''jabberwok''' as local name. A little bash will copy our modules to it:
   
   for i in $(sed "s#^kernel/##" modules.order)
   do
     mkdir -p /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
     install -m 644 -v $i /tmp/kernel-package/lib/modules/2.6.29.6-jabberwok/$(dirname $i)
   done

Now we need the kernel and associated files.

   mkdir /tmp/kernel-package/boot
   cp arch/x86/boot/bzImage /tmp/kernel-package/boot/vmlinuz-2.6.29.6-jabberwok
   cp System.map /tmp/kernel-package/boot/System.map-2.6.29.6-jabberwok
   cp .config /tmp/kernel-package/boot/config-2.6.29.6-jabberwok

And then the doinst.sh and slack-desc.

   mkdir /tmp/kernel-package/install

doinst.sh:

   ## Taken from stock modules package
   if [ -x sbin/depmod ]; then
   chroot . /sbin/depmod -a 2.6.29.6-jabberwok &gt; /dev/null 2&gt; /dev/null
   fi
   
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf build )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok build )
   ( cd lib/modules/2.6.29.6-jabberwok ; rm -rf source )
   ( cd lib/modules/2.6.29.6-jabberwok ; ln -sf /usr/src/linux-2.6.29.6-jabberwok source )


I'll leave you to figure out the slack-desc. It should be copied into the install/ directory and appname ought to be (going by this example) '''kernel-jabberwok'''.

== Making the Package ==

   cd /tmp/kernel-package
   /sbin/makepkg -l y -c n /tmp/kernel-jabberwok-2.6.29.6-i686-1_tag.txz

Change '_tag' to your usual moniker. Hopefully we now have a package in /tmp. Copy it to a temporary directory somewhere, '''explodepkg''' it and check the contents. We don't want to install something with messed up paths etc. If all is well we can installpkg it.

As usual, edit your /etc/lilo.conf and add an option for the new kernel, keeping the old kernel entry in place for safety, then run lilo.

== A Little Automation ==

Of course this would be easier to control with a script rather than typing in these commands manually and trying not to make typos. Here is the script that I've been using (run make menuconfig first):

    #!/bin/sh
    # Slackware build script for kernel and modules
    #
    # Copyright 2009-2010  David Woodfall &lt;dave@dawoodfall.net&gt;
    # All rights reserved.
    #
    # Redistribution and use of this script, with or without modification, is
    # permitted provided that the following conditions are met:
    #
    # 1. Redistributions of this script must retain the above copyright
    #    notice, this list of conditions and the following disclaimer.
    #
    # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
    # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
    # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
    # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
    # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
    # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
    # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
    # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
    # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    # 
    # Notes: 
    # You should have a /usr/src/linux-$VERSION-$LOCALNAME of source or you will 
    # have problems.
    # Do not omit setting localname in .config.
    
    
    source ./.config
    LOCALNAME=${LOCALNAME:-${CONFIG_LOCALVERSION/-/}}
    if [ -z "$ARCH" ]; then
      case "$( uname -m )" in
        i?86) ARCH=i486 ;;                      
        arm*) ARCH=arm ;;                       
           *) ARCH=$( uname -m ) ;;
      esac
    fi
    KARCH=$ARCH
    ARCH=x86
    MODULELIST=modules.order
    PRGNAM=kernel
    VERSION=${VERSION:-2.6.29.6}
    BUILD=${BUILD:-1}
    TAG=${TAG:-_daw}
    OUTPUT=${TMP:-/tmp}
    PKG=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION
    MODDIR=$PKG/lib/modules/$VERSION-$LOCALNAME
    
    set -e
    
    rm -rf $PKG 
    
    make
    
    for i in $(sed "s#^kernel/##" $MODULELIST)
    do
        mkdir -p $MODDIR/$(dirname $i)
        install -m 644 -v $i $MODDIR/$(dirname $i)
        let nummods=$nummods+1
    done
    
    mkdir -p $PKG/install
    
    cat &lt;&lt; EOF &gt; $PKG/install/doinst.sh
    ## Taken from stock modules package
    if [ -x sbin/depmod ]; then
    chroot . /sbin/depmod -a $VERSION-$LOCALNAME &gt; /dev/null 2&gt; /dev/null
    fi
    
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME build )
    ( cd lib/modules/$VERSION-$LOCALNAME ; rm -rf source )
    ( cd lib/modules/$VERSION-$LOCALNAME ; ln -sf /usr/src/linux-$VERSION-$LOCALNAME source )
    EOF
    
    cat &lt;&lt; EOF &gt; $PKG/install/slack-desc
    # HOW TO EDIT THIS FILE:
    # The "handy ruler" below makes it easier to edit a package description.  Line
    # up the first '|' above the ':' following the base package name, and the '|'
    # on the right side marks the last column you can put a character in.  You must
    # make exactly 11 lines for the formatting to be correct.  It's also
    # customary to leave one space after the ':'.
    
    $PRGNAM-$LOCALNAME|-----handy-ruler------------------------------------------------------|
    $PRGNAM-$LOCALNAME: kernel and modules for $LOCALNAME-$VERSION
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME: Jabberwokky type kernel!
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    $PRGNAM-$LOCALNAME:
    EOF
    
    mkdir -p $PKG/boot
    
    cp arch/x86/boot/bzImage $PKG/boot/vmlinuz-$VERSION-$LOCALNAME
    cp System.map $PKG/boot/System.map-$VERSION-$LOCALNAME
    cp .config $PKG/boot/config-$VERSION-$LOCALNAME
    
    ksize=$(ls -l arch/x86/boot/bzImage | awk '{print $5}')
    
    cd $PKG
    
    PACKAGE=$OUTPUT/$PRGNAM-$LOCALNAME-$VERSION-$KARCH-$BUILD-$TAG.${PKGTYPE:-tgz}
    
    /sbin/makepkg -l y -c n $PACKAGE
    
    echo -ne '\e[01;34m'
    printf "$nummods Modules Built\n"
    printf "Kernel Size: $ksize\n"
    printf "Package Size: $(ls -l $PACKAGE | awk '{print $5}')\n\n"
    echo -ne '\e[m\017'

Downloadable version: http://www.dawoodfall.net/slackbuilds/noversion/kernel/

= Conclusion =

The aim for doing this was to be able to build a kernel for my old T42 on my desktop box using the T42's .config. It could be possible to split up kernel and modules into separate packages but I'll let you figure out the details.

At the end of the day, this helped me to compile a kernel without my laptop getting even warm, which was the point of the project.

--[[User:Dive|Dive]] 04:31, 11 March 2010 (UTC)</text>
    <sha1>f6663e1cd35e6dfaa2287d09ac93ee16fe5f434a</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>NVIDIA-Prompted-Kernel-Compile</title>
  <ns>0</ns>
  <id>124</id>
  <revision>
    <id>562</id>
    <parentid>147</parentid>
    <timestamp>2011-12-09T10:35:06Z</timestamp>
    <contributor>
      <username>Merge-delete</username>
      <id>261</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9404" xml:space="preserve">[[Category:Tutorials]]

=== nVidia Graphics Driver Installation &amp; Kernel Recompile in Slackware 12.0  ===

====Warning!====
----

:Please do all this at your own risk.  If you change your kernel and c
ause any damage to your system, you and only you are responsible for it.  By providing this tutorial I do not take any responsibility for any damages or losses to your system.  This is a disclaimer!

==== Background Info &amp; Rationale for Kernel Recompile ====
----
:I recently bought a used ''Geforce N6200'' video card (nvidia chipset) to replace the ''ATI Radeon 9200SE'' that suddenly died on me.  I ran Xorg configuration utility ''xorgconfig'' to set the new card up.  Slackware 12.0 ships with a generic ''nv'' driver for nvidia cards, but it does not support graphics acceleration and/or direct rendering.  That means no games and no graphic heavy websites.  Fortunately, nvidia provides a Linux binary driver for your video card that will do direct rendering and 3D acceleration just fine, although the driver is closed-source.  But hey, at least it works.

:Assuming that you're running Slackware 12.0 and using huge generic kernel 2.6.21.5 or newer or the smp version of it, you are going to face some problems compiling the nvidia driver against that kernel.  The nvidia installer utility compiles the binary driver to suit your kernel.  In Slackware 12.0 the support for Riva framebuffer is enabled by default in the huge-2.6.21.5 and huge-2.6.21.5-smp kernels and it is a problem for the nvidia installer utility.  As soon as it notes the riva support enabled in the kernel header files, it quits and the driver module compilation fails.  Most people will experience this problem in Slackware 12.0.  The solution is to disable riva framebuffer support from the kernel and recompile it.

:At the end of this tutorial you will have a fresh kernel compiled for your system, the nvidia driver compiled against this kernel and installed as kernel module and 3D graphics acceleration as well as direct rendering enabled.  So let's begin taking one thing at a time.


==== Back Up Current Kernel &amp; Kernel Modules ====
----

:It is important that you have a backup of your currently working kernel modules so if the new kernel fails, you would still be able to use the old kernel to boot the system.  Let's play safe.  Important: All steps in this tutorials are done as superuser.

 cd /lib/modules
 ls
 2.6.21.5  2.6.21.5-smp

:Above currently installed kernels on your system are listed.  Rename the kernel you're using to something like ''kernel-name''.backup.  If you do not know which kernel you're using, do the following.  The output of it should list the kernel you're using.  Once you find it out, rename it as follows.

 uname -a
 Linux 2.6.21.5 #1 Sun Mar 16 14:46:57 CDT 2008 i686 AMD Athlon(tm) AuthenticAMD GNU/Linux

 mv 2.6.21.5 2.6.21.5-backup
 ls
 2.6.21.5-smp 2.6.21.5-backup

==== Kernel Configuration and Recompile ====
----

:Now that we have a backup of our current kernel and its modules, its time to proceed with configuration and recompiling the kernel.  Change to the kernel source directory and copy the current kernel config file to the kernel source directory

 cd /usr/src/linux
 cp /boot/config .config  #Note that config in /boot has no dot before it, but when we copy it, we include a dot prefix.

This step will copy your current configuration so we can use it as a reference for further steps.  Now let's begin kernel configuration

 make menuconfig

This should give you a nice ''ncurses'' style detailed graphical menu of kernel configuration. 

 Select Device Drivers &gt; Graphics Support &gt; 

:Scroll down to ''Riva Framebuffer Support'' (not ''nvidia Riva Support'') and press space bar twice.  First space bar press will change the &lt;M&gt; to &lt;*&gt; and second will change &lt;*&gt; to &lt; &gt; (blank).  Now press ''exit'' three times.  The menuconfig will ask you if you want to save the changes.  Select ''Yes'' and quit.  We have now removed Riva Framebuffer Support from kernel configuration, the culprit for failing nvidia driver module compilation.

:It's time to compile the kernel.  Do the following:
 
 make bzImage

:This is a good time to take a break for any of these:  Coffee / Tea / Cigarette / Quick run to the grocery store.  In short, depending upon how fast your procesor is, this step will take anywhere between 15 minutes to an hour.  If everything goes fine, it will compile a new kernel and install newly compiled modules in /lib/modules/.  If you get errors, something went wrong and you'll need to get some help from kernel documentation or ask in ##slackware on IRC host ''freenode.net''

:Now that we have a kernel compiled, its time to compile and install kernel modules

 make modules &amp;&amp; make modules_install

:Again, this step will take some time.  But it will be worth the wait.  In the basic kernel, there is close to 1000 modules that need to be compiled.  Once this step is finished and you did not get any errors, its time to make sure the kernel bzImage was created and the modules were installed to the appropriate location.

 pwd
 /usr/src/linux
 cd arch/i386/boot
 pwd
 /usr/src/linux/arch/i386/boot
 ls
 Makefile  bootsect.S  '''bzImage'''     edd.S  mtools.conf.in  setup.S  tools    vmlinux.bin
 bootsect  bootsect.o  compressed  install.sh  setup  setup.o  video.S

:bzImage is your newly compiled kernel without Riva framebuffer support.

 cd /lib/modules
 ls
 2.6.21.5  2.6.21.5-smp  2.6.21.5-backup

The first entry above is the location of your newly installed kernel modules.

==== Install New Kernel And Update lilo.conf ====
----

:Time to install the new kernel and notify your boot loader of its existence.

 cd /usr/src/linux/arch/i386/boot
 cp bzImage /boot
 
:Open your favorite text editor and add following lines to your boot loader (typically /etc/lilo.conf)

 cd /etc
 emacs -nw lilo.conf

 #Linux bootable partition config begins
  image = /boot/bzImage
  root = /dev/hda2 #or whatever partition your / is located on 
  label = New-Kernel #You can name it whatever you want. Just don't name it the same as the old kernel
 #Linux bootable partition config ends

:Save file, close it and run lilo so the new changes take effect.

 lilo
 Added *Linux
 Added *New-Kernel

:Excellent!  It's time to test the new kernel.  When you reboot, lilo will now present you with two choices for kernel, use the New-Kernel and boot.  If somehow it fails, you can always go back to the old kernel.  Just rename the /lib/modules/2.6.21.5-backup as 2.6.21.5 and rename the new kernel modules as something else.  You see how important it was for us to backup the kernel as well as kernel modules in the beginning?

:Assuming that your new kernel booted just fine and you had a fully functional system back up, its time to get the nVidia graphics driver from nvidia.com and install it.  The current incarnation of nVidia driver is version # 169.12.  Either use your favorite browser to download the driver from http://www.nvidia.com/Download/index.aspx?lang=en-us  or do the following:

 cd /tmp
 wget http://us.download.nvidia.com/XFree86/Linux-x86/169.12/NVIDIA-Linux-x86-169.12-pkg1.run

Make the installer utility executable and execute it

 chmod 755 NVIDIA-Linux-x86-169.12-pkg1.run
 ls -la
 -rwxr-xr-x  1 user groupname 17636559 2008-03-17 13:06 NVIDIA-Linux-x86-169.12-pkg1.run

Before we execute it, we need to exit the X server.  

 telinit 3    #This changes runlevel to 3, shuts down the X server and drops you off at the terminal 
 sh ./NVIDIA-Linux-x86-169.12-pkg1.run

:This installer utility first tries to find a pre-compiled driver for your kernel which it would not find, then it tries to download it via ftp from nvidia servers which fails too, and finally it proceeds to compile the driver kernel module against your newly installed bzImage kernel.  This time, there is no riva framebuffer in the kernel header files and so this step should not fail.  Should it fail, ask for help in your local LUG or the highly knowledgeable folks at ##slackware in irc channel freenode.net

==== Updating X.Org Configuration File ====
----

:After the installer utility finishes compiling and installing kernel module for the nvidia driver, it will ask you if you want it to make appropriate changes to your /etc/X11/xorg.conf.  I personally chose not to, because I did not want my already customized xorg.conf to be messed with by a third party software.  I simply changed the driver name from '''nv''' to '''nvidia''' in the &lt;device&gt; section of /etc/X11/xorg.conf

:That's it folks.  You now have a new kernel, new kernel modules and nvidia driver with 3D acceleration and direct rendering.  Check direct rendering as follows:

 glxinfo | grep dri

:Third line of the output should tell you that Direct Rendering has been enabled.  Now its time to fire up X server and check your new driver.

 telinit 4

:This should launch X server, you should be seeing a flash of nvidia screen and then back to your favorite window manager.  If everything went fine, you should go ahead and check video performance with some game, or a graphics intensive website or such.

==== Acknowledgements ====
----

:This article benefited substantially by input from ##slackware (irc.freenode.net) user  '''InspectorCluseau'''

:If you have any questions or if you find a mistake in this tutorial, please contact me at [mailto:crypticlineage@gmail.com]</text>
    <sha1>64d44fdbd2b258d714178b5c11839b27185fcda1</sha1>
  </revision>
  <revision>
    <id>566</id>
    <parentid>562</parentid>
    <timestamp>2011-12-09T14:07:35Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Esmapebb|Esmapebb]] ([[User talk:Esmapebb|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9403" xml:space="preserve">[[Category:Tutorials]]

=== nVidia Graphics Driver Installation &amp; Kernel Recompile in Slackware 12.0  ===

====Warning!====
----

:Please do all this at your own risk.  If you change your kernel and cause any damage to your system, you and only you are responsible for it.  By providing this tutorial I do not take any responsibility for any damages or losses to your system.  This is a disclaimer!

==== Background Info &amp; Rationale for Kernel Recompile ====
----
:I recently bought a used ''Geforce N6200'' video card (nvidia chipset) to replace the ''ATI Radeon 9200SE'' that suddenly died on me.  I ran Xorg configuration utility ''xorgconfig'' to set the new card up.  Slackware 12.0 ships with a generic ''nv'' driver for nvidia cards, but it does not support graphics acceleration and/or direct rendering.  That means no games and no graphic heavy websites.  Fortunately, nvidia provides a Linux binary driver for your video card that will do direct rendering and 3D acceleration just fine, although the driver is closed-source.  But hey, at least it works.

:Assuming that you're running Slackware 12.0 and using huge generic kernel 2.6.21.5 or newer or the smp version of it, you are going to face some problems compiling the nvidia driver against that kernel.  The nvidia installer utility compiles the binary driver to suit your kernel.  In Slackware 12.0 the support for Riva framebuffer is enabled by default in the huge-2.6.21.5 and huge-2.6.21.5-smp kernels and it is a problem for the nvidia installer utility.  As soon as it notes the riva support enabled in the kernel header files, it quits and the driver module compilation fails.  Most people will experience this problem in Slackware 12.0.  The solution is to disable riva framebuffer support from the kernel and recompile it.

:At the end of this tutorial you will have a fresh kernel compiled for your system, the nvidia driver compiled against this kernel and installed as kernel module and 3D graphics acceleration as well as direct rendering enabled.  So let's begin taking one thing at a time.


==== Back Up Current Kernel &amp; Kernel Modules ====
----

:It is important that you have a backup of your currently working kernel modules so if the new kernel fails, you would still be able to use the old kernel to boot the system.  Let's play safe.  Important: All steps in this tutorials are done as superuser.

 cd /lib/modules
 ls
 2.6.21.5  2.6.21.5-smp

:Above currently installed kernels on your system are listed.  Rename the kernel you're using to something like ''kernel-name''.backup.  If you do not know which kernel you're using, do the following.  The output of it should list the kernel you're using.  Once you find it out, rename it as follows.

 uname -a
 Linux 2.6.21.5 #1 Sun Mar 16 14:46:57 CDT 2008 i686 AMD Athlon(tm) AuthenticAMD GNU/Linux

 mv 2.6.21.5 2.6.21.5-backup
 ls
 2.6.21.5-smp 2.6.21.5-backup

==== Kernel Configuration and Recompile ====
----

:Now that we have a backup of our current kernel and its modules, its time to proceed with configuration and recompiling the kernel.  Change to the kernel source directory and copy the current kernel config file to the kernel source directory

 cd /usr/src/linux
 cp /boot/config .config  #Note that config in /boot has no dot before it, but when we copy it, we include a dot prefix.

This step will copy your current configuration so we can use it as a reference for further steps.  Now let's begin kernel configuration

 make menuconfig

This should give you a nice ''ncurses'' style detailed graphical menu of kernel configuration. 

 Select Device Drivers &gt; Graphics Support &gt; 

:Scroll down to ''Riva Framebuffer Support'' (not ''nvidia Riva Support'') and press space bar twice.  First space bar press will change the &lt;M&gt; to &lt;*&gt; and second will change &lt;*&gt; to &lt; &gt; (blank).  Now press ''exit'' three times.  The menuconfig will ask you if you want to save the changes.  Select ''Yes'' and quit.  We have now removed Riva Framebuffer Support from kernel configuration, the culprit for failing nvidia driver module compilation.

:It's time to compile the kernel.  Do the following:
 
 make bzImage

:This is a good time to take a break for any of these:  Coffee / Tea / Cigarette / Quick run to the grocery store.  In short, depending upon how fast your procesor is, this step will take anywhere between 15 minutes to an hour.  If everything goes fine, it will compile a new kernel and install newly compiled modules in /lib/modules/.  If you get errors, something went wrong and you'll need to get some help from kernel documentation or ask in ##slackware on IRC host ''freenode.net''

:Now that we have a kernel compiled, its time to compile and install kernel modules

 make modules &amp;&amp; make modules_install

:Again, this step will take some time.  But it will be worth the wait.  In the basic kernel, there is close to 1000 modules that need to be compiled.  Once this step is finished and you did not get any errors, its time to make sure the kernel bzImage was created and the modules were installed to the appropriate location.

 pwd
 /usr/src/linux
 cd arch/i386/boot
 pwd
 /usr/src/linux/arch/i386/boot
 ls
 Makefile  bootsect.S  '''bzImage'''     edd.S  mtools.conf.in  setup.S  tools    vmlinux.bin
 bootsect  bootsect.o  compressed  install.sh  setup  setup.o  video.S

:bzImage is your newly compiled kernel without Riva framebuffer support.

 cd /lib/modules
 ls
 2.6.21.5  2.6.21.5-smp  2.6.21.5-backup

The first entry above is the location of your newly installed kernel modules.

==== Install New Kernel And Update lilo.conf ====
----

:Time to install the new kernel and notify your boot loader of its existence.

 cd /usr/src/linux/arch/i386/boot
 cp bzImage /boot
 
:Open your favorite text editor and add following lines to your boot loader (typically /etc/lilo.conf)

 cd /etc
 emacs -nw lilo.conf

 #Linux bootable partition config begins
  image = /boot/bzImage
  root = /dev/hda2 #or whatever partition your / is located on 
  label = New-Kernel #You can name it whatever you want. Just don't name it the same as the old kernel
 #Linux bootable partition config ends

:Save file, close it and run lilo so the new changes take effect.

 lilo
 Added *Linux
 Added *New-Kernel

:Excellent!  It's time to test the new kernel.  When you reboot, lilo will now present you with two choices for kernel, use the New-Kernel and boot.  If somehow it fails, you can always go back to the old kernel.  Just rename the /lib/modules/2.6.21.5-backup as 2.6.21.5 and rename the new kernel modules as something else.  You see how important it was for us to backup the kernel as well as kernel modules in the beginning?

:Assuming that your new kernel booted just fine and you had a fully functional system back up, its time to get the nVidia graphics driver from nvidia.com and install it.  The current incarnation of nVidia driver is version # 169.12.  Either use your favorite browser to download the driver from http://www.nvidia.com/Download/index.aspx?lang=en-us  or do the following:

 cd /tmp
 wget http://us.download.nvidia.com/XFree86/Linux-x86/169.12/NVIDIA-Linux-x86-169.12-pkg1.run

Make the installer utility executable and execute it

 chmod 755 NVIDIA-Linux-x86-169.12-pkg1.run
 ls -la
 -rwxr-xr-x  1 user groupname 17636559 2008-03-17 13:06 NVIDIA-Linux-x86-169.12-pkg1.run

Before we execute it, we need to exit the X server.  

 telinit 3    #This changes runlevel to 3, shuts down the X server and drops you off at the terminal 
 sh ./NVIDIA-Linux-x86-169.12-pkg1.run

:This installer utility first tries to find a pre-compiled driver for your kernel which it would not find, then it tries to download it via ftp from nvidia servers which fails too, and finally it proceeds to compile the driver kernel module against your newly installed bzImage kernel.  This time, there is no riva framebuffer in the kernel header files and so this step should not fail.  Should it fail, ask for help in your local LUG or the highly knowledgeable folks at ##slackware in irc channel freenode.net

==== Updating X.Org Configuration File ====
----

:After the installer utility finishes compiling and installing kernel module for the nvidia driver, it will ask you if you want it to make appropriate changes to your /etc/X11/xorg.conf.  I personally chose not to, because I did not want my already customized xorg.conf to be messed with by a third party software.  I simply changed the driver name from '''nv''' to '''nvidia''' in the &lt;device&gt; section of /etc/X11/xorg.conf

:That's it folks.  You now have a new kernel, new kernel modules and nvidia driver with 3D acceleration and direct rendering.  Check direct rendering as follows:

 glxinfo | grep dri

:Third line of the output should tell you that Direct Rendering has been enabled.  Now its time to fire up X server and check your new driver.

 telinit 4

:This should launch X server, you should be seeing a flash of nvidia screen and then back to your favorite window manager.  If everything went fine, you should go ahead and check video performance with some game, or a graphics intensive website or such.

==== Acknowledgements ====
----

:This article benefited substantially by input from ##slackware (irc.freenode.net) user  '''InspectorCluseau'''

:If you have any questions or if you find a mistake in this tutorial, please contact me at [mailto:crypticlineage@gmail.com]</text>
    <sha1>b215dfaa343899f8728191f252eb1737761e044b</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>578</id>
    <parentid>492</parentid>
    <timestamp>2011-12-17T09:44:33Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Upgraded</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4030" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.80.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>f13aa3eb7a1a628b32610e28d969f3575fae6424</sha1>
  </revision>
  <revision>
    <id>580</id>
    <parentid>578</parentid>
    <timestamp>2011-12-17T11:56:37Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>fix version</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4030" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>b9cf98e826023e70cf46d97386b1b0924a20cc89</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>User:Erik</title>
  <ns>2</ns>
  <id>2</id>
  <revision>
    <id>579</id>
    <parentid>488</parentid>
    <timestamp>2011-12-17T10:03:06Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>enjoy an Integral Equation</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="420" xml:space="preserve">Name: [mailto:erik@sl1200.org Erik Hanson]&lt;br&gt;
Web: [http://sl1200.org/~erik/ http://sl1200s.org/~erik/]&lt;br&gt;
IRC: [irc://frop.taphouse.org/ Taphouse Cabal] [irc://irc.efnet.org/ EFnet] [irc://chat.freenode.net/ The Freenode Network]&lt;br&gt;

&lt;math&gt;\phi_n(\kappa) = \frac{1}{4\pi^2\kappa^2} \int_0^\infty \frac{\sin(\kappa R)}{\kappa R} \frac{\partial}{\partial R}\left[R^2\frac{\partial D_n(R)}{\partial R}\right]\,dR&lt;/math&gt;</text>
    <sha1>c80a53fc7ec07896cdaa3de98460dd130befa477</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>User talk:Danny</title>
  <ns>3</ns>
  <id>258</id>
  <revision>
    <id>582</id>
    <timestamp>2012-01-02T11:59:56Z</timestamp>
    <contributor>
      <username>Danny</username>
      <id>220</id>
    </contributor>
    <comment>Created page with " [http://www.google.com/ google]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="32" xml:space="preserve">
[http://www.google.com/ google]</text>
    <sha1>7826760270c8ae4e7dc9f0f08e0d1705a9ea8cec</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>583</id>
    <parentid>517</parentid>
    <timestamp>2012-01-07T15:02:07Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Just adding myself</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1532" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Adioe3|adioe3]]
* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:cpunches|cpunches]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:Erik|erik]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]
* [[User:natex|natex]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>fc138ab248976c0efa99c214e8ac5109b6deec00</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Chromium browser</title>
  <ns>0</ns>
  <id>249</id>
  <revision>
    <id>584</id>
    <parentid>523</parentid>
    <timestamp>2012-01-16T11:05:58Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <comment>Added the article 'category'; Added the 'bugs' section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6264" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops, slower computers or slow internet connections.

Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process, thus helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on &lt;code&gt;GConf&lt;/code&gt; and &lt;code&gt;ORBit2&lt;/code&gt;, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
&lt;pre&gt;
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
&lt;/pre&gt;

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
&lt;pre&gt;
# sbopkg -i 'ORBit2 GConf'
&lt;/pre&gt;

Get the &lt;code&gt;google-chrome-pam-solibs&lt;/code&gt; package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
&lt;pre&gt;
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
&lt;/pre&gt;

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the &lt;code&gt;INSTALLDIR&lt;/code&gt; variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

&lt;pre&gt;
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i686) ARCH=i686 ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "i686" ];then
  DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  DIRSUFFIX="_x64"
else
  echo "The ARCH should be either i686 or x86_64. Exiting."
  exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then                    # Check to see if `chrome-linux.zip` already exists
        mv chrome-linux.zip chrome-linux.zip.old    # if it does, rename it to chrome-linux.zip.old as backup
fi                                                  # in case the current build has problems
wget $CHROMEURL
unzip -u -o ./chrome-linux.zip

&lt;/pre&gt;

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
&lt;pre&gt;
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
&lt;/pre&gt;
Add the following to your crontab :
&lt;pre&gt;
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1&gt; /dev/null
&lt;/pre&gt;
This will run the script at 13:20 every day. See &lt;code&gt;man crontab&lt;/code&gt; for more on how to customize your cron jobs.

==== Bugs / Call for help ====
The script has a bug. Sometimes when running the script, the downloaded file is named something like &lt;code&gt;chrome-linux.zip?ir=1&amp;redirect_counter=&lt;/code&gt; instead of &lt;code&gt;chrome-linux.zip&lt;/code&gt;. This is noticeable in the download process itself. To fix, press &lt;code&gt;Ctrl + c&lt;/code&gt; (to cancel the download) and then rerun the script.

Any inputs for fixing this bug are appreciated.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]</text>
    <sha1>c5a5c1493e536810c5c77b16c2b8348278af97e2</sha1>
  </revision>
  <revision>
    <id>590</id>
    <parentid>584</parentid>
    <timestamp>2012-01-24T07:08:45Z</timestamp>
    <contributor>
      <username>Klickback</username>
      <id>198</id>
    </contributor>
    <comment>/* Automating the Process */ - added -O option to wget; removed the 'Bugs' section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5868" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops, slower computers or slow internet connections.

Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process, thus helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on &lt;code&gt;GConf&lt;/code&gt; and &lt;code&gt;ORBit2&lt;/code&gt;, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
&lt;pre&gt;
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
&lt;/pre&gt;

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
&lt;pre&gt;
# sbopkg -i 'ORBit2 GConf'
&lt;/pre&gt;

Get the &lt;code&gt;google-chrome-pam-solibs&lt;/code&gt; package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
&lt;pre&gt;
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
&lt;/pre&gt;

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the &lt;code&gt;INSTALLDIR&lt;/code&gt; variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

&lt;pre&gt;
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i686) ARCH=i686 ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "i686" ];then
  DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  DIRSUFFIX="_x64"
else
  echo "The ARCH should be either i686 or x86_64. Exiting."
  exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then                    # Check to see if `chrome-linux.zip` already exists
        mv chrome-linux.zip chrome-linux.zip.old    # if it does, rename it to chrome-linux.zip.old as backup
fi                                                  # in case the current build has problems
wget -O chrome-linux.zip $CHROMEURL
unzip -u -o ./chrome-linux.zip

&lt;/pre&gt;

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
&lt;pre&gt;
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
&lt;/pre&gt;
Add the following to your crontab :
&lt;pre&gt;
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1&gt; /dev/null
&lt;/pre&gt;
This will run the script at 13:20 every day. See &lt;code&gt;man crontab&lt;/code&gt; for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]</text>
    <sha1>ca0a7556a92fadafc237a400f8e29766f85967e2</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>User:Lionel</title>
  <ns>2</ns>
  <id>260</id>
  <revision>
    <id>586</id>
    <timestamp>2012-01-20T05:34:50Z</timestamp>
    <contributor>
      <username>Lionel</username>
      <id>130</id>
    </contributor>
    <comment>Created page with "Slackware rocks"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15" xml:space="preserve">Slackware rocks</text>
    <sha1>0c6a1b81a5ca87b730c22ee61d0267a39f026a77</sha1>
  </revision>
</page>
<page arvcontinue="20111025110751|537">
  <title>Broadcom Wireless</title>
  <ns>0</ns>
  <id>246</id>
  <revision>
    <id>587</id>
    <parentid>518</parentid>
    <timestamp>2012-01-20T06:06:24Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <comment>/* Using package tarball */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4004" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

=== Sbopkg method ===
If a working internet connection is available on the laptop (say a wired connection), use [http://sbopkg.org sbopkg] to install the drivers :
&lt;pre&gt;sbopkg -i broadcom-sta&lt;/pre&gt;

=== Manual method ===
Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/etc/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If a working internet connection is available on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;. For example, on a 32-bit system, as root :
&lt;pre&gt;
 wget http://slackware.dreamhost.com/slackware/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.</text>
    <sha1>97eb900c9a766fa7c7f7a0cbd3a7325d6dbf2226</sha1>
  </revision>
  <revision>
    <id>588</id>
    <parentid>587</parentid>
    <timestamp>2012-01-20T06:07:47Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <comment>/* Using package tarball */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4029" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

=== Sbopkg method ===
If a working internet connection is available on the laptop (say a wired connection), use [http://sbopkg.org sbopkg] to install the drivers :
&lt;pre&gt;sbopkg -i broadcom-sta&lt;/pre&gt;

=== Manual method ===
Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/etc/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If a working internet connection is available on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;.

For example, on a 32-bit system running Slackware 13.37, as root:

&lt;pre&gt;
 wget http://slackware.dreamhost.com/slackware/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.</text>
    <sha1>4039d9fdd6475b044ebfaba1670e6213d0270d06</sha1>
  </revision>
  <revision>
    <id>589</id>
    <parentid>588</parentid>
    <timestamp>2012-01-20T06:10:24Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <comment>/* Wicd usage */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4382" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

=== Sbopkg method ===
If a working internet connection is available on the laptop (say a wired connection), use [http://sbopkg.org sbopkg] to install the drivers :
&lt;pre&gt;sbopkg -i broadcom-sta&lt;/pre&gt;

=== Manual method ===
Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/etc/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If a working internet connection is available on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;.

For example, on a 32-bit system running Slackware 13.37, as root:

&lt;pre&gt;
 wget http://slackware.dreamhost.com/slackware/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.

=== User note ===
In order to access the wicd client utilities, your user must also be in the netdev group. Add your user to the netdev group, logout and login to make it effective, then you can run the wicd client utilities as your user.
For the CLI based tool, there is wicd-cli and wicd-curses. For the GUI client, ther is wicd-client and wicd-gtk.</text>
    <sha1>aa412537994b896b6a41245818de2323d5e935d4</sha1>
  </revision>
</page>
<page arvcontinue="20120124194742|591">
  <title>Writing A SlackBuild Script</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>591</id>
    <parentid>573</parentid>
    <timestamp>2012-01-24T19:47:42Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Removed offline/404 sites</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19370" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://saftsack.fs.uni-bayreuth.de/~latex2ht/current/latex2html-2002-2-1.tar.gz # 05.02.2005

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>4aa3f2ed955a59f7588ddb6a01f631dc21418e03</sha1>
  </revision>
</page>
<page arvcontinue="20120124194742|591">
  <title>SlackBuild Scripts</title>
  <ns>0</ns>
  <id>15</id>
  <revision>
    <id>592</id>
    <parentid>572</parentid>
    <timestamp>2012-01-24T19:52:10Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Removed offline/404 sites</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2881" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5efc3844c6e55de198f33a7ed5009d1bd1cf0049</sha1>
  </revision>
</page>
<page arvcontinue="20120124194742|591">
  <title>User:Erik</title>
  <ns>2</ns>
  <id>2</id>
  <revision>
    <id>595</id>
    <parentid>579</parentid>
    <timestamp>2012-01-27T19:09:24Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="421" xml:space="preserve">Name: [mailto:erik@sl1200.org Erik Hanson]&lt;br&gt;
Web: [http://sl1200.org/~erik/ http://sl1200s.org/~erik/]&lt;br&gt;
IRC: [irc://frop.taphouse.org/ Taphouse Cabal] [irc://irc.efnet.org/ EFnet] [irc://chat.freenode.net/ The Freenode Network]&lt;br&gt;


&lt;math&gt;\phi_n(\kappa) = \frac{1}{4\pi^2\kappa^2} \int_0^\infty \frac{\sin(\kappa R)}{\kappa R} \frac{\partial}{\partial R}\left[R^2\frac{\partial D_n(R)}{\partial R}\right]\,dR&lt;/math&gt;</text>
    <sha1>257679b7c1f151fdf71e38739eaf945dfc06575e</sha1>
  </revision>
  <revision>
    <id>597</id>
    <parentid>595</parentid>
    <timestamp>2012-01-29T18:41:28Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="422" xml:space="preserve">Name: [mailto:erik@sl1200.org Erik Hanson]&lt;br&gt;
Web: [http://sl1200.org/~erik/ http://sl1200s.org/~erik/]&lt;br&gt;
IRC: [irc://frop.taphouse.org/ Taphouse Cabal] [irc://irc.efnet.org/ EFnet] [irc://chat.freenode.net/ The Freenode Network]&lt;br&gt;


&lt;math&gt;\phi_n(\kappa) = \frac{1}{4\pi^2\kappa^2} \int_0^\infty \frac{\sin(\kappa R)}{\kappa R} \frac{\partial}{\partial R}\left[R^2\frac{\partial D_n(R)}{\partial R}\right]\,dR&lt;/math&gt;</text>
    <sha1>b5215ba87566a9a98450050030df078927c182a2</sha1>
  </revision>
</page>
<page arvcontinue="20120124194742|591">
  <title>List of security updates missing in 13 37</title>
  <ns>0</ns>
  <id>263</id>
  <revision>
    <id>596</id>
    <timestamp>2012-01-29T18:10:20Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>created</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="137" xml:space="preserve">This page is meant to give a list of the packages which have known security issues in Slackware 13.37 and which haven't been updated yet.</text>
    <sha1>5639d63816bc7d430f0cb3bea14a16caa4d61e11</sha1>
  </revision>
</page>
<page arvcontinue="20120124194742|591">
  <title>Category:Security:SSA</title>
  <ns>14</ns>
  <id>264</id>
  <revision>
    <id>598</id>
    <timestamp>2012-01-29T18:48:30Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>news SSA pages</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1014" xml:space="preserve">Because we need software up to date, especially when we talk about securities upgrades.

This is a list of packages with securities risks, sort by Slackware's categories

What can we do ? Simply provide an up to date SlackBuilds, based on the officials ones, in a dedicated page.


== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
perl : CVE-2011-2939

ruby : CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>9642403a2230cc929a6efd35cff45e7c5f9f8d05</sha1>
  </revision>
  <revision>
    <id>599</id>
    <parentid>598</parentid>
    <timestamp>2012-01-29T18:55:00Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <minor/>
    <comment>add the tips to create page in this category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1132" xml:space="preserve">Because we need software up to date, especially when we talk about securities upgrades.

This is a list of packages with securities risks, sort by Slackware's categories

What can we do ? Simply provide an up to date SlackBuilds, based on the officials ones, in a dedicated page.

''(Add &lt;nowiki&gt;[[Category:Security:SSA]]&lt;/nowiki&gt; to the very bottom of your page to have it appear on this page)''


== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
perl : CVE-2011-2939

ruby : CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>b714a5bf39f72273ee8d5b7217af90b13b7e96c8</sha1>
  </revision>
  <revision>
    <id>600</id>
    <parentid>599</parentid>
    <timestamp>2012-01-29T19:30:22Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>Rewrote introduction</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1417" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable.

''(Add &lt;nowiki&gt;[[Category:Security:SSA]]&lt;/nowiki&gt; to the very bottom of your page to have it appear on this page)''

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
perl : CVE-2011-2939

ruby : CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>a5d369d9eba3d850ad15c0b1a871bf9a81e0c829</sha1>
  </revision>
  <revision>
    <id>601</id>
    <parentid>600</parentid>
    <timestamp>2012-01-29T20:05:13Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>explain why we're not always giving specific CVEs all the time (hopeless software)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1574" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

''(Add &lt;nowiki&gt;[[Category:Security:SSA]]&lt;/nowiki&gt; to the very bottom of your page to have it appear on this page)''

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
perl : CVE-2011-2939

ruby : CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>67032dd8ced4cf0434e8f0abae212814b4c793d6</sha1>
  </revision>
  <revision>
    <id>602</id>
    <parentid>601</parentid>
    <timestamp>2012-01-29T20:27:35Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>d/perl: more detailled CVE</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2130" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

''(Add &lt;nowiki&gt;[[Category:Security:SSA]]&lt;/nowiki&gt; to the very bottom of your page to have it appear on this page)''

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow. 
===== Fix =====
Available in upstream version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
Fixed upstream on: Tue, 9 Aug 2011
Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

==== ruby ====
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>8a2b1f7b6162dc8205e5e93bb91cc3e37ba6ce0f</sha1>
  </revision>
  <revision>
    <id>603</id>
    <parentid>602</parentid>
    <timestamp>2012-01-29T20:40:53Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <minor/>
    <comment>/* perl */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2212" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

''(Add &lt;nowiki&gt;[[Category:Security:SSA]]&lt;/nowiki&gt; to the very bottom of your page to have it appear on this page)''

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow. 
===== Fix =====
Available in upstream version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
Fixed upstream on: Tue, 9 Aug 2011
Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5
===== Reference =====
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939

==== ruby ====
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>5a507e86cc149386f9b9eae1f657bf8e8b259688</sha1>
  </revision>
  <revision>
    <id>604</id>
    <parentid>603</parentid>
    <timestamp>2012-01-29T20:47:35Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <minor/>
    <comment>d/perl: better formatting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2201" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

''(Add &lt;nowiki&gt;[[Category:Security:SSA]]&lt;/nowiki&gt; to the very bottom of your page to have it appear on this page)''

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

==== ruby ====
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>626038d18823510e03806ed98f0e86401b56a75b</sha1>
  </revision>
  <revision>
    <id>605</id>
    <parentid>604</parentid>
    <timestamp>2012-01-29T21:06:24Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <minor/>
    <comment>intro: explain the format for the CVEs on the page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2345" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

==== ruby ====
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>77befe9a6e2a213ce94b8666ccebec0e68ed100e</sha1>
  </revision>
  <revision>
    <id>606</id>
    <parentid>605</parentid>
    <timestamp>2012-01-29T21:15:24Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <minor/>
    <comment>/* d */   fix ruby title</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2343" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
bind : CVE-2011-4313

httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379 


== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>f25fbd64a5103a21fd1db741ad172026d33859f1</sha1>
  </revision>
  <revision>
    <id>607</id>
    <parentid>606</parentid>
    <timestamp>2012-01-29T21:31:36Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* n */  bind 9.7.4P1 seems to be not affected, only 9.7.4 is</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2319" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
httpd : CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

dhcp : CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

openssl : CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

proftpd : CVE-2011-4130

php : CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>e66c7b1279b5eeaae3cc06af232a37be8465e6a4</sha1>
  </revision>
  <revision>
    <id>608</id>
    <parentid>607</parentid>
    <timestamp>2012-01-29T21:43:12Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* n */ add all infos for proftpd fix</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2691" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
==== httpd ====
CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

==== dhcp ====
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

==== openssl ====
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

==== proftpd  ====
[http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] ([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer. 


==== php ====
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>80f92dd39a1c7e62c7b6c33e7ef215da2202cf7d</sha1>
  </revision>
  <revision>
    <id>609</id>
    <parentid>608</parentid>
    <timestamp>2012-01-29T21:46:22Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>d/perl: more detailled title (kind of vuln; affected slackware releases)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2728" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
==== httpd ====
CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

==== dhcp ====
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

==== openssl ====
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

==== proftpd  ====
[http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] ([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer. 


==== php ====
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>92436cd29b3e02450848575d22b864916740c307</sha1>
  </revision>
  <revision>
    <id>610</id>
    <parentid>609</parentid>
    <timestamp>2012-01-29T21:46:46Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* proftpd */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2797" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Upstream commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
==== httpd ====
CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

==== dhcp ====
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

==== openssl ====
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] ([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711]) ====

AFFECTED : -current : 1.3.3e, -13.37 : 1.3.3e, and all before

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

==== php ====
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>5ab10794291b1b83c3e0d055b768e470cbfe314b</sha1>
  </revision>
  <revision>
    <id>611</id>
    <parentid>610</parentid>
    <timestamp>2012-01-29T21:46:48Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <minor/>
    <comment>/* CVE-2011-2939 (DDoS, affected: current and stable) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2788" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
==== httpd ====
CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

==== dhcp ====
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

==== openssl ====
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] ([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711]) ====

AFFECTED : -current : 1.3.3e, -13.37 : 1.3.3e, and all before

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

==== php ====
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>a1f71bed1e6a4882c6fddd5f13d78d4021e3f822</sha1>
  </revision>
  <revision>
    <id>612</id>
    <parentid>611</parentid>
    <timestamp>2012-01-29T21:53:26Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <minor/>
    <comment>/* CVE-2011-4130 (proftpd bug tracker #3711) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2783" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
==== httpd ====
CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

==== dhcp ====
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

==== openssl ====
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])


Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

==== php ====
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>0c598f7a5d1bae042a8d7f2d4b6e217e333dc38e</sha1>
  </revision>
  <revision>
    <id>613</id>
    <parentid>612</parentid>
    <timestamp>2012-01-29T21:53:42Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <minor/>
    <comment>/* CVE-2011-4130 (Execute Code, affected : current, 13.37, and all before */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2784" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
==== httpd ====
CVE-2011-4415 CVE-2011-4317 CVE-2011-3607 CVE-2011-3368

==== dhcp ====
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

==== openssl ====
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])


Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

==== php ====
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>50edcf79fa8d5715422324cfe28924738ee59ef2</sha1>
  </revision>
  <revision>
    <id>620</id>
    <parentid>613</parentid>
    <timestamp>2012-01-30T10:32:26Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* httpd */ detail for httpd holes</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4224" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (OverflowGain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (CSRF , affected : current, 13.37 and all before) ====
Cross-site request forgery (CSRF) vulnerability in post_bug.cgi in Bugzilla 2.x, 3.x, and 4.x before 4.2rc1 allows remote attackers to hijack the authentication of arbitrary users for requests that create bug reports.

==== dhcp ====
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

==== openssl ====
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])


Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

==== php ====
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>8834dddba34557f51ba08dc8def86b0608b84797</sha1>
  </revision>
  <revision>
    <id>621</id>
    <parentid>620</parentid>
    <timestamp>2012-01-30T10:33:31Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <minor/>
    <comment>/* n */ typo in title header</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4218" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (OverflowGain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (CSRF , affected : current, 13.37 and all before) ====
Cross-site request forgery (CSRF) vulnerability in post_bug.cgi in Bugzilla 2.x, 3.x, and 4.x before 4.2rc1 allows remote attackers to hijack the authentication of arbitrary users for requests that create bug reports.

=== dhcp ===
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

=== openssl ===
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])


Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>adc62cb1f3ad637ddbd58e434ebe8b1895633b3d</sha1>
  </revision>
  <revision>
    <id>622</id>
    <parentid>621</parentid>
    <timestamp>2012-01-30T10:40:33Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* CVE-2011-3368 (CSRF , affected : current, 13.37 and all before) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4373" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (OverflowGain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

=== openssl ===
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])


Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
CVE-2011-4885 CVE-2011-3379

== x ==
libXfont : CVE-2011-2895

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>7541d0a0e07d600fcdd9658e422d7a09dd0a7bbf</sha1>
  </revision>
  <revision>
    <id>623</id>
    <parentid>622</parentid>
    <timestamp>2012-01-30T10:59:24Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>add libXfont cve-2011-2895</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5109" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (OverflowGain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

=== openssl ===
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])


Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
CVE-2011-4885 CVE-2011-3379

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute CodeOverflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>d9ed089975a7113ad63b95dc7b020e144f15dead</sha1>
  </revision>
  <revision>
    <id>624</id>
    <parentid>623</parentid>
    <timestamp>2012-01-30T11:07:08Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* php */ add cve-2001-3379 for php</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5425" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (OverflowGain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

=== openssl ===
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])


Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== CVE-2011-4885 CVE-2011-3379 (Denial Of Service, affected : current, 13.37 and all before ) ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute CodeOverflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>e28162a0c95682017d57f58c0483fc35bb57de05</sha1>
  </revision>
  <revision>
    <id>625</id>
    <parentid>624</parentid>
    <timestamp>2012-01-30T11:08:13Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <minor/>
    <comment>/* CVE-2011-4130 (Execute Code, affected : current, 13.37, and all before) */  typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5424" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (OverflowGain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

=== openssl ===
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== CVE-2011-4885 CVE-2011-3379 (Denial Of Service, affected : current, 13.37 and all before ) ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute CodeOverflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
pidgin : CVE-2011-4603 CVE-2011-4602 CVE-2011-4601 CVE-2011-3594 CVE-2011-3184 CVE-2011-2943</text>
    <sha1>8679b722622d5ace318d5057e78970a1108aab49</sha1>
  </revision>
  <revision>
    <id>626</id>
    <parentid>625</parentid>
    <timestamp>2012-01-30T17:31:45Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>details for pidgin</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8029" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (OverflowGain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

=== openssl ===
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== CVE-2011-4885 CVE-2011-3379 (Denial Of Service, affected : current, 13.37 and all before ) ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute CodeOverflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>db4427e5edfc1f4864d3f4db8fdfa05568fa72f5</sha1>
  </revision>
  <revision>
    <id>627</id>
    <parentid>626</parentid>
    <timestamp>2012-01-30T17:33:01Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8033" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

=== openssl ===
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== CVE-2011-4885 CVE-2011-3379 (Denial Of Service, affected : current, 13.37 and all before ) ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>80c30591c0c9cac9da871ff1337e4409d9f3189c</sha1>
  </revision>
  <revision>
    <id>628</id>
    <parentid>627</parentid>
    <timestamp>2012-01-30T17:51:15Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>seperate php CVEs</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8434" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
linux

== ap ==
cups : CVE-2011-3170 CVE-2011-2896

== d ==
=== perl === 
==== CVE-2011-2939 (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
CVE-2011-2705 CVE-2011-1004 CVE-2011-0188

== e ==
emacs

== l ==
t1lib : CVE-2011-1554 CVE-2011-1553 CVE-2011-1552 CVE-2011-0764

freetype2 : CVE-2011-0226

libxml2 : CVE-2011-1944

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
CVE-2011-4868 CVE-2011-4539 CVE-2011-2749 CVE-2011-2748

=== openssl ===
CVE-2012-0027 CVE-2011-4619 CVE-2011-4576 CVE-2011-4109 CVE-2011-4108 CVE-2011-3210

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>c46ed7954714ba2a87e086438455b45fc7caaa9f</sha1>
  </revision>
  <revision>
    <id>629</id>
    <parentid>628</parentid>
    <timestamp>2012-01-30T18:00:36Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>make more CVEs into links</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9398" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== linux ===

== ap ==
=== cups ===
[http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170]
[http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896]

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== l ==
=== t1lib ===
[http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554]
[http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553]
[http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552]
[http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764]

=== freetype2 ===
[http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226]

=== libxml2 ===
[http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944]

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
[http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868]
[http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539]
[http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749]
[http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748]

=== openssl ===
[http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027]
[http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619]
[http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576]
[http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109]
[http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108]
[http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210]

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>bee8431a0ad1bf4eb952b5044f7eb6bf3efb909c</sha1>
  </revision>
  <revision>
    <id>630</id>
    <parentid>629</parentid>
    <timestamp>2012-01-30T18:04:41Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>added freetype2 details</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9871" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== linux ===

== ap ==
=== cups ===
[http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170]
[http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896]

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== l ==
=== t1lib ===
[http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554]
[http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553]
[http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552]
[http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764]

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
[http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944]

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
[http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868]
[http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539]
[http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749]
[http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748]

=== openssl ===
[http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027]
[http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619]
[http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576]
[http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109]
[http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108]
[http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210]

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>b27a5364afeb1cde7203e638ec7fb7ecdfbe4497</sha1>
  </revision>
  <revision>
    <id>631</id>
    <parentid>630</parentid>
    <timestamp>2012-01-30T18:07:24Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>added libxml2 details</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10333" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== linux ===

== ap ==
=== cups ===
[http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170]
[http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896]

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== l ==
=== t1lib ===
[http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554]
[http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553]
[http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552]
[http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764]

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
[http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868]
[http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539]
[http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749]
[http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748]

=== openssl ===
[http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027]
[http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619]
[http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576]
[http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109]
[http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108]
[http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210]

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>d643d6acdc56db187626e083cc7bd92a8e493e8f</sha1>
  </revision>
  <revision>
    <id>632</id>
    <parentid>631</parentid>
    <timestamp>2012-01-30T18:15:00Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>added cups details</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11493" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
[http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554]
[http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553]
[http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552]
[http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764]

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
[http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868]
[http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539]
[http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749]
[http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748]

=== openssl ===
[http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027]
[http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619]
[http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576]
[http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109]
[http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108]
[http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210]

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>eaed92dc1535cf6a77c5e7008edab274ced43a12</sha1>
  </revision>
  <revision>
    <id>633</id>
    <parentid>632</parentid>
    <timestamp>2012-01-30T18:25:18Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>added t1lib details</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13039" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected : current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
[http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868]
[http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539]
[http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749]
[http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748]

=== openssl ===
[http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027]
[http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619]
[http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576]
[http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109]
[http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108]
[http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210]

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>fa4e9172b3d9ccd08af63d5f8c9d6b0886f8446b</sha1>
  </revision>
  <revision>
    <id>634</id>
    <parentid>633</parentid>
    <timestamp>2012-01-30T18:43:53Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>added openssl details</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14874" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected : current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
[http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868]
[http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539]
[http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749]
[http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748]

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected : current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected : current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected : current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] affected : current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected : current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected : current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>c06c63ce5c903dc4840e5ab9339001b0bbf0a483</sha1>
  </revision>
  <revision>
    <id>635</id>
    <parentid>634</parentid>
    <timestamp>2012-01-30T18:59:23Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>added dhcp details</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16120" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (DDoS, affected: current and stable) ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected : current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected : current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected : current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected : current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected : current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected : current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] affected : current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected : current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected : current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>11dcc13b63076cd95b7b4d746bf4be1dbfc924c8</sha1>
  </revision>
  <revision>
    <id>636</id>
    <parentid>635</parentid>
    <timestamp>2012-01-30T19:04:49Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16171" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected : current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected : current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected : current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected : current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected : current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected : current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected : current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] affected : current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected : current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected : current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>9b1e55073ae89294a45c67e6b3d7ceca4262e180</sha1>
  </revision>
  <revision>
    <id>637</id>
    <parentid>636</parentid>
    <timestamp>2012-01-30T19:26:27Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16191" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected : current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-1004 CVE-2011-1004]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected : current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected : current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected : current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected : current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected : current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected : current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] affected : current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected : current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected : current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>e1d2cf22eba17c095edb55f4caf921751d0f0d2b</sha1>
  </revision>
  <revision>
    <id>638</id>
    <parentid>637</parentid>
    <timestamp>2012-01-30T19:52:14Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* ruby */  remove cve-2011-1004 which does not affect slackware current, nore 1337, nore 13.1</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16135" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected : current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
[http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705]
[http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188]

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected : current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected : current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected : current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected : current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected : current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected : current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] affected : current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected : current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected : current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>fd5b38ed1336e63c6300be3fc5d0cb890549894b</sha1>
  </revision>
  <revision>
    <id>639</id>
    <parentid>638</parentid>
    <timestamp>2012-01-30T19:56:18Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* ruby */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17029" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected : current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected : current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] affect current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID. 

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of ServiceExecute Code) affect current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected : current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected : current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected : current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected : current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (DoS, affected : current, 13.37 and all before) ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges, affected : current, 13.37 and all before) ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] (affected : current, 13.37 and all before) ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected : current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected : current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected : current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected : current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected : current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected : current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] affected : current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected : current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected : current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code, affected : current, 13.37, and all before) ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected : current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected : current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow, current, 13.37 and all before) ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected : current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected : current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected : current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected : current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected : current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected : current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>1b2161e29449a9a21657e88d34c2ca490844cf2d</sha1>
  </revision>
  <revision>
    <id>640</id>
    <parentid>639</parentid>
    <timestamp>2012-01-30T22:58:14Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>minor changes for consistency</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17024" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID. 

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected: current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected: current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected: current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] affected: current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected: current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected: current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>dea72b9dc0f51ad7003cfb75a4a2f504d62e28d2</sha1>
  </revision>
  <revision>
    <id>641</id>
    <parentid>640</parentid>
    <timestamp>2012-01-31T07:29:48Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <minor/>
    <comment>/* CVE-2011-4109 affected: current, 13.37 through 11.0 */ - title: add "unspecified impact"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17045" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID. 

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected: current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected: current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected: current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] (unspecified impact) affected: current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected: current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected: current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>7635dac35ee810cdc9bcb759a89195c238f263b5</sha1>
  </revision>
  <revision>
    <id>642</id>
    <parentid>641</parentid>
    <timestamp>2012-01-31T07:33:18Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <minor/>
    <comment>/* CVE-2011-2705 affected: current, 13.37 and all before */ - title: classify as "PRNG weakness"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17060" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected: current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected: current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected: current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] (unspecified impact) affected: current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected: current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected: current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>fe879915f3ccd46208e0317962cfd18cd71d898f</sha1>
  </revision>
  <revision>
    <id>643</id>
    <parentid>642</parentid>
    <timestamp>2012-01-31T10:21:39Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>xap/mozilla-*: new; quick note</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17148" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected: current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected: current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected: current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] (unspecified impact) affected: current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected: current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected: current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-* ===
No specific CVE, you know they are vulnerable to at leas tone thing.</text>
    <sha1>304789e99d75babb2d3cebfcb31d71ee670ee340</sha1>
  </revision>
  <revision>
    <id>644</id>
    <parentid>643</parentid>
    <timestamp>2012-01-31T10:34:29Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>Turn mozilla-* into mozilla-firefox; add _some_ know issues (those fixed in ff9)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17605" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected: current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected: current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected: current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] (unspecified impact) affected: current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected: current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected: current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders. 

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions vulnerable) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>3fd729f9fd020edd8c1d8a4ef3fb08095863b464</sha1>
  </revision>
  <revision>
    <id>645</id>
    <parentid>644</parentid>
    <timestamp>2012-01-31T10:39:25Z</timestamp>
    <contributor>
      <username>Cccc828</username>
      <id>262</id>
    </contributor>
    <comment>/* n */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18090" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected: current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected: current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected: current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] (unspecified impact) affected: current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected: current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected: current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions vulnerable) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>1542f7def137c233d78a4fdee328a600dc5ad102</sha1>
  </revision>
</page>
<page arvcontinue="20120124194742|591">
  <title>User talk:Merge-delete</title>
  <ns>3</ns>
  <id>255</id>
  <revision>
    <id>614</id>
    <parentid>539</parentid>
    <timestamp>2012-01-30T03:52:30Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>moved [[User talk:Amanda27]] to [[User talk:Merge-delete]]: Automatically moved page while merging the user "[[User:Amanda27|Amanda27]]" to "[[User:Merge-delete|Merge-delete]]"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2344" xml:space="preserve">Boutique Hotels In India

Indulge yourself in sheer luxury throughout your remain in boutique hotels in India.[http://hotelslonavala.net/ hotels in lonavala] These are the places where one can live like rajas and maharajas. They're simply unique within their architecture and hang up where one can get highly personalized services inside a distinctive manner. They are heritage hotels that supply you with a unique connection with living existence.[http://hotelslonavala.net/ hotels in lonavala] Just opposite to western style hotels, these places permit you to know and have the wealthy culture and history of India.

 On a trip from the beaten tracks in India, you might find several boutique hotels where one can unwind yourself and also have home-cooked food. With enchanting folk music, amazing architecture, peace and exceptional hospitality, these hotels can bring alive the times of rajas and maharajas of older occasions. Their architecture, gardens, food and luxuries echo from the glorious past of India. Although you will find several hotels in India but when youre searching for best hotels, then certainly Rajasthan may be the condition that you need to visit whenever you arrived at India.

 You will find several havelis-converted-hotels in Rajasthan where you can unwind yourself and dip your senses in luxury. Remaining during these hotels is definitely an entirely different experience. Youll feel like you aren't nowadays. For experience a completely different lifestyle, you have to visit these hotels and spend your trip. Trust, youll possess a lifetime experience. The deserted great thing about Rajasthan and wealthy tradition enables you to definitely go through the luxury in simplicity. You no more have to pretend as possible be genuine and do what youve always loved.

 The best hotels in Rajasthan are Rawla Narlai, Raas Hotel, The Serai, Udai Kothi, Bhainsrorgarh and Devigarh. From the sights of those hotels, regal inside and grass to authentic antiques, lodging and fooding may be worth admiring. You seem like wandering within the deserts, going through the wonder, studying wealthy tradition, listening folk music and gorging on local meals. Several companies offer vacation packages to Rajasthan. Whenever you arrived at India, you just cant manage to miss these places. They feature glorious past of India.</text>
    <sha1>41ee596bca7edd95e7e87a4ae8e86d225025fc69</sha1>
  </revision>
</page>
<page arvcontinue="20120124194742|591">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>618</id>
    <parentid>583</parentid>
    <timestamp>2012-01-30T04:18:02Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>cpunches is not a regular</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1503" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Adioe3|adioe3]]
* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:Erik|erik]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]
* [[User:natex|natex]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>e392d1ec0ab6533f48eb63e226c1c296c8eee6b9</sha1>
  </revision>
  <revision>
    <id>619</id>
    <parentid>618</parentid>
    <timestamp>2012-01-30T04:19:41Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1503" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Adioe3|adioe3]]
* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[USer:codermaniac|codermaniac]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:Erik|erik]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[User:natex|natex]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>a6cb9ddfd5e967a7ca0605ff0c4b957843fa85ae</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Category:Security:SSA</title>
  <ns>14</ns>
  <id>264</id>
  <revision>
    <id>646</id>
    <parentid>645</parentid>
    <timestamp>2012-01-31T10:49:13Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>seamonkey</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18635" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected: current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected: current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected: current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] (unspecified impact) affected: current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected: current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected: current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== seamonkey (various issues, all versions impacted) ===

From http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html#seamonkey2.6, at LEAST:
Fixed in SeaMonkey 2.6:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>389e3eecd81d2d5bca61d749fe1b666797682c14</sha1>
  </revision>
  <revision>
    <id>647</id>
    <parentid>646</parentid>
    <timestamp>2012-01-31T10:53:36Z</timestamp>
    <contributor>
      <username>Adrien</username>
      <id>260</id>
    </contributor>
    <comment>mozilla-thunderbird</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19194" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== openssl ===
==== [http://cvedetails.com/cve/CVE-2012-0027 CVE-2012-0027] (Denial Of Service) affected: current, 13.37, and all before ====
The GOST ENGINE in OpenSSL before 1.0.0f does not properly handle invalid parameters for the GOST block cipher, which allows remote attackers to cause a denial of service (daemon crash) via crafted data from a TLS client.

==== [http://cvedetails.com/cve/CVE-2011-4619 CVE-2011-4619] (Denial Of Service) affected: current, 13.37, and all before ====
The Server Gated Cryptography (SGC) implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly handle handshake restarts, which allows remote attackers to cause a denial of service via unspecified vectors.

==== [http://cvedetails.com/cve/CVE-2011-4576 CVE-2011-4576] (Obtain Information) affected: current, 13.37, and all before ====
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does not properly initialize data structures for block cipher padding, which might allow remote attackers to obtain sensitive information by decrypting the padding data sent by an SSL peer.

==== [http://cvedetails.com/cve/CVE-2011-4109 CVE-2011-4109] (unspecified impact) affected: current, 13.37 through 11.0 ====
Double free vulnerability in OpenSSL 0.9.8 before 0.9.8s, when X509_V_FLAG_POLICY_CHECK is enabled, allows remote attackers to have an unspecified impact by triggering failure of a policy check.

==== [http://cvedetails.com/cve/CVE-2011-4108 CVE-2011-4108] affected: current, 13.37, and all before ====
The DTLS implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f performs a MAC check only if certain padding is valid, which makes it easier for remote attackers to recover plaintext via a padding oracle attack.

==== [http://cvedetails.com/cve/CVE-2011-3210 CVE-2011-3210] (Denial Of Service) affected: current, 13.37 through 11.0 ====
The ephemeral ECDH ciphersuite functionality in OpenSSL 0.9.8 through 0.9.8r and 1.0.x before 1.0.0e does not ensure thread safety during processing of handshake messages from clients, which allows remote attackers to cause a denial of service (daemon crash) via out-of-order messages that violate the TLS protocol.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== mozilla-thunderbird (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/thunderbird.html#thunderbird9, at LEAST:

Fixed in Thunderbird 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== seamonkey (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html#seamonkey2.6, at LEAST:

Fixed in SeaMonkey 2.6:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>0f1acb17056835664f8a03a87481a827f5c42013</sha1>
  </revision>
  <revision>
    <id>648</id>
    <parentid>647</parentid>
    <timestamp>2012-02-03T08:58:30Z</timestamp>
    <contributor>
      <username>Asteroid</username>
      <id>259</id>
    </contributor>
    <comment>/* openssl */  OpenSSL up to date on february, 02 2012</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16991" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== freetype2 ===
==== [http://cvedetails.com/cve/CVE-2011-0226 CVE-2011-0226] (Denial Of Service, Execute Code, Memory corruption) affected: current, 13.37 and all before ====
Integer signedness error in psaux/t1decode.c in FreeType before 2.4.6, as used in CoreGraphics in Apple iOS before 4.2.9 and 4.3.x before 4.3.4 and other products, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted Type 1 font in a PDF document, as exploited in the wild in July 2011.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== mozilla-thunderbird (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/thunderbird.html#thunderbird9, at LEAST:

Fixed in Thunderbird 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== seamonkey (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html#seamonkey2.6, at LEAST:

Fixed in SeaMonkey 2.6:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>ad1e1868e4027f4dcc99800065c9a07646812a49</sha1>
  </revision>
  <revision>
    <id>649</id>
    <parentid>648</parentid>
    <timestamp>2012-02-04T02:34:56Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>freetype2 up to date</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="16444" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== httpd ===
==== [http://cvedetails.com/cve/CVE-2011-4415 CVE-2011-4415] (Denial Of Service) affected: current, 13.37 and all before ====
The ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, does not restrict the size of values of environment variables, which allows local users to cause a denial of service (memory consumption or NULL pointer dereference) via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, related to (1) the "len +=" statement and (2) the apr_pcalloc function call, a different vulnerability than CVE-2011-3607. 

==== [http://cvedetails.com/cve/CVE-2011-3607 CVE-2011-3607] (Overflow, Gain privileges) affected: current, 13.37 and all before ====
Integer overflow in the ap_pregsub function in server/util.c in the Apache HTTP Server 2.0.x through 2.0.64 and 2.2.x through 2.2.21, when the mod_setenvif module is enabled, allows local users to gain privileges via a .htaccess file with a crafted SetEnvIf directive, in conjunction with a crafted HTTP request header, leading to a heap-based buffer overflow. 

==== [http://cvedetails.com/cve/CVE-2011-3368 CVE-2011-3368] affected: current, 13.37 and all before ====
The mod_proxy module in the Apache HTTP Server 1.3.x through 1.3.42, 2.0.x through 2.0.64, and 2.2.x through 2.2.21 does not properly interact with use of (1) RewriteRule and (2) ProxyPassMatch pattern matches for configuration of a reverse proxy, which allows remote attackers to send requests to intranet servers via a malformed URI containing an initial @ (at sign) character.

=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== mozilla-thunderbird (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/thunderbird.html#thunderbird9, at LEAST:

Fixed in Thunderbird 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== seamonkey (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html#seamonkey2.6, at LEAST:

Fixed in SeaMonkey 2.6:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>460ebf65b951d572ed92f4e51c85ae58aab34f38</sha1>
  </revision>
  <revision>
    <id>650</id>
    <parentid>649</parentid>
    <timestamp>2012-02-10T14:28:17Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>httpd up to date</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14767" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== proftpd  ===
==== [http://cvedetails.com/cve/CVE-2011-4130 CVE-2011-4130] (Execute Code) affected: current, 13.37, and all before ====
([http://bugs.proftpd.org/show_bug.cgi?id=3711 proftpd bug tracker #3711])

Use-after-free vulnerability in the Response API in ProFTPD '''before 1.3.3g''' allows remote authenticated users to execute arbitrary code via vectors involving an error that occurs after an FTP data transfer.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== mozilla-thunderbird (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/thunderbird.html#thunderbird9, at LEAST:

Fixed in Thunderbird 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== seamonkey (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html#seamonkey2.6, at LEAST:

Fixed in SeaMonkey 2.6:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>325c355c4736c26fff473944faf2965cbbe2a3f2</sha1>
  </revision>
  <revision>
    <id>651</id>
    <parentid>650</parentid>
    <timestamp>2012-02-10T14:28:47Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>proftpd up to date</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14340" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

=== php ===
==== [http://cvedetails.com/cve/CVE-2011-4885 CVE-2011-4885] (Denial Of Service) affected: current, 13.37 and all before ====
PHP before 5.3.9 computes hash values for form parameters without restricting the ability to trigger hash collisions predictably, which allows remote attackers to cause a denial of service (CPU consumption) by sending many crafted parameters.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== mozilla-thunderbird (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/thunderbird.html#thunderbird9, at LEAST:

Fixed in Thunderbird 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== seamonkey (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html#seamonkey2.6, at LEAST:

Fixed in SeaMonkey 2.6:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>874770e79960ec5863254d7cb00aa7ead5483866</sha1>
  </revision>
  <revision>
    <id>652</id>
    <parentid>651</parentid>
    <timestamp>2012-02-10T14:29:23Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>php up to date</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13958" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.

=== mozilla-firefox (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/firefox.html#firefox9, at LEAST:

Fixed in Firefox 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== mozilla-thunderbird (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/thunderbird.html#thunderbird9, at LEAST:

Fixed in Thunderbird 9:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)

=== seamonkey (various issues, all versions impacted) ===
From http://www.mozilla.org/security/known-vulnerabilities/seamonkey.html#seamonkey2.6, at LEAST:

Fixed in SeaMonkey 2.6:
*MFSA 2011-58 Crash scaling &lt;video&gt; to extreme sizes
*MFSA 2011-57 Crash when plugin removes itself on Mac OS X
*MFSA 2011-56 Key detection without JavaScript via SVG animation
*MFSA 2011-55 nsSVGValue out-of-bounds access
*MFSA 2011-54 Potentially exploitable crash in the YARR regular expression library
*MFSA 2011-53 Miscellaneous memory safety hazards (rv:9.0)</text>
    <sha1>17420e6eb3400c211e5b033e79f0304ddbb7c48e</sha1>
  </revision>
  <revision>
    <id>653</id>
    <parentid>652</parentid>
    <timestamp>2012-02-10T14:30:07Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>mozilla-* up to date</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12309" xml:space="preserve">Slackware has recently started to be inactive. At the same time, a number of security issues have been found in various components. This page aims at listing them in order to help everyone know which components have known vulnerabilities.

The list below is provided as-is. It is meant to be as good as possible but we can't guarantee anything. It is sorted by slackware categories: a/, ap/, d/, ...

A more comprehensive effort might appear at some point in the future (binary packages?) but this is currently only a list of packages and their CVEs when applicable and useful. In some cases, we consider pointing out a specific CVE is not useful because of the number of issues (i.e. get the last version; e.g. mozilla-*).

The CVEs are typically listed as follow:
${SUMMARY}
* Fix:
** Fixed upstream on: ${DATE}
** Available in version: ${UPSTREAM_VERSION_WITH_FIX} (-current ${VERSION_IN_CURRENT}; -stable: ${VERSION_IN_13_37})
** Upstream commit: ${URL_TO_THE_SPECIFIC_FIX_COMMIT}

== a ==
=== cups ===
==== [http://cvedetails.com/cve/CVE-2011-3170 CVE-2011-3170] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The gif_read_lzw function in filter/image-gif.c in CUPS 1.4.8 and earlier does not properly handle the first code word in an LZW stream, which allows remote attackers to trigger a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted stream, a different vulnerability than CVE-2011-2896. 

==== [http://cvedetails.com/cve/CVE-2011-2896 CVE-2011-2896] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895. 

== d ==
=== perl === 
==== [http://cvedetails.com/cve/CVE-2011-2939 CVE-2011-2939] (Denial Of Service, Overflow, Memory corruption) affected: current, 13.37 through 10.0 ====
Off-by-one error in the decode_xs function in Unicode/Unicode.xs in the Encode module before 2.44, as used in Perl before 5.15.6, might allow context-dependent attackers to cause a denial of service (memory corruption) via a crafted Unicode string, which triggers a heap-based buffer overflow [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2939 (on cve.mitre.org)].
* Fix:
** Fixed upstream on: Tue, 9 Aug 2011
** Available in version: 5.14.2 (-current: 5.14.0; -stable: 5.12.3)
** Commit: http://perl5.git.perl.org/perl.git/commitdiff/e46d973584785af1f445c4dedbee4243419cb860#patch5

=== ruby ===
==== [http://cvedetails.com/cve/CVE-2011-2705 CVE-2011-2705] (PRNG weakness) affected: current, 13.37 and all before ====
The SecureRandom.random_bytes function in lib/securerandom.rb in Ruby before 1.8.7-p352 and 1.9.x before 1.9.2-p290 relies on PID values for initialization, which makes it easier for context-dependent attackers to predict the result string by leveraging knowledge of random strings obtained in an earlier process with the same PID.

==== [http://cvedetails.com/cve/CVE-2011-0188 CVE-2011-0188] (Denial Of Service, Execute Code) affected: current, 13.37 and all before ====
The VpMemAlloc function in bigdecimal.c in the BigDecimal class in Ruby 1.9.2-p136 and earlier, as used on Apple Mac OS X before 10.6.7 and other platforms, does not properly allocate memory, which allows context-dependent attackers to execute arbitrary code or cause a denial of service (application crash) via vectors involving creation of a large BigDecimal value within a 64-bit process, related to an "integer truncation issue."

== e ==
=== emacs ===

== k ==
=== kernel ===

== l ==
=== t1lib ===
==== [http://cvedetails.com/cve/CVE-2011-1554 CVE-2011-1554] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
Off-by-one error in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory read, integer overflow, and invalid pointer dereference, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1553 CVE-2011-1553] (Denial Of Service) affected: current, 13.37 and all before ====
Use-after-free vulnerability in t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, allows remote attackers to cause a denial of service (application crash) via a PDF document containing a crafted Type 1 font that triggers an invalid memory write, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-1552 CVE-2011-1552] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, reads from invalid memory locations, which allows remote attackers to cause a denial of service (application crash) via a crafted Type 1 font in a PDF document, a different vulnerability than CVE-2011-0764.

==== [http://cvedetails.com/cve/CVE-2011-0764 CVE-2011-0764] (Execute Code) affected: current, 13.37 and all before ====
t1lib 5.1.2 and earlier, as used in Xpdf before 3.02pl6 and other products, uses an invalid pointer in conjunction with a dereference operation, which allows remote attackers to execute arbitrary code via a crafted Type 1 font in a PDF document, as demonstrated by testz.2184122398.pdf.

=== libxml2 ===
==== [http://cvedetails.com/cve/CVE-2011-1944 CVE-2011-1944] (Denial Of Service, Execute Code, Overflow) affected: current, 13.37 and all before ====
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted XML file that triggers a heap-based buffer overflow when adding a new namespace node, related to handling of XPath expressions. 

== n ==
=== dhcp ===
==== [http://cvedetails.com/cve/CVE-2011-4868 CVE-2011-4868] (Denial Of Service) affected: current, 13.37, and all before ====
The logging functionality in dhcpd in ISC DHCP before 4.2.3-P2, when using Dynamic DNS (DDNS) and issuing IPv6 addresses, does not properly handle the DHCPv6 lease structure, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via crafted packets related to a lease-status update.

==== [http://cvedetails.com/cve/CVE-2011-4539 CVE-2011-4539] (Denial Of Service) affected: current, 13.37, 13.1 ====
dhcpd in ISC DHCP 4.x before 4.2.3-P1 and 4.1-ESV before 4.1-ESV-R4 does not properly handle regular expressions in dhcpd.conf, which allows remote attackers to cause a denial of service (daemon crash) via a crafted request packet.

==== [http://cvedetails.com/cve/CVE-2011-2749 CVE-2011-2749] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted BOOTP packet.

==== [http://cvedetails.com/cve/CVE-2011-2748 CVE-2011-2748] (Denial Of Service) affected: current, 13.37, and all before ====
The server in ISC DHCP 3.x and 4.x before 4.2.2, 3.1-ESV before 3.1-ESV-R3, and 4.1-ESV before 4.1-ESV-R3 allows remote attackers to cause a denial of service (daemon exit) via a crafted DHCP packet.

==== [http://cvedetails.com/cve/CVE-2011-3379 CVE-2011-3379] (Execute Code) affected: current, 13.37 through 12.0 ====
The is_a function in PHP 5.3.7 and 5.3.8 triggers a call to the __autoload function, which makes it easier for remote attackers to execute arbitrary code by providing a crafted URL and leveraging potentially unsafe behavior in certain PEAR packages and custom autoloaders.

=== curl ===
==== [http://curl.haxx.se/docs/adv_20120124.html CVE-2012-0036] (Execute Code) affected: current, and all before ====
curl is vulnerable to a data injection attack for certain protocols through control characters embedded or percent-encoded in URLs.

==== [http://curl.haxx.se/docs/adv_20120124B.html CVE-2011-3389] (man-in-the-middle attacks) affected: current, 13.37 ====
curl is vulnerable to a SSL CBC IV vulnerability when built to use OpenSSL for the SSL/TLS layer.

== x ==
=== libXfont ===
==== [http://cvedetails.com/cve/CVE-2011-2895 CVE-2011-2895] (Execute Code, Overflow) affected: current, 13.37 and all before ====
The LZW decompressor in (1) the BufCompressedFill function in fontfile/decompress.c in X.Org libXfont before 1.4.4 and (2) compress/compress.c in 4.3BSD, as used in zopen.c in OpenBSD before 3.8, FreeBSD, NetBSD 4.0.x and 5.0.x before 5.0.3 and 5.1.x before 5.1.1, FreeType 2.1.9, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows context-dependent attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2896.

== xap ==
=== pidgin ===
====  [http://cvedetails.com/cve/CVE-2011-4603 CVE-2011-4603] (Denial Of Service) affected: current, 13.37 and all before ====
The silc_channel_message function in ops.c in the SILC protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted message, a different vulnerability than CVE-2011-3594.

==== [http://cvedetails.com/cve/CVE-2011-4602 CVE-2011-4602] (Denial Of Service) affected: current, 13.37 and all before ====
The XMPP protocol plugin in libpurple in Pidgin before 2.10.1 does not properly handle missing fields in (1) voice-chat and (2) video-chat stanzas, which allows remote attackers to cause a denial of service (application crash) via a crafted message.

==== [http://cvedetails.com/cve/CVE-2011-4601 CVE-2011-4601] (Denial Of Service) affected: current, 13.37 and all before ====
family_feedbag.c in the oscar protocol plugin in libpurple in Pidgin before 2.10.1 does not perform the expected UTF-8 validation on message data, which allows remote attackers to cause a denial of service (application crash) via a crafted (1) AIM or (2) ICQ message associated with buddy-list addition.

==== [http://cvedetails.com/cve/CVE-2011-3594 CVE-2011-3594] (Denial Of Service, Overflow) affected: current, 13.37 and all before ====
The g_markup_escape_text function in the SILC protocol plug-in in libpurple 2.10.0 and earlier, as used in Pidgin and possibly other products, allows remote attackers to cause a denial of service (crash) via invalid UTF-8 sequences that trigger use of invalid pointers and an out-of-bounds read, related to interactions with certain versions of glib2.

==== [http://cvedetails.com/cve/CVE-2011-3184 CVE-2011-3184] (Denial Of Service) affected: current, 13.37 and all before ====
The msn_httpconn_parse_data function in httpconn.c in the MSN protocol plugin in libpurple in Pidgin before 2.10.0 does not properly handle HTTP 100 responses, which allows remote attackers to cause a denial of service (incorrect memory access and application crash) via vectors involving a crafted server message.

==== [http://cvedetails.com/cve/CVE-2011-2943 CVE-2011-2943] (Denial Of Service) affected: current, 13.37 and all before ====
The irc_msg_who function in msgs.c in the IRC protocol plugin in libpurple 2.8.0 through 2.9.0 in Pidgin before 2.10.0 does not properly validate characters in nicknames, which allows user-assisted remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a crafted nickname that is not properly handled in a WHO response.</text>
    <sha1>99ba4909f45381b03898a07fa88371a205c941a0</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Third Party Package Managers</title>
  <ns>0</ns>
  <id>170</id>
  <revision>
    <id>658</id>
    <parentid>198</parentid>
    <timestamp>2012-03-17T03:09:21Z</timestamp>
    <contributor>
      <username>Vegasseo</username>
      <id>268</id>
    </contributor>
    <comment>/* Purpose */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10379" xml:space="preserve">= Purpose =

The mere mention of third party package managers (such as [http://software.jaos.org/#slapt-get slapt-get] and [http://swaret.sourceforge.net/ swaret]) often results in a quick admonishment from Slackware users, and unfortunately, the only reason given in most cases is something along the lines of "they'll break your system."  This leaves users in a state of confusion, as the respective web sites of these third party tools tout them as an improvement.  The purpose of this page is to explain why and how these tools will often result in system breakage[http://www.bobsseo.com .]

= Overview of Slackware's Native Package Tools =

Slackware's native package management utilities (&lt;tt&gt;pkgtool(8)&lt;/tt&gt;, &lt;tt&gt;installpkg(8)&lt;/tt&gt;, &lt;tt&gt;removepkg(8)&lt;/tt&gt;, and &lt;tt&gt;upgradepkg(8)&lt;/tt&gt;) do not support any form of dependency checking.  A Slackware package is essentially a compressed tarball of the files associated with an application, a file containing a short description of the application (&lt;tt&gt;./install/slack-desc&lt;/tt&gt;), and a script that performs some essential post-installation tasks (&lt;tt&gt;./install/doinst.sh&lt;/tt&gt;).  Installing a Slackware package simply copies those files to the filesystem and then executes the post-install script, while removing the package removes the files and reverses the post-install script.  As result, there is no guarantee that libraries and other files needed by a particular package are already present on the system when that particular package is installed.

= Overview of Selected Third Party Tools =

As stated above, Slackware's native package management suite neither has nor supports dependency resolution.  Because the third-party add-ons all use Slackware's native package tools, they are bound by this same limitation, at least to some extent, but some of them try to mitigate this in various ways; the following is an overview.


== swaret ==

=== Overview ===

Swaret makes use of an unofficial file that tries to list all package dependencies based on output of &lt;tt&gt;ldd(1)&lt;/tt&gt;.  The idea is that by running &lt;tt&gt;ldd(1)&lt;/tt&gt; on some binary or shared object, you can see what that file is linked to, and then see what package(s) contain those files, and then install those packages.  

=== Potential Problems ===

Since some library developers don't see the need to update their shared object version strings when making changes that are incompatible with the previous release, it's easy to need a newer release of some package but for swaret to not be able to determine this.
Since swaret is meant for upgrading packages, it will fail to roll back a package's version number if this occurs in the upstream Slackware tree for some reason.


== slapt-get ==

=== Overview ===

Slapt-get makes use of additional files (&lt;tt&gt;slack-required&lt;/tt&gt;, &lt;tt&gt;slack-suggests&lt;/tt&gt;, &lt;tt&gt;slack-conflicts&lt;/tt&gt;) inside a Slackware package.  Essentially, if a package is listed in &lt;tt&gt;slack-required&lt;/tt&gt;, then slapt-get will install or upgrade it first; if a package is listed in &lt;tt&gt;slack-conflicts&lt;/tt&gt;, then slapt-get will remove it first; if a package is listed in &lt;tt&gt;slack-suggests&lt;/tt&gt;, then slapt-get will offer to install it in addition to the packages noted in &lt;tt&gt;slack-required&lt;/tt&gt;.

=== Potential Problems ===

Since official Slackware packages do not have the &lt;tt&gt;slack-required&lt;/tt&gt; and other files needed for slapt-get to determine dependencies, it is not able to resolve dependencies for them.  Therefore, slapt-get's perceived usefulness is in keeping unofficial third-party packages (or at least those which do contain the necessary files) up to date.  See the discussion below for more information on unofficial third-party packages.
Also, slapt-get, like swaret, will not "downgrade" a package to a previous version if it occurs in the upstream Slackware tree.

== sbopkg ==

=== Overview ===

[http://www.sbopkg.org/ SBopkg] is a tool for automating the download, compile and package build for SBo projects hosted in the [http://www.slackbuilds.org SlackBuilds.org ] repository.  SBo packages are reviewed by team members for completeness as well as applicability to each Slackware release.  SBo package documentation includes information regarding dependencies.

= Third Party (Unofficial) Packages =

This subject can elicit opinions just as strong as the topic of third-party package managers, and there are knowledgeable people on both sides of the issue.  Third party packages can obviously present a security risk, as there's no way to know what's really in them, but for the average user, there are (amazingly enough) bigger concerns.  On one hand, the user wants a package of some application that's not included with Slackware, but he doesn't want it to create other problems.  Oftentimes, third party packages are not built on "clean" systems -- that is, the computer on which they're built has quite a few other non-official packages installed -- so the resulting package needs those other things to work properly.  If the packager doesn't make note of all the different packages that this one depends on, the user installs it only to find that it still doesn't work.  Even worse, those other dependencies are often not even necessary if the package is built on a clean system - if the other package had not been present, the new one obviously wouldn't have linked against it.  
Installing third party packages from two different packagers can cause problems.  Package A might depend on Package B, which depends on Package C and optionally Package D.  If the person who built Package B only linked it against Package C (not D), but the Package A expects Package B to have both Package C and Package D dependencies, then Package A may not work, even though you (think you) have everything it needs installed.
Another frequent problem with third party packages is encountered by replacing stock (official) packages with unofficial ones.  In addition to the library version issues mentioned in the swaret discussion, newer package versions often require newer versions of other packages, which might require newer versions of still other packages, and before you know it, you have replaced a sizable portion of the official Slackware packages.  If/when something breaks, you will find it very difficult to find someone willing to help you, as there's no way to know how much effect the unofficial packages are having.


= Slackware -current =

Slackware -current is *not* a stable release of Slackware.  It is intended for advanced users who are familiar with how Slackware works to test (and report success/failure, find and fix bugs, etcetera) the new packages leading to the next stable release of Slackware.  Packages are constantly being added, removed, split up, merged, and otherwise mangled, and third party package managers (swaret/slapt-get/et al) should not be expected to know how to deal with this.  If you use one of those tools while trying to run Slackware -current and you don't understand how they work and their limitations, you *will* break your system and you will *not* have much luck finding someone who is sympathetic.  You have been warned.

You may be wondering why these tools have trouble with -current.  I won't even attempt to detail all of the potential issues, but here are a couple:
1. When upgrading to -current with one of these tools, the package sets are upgraded in alphabetical order (and the packages therein also in alphabetical order).  This means that a/bash will be upgraded before a/glibc-solibs.  If bash has been recompiled against newer glibc, and you upgrade to that new version, it will promptly stop working due to the fact that the needed version of glibc has not been upgraded yet; at that point, you are stuck with a "chicken and egg" problem.
2. Third party package tools will not install *new* packages that have been added in Slackware -current.  This is not a bug - it's a feature; if you purposefully didn't install something, then you don't want your automatic package updater reinstalling it.  However, when a package depends on something else that has been added or split out of an existing package, and your add-on package manager upgrades the existing package but doesn't install the added one, then the (upgraded) existing package will not work any more.


= Solutions and Suggestions =

For upgrading to Slackware -current, there is only *one* supported method: &lt;tt&gt;UPGRADE.TXT&lt;/tt&gt;  --  you can find this file on any Slackware mirror.  Note that this is also the only supported method to upgrade from one stable release of Slackware to another.

For keeping up to date on post-release patches added to a stable release of Slackware, you will *usually* be okay to use one of the third party package managers.  You should still read the &lt;tt&gt;ChangeLog.txt&lt;/tt&gt; before doing any upgrades, though, as new packages are occasionally added in /patches when circumstances require it.

For software not included in official Slackware, consider building it yourself or using a SlackBuild script from one of the projects which provides them.

One of the regular Slackware contributors, PiterPUNK, wrote and maintains a third-party package manager that minimizes all of the risks mentioned above.  [http://slackpkg.org Slackpkg] does not support downloading or installing unofficial packages, and it has provisions to install any added packages and uninstall any removed packages as well as the normal install/upgrade/remove routines.

Another third party package manager that promotes good practices is [http://slackroll.sourceforge.net/ SlackRoll] (see [[SlackRoll Tutorial|tutorial]]). Its philosophy is similar to that of Slackpkg but it is not included as part of Slackware. Programmed in Python, it is faster, has more features and detects more events from Slackware -current. However, the initial setup and workflow are a bit more complex.

= See Also =

* &lt;tt&gt;pkgtool(8)&lt;/tt&gt; -- man 8 pkgtool
* &lt;tt&gt;installpkg(8)&lt;/tt&gt; -- man 8 installpkg
* &lt;tt&gt;removepkg(8)&lt;/tt&gt; -- man 8 removepkg
* &lt;tt&gt;upgradepkg(8)&lt;/tt&gt; -- man 8 upgradepkg
* &lt;tt&gt;makepkg(8)&lt;/tt&gt; -- man 8 makepkg
* &lt;tt&gt;explodepkg(8)&lt;/tt&gt; -- man 8 explodepkg


= TODO =

* Add links to other wiki pages that are related to this topic (add to "See Also" above)
* Add hyperlinks to slapt-get, swaret, and other projects mentioned on this page
* Others?

[[Category:Information]]
[[Category:Tutorials]]</text>
    <sha1>88722135f2668827f33b5fbe260080d8a6a4dff5</sha1>
  </revision>
  <revision>
    <id>659</id>
    <parentid>658</parentid>
    <timestamp>2012-03-17T18:24:51Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Vegasseo|Vegasseo]] ([[User talk:Vegasseo|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10354" xml:space="preserve">= Purpose =

The mere mention of third party package managers (such as [http://software.jaos.org/#slapt-get slapt-get] and [http://swaret.sourceforge.net/ swaret]) often results in a quick admonishment from Slackware users, and unfortunately, the only reason given in most cases is something along the lines of "they'll break your system."  This leaves users in a state of confusion, as the respective web sites of these third party tools tout them as an improvement.  The purpose of this page is to explain why and how these tools will often result in system breakage.

= Overview of Slackware's Native Package Tools =

Slackware's native package management utilities (&lt;tt&gt;pkgtool(8)&lt;/tt&gt;, &lt;tt&gt;installpkg(8)&lt;/tt&gt;, &lt;tt&gt;removepkg(8)&lt;/tt&gt;, and &lt;tt&gt;upgradepkg(8)&lt;/tt&gt;) do not support any form of dependency checking.  A Slackware package is essentially a compressed tarball of the files associated with an application, a file containing a short description of the application (&lt;tt&gt;./install/slack-desc&lt;/tt&gt;), and a script that performs some essential post-installation tasks (&lt;tt&gt;./install/doinst.sh&lt;/tt&gt;).  Installing a Slackware package simply copies those files to the filesystem and then executes the post-install script, while removing the package removes the files and reverses the post-install script.  As result, there is no guarantee that libraries and other files needed by a particular package are already present on the system when that particular package is installed.

= Overview of Selected Third Party Tools =

As stated above, Slackware's native package management suite neither has nor supports dependency resolution.  Because the third-party add-ons all use Slackware's native package tools, they are bound by this same limitation, at least to some extent, but some of them try to mitigate this in various ways; the following is an overview.


== swaret ==

=== Overview ===

Swaret makes use of an unofficial file that tries to list all package dependencies based on output of &lt;tt&gt;ldd(1)&lt;/tt&gt;.  The idea is that by running &lt;tt&gt;ldd(1)&lt;/tt&gt; on some binary or shared object, you can see what that file is linked to, and then see what package(s) contain those files, and then install those packages.  

=== Potential Problems ===

Since some library developers don't see the need to update their shared object version strings when making changes that are incompatible with the previous release, it's easy to need a newer release of some package but for swaret to not be able to determine this.
Since swaret is meant for upgrading packages, it will fail to roll back a package's version number if this occurs in the upstream Slackware tree for some reason.


== slapt-get ==

=== Overview ===

Slapt-get makes use of additional files (&lt;tt&gt;slack-required&lt;/tt&gt;, &lt;tt&gt;slack-suggests&lt;/tt&gt;, &lt;tt&gt;slack-conflicts&lt;/tt&gt;) inside a Slackware package.  Essentially, if a package is listed in &lt;tt&gt;slack-required&lt;/tt&gt;, then slapt-get will install or upgrade it first; if a package is listed in &lt;tt&gt;slack-conflicts&lt;/tt&gt;, then slapt-get will remove it first; if a package is listed in &lt;tt&gt;slack-suggests&lt;/tt&gt;, then slapt-get will offer to install it in addition to the packages noted in &lt;tt&gt;slack-required&lt;/tt&gt;.

=== Potential Problems ===

Since official Slackware packages do not have the &lt;tt&gt;slack-required&lt;/tt&gt; and other files needed for slapt-get to determine dependencies, it is not able to resolve dependencies for them.  Therefore, slapt-get's perceived usefulness is in keeping unofficial third-party packages (or at least those which do contain the necessary files) up to date.  See the discussion below for more information on unofficial third-party packages.
Also, slapt-get, like swaret, will not "downgrade" a package to a previous version if it occurs in the upstream Slackware tree.

== sbopkg ==

=== Overview ===

[http://www.sbopkg.org/ SBopkg] is a tool for automating the download, compile and package build for SBo projects hosted in the [http://www.slackbuilds.org SlackBuilds.org ] repository.  SBo packages are reviewed by team members for completeness as well as applicability to each Slackware release.  SBo package documentation includes information regarding dependencies.

= Third Party (Unofficial) Packages =

This subject can elicit opinions just as strong as the topic of third-party package managers, and there are knowledgeable people on both sides of the issue.  Third party packages can obviously present a security risk, as there's no way to know what's really in them, but for the average user, there are (amazingly enough) bigger concerns.  On one hand, the user wants a package of some application that's not included with Slackware, but he doesn't want it to create other problems.  Oftentimes, third party packages are not built on "clean" systems -- that is, the computer on which they're built has quite a few other non-official packages installed -- so the resulting package needs those other things to work properly.  If the packager doesn't make note of all the different packages that this one depends on, the user installs it only to find that it still doesn't work.  Even worse, those other dependencies are often not even necessary if the package is built on a clean system - if the other package had not been present, the new one obviously wouldn't have linked against it.  
Installing third party packages from two different packagers can cause problems.  Package A might depend on Package B, which depends on Package C and optionally Package D.  If the person who built Package B only linked it against Package C (not D), but the Package A expects Package B to have both Package C and Package D dependencies, then Package A may not work, even though you (think you) have everything it needs installed.
Another frequent problem with third party packages is encountered by replacing stock (official) packages with unofficial ones.  In addition to the library version issues mentioned in the swaret discussion, newer package versions often require newer versions of other packages, which might require newer versions of still other packages, and before you know it, you have replaced a sizable portion of the official Slackware packages.  If/when something breaks, you will find it very difficult to find someone willing to help you, as there's no way to know how much effect the unofficial packages are having.


= Slackware -current =

Slackware -current is *not* a stable release of Slackware.  It is intended for advanced users who are familiar with how Slackware works to test (and report success/failure, find and fix bugs, etcetera) the new packages leading to the next stable release of Slackware.  Packages are constantly being added, removed, split up, merged, and otherwise mangled, and third party package managers (swaret/slapt-get/et al) should not be expected to know how to deal with this.  If you use one of those tools while trying to run Slackware -current and you don't understand how they work and their limitations, you *will* break your system and you will *not* have much luck finding someone who is sympathetic.  You have been warned.

You may be wondering why these tools have trouble with -current.  I won't even attempt to detail all of the potential issues, but here are a couple:
1. When upgrading to -current with one of these tools, the package sets are upgraded in alphabetical order (and the packages therein also in alphabetical order).  This means that a/bash will be upgraded before a/glibc-solibs.  If bash has been recompiled against newer glibc, and you upgrade to that new version, it will promptly stop working due to the fact that the needed version of glibc has not been upgraded yet; at that point, you are stuck with a "chicken and egg" problem.
2. Third party package tools will not install *new* packages that have been added in Slackware -current.  This is not a bug - it's a feature; if you purposefully didn't install something, then you don't want your automatic package updater reinstalling it.  However, when a package depends on something else that has been added or split out of an existing package, and your add-on package manager upgrades the existing package but doesn't install the added one, then the (upgraded) existing package will not work any more.


= Solutions and Suggestions =

For upgrading to Slackware -current, there is only *one* supported method: &lt;tt&gt;UPGRADE.TXT&lt;/tt&gt;  --  you can find this file on any Slackware mirror.  Note that this is also the only supported method to upgrade from one stable release of Slackware to another.

For keeping up to date on post-release patches added to a stable release of Slackware, you will *usually* be okay to use one of the third party package managers.  You should still read the &lt;tt&gt;ChangeLog.txt&lt;/tt&gt; before doing any upgrades, though, as new packages are occasionally added in /patches when circumstances require it.

For software not included in official Slackware, consider building it yourself or using a SlackBuild script from one of the projects which provides them.

One of the regular Slackware contributors, PiterPUNK, wrote and maintains a third-party package manager that minimizes all of the risks mentioned above.  [http://slackpkg.org Slackpkg] does not support downloading or installing unofficial packages, and it has provisions to install any added packages and uninstall any removed packages as well as the normal install/upgrade/remove routines.

Another third party package manager that promotes good practices is [http://slackroll.sourceforge.net/ SlackRoll] (see [[SlackRoll Tutorial|tutorial]]). Its philosophy is similar to that of Slackpkg but it is not included as part of Slackware. Programmed in Python, it is faster, has more features and detects more events from Slackware -current. However, the initial setup and workflow are a bit more complex.

= See Also =

* &lt;tt&gt;pkgtool(8)&lt;/tt&gt; -- man 8 pkgtool
* &lt;tt&gt;installpkg(8)&lt;/tt&gt; -- man 8 installpkg
* &lt;tt&gt;removepkg(8)&lt;/tt&gt; -- man 8 removepkg
* &lt;tt&gt;upgradepkg(8)&lt;/tt&gt; -- man 8 upgradepkg
* &lt;tt&gt;makepkg(8)&lt;/tt&gt; -- man 8 makepkg
* &lt;tt&gt;explodepkg(8)&lt;/tt&gt; -- man 8 explodepkg


= TODO =

* Add links to other wiki pages that are related to this topic (add to "See Also" above)
* Add hyperlinks to slapt-get, swaret, and other projects mentioned on this page
* Others?

[[Category:Information]]
[[Category:Tutorials]]</text>
    <sha1>87b633ead33c6105087ad9f9bdb3b153f769897e</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Writing A SlackBuild Script</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>661</id>
    <parentid>591</parentid>
    <timestamp>2012-03-27T15:42:57Z</timestamp>
    <contributor>
      <username>Badassbob</username>
      <id>270</id>
    </contributor>
    <minor/>
    <comment>/* Getting Started */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19361" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like linuxpackages.net, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://www.latex2html.org/~latex2ht/current/latex2html-2002-2-1.tar.gz # 03.27.2012

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>43ab669844750a4b9351243609edb30805849c87</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Chromium browser</title>
  <ns>0</ns>
  <id>249</id>
  <revision>
    <id>662</id>
    <parentid>590</parentid>
    <timestamp>2012-03-29T11:11:39Z</timestamp>
    <contributor>
      <username>Perlna</username>
      <id>272</id>
    </contributor>
    <minor/>
    <comment>/* Resources */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5918" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops, slower computers or slow internet connections.

Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process, thus helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on &lt;code&gt;GConf&lt;/code&gt; and &lt;code&gt;ORBit2&lt;/code&gt;, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
&lt;pre&gt;
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
&lt;/pre&gt;

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
&lt;pre&gt;
# sbopkg -i 'ORBit2 GConf'
&lt;/pre&gt;

Get the &lt;code&gt;google-chrome-pam-solibs&lt;/code&gt; package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
&lt;pre&gt;
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
&lt;/pre&gt;

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the &lt;code&gt;INSTALLDIR&lt;/code&gt; variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

&lt;pre&gt;
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i686) ARCH=i686 ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "i686" ];then
  DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  DIRSUFFIX="_x64"
else
  echo "The ARCH should be either i686 or x86_64. Exiting."
  exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then                    # Check to see if `chrome-linux.zip` already exists
        mv chrome-linux.zip chrome-linux.zip.old    # if it does, rename it to chrome-linux.zip.old as backup
fi                                                  # in case the current build has problems
wget -O chrome-linux.zip $CHROMEURL
unzip -u -o ./chrome-linux.zip

&lt;/pre&gt;

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
&lt;pre&gt;
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
&lt;/pre&gt;
Add the following to your crontab :
&lt;pre&gt;
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1&gt; /dev/null
&lt;/pre&gt;
This will run the script at 13:20 every day. See &lt;code&gt;man crontab&lt;/code&gt; for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[http://www.spywaretoolshed.com/ Spyware doctor]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]</text>
    <sha1>00ea7832d17f2e936af4a5e996fe16ef61a2efda</sha1>
  </revision>
  <revision>
    <id>663</id>
    <parentid>662</parentid>
    <timestamp>2012-03-29T14:08:01Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Perlna|Perlna]] ([[User talk:Perlna|talk]]) to last revision by [[User:Klickback|Klickback]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5868" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

Chromium is an open source web browser from Google. It is based on the WebKit rendering engine and is the upstream project for Google's popular Chrome Web Browser.

Keep in mind that Chromium is the '''testing''' branch of the Chrome web browser, and is not recommended for mission-critical systems. Consider using [http://www.google.com/chrome Google Chrome] or [http://www.mozilla.org/en-US/firefox/ Mozilla Firefox] for production systems.

=== Use Case ===

This tutorial explains how to install the latest Chromium build on Slackware and automate the process of updating it regularly. It is aimed at users on a personal desktop or laptop, especially on a single-user system.

While the [http://slackbuilds.org slackbuilds.org] project provides excellent quality build scripts for Chromium, downloading 140MB+ source code and doing compilations that often take more than a couple of hours to complete is generally not feasible for people with laptops, slower computers or slow internet connections.

Therefore, this guide aims on how to automate the process of installing and updating Chromium using daily binary builds that are much smaller in size and take up negligible resources for the install and update process, thus helping the user always run the latest and greatest builds without the hassle of downloading and compiling the source code.

== Getting started ==

Chromium depends on &lt;code&gt;GConf&lt;/code&gt; and &lt;code&gt;ORBit2&lt;/code&gt;, and these should be installed first. Newer versions may also need the PAM library.

=== Slackware 13.37 ===

The above mentioned dependencies are included in the '''extra/''' tree of Slackware 13.37, so these can be simply installed by :
&lt;pre&gt;
# slackpkg install GConf ORBit2 google-chrome-pam-solibs
&lt;/pre&gt;

=== Slackware 13.1 ===

GConf and ORBit2 are availabe at the [http://slackbuilds.org slackbuilds.org] repository. These can be installed manually or using [http://sbopkg.org Sbopkg] :
&lt;pre&gt;
# sbopkg -i 'ORBit2 GConf'
&lt;/pre&gt;

Get the &lt;code&gt;google-chrome-pam-solibs&lt;/code&gt; package [http://slackware.osuosl.org/slackware-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-i486-1.txz 32-bit] [http://slackware.osuosl.org/slackware64-13.37/extra/google-chrome/google-chrome-pam-solibs-1.1.3-x86_64-1.txz 64-bit] and install it :
&lt;pre&gt;
# installpkg ./google-chrome-pam-solibs-1.1.3-x86_64-1.txz
&lt;/pre&gt;

== Getting and installing the latest Chromium build ==

Google maintains a repository of daily chromium builds that you can get from [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux/ here] (32bit) or [http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/ here] for 64 bit. Scroll down to the bottom and navigate to the latest build directory, and download the 'chrome-linux.zip' file there.

Extract the zip file to a place of your liking (I like to keep mine in /home/username/soft), and run the 'chrome-wrapper' binary that will run Chromium and also generate a 'chromium-dev.desktop' file in /home/user/.local/share/applications/ and a Chromium entry will appear in your KDE or Xfce menu. Copy that file to your desktop if you prefer a desktop shortcut.

To upgrade Chromium, just download the latest zip file and extract it where you previously did, overwriting the previous files.

== Automating the Process ==

The following script helps to automate the process of installing and upgrading Chromium. Edit the &lt;code&gt;INSTALLDIR&lt;/code&gt; variable to your liking - that is the place where chromium will be installed. Its recommended to keep it in a folder in your home directory to make it easy to manage. make sure the folder exists before running the script, or the script will fail.

&lt;pre&gt;
#!/bin/bash

# Installation directory - change this to a directory of your choice
# Please make sure the directory exists first, or the script won't work
INSTALLDIR=$HOME/soft

# Determine the architecture of the machine in use and set variables accordingly
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i686) ARCH=i686 ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

if [ "$ARCH" = "i686" ];then
  DIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  DIRSUFFIX="_x64"
else
  echo "The ARCH should be either i686 or x86_64. Exiting."
  exit
fi

# Determine the build number of the latest build
LATESTBUILD=$(curl http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux/LAST_CHANGE)

# The URL to download from
CHROMEURL="http://commondatastorage.googleapis.com/chromium-browser-continuous/Linux"$DIRSUFFIX/$LATESTBUILD/"chrome-linux.zip"

cd $INSTALLDIR
if [ -e chrome-linux.zip ]; then                    # Check to see if `chrome-linux.zip` already exists
        mv chrome-linux.zip chrome-linux.zip.old    # if it does, rename it to chrome-linux.zip.old as backup
fi                                                  # in case the current build has problems
wget -O chrome-linux.zip $CHROMEURL
unzip -u -o ./chrome-linux.zip

&lt;/pre&gt;

To automate the process, first save the script as '''chromium-update.sh''' and add it to your users's cron jobs. Here is an example on how to set it up :
&lt;pre&gt;
$ cd $HOME
$ mkdir .cron
$ cp ./chromium-update.sh ./.cron/
$ chmod a+x ./.cron/chromium-update.sh
$ crontab -e
&lt;/pre&gt;
Add the following to your crontab :
&lt;pre&gt;
# Run daily cron job at 13:20 every day:
20 13 * * * ~/.cron/chromium-update.sh 1&gt; /dev/null
&lt;/pre&gt;
This will run the script at 13:20 every day. See &lt;code&gt;man crontab&lt;/code&gt; for more on how to customize your cron jobs.

== Resources ==
[http://www.chromium.org/Home Chromium home page]

[http://en.wikipedia.org/wiki/Chromium_(web_browser)#Differences_from_Google_Chrome Differences from Google Chrome]

[https://wiki.archlinux.org/index.php/Chromium#Configuration Tips on configuration and customization from Archwiki]</text>
    <sha1>ca0a7556a92fadafc237a400f8e29766f85967e2</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Macbook Air 1,1</title>
  <ns>0</ns>
  <id>275</id>
  <revision>
    <id>667</id>
    <timestamp>2012-04-13T07:08:16Z</timestamp>
    <contributor>
      <username>Gr4nf</username>
      <id>276</id>
    </contributor>
    <comment>Created page with "The following are (incomplete) instructions to install and configure Slackware 13.37 on the Macbook Air 1,1 (from early 2008). ===What You'll Need=== *External DVD-R drive (No..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="415" xml:space="preserve">The following are (incomplete) instructions to install and configure Slackware 13.37 on the Macbook Air 1,1 (from early 2008).
===What You'll Need===
*External DVD-R drive (No success so far with bootable USB drives)
*Bootable disc with some sort of disk utility (Optimally, the Snow Leopard DVD)
*Slackware 13.37 DVD (32 bit is best, but it's up to you)
*Bootable rEFIt CD

==Overview==
The plan of action is this:</text>
    <sha1>c6e653527619087349616e52a28d2f698cd8466b</sha1>
  </revision>
  <revision>
    <id>668</id>
    <parentid>667</parentid>
    <timestamp>2012-04-13T07:11:36Z</timestamp>
    <contributor>
      <username>Gr4nf</username>
      <id>276</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="439" xml:space="preserve">The following are (incomplete) instructions to install and configure Slackware 13.37 on the Macbook Air 1,1 (from early 2008).
===What You'll Need===
*External DVD-R drive (No success so far with bootable USB drives)
*Bootable disc with some sort of disk utility (Optimally, the Snow Leopard DVD)
*Slackware 13.37 DVD (32 bit is best, but it's up to you)
*Bootable rEFIt CD

==Overview==
The plan of action is this:


[[Category:Hardware]]</text>
    <sha1>034bd774330a000b2141850b10d45cc2f0e54087</sha1>
  </revision>
  <revision>
    <id>669</id>
    <parentid>668</parentid>
    <timestamp>2012-04-13T08:50:32Z</timestamp>
    <contributor>
      <username>Gr4nf</username>
      <id>276</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3722" xml:space="preserve">The following are (incomplete) instructions to install and configure Slackware 13.37 on the Macbook Air 1,1 (from early 2008).
===What You'll Need===
*External DVD-R drive (No success so far with bootable USB drives)
*Bootable disc with some sort of disk utility (Optimally, the Snow Leopard DVD)
*Slackware 13.37 DVD (32 bit is best, but it's up to you)
*Bootable rEFIt CD

==Overview==
The installation itself is not at all different from a slackware install on any other intel machine. The difficult parts are configuring afterwards and getting the machine to boot to an MBR scheme. Luckily, rEFIt does some arcane magic with it's partition manager that can set your scheme up as Hybrid GPT/MBR. Which brings us to step 1.

==Partitioning==
Okay, the first step is to partition your hard drive with the MBR scheme. Boot into the Snow Leopard DVD and run the Disk Utility. Re-partition the hard drive as free space, and make sure to select "Master Boot Record" in the Advanced menu. Now boot into your slackware disk. It will show up in the alt boot menu without any configuration. Partition slackware as you would for any other install and take note of the path to the boot partition (probably /dev/sda2).
==Installation==
Install slackware as you would on any intel machine. Make sure to select option 1 when installing the LILO boot loader.
==Make it Bootable==
Linux will not initially be bootable since the Apple firmware hates MBR drives. If you need to boot into your slackware install at any time, just put the slack disk back in and follow the instructions in the boot: menu to boot to the hard drive. To make the drive itself bootable, start up into the rEFIt cd. One of the options is the partition manager. Starting that will scan your disk and give you the option to configure it into Hybrid GPT/MBR. Do that. If all went well, your disk is now bootable!
===If it takes forever to boot===
If it is taking forever to go from the pale blue startup screen to the LILO boot loader (30 seconds or so), you need to bless the partition from a terminal with the bless utility. The Snow Leopard DVD has such a terminal. Boot back into that, start up a terminal, and run the command:
 bless –device /dev/disk0s2 –setboot –legacy –verbose
Where the device is your boot partition (it will be in the disk?s? format, not the sd?? format).
==Extra configurations==
Your slackware install is actually quite usable exactly as it is at this point. However, there are a number of extra configurations that are at least advisable.
===Runlevel===
The default runlevel is, for some unknowable reason, 3. You won't get a desktop session manager unless you edit your /etc/inittab file and change the line:
 id:3:initdefault:
to be 4 instead of 3. Restart, and you should get kdm (the KDE session manager) on boot.
===Desktop Environment===
The default desktop environment is KDE. This works quite well out of the box. Volume control works fine, the brightness keys are **recognized**, but they don't do anything. For somebody used to OS X or Windows, it's probably the most friendly. Almost every other popular desktop manager (besides Gnome, but there are reasons) is also available. You can change which one is run by default with the command:
 xwmconfig
===Sleep===
There is a utility called s2ram that will put the machine to sleep. Map it to a keystroke or hardware event to enable sleeping. The machine will not go to sleep by default when you shut the laptop!
===Brightness===
**This section needs to be expanded. If you have had success in this area, please edit this article**
===Fan control===
Install the mac fan control daemon macfanctld and set it to run on startup. It works just fine.


[[Category:Hardware]]</text>
    <sha1>b817e03d82a0cb53c08b9406f85ea9e9c5872359</sha1>
  </revision>
  <revision>
    <id>670</id>
    <parentid>669</parentid>
    <timestamp>2012-04-13T08:50:51Z</timestamp>
    <contributor>
      <username>Gr4nf</username>
      <id>276</id>
    </contributor>
    <comment>/* Brightness */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3723" xml:space="preserve">The following are (incomplete) instructions to install and configure Slackware 13.37 on the Macbook Air 1,1 (from early 2008).
===What You'll Need===
*External DVD-R drive (No success so far with bootable USB drives)
*Bootable disc with some sort of disk utility (Optimally, the Snow Leopard DVD)
*Slackware 13.37 DVD (32 bit is best, but it's up to you)
*Bootable rEFIt CD

==Overview==
The installation itself is not at all different from a slackware install on any other intel machine. The difficult parts are configuring afterwards and getting the machine to boot to an MBR scheme. Luckily, rEFIt does some arcane magic with it's partition manager that can set your scheme up as Hybrid GPT/MBR. Which brings us to step 1.

==Partitioning==
Okay, the first step is to partition your hard drive with the MBR scheme. Boot into the Snow Leopard DVD and run the Disk Utility. Re-partition the hard drive as free space, and make sure to select "Master Boot Record" in the Advanced menu. Now boot into your slackware disk. It will show up in the alt boot menu without any configuration. Partition slackware as you would for any other install and take note of the path to the boot partition (probably /dev/sda2).
==Installation==
Install slackware as you would on any intel machine. Make sure to select option 1 when installing the LILO boot loader.
==Make it Bootable==
Linux will not initially be bootable since the Apple firmware hates MBR drives. If you need to boot into your slackware install at any time, just put the slack disk back in and follow the instructions in the boot: menu to boot to the hard drive. To make the drive itself bootable, start up into the rEFIt cd. One of the options is the partition manager. Starting that will scan your disk and give you the option to configure it into Hybrid GPT/MBR. Do that. If all went well, your disk is now bootable!
===If it takes forever to boot===
If it is taking forever to go from the pale blue startup screen to the LILO boot loader (30 seconds or so), you need to bless the partition from a terminal with the bless utility. The Snow Leopard DVD has such a terminal. Boot back into that, start up a terminal, and run the command:
 bless –device /dev/disk0s2 –setboot –legacy –verbose
Where the device is your boot partition (it will be in the disk?s? format, not the sd?? format).
==Extra configurations==
Your slackware install is actually quite usable exactly as it is at this point. However, there are a number of extra configurations that are at least advisable.
===Runlevel===
The default runlevel is, for some unknowable reason, 3. You won't get a desktop session manager unless you edit your /etc/inittab file and change the line:
 id:3:initdefault:
to be 4 instead of 3. Restart, and you should get kdm (the KDE session manager) on boot.
===Desktop Environment===
The default desktop environment is KDE. This works quite well out of the box. Volume control works fine, the brightness keys are **recognized**, but they don't do anything. For somebody used to OS X or Windows, it's probably the most friendly. Almost every other popular desktop manager (besides Gnome, but there are reasons) is also available. You can change which one is run by default with the command:
 xwmconfig
===Sleep===
There is a utility called s2ram that will put the machine to sleep. Map it to a keystroke or hardware event to enable sleeping. The machine will not go to sleep by default when you shut the laptop!
===Brightness===
''This section needs to be expanded. If you have had success in this area, please edit this article''

===Fan control===
Install the mac fan control daemon macfanctld and set it to run on startup. It works just fine.


[[Category:Hardware]]</text>
    <sha1>12f1c77c3bb5ee270b5a323e695bc0d522370917</sha1>
  </revision>
  <revision>
    <id>671</id>
    <parentid>670</parentid>
    <timestamp>2012-04-13T08:51:08Z</timestamp>
    <contributor>
      <username>Gr4nf</username>
      <id>276</id>
    </contributor>
    <comment>/* Desktop Environment */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3724" xml:space="preserve">The following are (incomplete) instructions to install and configure Slackware 13.37 on the Macbook Air 1,1 (from early 2008).
===What You'll Need===
*External DVD-R drive (No success so far with bootable USB drives)
*Bootable disc with some sort of disk utility (Optimally, the Snow Leopard DVD)
*Slackware 13.37 DVD (32 bit is best, but it's up to you)
*Bootable rEFIt CD

==Overview==
The installation itself is not at all different from a slackware install on any other intel machine. The difficult parts are configuring afterwards and getting the machine to boot to an MBR scheme. Luckily, rEFIt does some arcane magic with it's partition manager that can set your scheme up as Hybrid GPT/MBR. Which brings us to step 1.

==Partitioning==
Okay, the first step is to partition your hard drive with the MBR scheme. Boot into the Snow Leopard DVD and run the Disk Utility. Re-partition the hard drive as free space, and make sure to select "Master Boot Record" in the Advanced menu. Now boot into your slackware disk. It will show up in the alt boot menu without any configuration. Partition slackware as you would for any other install and take note of the path to the boot partition (probably /dev/sda2).
==Installation==
Install slackware as you would on any intel machine. Make sure to select option 1 when installing the LILO boot loader.
==Make it Bootable==
Linux will not initially be bootable since the Apple firmware hates MBR drives. If you need to boot into your slackware install at any time, just put the slack disk back in and follow the instructions in the boot: menu to boot to the hard drive. To make the drive itself bootable, start up into the rEFIt cd. One of the options is the partition manager. Starting that will scan your disk and give you the option to configure it into Hybrid GPT/MBR. Do that. If all went well, your disk is now bootable!
===If it takes forever to boot===
If it is taking forever to go from the pale blue startup screen to the LILO boot loader (30 seconds or so), you need to bless the partition from a terminal with the bless utility. The Snow Leopard DVD has such a terminal. Boot back into that, start up a terminal, and run the command:
 bless –device /dev/disk0s2 –setboot –legacy –verbose
Where the device is your boot partition (it will be in the disk?s? format, not the sd?? format).
==Extra configurations==
Your slackware install is actually quite usable exactly as it is at this point. However, there are a number of extra configurations that are at least advisable.
===Runlevel===
The default runlevel is, for some unknowable reason, 3. You won't get a desktop session manager unless you edit your /etc/inittab file and change the line:
 id:3:initdefault:
to be 4 instead of 3. Restart, and you should get kdm (the KDE session manager) on boot.
===Desktop Environment===
The default desktop environment is KDE. This works quite well out of the box. Volume control works fine, the brightness keys are ''recognized'', but they don't do anything. For somebody used to OS X or Windows, it's probably the most friendly. Almost every other popular desktop manager (besides Gnome, but there are reasons) is also available. You can change which one is run by default with the command:
 xwmconfig

===Sleep===
There is a utility called s2ram that will put the machine to sleep. Map it to a keystroke or hardware event to enable sleeping. The machine will not go to sleep by default when you shut the laptop!
===Brightness===
''This section needs to be expanded. If you have had success in this area, please edit this article''

===Fan control===
Install the mac fan control daemon macfanctld and set it to run on startup. It works just fine.


[[Category:Hardware]]</text>
    <sha1>eb4d406c26b38a57c22d6fcb664201d115240840</sha1>
  </revision>
  <revision>
    <id>672</id>
    <parentid>671</parentid>
    <timestamp>2012-04-13T19:37:04Z</timestamp>
    <contributor>
      <username>Gr4nf</username>
      <id>276</id>
    </contributor>
    <comment>/* Brightness */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3787" xml:space="preserve">The following are (incomplete) instructions to install and configure Slackware 13.37 on the Macbook Air 1,1 (from early 2008).
===What You'll Need===
*External DVD-R drive (No success so far with bootable USB drives)
*Bootable disc with some sort of disk utility (Optimally, the Snow Leopard DVD)
*Slackware 13.37 DVD (32 bit is best, but it's up to you)
*Bootable rEFIt CD

==Overview==
The installation itself is not at all different from a slackware install on any other intel machine. The difficult parts are configuring afterwards and getting the machine to boot to an MBR scheme. Luckily, rEFIt does some arcane magic with it's partition manager that can set your scheme up as Hybrid GPT/MBR. Which brings us to step 1.

==Partitioning==
Okay, the first step is to partition your hard drive with the MBR scheme. Boot into the Snow Leopard DVD and run the Disk Utility. Re-partition the hard drive as free space, and make sure to select "Master Boot Record" in the Advanced menu. Now boot into your slackware disk. It will show up in the alt boot menu without any configuration. Partition slackware as you would for any other install and take note of the path to the boot partition (probably /dev/sda2).
==Installation==
Install slackware as you would on any intel machine. Make sure to select option 1 when installing the LILO boot loader.
==Make it Bootable==
Linux will not initially be bootable since the Apple firmware hates MBR drives. If you need to boot into your slackware install at any time, just put the slack disk back in and follow the instructions in the boot: menu to boot to the hard drive. To make the drive itself bootable, start up into the rEFIt cd. One of the options is the partition manager. Starting that will scan your disk and give you the option to configure it into Hybrid GPT/MBR. Do that. If all went well, your disk is now bootable!
===If it takes forever to boot===
If it is taking forever to go from the pale blue startup screen to the LILO boot loader (30 seconds or so), you need to bless the partition from a terminal with the bless utility. The Snow Leopard DVD has such a terminal. Boot back into that, start up a terminal, and run the command:
 bless –device /dev/disk0s2 –setboot –legacy –verbose
Where the device is your boot partition (it will be in the disk?s? format, not the sd?? format).
==Extra configurations==
Your slackware install is actually quite usable exactly as it is at this point. However, there are a number of extra configurations that are at least advisable.
===Runlevel===
The default runlevel is, for some unknowable reason, 3. You won't get a desktop session manager unless you edit your /etc/inittab file and change the line:
 id:3:initdefault:
to be 4 instead of 3. Restart, and you should get kdm (the KDE session manager) on boot.
===Desktop Environment===
The default desktop environment is KDE. This works quite well out of the box. Volume control works fine, the brightness keys are ''recognized'', but they don't do anything. For somebody used to OS X or Windows, it's probably the most friendly. Almost every other popular desktop manager (besides Gnome, but there are reasons) is also available. You can change which one is run by default with the command:
 xwmconfig

===Sleep===
There is a utility called s2ram that will put the machine to sleep. Map it to a keystroke or hardware event to enable sleeping. The machine will not go to sleep by default when you shut the laptop!
===Brightness===
The command line utility xbrightness works fine. If you map it with the '-inc' and '-dec' options to the brightness keys (keycodes 232 and 233) it should work fine.

===Fan control===
Install the mac fan control daemon macfanctld and set it to run on startup. It works just fine.


[[Category:Hardware]]</text>
    <sha1>20dcbebf30cdefaa4de9a1f241c90139e9318dda</sha1>
  </revision>
  <revision>
    <id>673</id>
    <parentid>672</parentid>
    <timestamp>2012-04-13T19:38:50Z</timestamp>
    <contributor>
      <username>Gr4nf</username>
      <id>276</id>
    </contributor>
    <comment>/* Extra configurations */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3956" xml:space="preserve">The following are (incomplete) instructions to install and configure Slackware 13.37 on the Macbook Air 1,1 (from early 2008).
===What You'll Need===
*External DVD-R drive (No success so far with bootable USB drives)
*Bootable disc with some sort of disk utility (Optimally, the Snow Leopard DVD)
*Slackware 13.37 DVD (32 bit is best, but it's up to you)
*Bootable rEFIt CD

==Overview==
The installation itself is not at all different from a slackware install on any other intel machine. The difficult parts are configuring afterwards and getting the machine to boot to an MBR scheme. Luckily, rEFIt does some arcane magic with it's partition manager that can set your scheme up as Hybrid GPT/MBR. Which brings us to step 1.

==Partitioning==
Okay, the first step is to partition your hard drive with the MBR scheme. Boot into the Snow Leopard DVD and run the Disk Utility. Re-partition the hard drive as free space, and make sure to select "Master Boot Record" in the Advanced menu. Now boot into your slackware disk. It will show up in the alt boot menu without any configuration. Partition slackware as you would for any other install and take note of the path to the boot partition (probably /dev/sda2).
==Installation==
Install slackware as you would on any intel machine. Make sure to select option 1 when installing the LILO boot loader.
==Make it Bootable==
Linux will not initially be bootable since the Apple firmware hates MBR drives. If you need to boot into your slackware install at any time, just put the slack disk back in and follow the instructions in the boot: menu to boot to the hard drive. To make the drive itself bootable, start up into the rEFIt cd. One of the options is the partition manager. Starting that will scan your disk and give you the option to configure it into Hybrid GPT/MBR. Do that. If all went well, your disk is now bootable!
===If it takes forever to boot===
If it is taking forever to go from the pale blue startup screen to the LILO boot loader (30 seconds or so), you need to bless the partition from a terminal with the bless utility. The Snow Leopard DVD has such a terminal. Boot back into that, start up a terminal, and run the command:
 bless –device /dev/disk0s2 –setboot –legacy –verbose
Where the device is your boot partition (it will be in the disk?s? format, not the sd?? format).
==Extra configurations==
Your slackware install is actually quite usable exactly as it is at this point. However, there are a number of extra configurations that are at least advisable.
===Wireless===
Broadcom's linux driver should work right out of the box. The readme file explains how to blacklist the conflicting drivers you may have in your install.
===Runlevel===
The default runlevel is, for some unknowable reason, 3. You won't get a desktop session manager unless you edit your /etc/inittab file and change the line:
 id:3:initdefault:
to be 4 instead of 3. Restart, and you should get kdm (the KDE session manager) on boot.
===Desktop Environment===
The default desktop environment is KDE. This works quite well out of the box. Volume control works fine, the brightness keys are ''recognized'', but they don't do anything. For somebody used to OS X or Windows, it's probably the most friendly. Almost every other popular desktop manager (besides Gnome, but there are reasons) is also available. You can change which one is run by default with the command:
 xwmconfig

===Sleep===
There is a utility called s2ram that will put the machine to sleep. Map it to a keystroke or hardware event to enable sleeping. The machine will not go to sleep by default when you shut the laptop!
===Brightness===
The command line utility xbrightness works fine. If you map it with the '-inc' and '-dec' options to the brightness keys (keycodes 232 and 233) it should work fine.

===Fan control===
Install the mac fan control daemon macfanctld and set it to run on startup. It works just fine.


[[Category:Hardware]]</text>
    <sha1>d1288ddecb02b84845f67096f206c18a0ef42b0c</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Customizing Bash Prompt</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>675</id>
    <parentid>508</parentid>
    <timestamp>2012-05-15T20:40:43Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4822" xml:space="preserve">[[Category:Tips]]

Originally posted by SU_PyRoW 
http://compelitepc.host56.com

There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@compelitepc.host56.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[support@compelitepc.host56.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes.</text>
    <sha1>d5b2ca4fceedfe3d08ce1e807712b2e2b5d0f27d</sha1>
  </revision>
  <revision>
    <id>676</id>
    <parentid>675</parentid>
    <timestamp>2012-05-15T20:42:53Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <comment>moved [[Customising Bash Prompt]] to [[Customizing Bash Prompt]] over redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4822" xml:space="preserve">[[Category:Tips]]

Originally posted by SU_PyRoW 
http://compelitepc.host56.com

There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@compelitepc.host56.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[support@compelitepc.host56.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes.</text>
    <sha1>d5b2ca4fceedfe3d08ce1e807712b2e2b5d0f27d</sha1>
  </revision>
  <revision>
    <id>727</id>
    <parentid>676</parentid>
    <timestamp>2012-08-05T22:15:26Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4807" xml:space="preserve">[[Category:Tips]]

Originally posted by 
http://insider.compelitepc.host56.com

There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@compelitepc.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[support@compelitepc.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes.</text>
    <sha1>b608907cd1e6cc170f0585303d8ed1fa69b22b14</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Customising Bash Prompt</title>
  <ns>0</ns>
  <id>277</id>
  <revision>
    <id>677</id>
    <timestamp>2012-05-15T20:42:53Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <comment>moved [[Customising Bash Prompt]] to [[Customizing Bash Prompt]] over redirect</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="37" xml:space="preserve">#REDIRECT [[Customizing Bash Prompt]]</text>
    <sha1>40b1752b8d0df62f9838a81eefe08530f9f2f3e3</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Directory Permissions Defaults</title>
  <ns>0</ns>
  <id>83</id>
  <revision>
    <id>683</id>
    <parentid>105</parentid>
    <timestamp>2012-05-19T22:34:14Z</timestamp>
    <contributor>
      <username>Thund3rstruck</username>
      <id>285</id>
    </contributor>
    <comment>/* Solution: ACL */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4488" xml:space="preserve">[[Category:Tutorials]]
= Problem: Sharing Directories =

My wife and I keep our pictures of our kids under a shared directory
called /home/shared.  We download them with Digikam and sometimes edit 
them to send out to relatives.  The problem was this: if I download the
pictures off the camera, then Megan can't edit them or read them.  We
also had problems with shared files (e.g., our accounting spreadsheets)
that I would create and she would modify, or vice versa.

= Solution: ACL =

To set, in effect, default file-creation masks, you can use [[ACL]] (access
control lists).  The user commands you need to set up [[ACL]] are
getfacl(1) and setfacl(1).

== Edit /etc/fstab ==

Edit the fourth field of the fstab entry of the partition you want
to use ACL on.  In this case, it was /dev/sda6  on /home:

&lt;pre&gt;
/dev/sda6  /home  ext3	   defaults,acl 1   1
&lt;/pre&gt;

adding "acl" to the list of permissions.  Without doing this, you'll
get

&lt;pre&gt;
setfacl: /mnt/backup Operation not supported
&lt;/pre&gt;

Then remount the partition: since I was doing this on /home, I
rebooted (mount -a did not work).

== ACL Commands ==

getfacl(1) shows you the current ACL status of a file:

&lt;pre&gt;
 
/media/multimedia: Zshell&gt; getfacl /home                                       
getfacl: Removing leading '/' from absolute path names
# file: home
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
&lt;/pre&gt;

Once the partitions are properly set up (that was the easy part),
enter the setfacl(1) commands:

&lt;pre&gt;
sudo setfacl --recursive -dm g:users:rwx /home/shared
&lt;/pre&gt;

--recursive was important so that each directory beneath /home/shared
inherits the default mask.

Now getfacl(1) gives me this:

&lt;pre&gt;
/media/multimedia: Zshell&gt; getfacl /home/shared
getfacl: Removing leading '/' from absolute path names
# file: home/shared
# owner: joel
# group: users
user::rwx
group::rwx
other::r-x
default:user::rwx
default:group::rwx
default:group:users:rwx
default:mask::rwx
default:other::r-x
&lt;/pre&gt;

And when creating a file:

&lt;pre&gt;
/media/multimedia: Zshell&gt; cd /home/shared
/home/shared: Zshell&gt; touch my_self
/home/shared: Zshell&gt; ls -l my_self
-rw-rw-r--+ 1 joel users 0 2008-04-06 14:36 my_self
&lt;/pre&gt;

The desired outcome!

Note: this did what I wanted, but it's just a beginning.  Read the
setfacl(1) and getfacl(1) man pages for the full story.


= Solution 2: SetGuid Flag =

Some users are not willing (or able) to apply ACLs on filesystems. There is a way to achieve a similar ''shared'' directory effect using native Linux access controls. For example, imagine a SAMBA server with a share called ''Photos''. You need a sub-set of users on the network to be able to manage the files on the share. Additionally, you need new directories created within the share to ''inherit'' permissions from the parent. 

To accomplish this goal you create a group called ''mgrphotos'' and you add the users that should manage the share into that group. 

&lt;pre&gt;
# Set ownership on shared folder
chown -R root:mgrphotos /media/share/disk1/Photos

# Set permissions on shared folder
chmod -R 775 /media/share/disk1/Photos

# Applying the setguid bit can allow for new files to "inherit" group membership from its parent (use this sparingly)
sudo chmod g+s /media/share/disk1/Photos 

# Verify the setguid bit
ls -all /media/share/disk1/Photos/ | grep -i family
  drwxrwsr-x 24 root mgrphotos 4096 2012-03-01 15:02 Family
&lt;/pre&gt;

All new files created in the path are now owned by the mgrphotos group. Since this volume is mounted as 775, all members of mgrphotos share the files/folders they create on this volume.

It's highly recommended that you leverage ACLs wherever possible but this is an alternate solution that works extremely well and required no extra packages or configuration.

= Official Package Data =
&lt;pre&gt;
PACKAGE NAME:     acl-2.2.39_1-i486-2
COMPRESSED PACKAGE SIZE:     139 K
UNCOMPRESSED PACKAGE SIZE:     350 K
PACKAGE LOCATION: ./acl-2.2.39_1-i486-2.tgz
PACKAGE DESCRIPTION:
acl: acl (tools for using POSIX Access Control Lists)
acl:
acl: This package contains a set of tools and libraries for manipulating
acl: POSIX Access Control Lists.  POSIX Access Control Lists (defined in
acl: POSIX 1003.1e draft standard 17) are used to define more fine-grained
acl: discretionary access rights for files and directories.
acl:
acl:
acl:
acl:
acl:
&lt;/pre&gt;
in slackware/a[http://packages.slackware.it/search.php?v=12.0&amp;t=1&amp;q=acl]
[[User:Trashbird1240|Trashbird1240]] 14:49, 6 April 2008 (EDT)</text>
    <sha1>df26bf5527c8d69f9becd59181a5599eb5eeb7a2</sha1>
  </revision>
  <revision>
    <id>684</id>
    <parentid>683</parentid>
    <timestamp>2012-05-19T22:35:59Z</timestamp>
    <contributor>
      <username>Thund3rstruck</username>
      <id>285</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4493" xml:space="preserve">[[Category:Tutorials]]
= Problem: Sharing Directories =

My wife and I keep our pictures of our kids under a shared directory
called /home/shared.  We download them with Digikam and sometimes edit 
them to send out to relatives.  The problem was this: if I download the
pictures off the camera, then Megan can't edit them or read them.  We
also had problems with shared files (e.g., our accounting spreadsheets)
that I would create and she would modify, or vice versa.

= Solution: ACL =

To set, in effect, default file-creation masks, you can use [[ACL]] (access
control lists).  The user commands you need to set up [[ACL]] are
getfacl(1) and setfacl(1).

== Edit /etc/fstab ==

Edit the fourth field of the fstab entry of the partition you want
to use ACL on.  In this case, it was /dev/sda6  on /home:

&lt;pre&gt;
/dev/sda6  /home  ext3	   defaults,acl 1   1
&lt;/pre&gt;

adding "acl" to the list of permissions.  Without doing this, you'll
get

&lt;pre&gt;
setfacl: /mnt/backup Operation not supported
&lt;/pre&gt;

Then remount the partition: since I was doing this on /home, I
rebooted (mount -a did not work).

== ACL Commands ==

getfacl(1) shows you the current ACL status of a file:

&lt;pre&gt;
 
/media/multimedia: Zshell&gt; getfacl /home                                       
getfacl: Removing leading '/' from absolute path names
# file: home
# owner: root
# group: root
user::rwx
group::r-x
other::r-x
&lt;/pre&gt;

Once the partitions are properly set up (that was the easy part),
enter the setfacl(1) commands:

&lt;pre&gt;
sudo setfacl --recursive -dm g:users:rwx /home/shared
&lt;/pre&gt;

--recursive was important so that each directory beneath /home/shared
inherits the default mask.

Now getfacl(1) gives me this:

&lt;pre&gt;
/media/multimedia: Zshell&gt; getfacl /home/shared
getfacl: Removing leading '/' from absolute path names
# file: home/shared
# owner: joel
# group: users
user::rwx
group::rwx
other::r-x
default:user::rwx
default:group::rwx
default:group:users:rwx
default:mask::rwx
default:other::r-x
&lt;/pre&gt;

And when creating a file:

&lt;pre&gt;
/media/multimedia: Zshell&gt; cd /home/shared
/home/shared: Zshell&gt; touch my_self
/home/shared: Zshell&gt; ls -l my_self
-rw-rw-r--+ 1 joel users 0 2008-04-06 14:36 my_self
&lt;/pre&gt;

The desired outcome!

Note: this did what I wanted, but it's just a beginning.  Read the
setfacl(1) and getfacl(1) man pages for the full story.

== Official ACL Package Data ==
&lt;pre&gt;
PACKAGE NAME:     acl-2.2.39_1-i486-2
COMPRESSED PACKAGE SIZE:     139 K
UNCOMPRESSED PACKAGE SIZE:     350 K
PACKAGE LOCATION: ./acl-2.2.39_1-i486-2.tgz
PACKAGE DESCRIPTION:
acl: acl (tools for using POSIX Access Control Lists)
acl:
acl: This package contains a set of tools and libraries for manipulating
acl: POSIX Access Control Lists.  POSIX Access Control Lists (defined in
acl: POSIX 1003.1e draft standard 17) are used to define more fine-grained
acl: discretionary access rights for files and directories.
acl:
acl:
acl:
acl:
acl:
&lt;/pre&gt;
in slackware/a[http://packages.slackware.it/search.php?v=12.0&amp;t=1&amp;q=acl]
[[User:Trashbird1240|Trashbird1240]] 14:49, 6 April 2008 (EDT)

= Solution 2: SetGuid Flag =

Some users are not willing (or able) to apply ACLs on filesystems. There is a way to achieve a similar ''shared'' directory effect using native Linux access controls. For example, imagine a SAMBA server with a share called ''Photos''. You need a sub-set of users on the network to be able to manage the files on the share. Additionally, you need new directories created within the share to ''inherit'' permissions from the parent. 

To accomplish this goal you create a group called ''mgrphotos'' and you add the users that should manage the share into that group. 

&lt;pre&gt;
# Set ownership on shared folder
chown -R root:mgrphotos /media/share/disk1/Photos

# Set permissions on shared folder
chmod -R 775 /media/share/disk1/Photos

# Applying the setguid bit can allow for new files to "inherit" group membership from its parent (use this sparingly)
sudo chmod g+s /media/share/disk1/Photos 

# Verify the setguid bit
ls -all /media/share/disk1/Photos/ | grep -i family
  drwxrwsr-x 24 root mgrphotos 4096 2012-03-01 15:02 Family
&lt;/pre&gt;

All new files created in the path are now owned by the mgrphotos group. Since this volume is mounted as 775, all members of mgrphotos share the files/folders they create on this volume.

It's highly recommended that you leverage ACLs wherever possible but this is an alternate solution that works extremely well and required no extra packages or configuration.</text>
    <sha1>2d5e9bfeff66af0294107a1139f0d6adf295ac6e</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>User talk:Tigersharke</title>
  <ns>3</ns>
  <id>281</id>
  <revision>
    <id>694</id>
    <timestamp>2012-05-21T19:31:30Z</timestamp>
    <contributor>
      <username>Tigersharke</username>
      <id>288</id>
    </contributor>
    <comment>Created page with "anti-spam researcher of sorts :)"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="32" xml:space="preserve">anti-spam researcher of sorts :)</text>
    <sha1>e1e94186660aa499c510346fe08030502168562a</sha1>
  </revision>
  <revision>
    <id>695</id>
    <parentid>694</parentid>
    <timestamp>2012-05-21T19:32:28Z</timestamp>
    <contributor>
      <username>Tigersharke</username>
      <id>288</id>
    </contributor>
    <comment>ok, so after the gatekeeper, no limits?</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>704</id>
    <parentid>580</parentid>
    <timestamp>2012-06-01T04:30:56Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>MediaWiki Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4137" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>0408a78241675f01659c1b1585e011ffe61cd6df</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>OpenVPN(ID)</title>
  <ns>0</ns>
  <id>284</id>
  <revision>
    <id>705</id>
    <timestamp>2012-06-06T23:43:07Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Moved from: http://www.slackwiki.com/OpenVPN</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14136" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.

__TOC__
== Instalasi ==

Download source dari [http://openvpn.net openvpn.net]

download versi 2.0

instalasi Lzo
&lt;pre&gt;
tar zxvf lzo-1.08.tar.gz
cd lzo-1-08.tar.gz
./configure --prefix=/usr
make ; make install-strip
&lt;/pre&gt;
insalasi OpenVPN
&lt;pre&gt;
tar zxvf openvpn-2.0.tar.gz
cd openvpn-2.0
./configure --prefix=/usr \
--sysconfdir=/etc/openvpn \
--enable-pthread \
--enable-iproute2 \
--with-ssl \
--with-lzo-header=/usr/include \
--with-lzo-lib=/usr/lib \
--with-ifconfig \
--with-route \
--with-mem-check=dmalloc 
make ; make install-strip
&lt;/pre&gt;
== Konfigurasi ==

==Konfigurasi Sertifikat==

Simpan seluruh sertifikat di '''''/etc/openvpn/certs'''''
&lt;pre&gt;
This is a small RSA key management package,
based on the openssl command line tool, that
can be found in the easy-rsa subdirectory
of the OpenVPN distribution.

These are reference notes.  For step
by step instructions, see the HOWTO:

http://openvpn.net/howto.html

INSTALL

1. Edit vars.
2. Set KEY_CONFIG to point to the openssl.cnf file
   included in this distribution.
3. Set KEY_DIR to point to a directory which will
   contain all keys, certificates, etc.  This
   directory need not exist, and if it does,
   it will be deleted with rm -rf, so BE
   CAREFUL how you set KEY_DIR.
4. (Optional) Edit other fields in vars
   per your site data.  You may want to
   increase KEY_SIZE to 2048 if you are
   paranoid and don't mind slower key
   processing, but certainly 1024 is
   fine for testing purposes.  KEY_SIZE
   must be compatible across both peers
   participating in a secure SSL/TLS
   connection.
5  . vars
6. ./clean-all
7. As you create certificates, keys, and
   certificate signing requests, understand that
   only .key files should be kept confidential.
   .crt and .csr files can be sent over insecure
   channels such as plaintext email.
8. You should never need to copy a .key file
   between computers.  Normally each computer
   will have its own certificate/key pair.

BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY

1. ./build-ca
2. ca.crt and ca.key will be built in your KEY_DIR
   directory

BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)

1. ./build-inter inter
2. inter.crt and inter.key will be built in your KEY_DIR
   directory and signed with your root certificate.

BUILD DIFFIE-HELLMAN PARAMETERS (necessary for
the server end of a SSL/TLS connection).

1. ./build-dh

BUILD A CERTIFICATE SIGNING REQUEST (If
you want to sign your certificate with a root
certificate controlled by another individual
or organization, or residing on a different machine).

1. Get ca.crt (the root certificate) from your
   certificate authority.  Though this
   transfer can be over an insecure channel, to prevent
   man-in-the-middle attacks you must confirm that
   ca.crt was not tampered with.  Large CAs solve this
   problem by hardwiring their root certificates into
   popular web browsers.  A simple way to verify a root
   CA is to call the issuer on the telephone and confirm
   that the md5sum or sha1sum signatures on the ca.crt
   files match (such as with the command: "md5sum ca.crt").
2. Choose a name for your certificate such as your computer
   name.  In our example we will use "mycert".
3. ./build-req mycert
4. You can ignore most of the fields, but set
   "Common Name" to something unique such as your
   computer's host name.  Leave all password
   fields blank, unless you want your private key
   to be protected by password.  Using a password
   is not required -- it will make your key more secure
   but also more inconvenient to use, because you will
   need to supply your password anytime the key is used.
   NOTE: if you are using a password, use ./build-req-pass
   instead of ./build-req
5. Your key will be written to $KEY_DIR/mycert.key
6. Your certificate signing request will be written to
   to $KEY_DIR/mycert.csr
7. Email mycert.csr to the individual or organization
   which controls the root certificate.  This can be
   done over an insecure channel.
8. After the .csr file is signed by the root certificate
   authority, you will receive a file mycert.crt
   (your certificate).  Place mycert.crt in your
   KEY_DIR directory.
9. The combined files of mycert.crt, mycert.key,
   and ca.crt can now be used to secure one end of
   an SSL/TLS connection.

SIGN A CERTIFICATE SIGNING REQUEST

1. ./sign-req mycert
2. mycert.crt will be built in your KEY_DIR
   directory using mycert.csr and your root CA
   file as input.

BUILD AND SIGN A CERTIFICATE SIGNING REQUEST
USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY -- this
script generates and signs a certificate in one step,
but it requires that the generated certificate and private
key files be copied to the destination host over a
secure channel.

1. ./build-key mycert (no password protection)
2. OR ./build-key-pass mycert (with password protection)
3. OR ./build-key-pkcs12 mycert (PKCS #12 format)
4. OR ./build-key-server mycert (with nsCertType=server)
5. mycert.crt and mycert.key will be built in your
   KEY_DIR directory, and mycert.crt will be signed
   by your root CA. If ./build-key-pkcs12 was used a
   mycert.p12 file will also be created including the
   private key, certificate and the ca certificate.

IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.
IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.

(4) Sign server certificates with one CA and client certificates
    with a different CA.  The client config "ca" directive should
    reference the server-signing CA while the server config "ca"
    directive should reference the client-signing CA.

NOTES

Show certificate fields:
  openssl x509 -in cert.crt -text
&lt;/pre&gt;
&lt;pre&gt;
# cd easy-rsa
# vi vars
. vars
./clean-all

## BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY
./build.ca

## BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)
./build-inter inter

## BUILD DIFFIE-HELLMAN PARAMETERS (necessary for the server end of a SSL/TLS connection).
./build.dh

## BUILD A CERTIFICATE SIGNING REQUEST 
## (If you want to sign your certificate with a root certificate controlled by another individual 
## or organization, or residing on a different machine)

./build-req mycert
## SIGN A CERTIFICATE SIGNING REQUEST
./sign-req mycert

## BUILD AND SIGN A CERTIFICATE SIGNING REQUEST USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY
./build-key mycert (no password protection)
OR 
./build-key-pass mycert (with password protection)
OR 
./build-key-pkcs12 mycert (PKCS #12 format)
OR 
./build-key-server mycert (with nsCertType=server)
&lt;/pre&gt;

==Konfigurasi Server==

edit server.conf '''''vi /etc/openvpn/server.conf'''''
&lt;pre&gt;
## Mode Server
mode server

## Local Host Name/IP Server
;local 127.0.0.1

## Protocol
;proto tcp
proto udp

## Port
; port 1194

## Device Interface
;dev tap
dev tun

## TAP-Win32 adapter name
;dev-node MyTap

## SSL/TLS 
## root certificate (ca)
## certificate (cert)
## private key (key)
ca /etc/openvpn/certs/ca.crt
cert /etc/openvpn/certs/server.crt
key /etc/openvpn/certs/server.key

## Diffie hellman parameters
dh dh1024.pem

## VPN subnet
server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

##ethernet bridging
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

## dhcpcaveats
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

;learn-address ./script

## dhcpcaveats
;push "redirect-gateway"
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

##
;client-to-client

## same "COMMON NAME" certificate/key
;duplicate-cn

## Status Connection
keepalive 10 120

## tls-auth key
;tls-auth ta.key 0 

## Cryptographic cipher
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

## Link Compresion
comp-lzo

## Max Client Connections
;max-clients 100

## daemon privileges (non windows saja)
user nobody
group nobody

persist-key
persist-tun

## Openvpn Log
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

## Output Log
status /var/log/openvpn/openvpn-status.log

## Log Verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## Repeating Messages
;mute 20

## Pid File
writepid /var/run/openvpn.pid
&lt;/pre&gt;

'''Routing'''

&lt;pre&gt;
echo 1 &gt; /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.4.0.2
&lt;/pre&gt;

'''Firewall'''
&lt;pre&gt;
iptables -A INPUT -p udp -s 1.2.3.4 --dport 1194 -j ACCEPT
OR
iptables -A INPUT -p udp --dport 1194 -j ACCEPT

## Tun Device
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT

## Tap Device
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
&lt;/pre&gt;

==Konfigurasi client==

edit file client.conf '''''vi /etc/openvpn/client.conf'''''
&lt;pre&gt;
## Config
client

## Device Interface
;dev tap
dev tun

## Tap adapter name (Win only)
;dev-node MyTap

## Conectivity
;proto tcp
proto udp

## Server [hostname/ip] [port]
remote my-server-1 1194
;remote my-server-2 1194

## load-balancing
;remote-random

## resolve host name OpenVPN server
resolv-retry infinite

# local port
nobind

## privileges (non windows saja)
user nobody
group nobody

## preserve
persist-key
persist-tun

## HTTP proxy
;http-proxy-retry 
;http-proxy [proxy server] [proxy port]

## duplicate packet warnings
;mute-replay-warnings

## SSL/TLS parms
/etc/openvpn/certs/ca ca.crt
/etc/openvpn/certs/cert client.crt
/etc/openvpn/certs/key client.key

## nsCertType key
;ns-cert-type server

## tls-auth key
;tls-auth /etc/openvpn/certs/ta.key 1

## Cryptographic cipher
;cipher x

## Link compression
comp-lzo

## verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## repeating messages
;mute 20
&lt;/pre&gt;
'''Routing'''
&lt;pre&gt;
route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.4.0.1 
&lt;/pre&gt;


==Example==

'''Example 1:''' A simple tunnel without security&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 --verb 9
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 --verb 9 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 2:''' A tunnel with static-key security (i.e. using a pre-shared secret)&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--verb 5 --secret key
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--verb 5 --secret key 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 3:''' A tunnel with full TLS-based security &lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--tls-client --ca tmp-ca.crt --cert client.crt --key client.key \
--reneg-sec 60 --verb 5 
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--tls-server --ca tmp-ca.crt --cert server.crt --key server.key \
--reneg-sec 60 --verb 5 --dh dh1024.pem
&lt;/pre&gt;

On May:

    ping 10.4.0.2 

On Jun:

    ping 10.4.0.1

== External Links ==

* http://dmalloc.com/
* http://valgrind.org/
* http://www.oberhumer.com/opensource/lzo/
* http://openvpn.net/
* http://openvpn.net/howto.html
* http://openvpn.net/1xhowto.html (Old-v1.06)
* http://openvpn.net/man.html</text>
    <sha1>a1601b7ee4db3b7301b533a706c6829931779591</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>OpenVPN</title>
  <ns>0</ns>
  <id>127</id>
  <revision>
    <id>706</id>
    <parentid>150</parentid>
    <timestamp>2012-06-06T23:52:31Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Moved English page here, made a new page for Indonesian translation and added link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14223" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.

'''[[OpenVPN(ID)|OpenVPN Instructions - Bahasa Indonesia]]'''


__TOC__
== Installation ==

Download source from [http://openvpn.net openvpn.net]

Download verison 2.0

install Lzo
&lt;pre&gt;
tar zxvf lzo-1.08.tar.gz
cd lzo-1-08.tar.gz
./configure --prefix=/usr
make ; make install-strip
&lt;/pre&gt;
install OpenVPN
&lt;pre&gt;
tar zxvf openvpn-2.0.tar.gz
cd openvpn-2.0
./configure --prefix=/usr \
--sysconfdir=/etc/openvpn \
--enable-pthread \
--enable-iproute2 \
--with-ssl \
--with-lzo-header=/usr/include \
--with-lzo-lib=/usr/lib \
--with-ifconfig \
--with-route \
--with-mem-check=dmalloc 
make ; make install-strip
&lt;/pre&gt;
== Configuration ==

==Configuring Certificates==

Save all certificates in '''''/etc/openvpn/certs'''''
&lt;pre&gt;
This is a small RSA key management package,
based on the openssl command line tool, that
can be found in the easy-rsa subdirectory
of the OpenVPN distribution.

These are reference notes.  For step
by step instructions, see the HOWTO:

http://openvpn.net/howto.html

INSTALL

1. Edit vars.
2. Set KEY_CONFIG to point to the openssl.cnf file
   included in this distribution.
3. Set KEY_DIR to point to a directory which will
   contain all keys, certificates, etc.  This
   directory need not exist, and if it does,
   it will be deleted with rm -rf, so BE
   CAREFUL how you set KEY_DIR.
4. (Optional) Edit other fields in vars
   per your site data.  You may want to
   increase KEY_SIZE to 2048 if you are
   paranoid and don't mind slower key
   processing, but certainly 1024 is
   fine for testing purposes.  KEY_SIZE
   must be compatible across both peers
   participating in a secure SSL/TLS
   connection.
5  . vars
6. ./clean-all
7. As you create certificates, keys, and
   certificate signing requests, understand that
   only .key files should be kept confidential.
   .crt and .csr files can be sent over insecure
   channels such as plaintext email.
8. You should never need to copy a .key file
   between computers.  Normally each computer
   will have its own certificate/key pair.

BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY

1. ./build-ca
2. ca.crt and ca.key will be built in your KEY_DIR
   directory

BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)

1. ./build-inter inter
2. inter.crt and inter.key will be built in your KEY_DIR
   directory and signed with your root certificate.

BUILD DIFFIE-HELLMAN PARAMETERS (necessary for
the server end of a SSL/TLS connection).

1. ./build-dh

BUILD A CERTIFICATE SIGNING REQUEST (If
you want to sign your certificate with a root
certificate controlled by another individual
or organization, or residing on a different machine).

1. Get ca.crt (the root certificate) from your
   certificate authority.  Though this
   transfer can be over an insecure channel, to prevent
   man-in-the-middle attacks you must confirm that
   ca.crt was not tampered with.  Large CAs solve this
   problem by hardwiring their root certificates into
   popular web browsers.  A simple way to verify a root
   CA is to call the issuer on the telephone and confirm
   that the md5sum or sha1sum signatures on the ca.crt
   files match (such as with the command: "md5sum ca.crt").
2. Choose a name for your certificate such as your computer
   name.  In our example we will use "mycert".
3. ./build-req mycert
4. You can ignore most of the fields, but set
   "Common Name" to something unique such as your
   computer's host name.  Leave all password
   fields blank, unless you want your private key
   to be protected by password.  Using a password
   is not required -- it will make your key more secure
   but also more inconvenient to use, because you will
   need to supply your password anytime the key is used.
   NOTE: if you are using a password, use ./build-req-pass
   instead of ./build-req
5. Your key will be written to $KEY_DIR/mycert.key
6. Your certificate signing request will be written to
   to $KEY_DIR/mycert.csr
7. Email mycert.csr to the individual or organization
   which controls the root certificate.  This can be
   done over an insecure channel.
8. After the .csr file is signed by the root certificate
   authority, you will receive a file mycert.crt
   (your certificate).  Place mycert.crt in your
   KEY_DIR directory.
9. The combined files of mycert.crt, mycert.key,
   and ca.crt can now be used to secure one end of
   an SSL/TLS connection.

SIGN A CERTIFICATE SIGNING REQUEST

1. ./sign-req mycert
2. mycert.crt will be built in your KEY_DIR
   directory using mycert.csr and your root CA
   file as input.

BUILD AND SIGN A CERTIFICATE SIGNING REQUEST
USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY -- this
script generates and signs a certificate in one step,
but it requires that the generated certificate and private
key files be copied to the destination host over a
secure channel.

1. ./build-key mycert (no password protection)
2. OR ./build-key-pass mycert (with password protection)
3. OR ./build-key-pkcs12 mycert (PKCS #12 format)
4. OR ./build-key-server mycert (with nsCertType=server)
5. mycert.crt and mycert.key will be built in your
   KEY_DIR directory, and mycert.crt will be signed
   by your root CA. If ./build-key-pkcs12 was used a
   mycert.p12 file will also be created including the
   private key, certificate and the ca certificate.

IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.
IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.

(4) Sign server certificates with one CA and client certificates
    with a different CA.  The client config "ca" directive should
    reference the server-signing CA while the server config "ca"
    directive should reference the client-signing CA.

NOTES

Show certificate fields:
  openssl x509 -in cert.crt -text
&lt;/pre&gt;
&lt;pre&gt;
# cd easy-rsa
# vi vars
. vars
./clean-all

## BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY
./build.ca

## BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)
./build-inter inter

## BUILD DIFFIE-HELLMAN PARAMETERS (necessary for the server end of a SSL/TLS connection).
./build.dh

## BUILD A CERTIFICATE SIGNING REQUEST 
## (If you want to sign your certificate with a root certificate controlled by another individual 
## or organization, or residing on a different machine)

./build-req mycert
## SIGN A CERTIFICATE SIGNING REQUEST
./sign-req mycert

## BUILD AND SIGN A CERTIFICATE SIGNING REQUEST USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY
./build-key mycert (no password protection)
OR 
./build-key-pass mycert (with password protection)
OR 
./build-key-pkcs12 mycert (PKCS #12 format)
OR 
./build-key-server mycert (with nsCertType=server)
&lt;/pre&gt;

==Configuring the Server==

Edit the server.conf file: '''''vi /etc/openvpn/server.conf'''''
&lt;pre&gt;
## Mode Server
mode server

## Local Host Name/IP Server
;local 127.0.0.1

## Protocol
;proto tcp
proto udp

## Port
; port 1194

## Device Interface
;dev tap
dev tun

## TAP-Win32 adapter name
;dev-node MyTap

## SSL/TLS 
## root certificate (ca)
## certificate (cert)
## private key (key)
ca /etc/openvpn/certs/ca.crt
cert /etc/openvpn/certs/server.crt
key /etc/openvpn/certs/server.key

## Diffie hellman parameters
dh dh1024.pem

## VPN subnet
server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

##ethernet bridging
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

## dhcpcaveats
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

;learn-address ./script

## dhcpcaveats
;push "redirect-gateway"
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

##
;client-to-client

## same "COMMON NAME" certificate/key
;duplicate-cn

## Status Connection
keepalive 10 120

## tls-auth key
;tls-auth ta.key 0 

## Cryptographic cipher
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

## Link Compresion
comp-lzo

## Max Client Connections
;max-clients 100

## daemon privileges (non windows saja)
user nobody
group nobody

persist-key
persist-tun

## Openvpn Log
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

## Output Log
status /var/log/openvpn/openvpn-status.log

## Log Verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## Repeating Messages
;mute 20

## Pid File
writepid /var/run/openvpn.pid
&lt;/pre&gt;

'''Routing'''

&lt;pre&gt;
echo 1 &gt; /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.4.0.2
&lt;/pre&gt;

'''Firewall'''
&lt;pre&gt;
iptables -A INPUT -p udp -s 1.2.3.4 --dport 1194 -j ACCEPT
OR
iptables -A INPUT -p udp --dport 1194 -j ACCEPT

## Tun Device
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT

## Tap Device
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
&lt;/pre&gt;

==Configuring the Client==

Edit the client.conf file: '''''vi /etc/openvpn/client.conf'''''
&lt;pre&gt;
## Config
client

## Device Interface
;dev tap
dev tun

## Tap adapter name (Win only)
;dev-node MyTap

## Conectivity
;proto tcp
proto udp

## Server [hostname/ip] [port]
remote my-server-1 1194
;remote my-server-2 1194

## load-balancing
;remote-random

## resolve host name OpenVPN server
resolv-retry infinite

# local port
nobind

## privileges (non windows saja)
user nobody
group nobody

## preserve
persist-key
persist-tun

## HTTP proxy
;http-proxy-retry 
;http-proxy [proxy server] [proxy port]

## duplicate packet warnings
;mute-replay-warnings

## SSL/TLS parms
/etc/openvpn/certs/ca ca.crt
/etc/openvpn/certs/cert client.crt
/etc/openvpn/certs/key client.key

## nsCertType key
;ns-cert-type server

## tls-auth key
;tls-auth /etc/openvpn/certs/ta.key 1

## Cryptographic cipher
;cipher x

## Link compression
comp-lzo

## verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## repeating messages
;mute 20
&lt;/pre&gt;
'''Routing'''
&lt;pre&gt;
route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.4.0.1 
&lt;/pre&gt;

==Example==

'''Example 1:''' A simple tunnel without security&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 --verb 9
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 --verb 9 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 2:''' A tunnel with static-key security (i.e. using a pre-shared secret)&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--verb 5 --secret key
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--verb 5 --secret key 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 3:''' A tunnel with full TLS-based security &lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--tls-client --ca tmp-ca.crt --cert client.crt --key client.key \
--reneg-sec 60 --verb 5 
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--tls-server --ca tmp-ca.crt --cert server.crt --key server.key \
--reneg-sec 60 --verb 5 --dh dh1024.pem
&lt;/pre&gt;

On May:

    ping 10.4.0.2 

On Jun:

    ping 10.4.0.1

== External Links ==

* http://dmalloc.com/
* http://valgrind.org/
* http://www.oberhumer.com/opensource/lzo/
* http://openvpn.net/
* http://openvpn.net/howto.html
* http://openvpn.net/1xhowto.html (Old-v1.06)
* http://openvpn.net/man.html</text>
    <sha1>16cf36f6e50d2eddcad9877ac59cc03d3ef1c699</sha1>
  </revision>
  <revision>
    <id>707</id>
    <parentid>706</parentid>
    <timestamp>2012-06-07T00:05:04Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>ADDED: Install from Slackbuilds.org</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14317" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.

'''[[OpenVPN(ID)|OpenVPN Instructions - Bahasa Indonesia]]'''


__TOC__
== Installation ==

'''EASY WAY:'''
Download and install from Slackbuilds.org or sbopkg.

or

'''HARD WAY:'''
Install from source.

Download source from [http://openvpn.net openvpn.net]

Download verison 2.0

install Lzo
&lt;pre&gt;
tar zxvf lzo-1.08.tar.gz
cd lzo-1-08.tar.gz
./configure --prefix=/usr
make ; make install-strip
&lt;/pre&gt;
install OpenVPN
&lt;pre&gt;
tar zxvf openvpn-2.0.tar.gz
cd openvpn-2.0
./configure --prefix=/usr \
--sysconfdir=/etc/openvpn \
--enable-pthread \
--enable-iproute2 \
--with-ssl \
--with-lzo-header=/usr/include \
--with-lzo-lib=/usr/lib \
--with-ifconfig \
--with-route \
--with-mem-check=dmalloc 
make ; make install-strip
&lt;/pre&gt;


==Creating The Certificates==

Save all certificates in '''''/etc/openvpn/certs'''''
&lt;pre&gt;
This is a small RSA key management package,
based on the openssl command line tool, that
can be found in the easy-rsa subdirectory
of the OpenVPN distribution.

These are reference notes.  For step
by step instructions, see the HOWTO:

http://openvpn.net/howto.html

INSTALL

1. Edit vars.
2. Set KEY_CONFIG to point to the openssl.cnf file
   included in this distribution.
3. Set KEY_DIR to point to a directory which will
   contain all keys, certificates, etc.  This
   directory need not exist, and if it does,
   it will be deleted with rm -rf, so BE
   CAREFUL how you set KEY_DIR.
4. (Optional) Edit other fields in vars
   per your site data.  You may want to
   increase KEY_SIZE to 2048 if you are
   paranoid and don't mind slower key
   processing, but certainly 1024 is
   fine for testing purposes.  KEY_SIZE
   must be compatible across both peers
   participating in a secure SSL/TLS
   connection.
5  . vars
6. ./clean-all
7. As you create certificates, keys, and
   certificate signing requests, understand that
   only .key files should be kept confidential.
   .crt and .csr files can be sent over insecure
   channels such as plaintext email.
8. You should never need to copy a .key file
   between computers.  Normally each computer
   will have its own certificate/key pair.

BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY

1. ./build-ca
2. ca.crt and ca.key will be built in your KEY_DIR
   directory

BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)

1. ./build-inter inter
2. inter.crt and inter.key will be built in your KEY_DIR
   directory and signed with your root certificate.

BUILD DIFFIE-HELLMAN PARAMETERS (necessary for
the server end of a SSL/TLS connection).

1. ./build-dh

BUILD A CERTIFICATE SIGNING REQUEST (If
you want to sign your certificate with a root
certificate controlled by another individual
or organization, or residing on a different machine).

1. Get ca.crt (the root certificate) from your
   certificate authority.  Though this
   transfer can be over an insecure channel, to prevent
   man-in-the-middle attacks you must confirm that
   ca.crt was not tampered with.  Large CAs solve this
   problem by hardwiring their root certificates into
   popular web browsers.  A simple way to verify a root
   CA is to call the issuer on the telephone and confirm
   that the md5sum or sha1sum signatures on the ca.crt
   files match (such as with the command: "md5sum ca.crt").
2. Choose a name for your certificate such as your computer
   name.  In our example we will use "mycert".
3. ./build-req mycert
4. You can ignore most of the fields, but set
   "Common Name" to something unique such as your
   computer's host name.  Leave all password
   fields blank, unless you want your private key
   to be protected by password.  Using a password
   is not required -- it will make your key more secure
   but also more inconvenient to use, because you will
   need to supply your password anytime the key is used.
   NOTE: if you are using a password, use ./build-req-pass
   instead of ./build-req
5. Your key will be written to $KEY_DIR/mycert.key
6. Your certificate signing request will be written to
   to $KEY_DIR/mycert.csr
7. Email mycert.csr to the individual or organization
   which controls the root certificate.  This can be
   done over an insecure channel.
8. After the .csr file is signed by the root certificate
   authority, you will receive a file mycert.crt
   (your certificate).  Place mycert.crt in your
   KEY_DIR directory.
9. The combined files of mycert.crt, mycert.key,
   and ca.crt can now be used to secure one end of
   an SSL/TLS connection.

SIGN A CERTIFICATE SIGNING REQUEST

1. ./sign-req mycert
2. mycert.crt will be built in your KEY_DIR
   directory using mycert.csr and your root CA
   file as input.

BUILD AND SIGN A CERTIFICATE SIGNING REQUEST
USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY -- this
script generates and signs a certificate in one step,
but it requires that the generated certificate and private
key files be copied to the destination host over a
secure channel.

1. ./build-key mycert (no password protection)
2. OR ./build-key-pass mycert (with password protection)
3. OR ./build-key-pkcs12 mycert (PKCS #12 format)
4. OR ./build-key-server mycert (with nsCertType=server)
5. mycert.crt and mycert.key will be built in your
   KEY_DIR directory, and mycert.crt will be signed
   by your root CA. If ./build-key-pkcs12 was used a
   mycert.p12 file will also be created including the
   private key, certificate and the ca certificate.

IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.
IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.

(4) Sign server certificates with one CA and client certificates
    with a different CA.  The client config "ca" directive should
    reference the server-signing CA while the server config "ca"
    directive should reference the client-signing CA.

NOTES

Show certificate fields:
  openssl x509 -in cert.crt -text
&lt;/pre&gt;
&lt;pre&gt;
# cd easy-rsa
# vi vars
. vars
./clean-all

## BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY
./build.ca

## BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)
./build-inter inter

## BUILD DIFFIE-HELLMAN PARAMETERS (necessary for the server end of a SSL/TLS connection).
./build.dh

## BUILD A CERTIFICATE SIGNING REQUEST 
## (If you want to sign your certificate with a root certificate controlled by another individual 
## or organization, or residing on a different machine)

./build-req mycert
## SIGN A CERTIFICATE SIGNING REQUEST
./sign-req mycert

## BUILD AND SIGN A CERTIFICATE SIGNING REQUEST USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY
./build-key mycert (no password protection)
OR 
./build-key-pass mycert (with password protection)
OR 
./build-key-pkcs12 mycert (PKCS #12 format)
OR 
./build-key-server mycert (with nsCertType=server)
&lt;/pre&gt;

==Configuring the Server==

Edit the server.conf file: '''''vi /etc/openvpn/server.conf'''''
&lt;pre&gt;
## Mode Server
mode server

## Local Host Name/IP Server
;local 127.0.0.1

## Protocol
;proto tcp
proto udp

## Port
; port 1194

## Device Interface
;dev tap
dev tun

## TAP-Win32 adapter name
;dev-node MyTap

## SSL/TLS 
## root certificate (ca)
## certificate (cert)
## private key (key)
ca /etc/openvpn/certs/ca.crt
cert /etc/openvpn/certs/server.crt
key /etc/openvpn/certs/server.key

## Diffie hellman parameters
dh dh1024.pem

## VPN subnet
server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

##ethernet bridging
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

## dhcpcaveats
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

;learn-address ./script

## dhcpcaveats
;push "redirect-gateway"
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

##
;client-to-client

## same "COMMON NAME" certificate/key
;duplicate-cn

## Status Connection
keepalive 10 120

## tls-auth key
;tls-auth ta.key 0 

## Cryptographic cipher
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

## Link Compresion
comp-lzo

## Max Client Connections
;max-clients 100

## daemon privileges (non windows saja)
user nobody
group nobody

persist-key
persist-tun

## Openvpn Log
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

## Output Log
status /var/log/openvpn/openvpn-status.log

## Log Verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## Repeating Messages
;mute 20

## Pid File
writepid /var/run/openvpn.pid
&lt;/pre&gt;

'''Routing'''

&lt;pre&gt;
echo 1 &gt; /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.4.0.2
&lt;/pre&gt;

'''Firewall'''
&lt;pre&gt;
iptables -A INPUT -p udp -s 1.2.3.4 --dport 1194 -j ACCEPT
OR
iptables -A INPUT -p udp --dport 1194 -j ACCEPT

## Tun Device
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT

## Tap Device
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
&lt;/pre&gt;

==Configuring the Client==

Edit the client.conf file: '''''vi /etc/openvpn/client.conf'''''
&lt;pre&gt;
## Config
client

## Device Interface
;dev tap
dev tun

## Tap adapter name (Win only)
;dev-node MyTap

## Conectivity
;proto tcp
proto udp

## Server [hostname/ip] [port]
remote my-server-1 1194
;remote my-server-2 1194

## load-balancing
;remote-random

## resolve host name OpenVPN server
resolv-retry infinite

# local port
nobind

## privileges (non windows saja)
user nobody
group nobody

## preserve
persist-key
persist-tun

## HTTP proxy
;http-proxy-retry 
;http-proxy [proxy server] [proxy port]

## duplicate packet warnings
;mute-replay-warnings

## SSL/TLS parms
/etc/openvpn/certs/ca ca.crt
/etc/openvpn/certs/cert client.crt
/etc/openvpn/certs/key client.key

## nsCertType key
;ns-cert-type server

## tls-auth key
;tls-auth /etc/openvpn/certs/ta.key 1

## Cryptographic cipher
;cipher x

## Link compression
comp-lzo

## verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## repeating messages
;mute 20
&lt;/pre&gt;
'''Routing'''
&lt;pre&gt;
route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.4.0.1 
&lt;/pre&gt;

==Example==

'''Example 1:''' A simple tunnel without security&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 --verb 9
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 --verb 9 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 2:''' A tunnel with static-key security (i.e. using a pre-shared secret)&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--verb 5 --secret key
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--verb 5 --secret key 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 3:''' A tunnel with full TLS-based security &lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--tls-client --ca tmp-ca.crt --cert client.crt --key client.key \
--reneg-sec 60 --verb 5 
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--tls-server --ca tmp-ca.crt --cert server.crt --key server.key \
--reneg-sec 60 --verb 5 --dh dh1024.pem
&lt;/pre&gt;

On May:

    ping 10.4.0.2 

On Jun:

    ping 10.4.0.1

== External Links ==

* http://dmalloc.com/
* http://valgrind.org/
* http://www.oberhumer.com/opensource/lzo/
* http://openvpn.net/
* http://openvpn.net/howto.html
* http://openvpn.net/1xhowto.html (Old-v1.06)
* http://openvpn.net/man.html</text>
    <sha1>0462ca3047258dda5e6c37ec123b891898da6831</sha1>
  </revision>
  <revision>
    <id>712</id>
    <parentid>707</parentid>
    <timestamp>2012-06-09T19:10:37Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Moved old instructions to their own page. Made this page a menu for the instructions</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="518" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.


[[openvpn_smcr_2012|OpenVPN server setup on Slackware 13.37]] - Multi-client with routing (not bridged). (2012)

[[openvpn_pre-2009|OpenVPN server/client instructions]] (Pre-2009)


[[OpenVPN(ID)|OpenVPN Instructions - Bahasa Indonesia]] (Pre-2009)</text>
    <sha1>c4dcfbe0b1b7c77302665f1f61a11c36b109a679</sha1>
  </revision>
  <revision>
    <id>713</id>
    <parentid>712</parentid>
    <timestamp>2012-06-09T19:12:02Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>Fixed broken link</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="518" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.


[[OpenVPN_smcr_2012|OpenVPN server setup on Slackware 13.37]] - Multi-client with routing (not bridged). (2012)

[[OpenVPN_pre-2009|OpenVPN server/client instructions]] (Pre-2009)


[[OpenVPN(ID)|OpenVPN Instructions - Bahasa Indonesia]] (Pre-2009)</text>
    <sha1>46595cab4b4db12413ceb82b2c8e661358a584d9</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Pptp</title>
  <ns>0</ns>
  <id>285</id>
  <revision>
    <id>708</id>
    <timestamp>2012-06-09T18:13:06Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Created!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3233" xml:space="preserve">==(Poptop) pptpd Server Setup==

Here's what I did to get Poptop pptpd (1.3.4) running on my Slackware (13.37) box.

 1) Install the official Slackware ppp package using pkgtool or slackpkg.
 
 2) Install the ppptpd package from Slackbuilds.org using sbopkg.
 	***NOTE: The package name is NOT Poptop, it's pptpd***
 
 3) Edit /etc/pptpd.conf
 
 	ADD:
 		localip 10.7.0.1
 		remoteip 10.7.0.2-50
 	CHANGE:
 		option /etc/ppp/options.pptpd -&gt; option /etc/ppp/options
 
 4) Edit /etc/ppp/options
 	HERE IS A GOTCHA- The official Slackware ppp package (at the time of this writing) contains an error in the options
 	file. The pppd binary was compiled to look for the new ms-dns parameter but the option file has the old dns-addr
 	parameter.
 
 	CHANGE:
 	# dns-addr 192.168.1.1 -&gt; ms-dns 8.8.8.8 (or whatever your dns server is)
 
 5) Edit the /etc/ppp/chap-secrets file.
 	For some reason, the default Slackware package has 4 example entries in it that are not commented (jacco,*,sam,*)
 	delete these.  You don't want jacco or sam to have a free connection into your box...
 
 	ADD: one entry for each user you want to allow access.
 	Format is: CLIENT [tab] SERVER [tab] PASSWORD [tab] IP ADDRESS
 	Mine looks like this:
 
 	bob	*	"BobsPasswordIsStrong"	*
 	sue	*	"FluffyBunnies92"	*
 
 6) Finally to start pptpd, n0rmally you would just execute 'pptpd &amp;' but being that I'm a good Slacker, I wrote an
 rc.pptpd script.
 	Create /etc/rc.d/rc.pptpd
 	contents:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.pptpd
 		#
 		# Start/stop/restart the pptpd server.
 		#
 		# To make PopTop start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.pptpd
 		#
 		
 		pptpd_start() {
 		  if [ -x /usr/sbin/pptpd ]; then
 		    echo "Starting PopTop pptpd:  /usr/sbin/pptpd server.conf"
 		    /usr/sbin/pptpd &amp;
 		  fi
 		}
 		
 		pptpd_stop() {
 		  killall pptpd
 		}
 		
 		pptpd_restart() {
 		  pptpd_stop
 		  sleep 2
 		  pptpd_start
 		}
 		
 		case "$1" in
 		'start')
 		  pptpd_start
 		  ;;
 		'stop')
 		  pptpd_stop
 		  ;;
 		'restart')
 		  pptpd_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  pptpd_start
 		esac
 
 
 7) Make it executable (and autobootable on start up)
 
 	chmod 755 /etc/rc.d/rc.pptpd
 
 To start it manually- /etc/rc.d/rc.pptpd start
 
 To be useful you next need to configure your firewall to forward and masquerade traffic from the vpn out to
 the world...
 
 8) Edit/create: /etc/rc.d/rc.firewall
 
 	ADD:
 		iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 		iptables -A FORWARD -i ppp+ -j ACCEPT
 		iptables -A FORWARD -o ppp+ -j ACCEPT
 		iptables -A FORWARD -j ACCEPT
 		iptables -t nat -A POSTROUTING -s 10.7.0.0/24 -o ppp+ -j MASQUERADE
 
 9) Make it executable
 
 	chmod 755 /etc/rc.d/rc.firewall
 
 10) Flush the old firewall rules (forgetting to do this caused me all sorts of grief (Thanks mancha))
 
 	iptables -f
 
 11) Execute the new firewall rules
 
 	/etc/rc.d/rc.firewall
 
 If you and I haven't made any mistakes, you should now have pptp (server) and router working on your box.


==pptp Client Setup==

Needs to be added.</text>
    <sha1>04087f08d587a72677a2abcec795f43b6fcba306</sha1>
  </revision>
  <revision>
    <id>709</id>
    <parentid>708</parentid>
    <timestamp>2012-06-09T18:16:31Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>/* (Poptop) pptpd Server Setup */  typo fix</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3232" xml:space="preserve">==(Poptop) pptpd Server Setup==

Here's what I did to get Poptop pptpd (1.3.4) running on my Slackware (13.37) box.

 1) Install the official Slackware ppp package using pkgtool or slackpkg.
 
 2) Install the ppptpd package from Slackbuilds.org using sbopkg.
 	***NOTE: The package name is NOT Poptop, it's pptpd***
 
 3) Edit /etc/pptpd.conf
 
 	ADD:
 		localip 10.7.0.1
 		remoteip 10.7.0.2-50
 	CHANGE:
 		option /etc/ppp/options.pptpd -&gt; option /etc/ppp/options
 
 4) Edit /etc/ppp/options
 	HERE IS A GOTCHA- The official Slackware ppp package (at the time of this writing) contains an error in the options
 	file. The pppd binary was compiled to look for the new ms-dns parameter but the option file has the old dns-addr
 	parameter.
 
 	CHANGE:
 	# dns-addr 192.168.1.1 -&gt; ms-dns 8.8.8.8 (or whatever your dns server is)
 
 5) Edit the /etc/ppp/chap-secrets file.
 	For some reason, the default Slackware package has 4 example entries in it that are not commented (jacco,*,sam,*)
 	delete these.  You don't want jacco or sam to have a free connection into your box...
 
 	ADD: one entry for each user you want to allow access.
 	Format is: CLIENT [tab] SERVER [tab] PASSWORD [tab] IP ADDRESS
 	Mine looks like this:
 
 	bob	*	"BobsPasswordIsStrong"	*
 	sue	*	"FluffyBunnies92"	*
 
 6) Finally to start pptpd, normally you would just execute 'pptpd &amp;' but being that I'm a good Slacker, I wrote an
 rc.pptpd script.
 	Create /etc/rc.d/rc.pptpd
 	contents:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.pptpd
 		#
 		# Start/stop/restart the pptpd server.
 		#
 		# To make PopTop start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.pptpd
 		#
 		
 		pptpd_start() {
 		  if [ -x /usr/sbin/pptpd ]; then
 		    echo "Starting PopTop pptpd:  /usr/sbin/pptpd server.conf"
 		    /usr/sbin/pptpd &amp;
 		  fi
 		}
 		
 		pptpd_stop() {
 		  killall pptpd
 		}
 		
 		pptpd_restart() {
 		  pptpd_stop
 		  sleep 2
 		  pptpd_start
 		}
 		
 		case "$1" in
 		'start')
 		  pptpd_start
 		  ;;
 		'stop')
 		  pptpd_stop
 		  ;;
 		'restart')
 		  pptpd_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  pptpd_start
 		esac
 
 
 7) Make it executable (and autobootable on start up)
 
 	chmod 755 /etc/rc.d/rc.pptpd
 
 To start it manually- /etc/rc.d/rc.pptpd start
 
 To be useful you next need to configure your firewall to forward and masquerade traffic from the vpn out to
 the world...
 
 8) Edit/create: /etc/rc.d/rc.firewall
 
 	ADD:
 		iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 		iptables -A FORWARD -i ppp+ -j ACCEPT
 		iptables -A FORWARD -o ppp+ -j ACCEPT
 		iptables -A FORWARD -j ACCEPT
 		iptables -t nat -A POSTROUTING -s 10.7.0.0/24 -o ppp+ -j MASQUERADE
 
 9) Make it executable
 
 	chmod 755 /etc/rc.d/rc.firewall
 
 10) Flush the old firewall rules (forgetting to do this caused me all sorts of grief (Thanks mancha))
 
 	iptables -f
 
 11) Execute the new firewall rules
 
 	/etc/rc.d/rc.firewall
 
 If you and I haven't made any mistakes, you should now have pptp (server) and router working on your box.

==pptp Client Setup==

Needs to be added.</text>
    <sha1>f5a5426ef0503c838e44548b65e63465012b2af8</sha1>
  </revision>
  <revision>
    <id>710</id>
    <parentid>709</parentid>
    <timestamp>2012-06-09T19:00:22Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>/* (Poptop) pptpd Server Setup */  iptables -f --&gt; iptables -F</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3232" xml:space="preserve">==(Poptop) pptpd Server Setup==

Here's what I did to get Poptop pptpd (1.3.4) running on my Slackware (13.37) box.

 1) Install the official Slackware ppp package using pkgtool or slackpkg.
 
 2) Install the ppptpd package from Slackbuilds.org using sbopkg.
 	***NOTE: The package name is NOT Poptop, it's pptpd***
 
 3) Edit /etc/pptpd.conf
 
 	ADD:
 		localip 10.7.0.1
 		remoteip 10.7.0.2-50
 	CHANGE:
 		option /etc/ppp/options.pptpd -&gt; option /etc/ppp/options
 
 4) Edit /etc/ppp/options
 	HERE IS A GOTCHA- The official Slackware ppp package (at the time of this writing) contains an error in the options
 	file. The pppd binary was compiled to look for the new ms-dns parameter but the option file has the old dns-addr
 	parameter.
 
 	CHANGE:
 	# dns-addr 192.168.1.1 -&gt; ms-dns 8.8.8.8 (or whatever your dns server is)
 
 5) Edit the /etc/ppp/chap-secrets file.
 	For some reason, the default Slackware package has 4 example entries in it that are not commented (jacco,*,sam,*)
 	delete these.  You don't want jacco or sam to have a free connection into your box...
 
 	ADD: one entry for each user you want to allow access.
 	Format is: CLIENT [tab] SERVER [tab] PASSWORD [tab] IP ADDRESS
 	Mine looks like this:
 
 	bob	*	"BobsPasswordIsStrong"	*
 	sue	*	"FluffyBunnies92"	*
 
 6) Finally to start pptpd, normally you would just execute 'pptpd &amp;' but being that I'm a good Slacker, I wrote an
 rc.pptpd script.
 	Create /etc/rc.d/rc.pptpd
 	contents:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.pptpd
 		#
 		# Start/stop/restart the pptpd server.
 		#
 		# To make PopTop start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.pptpd
 		#
 		
 		pptpd_start() {
 		  if [ -x /usr/sbin/pptpd ]; then
 		    echo "Starting PopTop pptpd:  /usr/sbin/pptpd server.conf"
 		    /usr/sbin/pptpd &amp;
 		  fi
 		}
 		
 		pptpd_stop() {
 		  killall pptpd
 		}
 		
 		pptpd_restart() {
 		  pptpd_stop
 		  sleep 2
 		  pptpd_start
 		}
 		
 		case "$1" in
 		'start')
 		  pptpd_start
 		  ;;
 		'stop')
 		  pptpd_stop
 		  ;;
 		'restart')
 		  pptpd_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  pptpd_start
 		esac
 
 
 7) Make it executable (and autobootable on start up)
 
 	chmod 755 /etc/rc.d/rc.pptpd
 
 To start it manually- /etc/rc.d/rc.pptpd start
 
 To be useful you next need to configure your firewall to forward and masquerade traffic from the vpn out to
 the world...
 
 8) Edit/create: /etc/rc.d/rc.firewall
 
 	ADD:
 		iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 		iptables -A FORWARD -i ppp+ -j ACCEPT
 		iptables -A FORWARD -o ppp+ -j ACCEPT
 		iptables -A FORWARD -j ACCEPT
 		iptables -t nat -A POSTROUTING -s 10.7.0.0/24 -o ppp+ -j MASQUERADE
 
 9) Make it executable
 
 	chmod 755 /etc/rc.d/rc.firewall
 
 10) Flush the old firewall rules (forgetting to do this caused me all sorts of grief (Thanks mancha))
 
 	iptables -F
 
 11) Execute the new firewall rules
 
 	/etc/rc.d/rc.firewall
 
 If you and I haven't made any mistakes, you should now have pptp (server) and router working on your box.

==pptp Client Setup==

Needs to be added.</text>
    <sha1>d6ca6f32fbd8bdc4361414e4b2f4a70f84d87995</sha1>
  </revision>
  <revision>
    <id>725</id>
    <parentid>710</parentid>
    <timestamp>2012-06-13T14:50:40Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>ADDED: categories</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3300" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]

==(Poptop) pptpd Server Setup==

Here's what I did to get Poptop pptpd (1.3.4) running on my Slackware (13.37) box.

 1) Install the official Slackware ppp package using pkgtool or slackpkg.
 
 2) Install the ppptpd package from Slackbuilds.org using sbopkg.
 	***NOTE: The package name is NOT Poptop, it's pptpd***
 
 3) Edit /etc/pptpd.conf
 
 	ADD:
 		localip 10.7.0.1
 		remoteip 10.7.0.2-50
 	CHANGE:
 		option /etc/ppp/options.pptpd -&gt; option /etc/ppp/options
 
 4) Edit /etc/ppp/options
 	HERE IS A GOTCHA- The official Slackware ppp package (at the time of this writing) contains an error in the options
 	file. The pppd binary was compiled to look for the new ms-dns parameter but the option file has the old dns-addr
 	parameter.
 
 	CHANGE:
 	# dns-addr 192.168.1.1 -&gt; ms-dns 8.8.8.8 (or whatever your dns server is)
 
 5) Edit the /etc/ppp/chap-secrets file.
 	For some reason, the default Slackware package has 4 example entries in it that are not commented (jacco,*,sam,*)
 	delete these.  You don't want jacco or sam to have a free connection into your box...
 
 	ADD: one entry for each user you want to allow access.
 	Format is: CLIENT [tab] SERVER [tab] PASSWORD [tab] IP ADDRESS
 	Mine looks like this:
 
 	bob	*	"BobsPasswordIsStrong"	*
 	sue	*	"FluffyBunnies92"	*
 
 6) Finally to start pptpd, normally you would just execute 'pptpd &amp;' but being that I'm a good Slacker, I wrote an
 rc.pptpd script.
 	Create /etc/rc.d/rc.pptpd
 	contents:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.pptpd
 		#
 		# Start/stop/restart the pptpd server.
 		#
 		# To make PopTop start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.pptpd
 		#
 		
 		pptpd_start() {
 		  if [ -x /usr/sbin/pptpd ]; then
 		    echo "Starting PopTop pptpd:  /usr/sbin/pptpd server.conf"
 		    /usr/sbin/pptpd &amp;
 		  fi
 		}
 		
 		pptpd_stop() {
 		  killall pptpd
 		}
 		
 		pptpd_restart() {
 		  pptpd_stop
 		  sleep 2
 		  pptpd_start
 		}
 		
 		case "$1" in
 		'start')
 		  pptpd_start
 		  ;;
 		'stop')
 		  pptpd_stop
 		  ;;
 		'restart')
 		  pptpd_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  pptpd_start
 		esac
 
 
 7) Make it executable (and autobootable on start up)
 
 	chmod 755 /etc/rc.d/rc.pptpd
 
 To start it manually- /etc/rc.d/rc.pptpd start
 
 To be useful you next need to configure your firewall to forward and masquerade traffic from the vpn out to
 the world...
 
 8) Edit/create: /etc/rc.d/rc.firewall
 
 	ADD:
 		iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 		iptables -A FORWARD -i ppp+ -j ACCEPT
 		iptables -A FORWARD -o ppp+ -j ACCEPT
 		iptables -A FORWARD -j ACCEPT
 		iptables -t nat -A POSTROUTING -s 10.7.0.0/24 -o ppp+ -j MASQUERADE
 
 9) Make it executable
 
 	chmod 755 /etc/rc.d/rc.firewall
 
 10) Flush the old firewall rules (forgetting to do this caused me all sorts of grief (Thanks mancha))
 
 	iptables -F
 
 11) Execute the new firewall rules
 
 	/etc/rc.d/rc.firewall
 
 If you and I haven't made any mistakes, you should now have pptp (server) and router working on your box.

==pptp Client Setup==

Needs to be added.</text>
    <sha1>a28dd0fdb696a708217fbb99c929d401a1f060b9</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>OpenVPN pre-2009</title>
  <ns>0</ns>
  <id>286</id>
  <revision>
    <id>711</id>
    <timestamp>2012-06-09T19:03:37Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Moved from OpenVPN</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="14317" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]
As a user-space VPN daemon, OpenVPN is compatible with with SSL/TLS, RSA Certificates and X509 PKI, NAT, DHCP, and TUN/TAP virtual devices.

OpenVPN is not compatible with IPSec, IKE, PPTP, or L2TP.

'''[[OpenVPN(ID)|OpenVPN Instructions - Bahasa Indonesia]]'''


__TOC__
== Installation ==

'''EASY WAY:'''
Download and install from Slackbuilds.org or sbopkg.

or

'''HARD WAY:'''
Install from source.

Download source from [http://openvpn.net openvpn.net]

Download verison 2.0

install Lzo
&lt;pre&gt;
tar zxvf lzo-1.08.tar.gz
cd lzo-1-08.tar.gz
./configure --prefix=/usr
make ; make install-strip
&lt;/pre&gt;
install OpenVPN
&lt;pre&gt;
tar zxvf openvpn-2.0.tar.gz
cd openvpn-2.0
./configure --prefix=/usr \
--sysconfdir=/etc/openvpn \
--enable-pthread \
--enable-iproute2 \
--with-ssl \
--with-lzo-header=/usr/include \
--with-lzo-lib=/usr/lib \
--with-ifconfig \
--with-route \
--with-mem-check=dmalloc 
make ; make install-strip
&lt;/pre&gt;


==Creating The Certificates==

Save all certificates in '''''/etc/openvpn/certs'''''
&lt;pre&gt;
This is a small RSA key management package,
based on the openssl command line tool, that
can be found in the easy-rsa subdirectory
of the OpenVPN distribution.

These are reference notes.  For step
by step instructions, see the HOWTO:

http://openvpn.net/howto.html

INSTALL

1. Edit vars.
2. Set KEY_CONFIG to point to the openssl.cnf file
   included in this distribution.
3. Set KEY_DIR to point to a directory which will
   contain all keys, certificates, etc.  This
   directory need not exist, and if it does,
   it will be deleted with rm -rf, so BE
   CAREFUL how you set KEY_DIR.
4. (Optional) Edit other fields in vars
   per your site data.  You may want to
   increase KEY_SIZE to 2048 if you are
   paranoid and don't mind slower key
   processing, but certainly 1024 is
   fine for testing purposes.  KEY_SIZE
   must be compatible across both peers
   participating in a secure SSL/TLS
   connection.
5  . vars
6. ./clean-all
7. As you create certificates, keys, and
   certificate signing requests, understand that
   only .key files should be kept confidential.
   .crt and .csr files can be sent over insecure
   channels such as plaintext email.
8. You should never need to copy a .key file
   between computers.  Normally each computer
   will have its own certificate/key pair.

BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY

1. ./build-ca
2. ca.crt and ca.key will be built in your KEY_DIR
   directory

BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)

1. ./build-inter inter
2. inter.crt and inter.key will be built in your KEY_DIR
   directory and signed with your root certificate.

BUILD DIFFIE-HELLMAN PARAMETERS (necessary for
the server end of a SSL/TLS connection).

1. ./build-dh

BUILD A CERTIFICATE SIGNING REQUEST (If
you want to sign your certificate with a root
certificate controlled by another individual
or organization, or residing on a different machine).

1. Get ca.crt (the root certificate) from your
   certificate authority.  Though this
   transfer can be over an insecure channel, to prevent
   man-in-the-middle attacks you must confirm that
   ca.crt was not tampered with.  Large CAs solve this
   problem by hardwiring their root certificates into
   popular web browsers.  A simple way to verify a root
   CA is to call the issuer on the telephone and confirm
   that the md5sum or sha1sum signatures on the ca.crt
   files match (such as with the command: "md5sum ca.crt").
2. Choose a name for your certificate such as your computer
   name.  In our example we will use "mycert".
3. ./build-req mycert
4. You can ignore most of the fields, but set
   "Common Name" to something unique such as your
   computer's host name.  Leave all password
   fields blank, unless you want your private key
   to be protected by password.  Using a password
   is not required -- it will make your key more secure
   but also more inconvenient to use, because you will
   need to supply your password anytime the key is used.
   NOTE: if you are using a password, use ./build-req-pass
   instead of ./build-req
5. Your key will be written to $KEY_DIR/mycert.key
6. Your certificate signing request will be written to
   to $KEY_DIR/mycert.csr
7. Email mycert.csr to the individual or organization
   which controls the root certificate.  This can be
   done over an insecure channel.
8. After the .csr file is signed by the root certificate
   authority, you will receive a file mycert.crt
   (your certificate).  Place mycert.crt in your
   KEY_DIR directory.
9. The combined files of mycert.crt, mycert.key,
   and ca.crt can now be used to secure one end of
   an SSL/TLS connection.

SIGN A CERTIFICATE SIGNING REQUEST

1. ./sign-req mycert
2. mycert.crt will be built in your KEY_DIR
   directory using mycert.csr and your root CA
   file as input.

BUILD AND SIGN A CERTIFICATE SIGNING REQUEST
USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY -- this
script generates and signs a certificate in one step,
but it requires that the generated certificate and private
key files be copied to the destination host over a
secure channel.

1. ./build-key mycert (no password protection)
2. OR ./build-key-pass mycert (with password protection)
3. OR ./build-key-pkcs12 mycert (PKCS #12 format)
4. OR ./build-key-server mycert (with nsCertType=server)
5. mycert.crt and mycert.key will be built in your
   KEY_DIR directory, and mycert.crt will be signed
   by your root CA. If ./build-key-pkcs12 was used a
   mycert.p12 file will also be created including the
   private key, certificate and the ca certificate.

IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.
IMPORTANT

To avoid a possible Man-in-the-Middle attack where an authorized
client tries to connect to another client by impersonating the
server, make sure to enforce some kind of server certificate
verification by clients.  There are currently four different ways
of accomplishing this, listed in the order of preference:

(1) Build your server certificates with the build-key-server
    script.  This will designate the certificate as a
    server-only certificate by setting nsCertType=server.
    Now add the following line to your client configuration:

    ns-cert-type server

    This will block clients from connecting to any
    server which lacks the nsCertType=server designation
    in its certificate, even if the certificate has been
    signed by the CA which is cited in the OpenVPN configuration
    file (--ca directive).

(2) Use the --tls-remote directive on the client to
    accept/reject the server connection based on the common
    name of the server certificate.

(3) Use a --tls-verify script or plugin to accept/reject the
    server connection based on a custom test of the server
    certificate's embedded X509 subject details.

(4) Sign server certificates with one CA and client certificates
    with a different CA.  The client config "ca" directive should
    reference the server-signing CA while the server config "ca"
    directive should reference the client-signing CA.

NOTES

Show certificate fields:
  openssl x509 -in cert.crt -text
&lt;/pre&gt;
&lt;pre&gt;
# cd easy-rsa
# vi vars
. vars
./clean-all

## BUILD YOUR OWN ROOT CERTIFICATE AUTHORITY (CA) CERTIFICATE/KEY
./build.ca

## BUILD AN INTERMEDIATE CERTIFICATE AUTHORITY CERTIFICATE/KEY (optional)
./build-inter inter

## BUILD DIFFIE-HELLMAN PARAMETERS (necessary for the server end of a SSL/TLS connection).
./build.dh

## BUILD A CERTIFICATE SIGNING REQUEST 
## (If you want to sign your certificate with a root certificate controlled by another individual 
## or organization, or residing on a different machine)

./build-req mycert
## SIGN A CERTIFICATE SIGNING REQUEST
./sign-req mycert

## BUILD AND SIGN A CERTIFICATE SIGNING REQUEST USING A LOCALLY INSTALLED ROOT CERTIFICATE/KEY
./build-key mycert (no password protection)
OR 
./build-key-pass mycert (with password protection)
OR 
./build-key-pkcs12 mycert (PKCS #12 format)
OR 
./build-key-server mycert (with nsCertType=server)
&lt;/pre&gt;

==Configuring the Server==

Edit the server.conf file: '''''vi /etc/openvpn/server.conf'''''
&lt;pre&gt;
## Mode Server
mode server

## Local Host Name/IP Server
;local 127.0.0.1

## Protocol
;proto tcp
proto udp

## Port
; port 1194

## Device Interface
;dev tap
dev tun

## TAP-Win32 adapter name
;dev-node MyTap

## SSL/TLS 
## root certificate (ca)
## certificate (cert)
## private key (key)
ca /etc/openvpn/certs/ca.crt
cert /etc/openvpn/certs/server.crt
key /etc/openvpn/certs/server.key

## Diffie hellman parameters
dh dh1024.pem

## VPN subnet
server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

##ethernet bridging
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

## dhcpcaveats
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

;client-config-dir ccd

;route 192.168.40.128 255.255.255.248

;client-config-dir ccd

;route 10.9.0.0 255.255.255.252

;learn-address ./script

## dhcpcaveats
;push "redirect-gateway"
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"

##
;client-to-client

## same "COMMON NAME" certificate/key
;duplicate-cn

## Status Connection
keepalive 10 120

## tls-auth key
;tls-auth ta.key 0 

## Cryptographic cipher
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

## Link Compresion
comp-lzo

## Max Client Connections
;max-clients 100

## daemon privileges (non windows saja)
user nobody
group nobody

persist-key
persist-tun

## Openvpn Log
;log         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/openvpn.log

## Output Log
status /var/log/openvpn/openvpn-status.log

## Log Verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## Repeating Messages
;mute 20

## Pid File
writepid /var/run/openvpn.pid
&lt;/pre&gt;

'''Routing'''

&lt;pre&gt;
echo 1 &gt; /proc/sys/net/ipv4/ip_forward
route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.4.0.2
&lt;/pre&gt;

'''Firewall'''
&lt;pre&gt;
iptables -A INPUT -p udp -s 1.2.3.4 --dport 1194 -j ACCEPT
OR
iptables -A INPUT -p udp --dport 1194 -j ACCEPT

## Tun Device
iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT

## Tap Device
iptables -A INPUT -i tap+ -j ACCEPT
iptables -A FORWARD -i tap+ -j ACCEPT
&lt;/pre&gt;

==Configuring the Client==

Edit the client.conf file: '''''vi /etc/openvpn/client.conf'''''
&lt;pre&gt;
## Config
client

## Device Interface
;dev tap
dev tun

## Tap adapter name (Win only)
;dev-node MyTap

## Conectivity
;proto tcp
proto udp

## Server [hostname/ip] [port]
remote my-server-1 1194
;remote my-server-2 1194

## load-balancing
;remote-random

## resolve host name OpenVPN server
resolv-retry infinite

# local port
nobind

## privileges (non windows saja)
user nobody
group nobody

## preserve
persist-key
persist-tun

## HTTP proxy
;http-proxy-retry 
;http-proxy [proxy server] [proxy port]

## duplicate packet warnings
;mute-replay-warnings

## SSL/TLS parms
/etc/openvpn/certs/ca ca.crt
/etc/openvpn/certs/cert client.crt
/etc/openvpn/certs/key client.key

## nsCertType key
;ns-cert-type server

## tls-auth key
;tls-auth /etc/openvpn/certs/ta.key 1

## Cryptographic cipher
;cipher x

## Link compression
comp-lzo

## verbosity
## 0 is silent, except for fatal errors
## 4 is reasonable for general usage
## 5 and 6 can help to debug connection problems
## 9 is extremely verbose
verb 3

## repeating messages
;mute 20
&lt;/pre&gt;
'''Routing'''
&lt;pre&gt;
route add -net 10.0.0.0 netmask 255.255.255.0 gw 10.4.0.1 
&lt;/pre&gt;

==Example==

'''Example 1:''' A simple tunnel without security&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 --verb 9
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 --verb 9 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 2:''' A tunnel with static-key security (i.e. using a pre-shared secret)&lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--verb 5 --secret key
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--verb 5 --secret key 
&lt;/pre&gt;

On May:
    ping 10.4.0.2 

On Jun:
    ping 10.4.0.1

'''Example 3:''' A tunnel with full TLS-based security &lt;br&gt;
'''On May: Server Side'''
&lt;pre&gt;
openvpn --remote jun.kg --dev tun1 --ifconfig 10.4.0.1 10.4.0.2 \
--tls-client --ca tmp-ca.crt --cert client.crt --key client.key \
--reneg-sec 60 --verb 5 
&lt;/pre&gt;

'''On Jun: Client Side'''
&lt;pre&gt;
openvpn --remote may.kg --dev tun1 --ifconfig 10.4.0.2 10.4.0.1 \
--tls-server --ca tmp-ca.crt --cert server.crt --key server.key \
--reneg-sec 60 --verb 5 --dh dh1024.pem
&lt;/pre&gt;

On May:

    ping 10.4.0.2 

On Jun:

    ping 10.4.0.1

== External Links ==

* http://dmalloc.com/
* http://valgrind.org/
* http://www.oberhumer.com/opensource/lzo/
* http://openvpn.net/
* http://openvpn.net/howto.html
* http://openvpn.net/1xhowto.html (Old-v1.06)
* http://openvpn.net/man.html</text>
    <sha1>0462ca3047258dda5e6c37ec123b891898da6831</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>OpenVPN smcr 2012</title>
  <ns>0</ns>
  <id>287</id>
  <revision>
    <id>714</id>
    <timestamp>2012-06-09T19:16:19Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>CREATED!  Saved because I put a lot of work into it so far and don't wanna lose it</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3755" xml:space="preserve">Here's what I did yo get OpenVPN (2.1.4) on my Slackware (13.37) box.

I wanted to get on the internet from public wifi WITHOUT being snooped on so I installed a MULTI-CLIENT, ROUTED (not bridged) OpenVPN server on my Linode.  Again, this is MULTI-CLIENT and ROUTED.

 1) Install OpenVPN from Slackbuilds.org or using sbopkg
 
 2) Generate the needed certificates and keys-
 
 	cd /usr/doc/openvpn-2.1.4/easy-rsa/2.0/
 	vi vars
 		Set the KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, and KEY_EMAIL parameters.
 		Don't leave any of these parameters blank.
 
 	source ./vars
 	./clean-all
 	./build-ca
 		answer questions
 	./build-key-server server (server could be anything e.g. VPN1.blah.net)
 		answer questions
 	./build-key client1 (client1 can be anything e.g bobs-phone)
 		answer questions
 		repeat for each client to have
 	./build-dh
 
 3) Put the server certs and keys where they need to be-
 	mkdir /etc/openvpn/certsnkeys
 	cp ca.crt /etc/openvpn/certsnkeys/
 	cp ca.key /etc/openvpn/certsnkeys/
 	cp server.crt /etc/openvpn/certsnkeys/
 	cp server.key /etc/openvpn/certsnkeys/
 	cp dh1024.pem /etc/openvpn/
 
 4) Send the client certs and keys where they need to be-
 	Each client gets a copy of his client.crt and client.key AND a copy of ca.crt
 	EXAMPLE: My android got a copy of client1.crt, client2.key and ca.crt.
 		My laptop got a copy of client2.crt, client2.key and ca.crt
 	NOTE: my android need a .p12 file, more on that below.
 
 5) Configure the server.conf file-
 	cd /usr/doc/openvpn-2.1.4
 	cp server.conf.sample /etc/openvpn/server.conf
 	cd /etc/openvpn
 
 ***NOTE: in /etc/openvpn you will see a file called openvpn.conf.  DO NOT USE THAT!
 Use server.conf***
 
 	Edit /etc/openvpn/server.conf
 	CHANGE:
 		ca ca.crt	-&gt; ca /etc/openvpn/certs/ca.crt
 		cert server.crt	-&gt; cert /etc/openvpn/certsnkeys/server.crt
 		key server.key	-&gt; key /etc/openvpn/certsnkeys/server.key
 		dh dh.pem	-&gt; dh /etc/openvpn/dh1024.pem
 
 6) Start OpenVPN-
 Normally you would start OpenVPN by: openvpn /etc/openvpn/server.conf
 but, being that I'm a good Slacker, I created an rc.openvpn file...
 
 	CREATE: /etc/rc.d/rc.openvpn
 	CONTAINS:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.openvpn
 		#
 		# Start/stop/restart the openvpn server.
 		#
 		# To make OpenVPN start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.openvpn
 		#
 		
 		ovpn_start() {
 		  if [ -x /usr/sbin/openvpn -a -r /etc/openvpn/server.conf ]; then
 		    echo "Starting OpenVPN:  /usr/sbin/openvpn server.conf"
 		    /usr/sbin/openvpn /etc/openvpn/server.conf &amp;
 		  fi
 		}
 		
 		ovpn_stop() {
 		  killall openvpn
 		}
 		
 		ovpn_restart() {
 		  ovpn_stop
 		  sleep 2
 		  ovpn_start
 		}
 		
 		case "$1" in
 		'start')
 		  ovpn_start
 		  ;;
 		'stop')
 		  ovpn_stop
 		  ;;
 		'restart')
 		  ovpn_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  ovpn_start
 		esac
 
 7) Make it executable (and autostart on reboots)-
 
 	chmod 755 /etc/rc.d/rc.openvpn
 
 To start/stop it manually- /etc/rc.d/rc.openvpn start (or stop or restart)
 
 Now let's fix the firewall so our clients can get to the rest of the world...
 
 8) Edit/create /etc/rc.d/rc.firewall
 
 	ADD:
 	iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 	iptables -A FORWARD -i tun+ -j ACCEPT
 	iptables -A FORWARD -o tun+ -j ACCEPT
 	iptables -A FORWARD -j ACCEPT
 	iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
 
 9) Flush the old firewall rules-
 
 	iptables -F
 
 10) Activate the new rules now-
 
 	/etc/rc.d/rc.firewall

If the planets are aligned, you should now have a working OpenVPN server/router.</text>
    <sha1>219738788818d7a21a5c5ec28e7438c7f5a654bb</sha1>
  </revision>
  <revision>
    <id>715</id>
    <parentid>714</parentid>
    <timestamp>2012-06-09T19:18:24Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Fixed some trash</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3797" xml:space="preserve">'''OPENVPN MULTI-CLIENT ROUTED SERVER'''

Here's what I did to get OpenVPN (2.1.4) on my Slackware (13.37) box.

I wanted to get on the internet from public wifi WITHOUT being snooped on so I installed a MULTI-CLIENT, ROUTED (not bridged) OpenVPN server on my Linode.  Again, this is MULTI-CLIENT and ROUTED.

 1) Install OpenVPN from Slackbuilds.org or using sbopkg
 
 2) Generate the needed certificates and keys-
 
 	cd /usr/doc/openvpn-2.1.4/easy-rsa/2.0/
 	vi vars
 		Set the KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, and KEY_EMAIL parameters.
 		Don't leave any of these parameters blank.
 
 	source ./vars
 	./clean-all
 	./build-ca
 		answer questions
 	./build-key-server server (server could be anything e.g. VPN1.blah.net)
 		answer questions
 	./build-key client1 (client1 can be anything e.g bobs-phone)
 		answer questions
 		repeat for each client to have
 	./build-dh
 
 3) Put the server certs and keys where they need to be-
 	mkdir /etc/openvpn/certsnkeys
 	cp ca.crt /etc/openvpn/certsnkeys/
 	cp ca.key /etc/openvpn/certsnkeys/
 	cp server.crt /etc/openvpn/certsnkeys/
 	cp server.key /etc/openvpn/certsnkeys/
 	cp dh1024.pem /etc/openvpn/
 
 4) Send the client certs and keys where they need to be-
 	Each client gets a copy of his client.crt and client.key AND a copy of ca.crt
 	EXAMPLE: My android got a copy of client1.crt, client2.key and ca.crt.
 		My laptop got a copy of client2.crt, client2.key and ca.crt
 	NOTE: my android need a .p12 file, more on that below.
 
 5) Configure the server.conf file-
 	cd /usr/doc/openvpn-2.1.4
 	cp server.conf.sample /etc/openvpn/server.conf
 	cd /etc/openvpn
 
 ***NOTE: in /etc/openvpn you will see a file called openvpn.conf.  DO NOT USE THAT!
 Use server.conf***
 
 	Edit /etc/openvpn/server.conf
 	CHANGE:
 		ca ca.crt	-&gt; ca /etc/openvpn/certs/ca.crt
 		cert server.crt	-&gt; cert /etc/openvpn/certsnkeys/server.crt
 		key server.key	-&gt; key /etc/openvpn/certsnkeys/server.key
 		dh dh.pem	-&gt; dh /etc/openvpn/dh1024.pem
 
 6) Start OpenVPN-
 Normally you would start OpenVPN by: openvpn /etc/openvpn/server.conf
 but, being that I'm a good Slacker, I created an rc.openvpn file...
 
 	CREATE: /etc/rc.d/rc.openvpn
 	CONTAINS:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.openvpn
 		#
 		# Start/stop/restart the openvpn server.
 		#
 		# To make OpenVPN start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.openvpn
 		#
 		
 		ovpn_start() {
 		  if [ -x /usr/sbin/openvpn -a -r /etc/openvpn/server.conf ]; then
 		    echo "Starting OpenVPN:  /usr/sbin/openvpn server.conf"
 		    /usr/sbin/openvpn /etc/openvpn/server.conf &amp;
 		  fi
 		}
 		
 		ovpn_stop() {
 		  killall openvpn
 		}
 		
 		ovpn_restart() {
 		  ovpn_stop
 		  sleep 2
 		  ovpn_start
 		}
 		
 		case "$1" in
 		'start')
 		  ovpn_start
 		  ;;
 		'stop')
 		  ovpn_stop
 		  ;;
 		'restart')
 		  ovpn_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  ovpn_start
 		esac
 
 7) Make it executable (and autostart on reboots)-
 
 	chmod 755 /etc/rc.d/rc.openvpn
 
 To start/stop it manually- /etc/rc.d/rc.openvpn start (or stop or restart)
 
 Now let's fix the firewall so our clients can get to the rest of the world...
 
 8) Edit/create /etc/rc.d/rc.firewall
 
 	ADD:
 	iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 	iptables -A FORWARD -i tun+ -j ACCEPT
 	iptables -A FORWARD -o tun+ -j ACCEPT
 	iptables -A FORWARD -j ACCEPT
 	iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
 
 9) Flush the old firewall rules-
 
 	iptables -F
 
 10) Activate the new rules now-
 
 	/etc/rc.d/rc.firewall

If the planets are aligned, you should now have a working OpenVPN server/router.</text>
    <sha1>c916ddaf07d38f37e5dc5736e0a24b3d9d277398</sha1>
  </revision>
  <revision>
    <id>716</id>
    <parentid>715</parentid>
    <timestamp>2012-06-09T19:21:54Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>ADDED: Categories</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3865" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]

'''OPENVPN MULTI-CLIENT ROUTED SERVER'''

Here's what I did to get OpenVPN (2.1.4) on my Slackware (13.37) box.

I wanted to get on the internet from public wifi WITHOUT being snooped on so I installed a MULTI-CLIENT, ROUTED (not bridged) OpenVPN server on my Linode.  Again, this is MULTI-CLIENT and ROUTED.

 1) Install OpenVPN from Slackbuilds.org or using sbopkg
 
 2) Generate the needed certificates and keys-
 
 	cd /usr/doc/openvpn-2.1.4/easy-rsa/2.0/
 	vi vars
 		Set the KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, and KEY_EMAIL parameters.
 		Don't leave any of these parameters blank.
 
 	source ./vars
 	./clean-all
 	./build-ca
 		answer questions
 	./build-key-server server (server could be anything e.g. VPN1.blah.net)
 		answer questions
 	./build-key client1 (client1 can be anything e.g bobs-phone)
 		answer questions
 		repeat for each client to have
 	./build-dh
 
 3) Put the server certs and keys where they need to be-
 	mkdir /etc/openvpn/certsnkeys
 	cp ca.crt /etc/openvpn/certsnkeys/
 	cp ca.key /etc/openvpn/certsnkeys/
 	cp server.crt /etc/openvpn/certsnkeys/
 	cp server.key /etc/openvpn/certsnkeys/
 	cp dh1024.pem /etc/openvpn/
 
 4) Send the client certs and keys where they need to be-
 	Each client gets a copy of his client.crt and client.key AND a copy of ca.crt
 	EXAMPLE: My android got a copy of client1.crt, client2.key and ca.crt.
 		My laptop got a copy of client2.crt, client2.key and ca.crt
 	NOTE: my android need a .p12 file, more on that below.
 
 5) Configure the server.conf file-
 	cd /usr/doc/openvpn-2.1.4
 	cp server.conf.sample /etc/openvpn/server.conf
 	cd /etc/openvpn
 
 ***NOTE: in /etc/openvpn you will see a file called openvpn.conf.  DO NOT USE THAT!
 Use server.conf***
 
 	Edit /etc/openvpn/server.conf
 	CHANGE:
 		ca ca.crt	-&gt; ca /etc/openvpn/certs/ca.crt
 		cert server.crt	-&gt; cert /etc/openvpn/certsnkeys/server.crt
 		key server.key	-&gt; key /etc/openvpn/certsnkeys/server.key
 		dh dh.pem	-&gt; dh /etc/openvpn/dh1024.pem
 
 6) Start OpenVPN-
 Normally you would start OpenVPN by: openvpn /etc/openvpn/server.conf
 but, being that I'm a good Slacker, I created an rc.openvpn file...
 
 	CREATE: /etc/rc.d/rc.openvpn
 	CONTAINS:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.openvpn
 		#
 		# Start/stop/restart the openvpn server.
 		#
 		# To make OpenVPN start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.openvpn
 		#
 		
 		ovpn_start() {
 		  if [ -x /usr/sbin/openvpn -a -r /etc/openvpn/server.conf ]; then
 		    echo "Starting OpenVPN:  /usr/sbin/openvpn server.conf"
 		    /usr/sbin/openvpn /etc/openvpn/server.conf &amp;
 		  fi
 		}
 		
 		ovpn_stop() {
 		  killall openvpn
 		}
 		
 		ovpn_restart() {
 		  ovpn_stop
 		  sleep 2
 		  ovpn_start
 		}
 		
 		case "$1" in
 		'start')
 		  ovpn_start
 		  ;;
 		'stop')
 		  ovpn_stop
 		  ;;
 		'restart')
 		  ovpn_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  ovpn_start
 		esac
 
 7) Make it executable (and autostart on reboots)-
 
 	chmod 755 /etc/rc.d/rc.openvpn
 
 To start/stop it manually- /etc/rc.d/rc.openvpn start (or stop or restart)
 
 Now let's fix the firewall so our clients can get to the rest of the world...
 
 8) Edit/create /etc/rc.d/rc.firewall
 
 	ADD:
 	iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 	iptables -A FORWARD -i tun+ -j ACCEPT
 	iptables -A FORWARD -o tun+ -j ACCEPT
 	iptables -A FORWARD -j ACCEPT
 	iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
 
 9) Flush the old firewall rules-
 
 	iptables -F
 
 10) Activate the new rules now-
 
 	/etc/rc.d/rc.firewall

If the planets are aligned, you should now have a working OpenVPN server/router.</text>
    <sha1>02f89eb91c02afbee29c7a3279e93a9294796f01</sha1>
  </revision>
  <revision>
    <id>724</id>
    <parentid>716</parentid>
    <timestamp>2012-06-13T14:50:07Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>ca /etc/openvpn/certs/ca.crt --&gt;ca /etc/openvpn/certsnkeys/ca.crt</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3870" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]

'''OPENVPN MULTI-CLIENT ROUTED SERVER'''

Here's what I did to get OpenVPN (2.1.4) on my Slackware (13.37) box.

I wanted to get on the internet from public wifi WITHOUT being snooped on so I installed a MULTI-CLIENT, ROUTED (not bridged) OpenVPN server on my Linode.  Again, this is MULTI-CLIENT and ROUTED.

 1) Install OpenVPN from Slackbuilds.org or using sbopkg
 
 2) Generate the needed certificates and keys-
 
 	cd /usr/doc/openvpn-2.1.4/easy-rsa/2.0/
 	vi vars
 		Set the KEY_COUNTRY, KEY_PROVINCE, KEY_CITY, KEY_ORG, and KEY_EMAIL parameters.
 		Don't leave any of these parameters blank.
 
 	source ./vars
 	./clean-all
 	./build-ca
 		answer questions
 	./build-key-server server (server could be anything e.g. VPN1.blah.net)
 		answer questions
 	./build-key client1 (client1 can be anything e.g bobs-phone)
 		answer questions
 		repeat for each client to have
 	./build-dh
 
 3) Put the server certs and keys where they need to be-
 	mkdir /etc/openvpn/certsnkeys
 	cp ca.crt /etc/openvpn/certsnkeys/
 	cp ca.key /etc/openvpn/certsnkeys/
 	cp server.crt /etc/openvpn/certsnkeys/
 	cp server.key /etc/openvpn/certsnkeys/
 	cp dh1024.pem /etc/openvpn/
 
 4) Send the client certs and keys where they need to be-
 	Each client gets a copy of his client.crt and client.key AND a copy of ca.crt
 	EXAMPLE: My android got a copy of client1.crt, client2.key and ca.crt.
 		My laptop got a copy of client2.crt, client2.key and ca.crt
 	NOTE: my android need a .p12 file, more on that below.
 
 5) Configure the server.conf file-
 	cd /usr/doc/openvpn-2.1.4
 	cp server.conf.sample /etc/openvpn/server.conf
 	cd /etc/openvpn
 
 ***NOTE: in /etc/openvpn you will see a file called openvpn.conf.  DO NOT USE THAT!
 Use server.conf***
 
 	Edit /etc/openvpn/server.conf
 	CHANGE:
 		ca ca.crt	-&gt; ca /etc/openvpn/certsnkeys/ca.crt
 		cert server.crt	-&gt; cert /etc/openvpn/certsnkeys/server.crt
 		key server.key	-&gt; key /etc/openvpn/certsnkeys/server.key
 		dh dh.pem	-&gt; dh /etc/openvpn/dh1024.pem
 
 6) Start OpenVPN-
 Normally you would start OpenVPN by: openvpn /etc/openvpn/server.conf
 but, being that I'm a good Slacker, I created an rc.openvpn file...
 
 	CREATE: /etc/rc.d/rc.openvpn
 	CONTAINS:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.openvpn
 		#
 		# Start/stop/restart the openvpn server.
 		#
 		# To make OpenVPN start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.openvpn
 		#
 		
 		ovpn_start() {
 		  if [ -x /usr/sbin/openvpn -a -r /etc/openvpn/server.conf ]; then
 		    echo "Starting OpenVPN:  /usr/sbin/openvpn server.conf"
 		    /usr/sbin/openvpn /etc/openvpn/server.conf &amp;
 		  fi
 		}
 		
 		ovpn_stop() {
 		  killall openvpn
 		}
 		
 		ovpn_restart() {
 		  ovpn_stop
 		  sleep 2
 		  ovpn_start
 		}
 		
 		case "$1" in
 		'start')
 		  ovpn_start
 		  ;;
 		'stop')
 		  ovpn_stop
 		  ;;
 		'restart')
 		  ovpn_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  ovpn_start
 		esac
 
 7) Make it executable (and autostart on reboots)-
 
 	chmod 755 /etc/rc.d/rc.openvpn
 
 To start/stop it manually- /etc/rc.d/rc.openvpn start (or stop or restart)
 
 Now let's fix the firewall so our clients can get to the rest of the world...
 
 8) Edit/create /etc/rc.d/rc.firewall
 
 	ADD:
 	iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 	iptables -A FORWARD -i tun+ -j ACCEPT
 	iptables -A FORWARD -o tun+ -j ACCEPT
 	iptables -A FORWARD -j ACCEPT
 	iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
 
 9) Flush the old firewall rules-
 
 	iptables -F
 
 10) Activate the new rules now-
 
 	/etc/rc.d/rc.firewall

If the planets are aligned, you should now have a working OpenVPN server/router.</text>
    <sha1>176ae7b4314390a2384cd456f311264c4ebde422</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>User:Arfon</title>
  <ns>2</ns>
  <id>288</id>
  <revision>
    <id>717</id>
    <timestamp>2012-06-09T19:25:49Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Created page with "Find me on freenode ##Slackware as either arfon or urmom_  or drop me an email: REMOVETHIS arfon REMOVETHIS atsign REMOVETHIS 1337mail REMOVETHIS period REMOVETHIS net"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="167" xml:space="preserve">Find me on freenode ##Slackware as either arfon or urmom_

or drop me an email: REMOVETHIS arfon REMOVETHIS atsign REMOVETHIS 1337mail REMOVETHIS period REMOVETHIS net</text>
    <sha1>01d799c83fd43cbd45c7fd818f6ce033c1787394</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>ALSA</title>
  <ns>0</ns>
  <id>35</id>
  <revision>
    <id>726</id>
    <parentid>495</parentid>
    <timestamp>2012-06-30T21:31:34Z</timestamp>
    <contributor>
      <username>Drhouse</username>
      <id>292</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1223" xml:space="preserve">[[Category:Tutorials]]

Sound problems *should* be rare these days, and of the ones that still exist, they are likely related to suspend/resume.  Those are driver issues which are largely out of your control, but see the documentation with the pm-utils package for details on handling those issues.

: &lt;code&gt;alsaconf&lt;/code&gt; used to be needed to set up sound cards in linux, but even that shouldn't be needed in recent linux distributions - everything should be handled automatically.

: &lt;code&gt;alsamixer&lt;/code&gt; can be used to change the volume.

: &lt;code&gt;alsactl store&lt;/code&gt; is used to save the volume settings.

: &lt;code&gt;alsactl restore&lt;/code&gt; is used to restore the volume settings.  This is automatically run on boot, so you usually won't need to run this command.

There is one tip for the Sound Baster 5.1 cards: sometimes you want to MUTE digital out so you can hear on all the speakers; in alsamixer, you just press M on the &lt;tt&gt;Analog/Digital Output Jack&lt;/tt&gt; item.

For change boot ordering for your sound cards just create /etc/modprobe.d/sound.conf and put these lines into it: 

: &lt;code&gt;options snd-hda-intel index=0&lt;/code&gt;
: &lt;code&gt;options snd-usb-audio index=1&lt;/code&gt;

Replace 'snd-hda-intel' to your card module</text>
    <sha1>25d1eb4bcb8c5eb5629346d5c6252c968cfb7bfd</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>MySQL Configuration</title>
  <ns>0</ns>
  <id>74</id>
  <revision>
    <id>728</id>
    <parentid>95</parentid>
    <timestamp>2012-08-06T15:22:36Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>chmod 755 /etc/rc.d/rc.mysql --&gt; chmod 755 /etc/rc.d/rc.mysqld</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6388" xml:space="preserve">[[Category:Tutorials]]
''Have you just installed Slackware and now see a MySQL error at the login prompt?''

This is a VERY quick HowTo and should take maybe 30 seconds to complete at its slowest.  The reason I decided to do a write-up is because of the sheer number of people asking how to fix it.

== Option 1 ==
In a shell or xterm, type (you have to be logged in as superuser to use the mysql login):

 su mysql

This logs you into the 'mysql' user account.

Next, run:

 mysql_install_db

This will create the needed databases and set their permissions properly.

if your not logon as mysql user (root)

Don't forget to chown folder /var/lib/mysql
&lt;pre&gt;
chown -R mysql.mysql /var/lib/mysql
chmod 755 /etc/rc.d/rc.mysqld
&lt;/pre&gt;

You're now finished and should not see the typical MySQL errors at the login prompt.

 /etc/rc.d/rc.mysql start

Now you should set a password for MySQL's root password:

 mysqladmin -u root password 'new-password-here'


You can connect to your MySQL server with:
 mysql -u root -p


For security reasons you should delete an empy user for localhost server
&lt;pre&gt;
mysql&gt; SELECT user, host FROM user;
mysql&gt; DELETE FROM user WHERE host='localhost' AND user=''; 
&lt;/pre&gt;
*''This tutorial is currently linked at ''
* ''http://www.unixfool.com/mysql-slack.shtml''

== Option 2 ==
1. log in as &lt;b&gt;root&lt;/b&gt; and install the mysql package

2. &lt;code&gt;killall -9 mysqld mysqld_safe&lt;/code&gt; to kill any running MySQL processes.

3. copy one of the my-size.cnf files in /etc to my.cnf (picking an apporpriate size):&lt;br&gt;
::&lt;code&gt;cp /etc/my-medium.cnf /etc/my.cnf&lt;/code&gt;

4. Install the MySQL database-

::'''Slackware 12.1''' (and later):
::::&lt;code&gt;mysql_install_db --user=mysql&lt;/code&gt;

::'''Slackware 12.0''' (and before):
::::&lt;code&gt;su mysql&lt;/code&gt;
::::&lt;code&gt;mysql_install_db&lt;/code&gt;
:::: &lt;code&gt;exit&lt;/code&gt; (to get out of the mysql login and back to root).

5. &lt;code&gt;mysqld_safe --skip-grant-tables &amp;&lt;/code&gt;

6. &lt;code&gt;mysql -u root mysql&lt;/code&gt;

7. &lt;code&gt;UPDATE user SET Password=PASSWORD('&lt;i&gt;new_password&lt;/i&gt;') WHERE user='root';&lt;/code&gt;

8. &lt;code&gt;FLUSH PRIVILEGES;&lt;/code&gt;

9. &lt;code&gt;exit&lt;/code&gt;

10. &lt;code&gt;killall -9 mysqld mysqld_safe&lt;/code&gt;

11. &lt;code&gt;mysqld_safe &amp;&lt;/code&gt;


to check the new password, (as root) type:&lt;br&gt;
::&lt;code&gt;mysqladmin -u root -p status&lt;/code&gt;&lt;br&gt;
:::::...and enter the new password.


== Option 3 ==

I'm starting from a [http://www.slackwiki.org/Minimal_System very basic install]. 

The only additional package needed is '''mysql''' in the '''AP''' group.

&lt;pre&gt;
# installpkg mysql-5.0.37-i486-1.tgz
# su mysql
$ mysql_install_db
Installing all prepared tables
Fill help tables
...
$ exit
# chmod 755 /etc/rc.d/rc.mysqld 
# /etc/rc.d/rc.mysqld start
Starting mysqld daemon with databases from /var/lib/mysql
&lt;/pre&gt;

MySQL is now installed, but there are no passwords defined yet.

&lt;pre&gt;
# mysql -u root
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.0.37 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
&lt;/pre&gt;

We can now set passwords from within the MySQL console. I know this can be achieved with '''mysqladmin''', but then, several ways lead to Rome. It's a simple matter of habit.

&lt;pre&gt;
mysql&gt; show databases;
 +--------------------+
| Database           |
+--------------------+
| information_schema | 
| mysql              | 
| test               | 
+--------------------+
3 rows in set (0.01 sec)

mysql&gt; use mysql;
Database changed

mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+----------+
| user | host      | password |
+------+-----------+----------+
| root | localhost |          | 
| root | slacktest |          | 
+------+-----------+----------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

As you can see, there are two 'root' users here (and none of them is our system's root user, don't forget): root@localhost... and root@slacktest. We have to set a password for both of them. In theory, these can be different, but why make things more complicated than they already are? ;o)

&lt;pre&gt;
mysql&gt; set password for root@localhost = password('yatahongaga');
Query OK, 0 rows affected (0.00 sec)
&lt;/pre&gt;

Let's repeat our query above to see the actual changes:

&lt;pre&gt;
mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+-------------------------------------------+
| user | host      | password                                  |
+------+-----------+-------------------------------------------+
| root | localhost | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
| root | slacktest |                                           | 
+------+-----------+-------------------------------------------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

You can see that root@localhost's password is displayed as a shadow password. Now let's set the password for root@slacktest (replace ''slacktest'' by your machine's hostname):

&lt;pre&gt;
mysql&gt; set password for root@slacktest = password('yatahongaga');
Query OK, 0 rows affected (0.00 sec)
&lt;/pre&gt;

What do we have now?

&lt;pre&gt;
mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+-------------------------------------------+
| user | host      | password                                  |
+------+-----------+-------------------------------------------+
| root | localhost | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
| root | slacktest | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
+------+-----------+-------------------------------------------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

Now we have some (very) basic security, we can leave the MySQL monitor.

&lt;pre&gt;
mysql&gt; quit;
Bye
&lt;/pre&gt;

To connect to our MySQL database as MySQL's root user (who, remember, is ''not'' the system's root), we can do the following:

&lt;pre&gt;
# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.0.37 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql&gt;
&lt;/pre&gt;

If we have to do this often, we can create a /root/.my.cnf file and edit it as follows:

&lt;pre&gt;
[mysql]
user            =       root
password        =       yatahongaga
&lt;/pre&gt;

Just to be on the safe side:

&lt;pre&gt;
# chmod 0600 /root/.my.cnf
&lt;/pre&gt;

From now on, you can connect directly to the MySQL monitor, without having to type your password every time.</text>
    <sha1>d19bf68998e07eac2fd4ce2d1fc6ec10a82ea4ea</sha1>
  </revision>
  <revision>
    <id>729</id>
    <parentid>728</parentid>
    <timestamp>2012-08-06T15:30:58Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>/etc/rc.d/rc.mysql start --&gt; /etc/rc.d/rc.mysqld start    AND ADDED: mysql&gt; use mysql</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6406" xml:space="preserve">[[Category:Tutorials]]
''Have you just installed Slackware and now see a MySQL error at the login prompt?''

This is a VERY quick HowTo and should take maybe 30 seconds to complete at its slowest.  The reason I decided to do a write-up is because of the sheer number of people asking how to fix it.

== Option 1 ==
In a shell or xterm, type (you have to be logged in as superuser to use the mysql login):

 su mysql

This logs you into the 'mysql' user account.

Next, run:

 mysql_install_db

This will create the needed databases and set their permissions properly.

if your not logon as mysql user (root)

Don't forget to chown folder /var/lib/mysql
&lt;pre&gt;
chown -R mysql.mysql /var/lib/mysql
chmod 755 /etc/rc.d/rc.mysqld
&lt;/pre&gt;

You're now finished and should not see the typical MySQL errors at the login prompt.

 /etc/rc.d/rc.mysqld start

Now you should set a password for MySQL's root password:

 mysqladmin -u root password 'new-password-here'


You can connect to your MySQL server with:
 mysql -u root -p


For security reasons you should delete an empy user for localhost server
&lt;pre&gt;
mysql&gt; use mysql
mysql&gt; SELECT user, host FROM user;
mysql&gt; DELETE FROM user WHERE host='localhost' AND user=''; 
&lt;/pre&gt;
*''This tutorial is currently linked at ''
* ''http://www.unixfool.com/mysql-slack.shtml''

== Option 2 ==
1. log in as &lt;b&gt;root&lt;/b&gt; and install the mysql package

2. &lt;code&gt;killall -9 mysqld mysqld_safe&lt;/code&gt; to kill any running MySQL processes.

3. copy one of the my-size.cnf files in /etc to my.cnf (picking an apporpriate size):&lt;br&gt;
::&lt;code&gt;cp /etc/my-medium.cnf /etc/my.cnf&lt;/code&gt;

4. Install the MySQL database-

::'''Slackware 12.1''' (and later):
::::&lt;code&gt;mysql_install_db --user=mysql&lt;/code&gt;

::'''Slackware 12.0''' (and before):
::::&lt;code&gt;su mysql&lt;/code&gt;
::::&lt;code&gt;mysql_install_db&lt;/code&gt;
:::: &lt;code&gt;exit&lt;/code&gt; (to get out of the mysql login and back to root).

5. &lt;code&gt;mysqld_safe --skip-grant-tables &amp;&lt;/code&gt;

6. &lt;code&gt;mysql -u root mysql&lt;/code&gt;

7. &lt;code&gt;UPDATE user SET Password=PASSWORD('&lt;i&gt;new_password&lt;/i&gt;') WHERE user='root';&lt;/code&gt;

8. &lt;code&gt;FLUSH PRIVILEGES;&lt;/code&gt;

9. &lt;code&gt;exit&lt;/code&gt;

10. &lt;code&gt;killall -9 mysqld mysqld_safe&lt;/code&gt;

11. &lt;code&gt;mysqld_safe &amp;&lt;/code&gt;


to check the new password, (as root) type:&lt;br&gt;
::&lt;code&gt;mysqladmin -u root -p status&lt;/code&gt;&lt;br&gt;
:::::...and enter the new password.


== Option 3 ==

I'm starting from a [http://www.slackwiki.org/Minimal_System very basic install]. 

The only additional package needed is '''mysql''' in the '''AP''' group.

&lt;pre&gt;
# installpkg mysql-5.0.37-i486-1.tgz
# su mysql
$ mysql_install_db
Installing all prepared tables
Fill help tables
...
$ exit
# chmod 755 /etc/rc.d/rc.mysqld 
# /etc/rc.d/rc.mysqld start
Starting mysqld daemon with databases from /var/lib/mysql
&lt;/pre&gt;

MySQL is now installed, but there are no passwords defined yet.

&lt;pre&gt;
# mysql -u root
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 5.0.37 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
&lt;/pre&gt;

We can now set passwords from within the MySQL console. I know this can be achieved with '''mysqladmin''', but then, several ways lead to Rome. It's a simple matter of habit.

&lt;pre&gt;
mysql&gt; show databases;
 +--------------------+
| Database           |
+--------------------+
| information_schema | 
| mysql              | 
| test               | 
+--------------------+
3 rows in set (0.01 sec)

mysql&gt; use mysql;
Database changed

mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+----------+
| user | host      | password |
+------+-----------+----------+
| root | localhost |          | 
| root | slacktest |          | 
+------+-----------+----------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

As you can see, there are two 'root' users here (and none of them is our system's root user, don't forget): root@localhost... and root@slacktest. We have to set a password for both of them. In theory, these can be different, but why make things more complicated than they already are? ;o)

&lt;pre&gt;
mysql&gt; set password for root@localhost = password('yatahongaga');
Query OK, 0 rows affected (0.00 sec)
&lt;/pre&gt;

Let's repeat our query above to see the actual changes:

&lt;pre&gt;
mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+-------------------------------------------+
| user | host      | password                                  |
+------+-----------+-------------------------------------------+
| root | localhost | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
| root | slacktest |                                           | 
+------+-----------+-------------------------------------------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

You can see that root@localhost's password is displayed as a shadow password. Now let's set the password for root@slacktest (replace ''slacktest'' by your machine's hostname):

&lt;pre&gt;
mysql&gt; set password for root@slacktest = password('yatahongaga');
Query OK, 0 rows affected (0.00 sec)
&lt;/pre&gt;

What do we have now?

&lt;pre&gt;
mysql&gt; select user, host, password from user where user = 'root';
+------+-----------+-------------------------------------------+
| user | host      | password                                  |
+------+-----------+-------------------------------------------+
| root | localhost | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
| root | slacktest | *71CDE2704222D8D5A7608C92AF78C53F78DA5EBA | 
+------+-----------+-------------------------------------------+
2 rows in set (0.00 sec)
&lt;/pre&gt;

Now we have some (very) basic security, we can leave the MySQL monitor.

&lt;pre&gt;
mysql&gt; quit;
Bye
&lt;/pre&gt;

To connect to our MySQL database as MySQL's root user (who, remember, is ''not'' the system's root), we can do the following:

&lt;pre&gt;
# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.0.37 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql&gt;
&lt;/pre&gt;

If we have to do this often, we can create a /root/.my.cnf file and edit it as follows:

&lt;pre&gt;
[mysql]
user            =       root
password        =       yatahongaga
&lt;/pre&gt;

Just to be on the safe side:

&lt;pre&gt;
# chmod 0600 /root/.my.cnf
&lt;/pre&gt;

From now on, you can connect directly to the MySQL monitor, without having to type your password every time.</text>
    <sha1>5d9d0ee1af771f868c846413bbc8353a451f6d32</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>Hibernate</title>
  <ns>0</ns>
  <id>223</id>
  <revision>
    <id>730</id>
    <parentid>525</parentid>
    <timestamp>2012-08-17T21:47:49Z</timestamp>
    <contributor>
      <username>Yenn</username>
      <id>297</id>
    </contributor>
    <comment>major rewrite + hibernating from console</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2025" xml:space="preserve">In Slackware, hibernation works out-of-the-box and can be easily done from KDE's menu or XFCE logout dialog. Resuming from hibernation, however, is not set up, so when you turn on your computer again, it starts as normal. That is, if your hardware supports it and if you've set up a swap space larger than your RAM.

== Hibernating in lightweight windows managers ==

In case you aren't using KDE, XFCE or other desktop environments, you can hibernate your system from console.  

=== pm-utils ===

As root, you can hibernate via &lt;tt&gt;pm-hibernate&lt;/tt&gt; command.

=== As regular user ===

==== HAL ====

Since HAL is deprecated and removed from Slackware 14.0, this works for older Slackware releases.

 $ dbus-send --system --print-reply --dest="org.freedesktop.Hal" \
 /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Hibernate

==== UPower ==== 
 dbus-send --system --print-reply --dest="org.freedesktop.UPower" \
 /org/freedesktop/UPower org.freedesktop.UPower.Hibernate

== Booloader configuration ==

=== Non-LVM setup ===

==== LILO configuration ====

To tell your kernel where to resume from, you need to write the info to ''lilo.conf'':

 append=" resume=/dev/sda6"

Replace ''/dev/sda6'' with your actual swap space. Swap partitions are perfect, I think swap files should work too. If you don't know where your swap lies, look at ''/proc/swaps''.

=== LVM setup ===

LILO doesn't support booting from LVM, therefore you have to create initial ramdisk (initrd). You need one even though your kernel has build-in support for LVM.

You don't have to adjust ''lilo.conf'' because you can set everything resume-related in initrd.

 mkinitrd -c -k &lt;kernel-version&gt; -f &lt;fs_type&gt; -m &lt;fs_type&gt; -r &lt;root_partition&gt; -h /dev/volumegroup/swap -L

* -h set your hibernation/swap logical volume
* -L activate LVM

Afterwards, run lilo.

== Further reading ==

* Hibernate to encrypted swap - [http://slackware.osuosl.org/slackware-13.1/README_CRYPT.TXT REAME_CRYPT.TXT]

[[Category:Tutorials]]</text>
    <sha1>7ac83769e82f9ee92172a74dd5b4bcbd2201506f</sha1>
  </revision>
</page>
<page arvcontinue="20120131104913|646">
  <title>ZFS root</title>
  <ns>0</ns>
  <id>290</id>
  <revision>
    <id>731</id>
    <timestamp>2012-08-18T09:27:49Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <comment>installing slackware into a ZFS root</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="46867" xml:space="preserve">If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

(on install-dvd)
cgdisk /dev/sda
setup
reboot

When this simple development guest boots, login as root, and continue:

(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages

The install-dvd should boot, and then begin installation steps on the installer command line:

(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man

The manual pages should be readable:

man zpool
man zfs

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

(still on install-dvd)
ls -l /dev/sd*

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

cgdisk /dev/sda

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

We'll continue with this partitioning (numbers are in MiB):
0 to 4: unused
4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.


Create a zpool called zfs-root:

zpool create -m none zfs-root /dev/sda2

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
Now there is no status.

zpool import zfs-root
Now it is back.

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

rm /mnt/README

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

zfs set readonly=on zfs-root
zfs set readonly=off zfs-root

Slackware expects root to be mounted readonly when /etc/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root

mount zfs-root -t zfs /mnt
umount /mnt

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options -o ro, -o rw, -o remount,ro, and -o remount,rw can also be used and will override readonly=on|off property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current readonly=off setting (rw mount):

zfs set mountpoint=/mnt zfs-root

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

cat /etc/mtab &gt;&gt; /etc/fstab

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

zfs set mountpoint=none zfs-root

Mount again, now using all options from /etc/fstab:

mount zfs-root

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
 mount -i zfs-root 
 mount -i zfs-root -t zfs /mnt
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

umount /dev/sr0
setup

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

umount /dev/sr0

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

cp /etc/fstab /mnt/etc/fstab.initrd

The fstab.initrd will look like:
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2

These two lines in /mnt/etc/fstab are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys

Make sure /boot is mounted:

mount /dev/sda1 /mnt/boot

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

chroot /mnt

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/sda1
   label = vmlinuz
   read-only

The line, root = /dev/sda1, is not really a true statement but lilo needs a device there that it at least understands. This root = line is a kernel parameter, but since the initrd is what is actually the root, initially, then the root = line is probably useless here. It might even be okay to just delete the root line.

Setup mkinitrd:

cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf

Edit it to look like this (other defaults should be ok):

 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"

Module sym53c8xx is the driver for qemu's if=scsi drive device.
Module ext4 for /boot.
Module 8139cp for eth0 net device.
Module zfs for ZFSonLinux.
Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:

modprobe --show-depends zfs

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.

mkinitrd

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).

touch /boot/initrd-tree/etc/mtab

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.

cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:

/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:

/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):

cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc

The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:

(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
comment out the line
#    /sbin/mount -w -v -n -o remount /
add the line
     /sbin/zfs set readonly=off zfs-root

In /etc/rc.d/rc.6
comment out the line
#    /bin/mount -v -n -o remount,ro /
add the line
     /sbin/zfs set readonly=on zfs-root

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:

########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:

touch /etc/fastboot

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:

mkinitrd -F
lilo

We finished! All that's left to do is clean up.

Exit the chroot.

exit

Try to mount everything:

umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

Remove the DVD.

reboot

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):

boot: vmlinuz rescue

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: udevadm info --cleanup-db; udevadm control --exit
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: exec switch_root /mnt /sbin/init 1

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:

zfs set readonly=on zfs-root

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.


slackpkg upgrade-all

Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;

cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot


After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.


More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:

################################################
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
################################################</text>
    <sha1>b317829dee4456df976db638e9f95e3778dae63e</sha1>
  </revision>
  <revision>
    <id>732</id>
    <parentid>731</parentid>
    <timestamp>2012-08-18T18:36:51Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47794" xml:space="preserve">If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;/pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;/pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root 
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/sda1
   label = vmlinuz
   read-only
&lt;/pre&gt;

The line, root = /dev/sda1, is not really a true statement but lilo needs a device there that it at least understands. This root = line is a kernel parameter, but since the initrd is what is actually the root, initially, then the root = line is probably useless here. It might even be okay to just delete the root line.

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
################################################
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
################################################
&lt;/pre&gt;</text>
    <sha1>69811bd6f28ec00ea429254fdce1eeff382ec644</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>ZFS root</title>
  <ns>0</ns>
  <id>290</id>
  <revision>
    <id>733</id>
    <parentid>732</parentid>
    <timestamp>2012-08-18T18:44:38Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47696" xml:space="preserve">If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;/pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;/pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root 
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/sda1
   label = vmlinuz
   read-only
&lt;/pre&gt;

The line, root = /dev/sda1, is not really a true statement but lilo needs a device there that it at least understands. This root = line is a kernel parameter, but since the initrd is what is actually the root, initially, then the root = line is probably useless here. It might even be okay to just delete the root line.

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;</text>
    <sha1>21d4a5e2fe6f4f1f05801c7372c7d1454fad9e7c</sha1>
  </revision>
  <revision>
    <id>734</id>
    <parentid>733</parentid>
    <timestamp>2012-08-18T19:00:07Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47696" xml:space="preserve">If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;/pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root 
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/sda1
   label = vmlinuz
   read-only
&lt;/pre&gt;

The line, root = /dev/sda1, is not really a true statement but lilo needs a device there that it at least understands. This root = line is a kernel parameter, but since the initrd is what is actually the root, initially, then the root = line is probably useless here. It might even be okay to just delete the root line.

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;</text>
    <sha1>018c8195294e31c63d7ffc45f6e809bb0bba570f</sha1>
  </revision>
  <revision>
    <id>735</id>
    <parentid>734</parentid>
    <timestamp>2012-08-18T19:02:24Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47695" xml:space="preserve">If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root 
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/sda1
   label = vmlinuz
   read-only
&lt;/pre&gt;

The line, root = /dev/sda1, is not really a true statement but lilo needs a device there that it at least understands. This root = line is a kernel parameter, but since the initrd is what is actually the root, initially, then the root = line is probably useless here. It might even be okay to just delete the root line.

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;</text>
    <sha1>d11fdb90c7825e8207421651bfeeb201d36f6886</sha1>
  </revision>
  <revision>
    <id>736</id>
    <parentid>735</parentid>
    <timestamp>2012-08-18T19:07:24Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47700" xml:space="preserve">If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root 
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/sda1
   label = vmlinuz
   read-only
&lt;/pre&gt;

The line, root = /dev/sda1, is not really a true statement but lilo needs a device there that it at least understands. This root = line is a kernel parameter, but since the initrd is what is actually the root, initially, then the root = line is probably useless here. It might even be okay to just delete the root line.

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;</text>
    <sha1>50bc1fd4237c0aee65eb062cd707105eacd491a5</sha1>
  </revision>
  <revision>
    <id>737</id>
    <parentid>736</parentid>
    <timestamp>2012-08-18T19:38:56Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="47723" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root 
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/sda1
   label = vmlinuz
   read-only
&lt;/pre&gt;

The line, root = /dev/sda1, is not really a true statement but lilo needs a device there that it at least understands. This root = line is a kernel parameter, but since the initrd is what is actually the root, initially, then the root = line is probably useless here. It might even be okay to just delete the root line.

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;</text>
    <sha1>37f53e6dc57388109c6948f1519f940817c09174</sha1>
  </revision>
  <revision>
    <id>738</id>
    <parentid>737</parentid>
    <timestamp>2012-08-19T01:51:42Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48273" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

Note: when using a initrd (see /usr/src/linux/Documentation/initrd.txt), the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0 (see /usr/src/linux/Documentation/devices.txt). This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise.

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;</text>
    <sha1>14d51103df02bf07b300fe5a5adf7f196574aee9</sha1>
  </revision>
  <revision>
    <id>739</id>
    <parentid>738</parentid>
    <timestamp>2012-08-20T02:22:17Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="50774" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root changes the effective root filesystem from the initrd (unpacked in rootfs at /) to new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3");
&lt;/pre&gt;
The kernel startup rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or else an instance of a ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on:

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;</text>
    <sha1>2d69b9c8e33f3f6d9e0018f9ae106e25469c8c57</sha1>
  </revision>
  <revision>
    <id>780</id>
    <parentid>739</parentid>
    <timestamp>2012-09-03T19:18:14Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="51452" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, add or remove "boot=on", or change "order=dc".

Note: If you are using a newer version of qemu-kvm, the support for if=scsi might be missing the needed option-rom. You might need to download http://www.lsi.com/downloads/Public/Host Bus Adapters/Host Bus Adapters Common Files/lsi_bios.zip. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors side the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-system-x86_64 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=rtl8139 -net user \
 -cdrom dvd.iso \
 -drive boot=on,format=raw,media=disk,cache=none,aio=native,if=scsi,bus=0,unit=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is mostly likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Lets use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactived without need to issue the import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how to the methods of mounting interact.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process it normal.

&lt;pre&gt;
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We install spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root changes the effective root filesystem from the initrd (unpacked in rootfs at /) to new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3");
&lt;/pre&gt;
The kernel startup rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or else an instance of a ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on:

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:8139cp:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module 8139cp for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using zpool import and export and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out zpool import/export lines.

As mentioned, the import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, root will not be mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "import -f" then "mount zfs-root" and then "exit" to continue on to booting the root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip found assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). That is ip-based hostid value, a 32bit hexadecimal number. This has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could be come invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and exit.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as a readonly property changes

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem checks. The rc.S script will complain a lot in many places about not being about to run fsck on the zfs-root. To disable all attempts of run fsck, we can simple create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to mount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrat!

If this seem to go badly, and this might happen if the import fails as explain some before, then you will be on the initrd's rescue command line just before the part in it's init where it wants to mount and switch_root to boot your root. Instead, you typically got commands like this to do:

If you get dumped to rescue because import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.


If you get into a jam and need to boot into the initrd and skip zfs import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your root as readonly=on to /mnt, then exit to continue.

In other emergency modes, you might need to run the lines at end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line is run is: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning... this switch_root command is kind of dangerous, so read the manual page about it.
From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete!
Make sure nothing got mounted outside of "/mnt" before you run it.

Also, in rescue or anytime you have finished making changes and are about to reboot in some abnormal mode, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.


Upgrading.

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuilt and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, and kernel-headers.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SQL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;

Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>019e50e0645b5fd1a71b8f485d65fe3411a4b5c6</sha1>
  </revision>
  <revision>
    <id>781</id>
    <parentid>780</parentid>
    <timestamp>2012-09-04T17:40:07Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="52452" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at http://www.lsi.com/downloads/Public/Host Bus Adapters/Host Bus Adapters Common Files/lsi_bios.zip. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on:

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "zpool import -f zfs-root", "mount zfs-root", and then "exit" to continue booting onto zfs-root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set, and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as readonly property changes. Note: if you use mountpoint=legacy, then you do not need to make the following changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts of run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>329cec425a96995e2d0a076120fae625921eda20</sha1>
  </revision>
  <revision>
    <id>782</id>
    <parentid>781</parentid>
    <timestamp>2012-09-04T17:54:28Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="52474" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at [http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device. On a real ZFS installation, users will typically want to use the ZFS raidz1 or raidz2 virtual device types for reliability against hard drive failures.

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on:

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "zpool import -f zfs-root", "mount zfs-root", and then "exit" to continue booting onto zfs-root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set, and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as readonly property changes. Note: if you use mountpoint=legacy, then you do not need to make the following changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts of run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>8c0febdd32b35b8af24e60457f4fc510f214c43c</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>ZFS root (builtin)</title>
  <ns>0</ns>
  <id>291</id>
  <revision>
    <id>740</id>
    <timestamp>2012-08-21T18:28:52Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <comment>how to run ZFS root with builtin modules and minimal initramfs</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10040" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run
~/src

tar xvzf ~/spl-0.6.0-rc10.tar.gz
cd spl-0.6.0-rc10
mkdir install
./configure --prefix=/ --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share --enable-linux-builtin=yes --with-linux=/usr/src/linux-3.2.27b --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
cd spl-0.6.0-rc10
mkdir install
./configure --prefix=/ --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share --enable-linux-builtin=yes --with-linux=/usr/src/linux-3.2.27b --with-linux-obj=/usr/src/linux-3.2.27b --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS

cd /boot/initramfs-source
mkdir -p etc/zfs dev mnt
touch etc/mtab
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

### make the rootfs /init program
cat &gt; init.c &lt;&lt;"EOF"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

int main(int argc, char* argv[]) {
 FILE* kmsg = NULL;
 char* fnkmsg = "/dev/kmsg";
 mknod(fnkmsg, S_IFCHR , makedev(1,11) );
 kmsg = fopen(fnkmsg, "w");
 fprintf(kmsg, "foobarz-zinit starting.\n");

 fprintf(kmsg, "Attempting mount devtmpfs to /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }

 if( access("/dev/zfs", F_OK) != 0 ) {
  fprintf(kmsg, "File /dev/zfs does not exist; making nod.\n");
  mknod("/dev/zfs", S_IFCHR , makedev(10,58) );
 } else {
  fprintf(kmsg, "File /dev/zfs already exists. Good.\n");
 }

 if( access("/dev/sda1", F_OK) != 0 ) {
  fprintf(kmsg, "Files /dev/sd{a,a1} do not exist; making nods.\n");
  mknod("/dev/sda", S_IFBLK , makedev(8,0) );
  mknod("/dev/sda1", S_IFBLK , makedev(8,1) );
 } else {
  fprintf(kmsg, "Files /dev/sd{a,a1} already exist. Good.\n");
 }

 fprintf(kmsg, "Attempting mount-ro newroot to /mnt\n");
 if( mount("zfs-root", "/mnt", "zfs", MS_RDONLY, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move /dev to /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 fprintf(kmsg, "Execing root system /sbin/init.\n");
 if( execl("/sbin/init", "3", (char *) NULL ) != 0 ) {
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

}
EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
# note: root=, rootfstype, ro, rootwait are "legacy" kernel boot options and are not really being used here
#       so, they probably can be removed but are not hurting

# if you have errors using zfs and zpool commands on booted system with builtin modules, then
# upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries
# renamed like zpoolb, zfsb etc for builtin

# if you have boot problem, you might want to run in qemu's -nographic console mode:
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
# wait for the lilo prompt, it takes time to show up
boot: vm3.2.27b console=ttyS0
# ctrl-a h    for help
# ctrl-a c    for (QEMU) console
# BECAREFUL not to start qemu twice on the same ZFS guest
#  two simultaneous running qemu on the same ZFS will corrupt the pool
#  then it will NOT recover... you lose your whole installation!
# BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST!
# only use -nographic to see kernel problems then quit it
# Doing this is only useful until the kernel panics because additional console switching needs
# to be done still. If it does boot, then ctrl-a c, and quit (sorry) and reboot normal
# The console switching part missing in init would look similar to this:
#
#if (console) {
#		close(0);
#		xopen(console, O_RDWR);
#		xdup2(0, 1);
#		xdup2(0, 2);
#	}

# to use if=scsi, linux module sym53c8xx, may need to use the qemu option:
#       -option-rom 8xx_64.rom,bootindex=1
# download it here:
# http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
# extract 8xx_64.rom to /usr/share/qemu/

Then, at the lilo prompt, use kernel parameter: console=ttyS0     (do NOT say /dev/ttS0)
There is a delay before you see LILO so be patient. You should see full messages of kernel.
The purpose of sgabios is that it is the "serial graphics adapter" video BIOS that sends all its text mode I/O over ttyS0.
The -nographic option redirects the guest's ttyS0 to your console.
The purpose of 8xx_64.rom is the SCSI interface firmware, and it boots after the SGABIOS so that everything will be visible.
For QEMU help, press ctrl-a then hit h.

&lt;/pre&gt;

Good luck!</text>
    <sha1>557be652f03d56c92abdd034a19e196a00c85bc0</sha1>
  </revision>
  <revision>
    <id>741</id>
    <parentid>740</parentid>
    <timestamp>2012-08-21T18:35:03Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10043" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
cd spl-0.6.0-rc10
mkdir install
./configure --prefix=/ --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share --enable-linux-builtin=yes --with-linux=/usr/src/linux-3.2.27b --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
cd spl-0.6.0-rc10
mkdir install
./configure --prefix=/ --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share --enable-linux-builtin=yes --with-linux=/usr/src/linux-3.2.27b --with-linux-obj=/usr/src/linux-3.2.27b --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS

cd /boot/initramfs-source
mkdir -p etc/zfs dev mnt
touch etc/mtab
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

### make the rootfs /init program
cat &gt; init.c &lt;&lt;"EOF"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

int main(int argc, char* argv[]) {
 FILE* kmsg = NULL;
 char* fnkmsg = "/dev/kmsg";
 mknod(fnkmsg, S_IFCHR , makedev(1,11) );
 kmsg = fopen(fnkmsg, "w");
 fprintf(kmsg, "foobarz-zinit starting.\n");

 fprintf(kmsg, "Attempting mount devtmpfs to /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }

 if( access("/dev/zfs", F_OK) != 0 ) {
  fprintf(kmsg, "File /dev/zfs does not exist; making nod.\n");
  mknod("/dev/zfs", S_IFCHR , makedev(10,58) );
 } else {
  fprintf(kmsg, "File /dev/zfs already exists. Good.\n");
 }

 if( access("/dev/sda1", F_OK) != 0 ) {
  fprintf(kmsg, "Files /dev/sd{a,a1} do not exist; making nods.\n");
  mknod("/dev/sda", S_IFBLK , makedev(8,0) );
  mknod("/dev/sda1", S_IFBLK , makedev(8,1) );
 } else {
  fprintf(kmsg, "Files /dev/sd{a,a1} already exist. Good.\n");
 }

 fprintf(kmsg, "Attempting mount-ro newroot to /mnt\n");
 if( mount("zfs-root", "/mnt", "zfs", MS_RDONLY, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move /dev to /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 fprintf(kmsg, "Execing root system /sbin/init.\n");
 if( execl("/sbin/init", "3", (char *) NULL ) != 0 ) {
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

}
EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
# note: root=, rootfstype, ro, rootwait are "legacy" kernel boot options and are not really being used here
#       so, they probably can be removed but are not hurting

# if you have errors using zfs and zpool commands on booted system with builtin modules, then
# upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries
# renamed like zpoolb, zfsb etc for builtin

# if you have boot problem, you might want to run in qemu's -nographic console mode:
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
# wait for the lilo prompt, it takes time to show up
boot: vm3.2.27b console=ttyS0
# ctrl-a h    for help
# ctrl-a c    for (QEMU) console
# BECAREFUL not to start qemu twice on the same ZFS guest
#  two simultaneous running qemu on the same ZFS will corrupt the pool
#  then it will NOT recover... you lose your whole installation!
# BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST!
# only use -nographic to see kernel problems then quit it
# Doing this is only useful until the kernel panics because additional console switching needs
# to be done still. If it does boot, then ctrl-a c, and quit (sorry) and reboot normal
# The console switching part missing in init would look similar to this:
#
#if (console) {
#		close(0);
#		xopen(console, O_RDWR);
#		xdup2(0, 1);
#		xdup2(0, 2);
#	}

# to use if=scsi, linux module sym53c8xx, may need to use the qemu option:
#       -option-rom 8xx_64.rom,bootindex=1
# download it here:
# http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
# extract 8xx_64.rom to /usr/share/qemu/

Then, at the lilo prompt, use kernel parameter: console=ttyS0     (do NOT say /dev/ttS0)
There is a delay before you see LILO so be patient. You should see full messages of kernel.
The purpose of sgabios is that it is the "serial graphics adapter" video BIOS that sends all its text mode I/O over ttyS0.
The -nographic option redirects the guest's ttyS0 to your console.
The purpose of 8xx_64.rom is the SCSI interface firmware, and it boots after the SGABIOS so that everything will be visible.
For QEMU help, press ctrl-a then hit h.

&lt;/pre&gt;

Good luck!</text>
    <sha1>f34aa97a412e10d7136bbfe00f3d9669ef662351</sha1>
  </revision>
  <revision>
    <id>742</id>
    <parentid>741</parentid>
    <timestamp>2012-08-21T18:36:20Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10043" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure --prefix=/ --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share --enable-linux-builtin=yes --with-linux=/usr/src/linux-3.2.27b --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure --prefix=/ --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share --enable-linux-builtin=yes --with-linux=/usr/src/linux-3.2.27b --with-linux-obj=/usr/src/linux-3.2.27b --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS

cd /boot/initramfs-source
mkdir -p etc/zfs dev mnt
touch etc/mtab
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

### make the rootfs /init program
cat &gt; init.c &lt;&lt;"EOF"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

int main(int argc, char* argv[]) {
 FILE* kmsg = NULL;
 char* fnkmsg = "/dev/kmsg";
 mknod(fnkmsg, S_IFCHR , makedev(1,11) );
 kmsg = fopen(fnkmsg, "w");
 fprintf(kmsg, "foobarz-zinit starting.\n");

 fprintf(kmsg, "Attempting mount devtmpfs to /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }

 if( access("/dev/zfs", F_OK) != 0 ) {
  fprintf(kmsg, "File /dev/zfs does not exist; making nod.\n");
  mknod("/dev/zfs", S_IFCHR , makedev(10,58) );
 } else {
  fprintf(kmsg, "File /dev/zfs already exists. Good.\n");
 }

 if( access("/dev/sda1", F_OK) != 0 ) {
  fprintf(kmsg, "Files /dev/sd{a,a1} do not exist; making nods.\n");
  mknod("/dev/sda", S_IFBLK , makedev(8,0) );
  mknod("/dev/sda1", S_IFBLK , makedev(8,1) );
 } else {
  fprintf(kmsg, "Files /dev/sd{a,a1} already exist. Good.\n");
 }

 fprintf(kmsg, "Attempting mount-ro newroot to /mnt\n");
 if( mount("zfs-root", "/mnt", "zfs", MS_RDONLY, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move /dev to /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 fprintf(kmsg, "Execing root system /sbin/init.\n");
 if( execl("/sbin/init", "3", (char *) NULL ) != 0 ) {
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

}
EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
# note: root=, rootfstype, ro, rootwait are "legacy" kernel boot options and are not really being used here
#       so, they probably can be removed but are not hurting

# if you have errors using zfs and zpool commands on booted system with builtin modules, then
# upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries
# renamed like zpoolb, zfsb etc for builtin

# if you have boot problem, you might want to run in qemu's -nographic console mode:
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
# wait for the lilo prompt, it takes time to show up
boot: vm3.2.27b console=ttyS0
# ctrl-a h    for help
# ctrl-a c    for (QEMU) console
# BECAREFUL not to start qemu twice on the same ZFS guest
#  two simultaneous running qemu on the same ZFS will corrupt the pool
#  then it will NOT recover... you lose your whole installation!
# BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST!
# only use -nographic to see kernel problems then quit it
# Doing this is only useful until the kernel panics because additional console switching needs
# to be done still. If it does boot, then ctrl-a c, and quit (sorry) and reboot normal
# The console switching part missing in init would look similar to this:
#
#if (console) {
#		close(0);
#		xopen(console, O_RDWR);
#		xdup2(0, 1);
#		xdup2(0, 2);
#	}

# to use if=scsi, linux module sym53c8xx, may need to use the qemu option:
#       -option-rom 8xx_64.rom,bootindex=1
# download it here:
# http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
# extract 8xx_64.rom to /usr/share/qemu/

Then, at the lilo prompt, use kernel parameter: console=ttyS0     (do NOT say /dev/ttS0)
There is a delay before you see LILO so be patient. You should see full messages of kernel.
The purpose of sgabios is that it is the "serial graphics adapter" video BIOS that sends all its text mode I/O over ttyS0.
The -nographic option redirects the guest's ttyS0 to your console.
The purpose of 8xx_64.rom is the SCSI interface firmware, and it boots after the SGABIOS so that everything will be visible.
For QEMU help, press ctrl-a then hit h.

&lt;/pre&gt;

Good luck!</text>
    <sha1>32108e7329cd1ea2224a5f7294deab04666eecd0</sha1>
  </revision>
  <revision>
    <id>743</id>
    <parentid>742</parentid>
    <timestamp>2012-08-23T10:15:14Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22777" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.0"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 FILE* kmsg = NULL;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 int usage = EX_OK;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; };
 struct nv param[] = {
   { "root=", NULL, NULL, 1 },      /* required; root device to boot */
   { "rootfs=", NULL, NULL, 1 },    /* required; root filesystem type */
   { "mountopt=", NULL, NULL, 0 },  /* optional; mount option ro or rw; default ro */
   { "init=", NULL, NULL, 0 },      /* optional; alt. init prgm; default /sbin/init */
   { "runlevel=", NULL, NULL, 0 },  /* optional; runlevel 0123456Ss; default 3 multiuser */
   { "console=", NULL, NULL, 0 }          /* optional; alt. console; e.g. ttyS0 */
 };
 enum { iroot, irootfs, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 kmsg = fopen("/dev/kmsg", "w");
 fprintf(kmsg, "foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   fprintf(kmsg, "Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 fprintf(kmsg, "Attempting mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 fprintf(kmsg, "Attempting mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 fprintf(kmsg, "Kernel cmdline size: %i\n", cmdline_size);
 fprintf(kmsg, "Kernel cmdline: \"%s\"\n", cmdline);

 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       fprintf(kmsg, "Kernel parameter %s: value missing.\n", param[i].n);
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults on non-required params, except for console */
 if( param[imountopt].v == NULL ) param[imountopt].v = "ro";
 if( param[iinit].v == NULL )     param[iinit].v = "/sbin/init";
 if( param[irunlevel].v == NULL ) param[irunlevel].v = "3";

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   fprintf(kmsg, "Using %s \"%s\"\n", param[i].n, param[i].v);
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( (param[i].req == 1) &amp;&amp; (param[i].v == NULL) ) {
     printf("Error: missing required kernel parameter: %s\n", param[i].n);
     usage = EX_USAGE;
   }
 }
 if( usage != EX_OK ) {
   printf("Aborting boot process. Missing required kernel parameter(s).\n");
   return usage;
 }
 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfs]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfs].v) == NULL ) {
   fprintf(kmsg, "%s \"%s\": filesystem type not available.\n",
	   param[irootfs].n, param[irootfs].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfs].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfs].v);
   else
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfs].v);
   if( access("/etc/hostid", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/hostid is present in initramfs.\n", param[irootfs].v);
   else
     fprintf(kmsg, "%s: /etc/hostid not present in initramfs.\n", param[irootfs].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   fprintf(kmsg, "% \"%\": invalid parameter value;\n"
		 "   use \"ro\" or \"rw\" (no quotes or spaces);\n"
		 "   defaulting to \"ro\".\n",
		 param[imountopt].n, param[imountopt].v
	  );
   mountflags = MS_RDONLY;
 }

 fprintf(kmsg, "Attempting %s %s mount %s /mnt.\n",
	 param[irootfs].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfs].v, mountflags, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "%s mounted successfully.\n", param[iroot].v);

 fprintf(kmsg, "Attempting mount --move /dev /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount --move /proc /mnt/proc\n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].v != NULL ) {
   fprintf(kmsg, "Console redirection to device %s requested.\n", param[iconsole].v);
   fprintf(kmsg, "Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
   close(0);
   /* expect only basename of device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   open(param[iconsole].v, O_RDWR);
   dup2(0, 1);
   dup2(0, 2);
   chdir("/");
 }

 fprintf(kmsg, "Execing: \"%s %s\" to boot mounted root system.\n",
	 param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 fclose(kmsg);
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  kmsg = fopen("/dev/kmsg", "w");
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  fclose(kmsg);
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
# note: root=, rootfstype, ro, rootwait are "legacy" kernel boot options and are not really being used here
#       so, they probably can be removed but are not hurting

# if you have errors using zfs and zpool commands on booted system with builtin modules, then
# upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries
# renamed like zpoolb, zfsb etc for builtin

# if you have boot problem, you might want to run in qemu's -nographic console mode:
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
# wait for the lilo prompt, it takes time to show up
boot: vm3.2.27b console=ttyS0
# ctrl-a h    for help
# ctrl-a c    for (QEMU) console
# BECAREFUL not to start qemu twice on the same ZFS guest
#  two simultaneous running qemu on the same ZFS will corrupt the pool
#  then it will NOT recover... you lose your whole installation!
# BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST!
# only use -nographic to see kernel problems then quit it
# Doing this is only useful until the kernel panics because additional console switching needs
# to be done still. If it does boot, then ctrl-a c, and quit (sorry) and reboot normal
# The console switching part missing in init would look similar to this:
#
#if (console) {
#		close(0);
#		xopen(console, O_RDWR);
#		xdup2(0, 1);
#		xdup2(0, 2);
#	}

# to use if=scsi, linux module sym53c8xx, may need to use the qemu option:
#       -option-rom 8xx_64.rom,bootindex=1
# download it here:
# http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
# extract 8xx_64.rom to /usr/share/qemu/

Then, at the lilo prompt, use kernel parameter: console=ttyS0     (do NOT say /dev/ttS0)
There is a delay before you see LILO so be patient. You should see full messages of kernel.
The purpose of sgabios is that it is the "serial graphics adapter" video BIOS that sends all its text mode I/O over ttyS0.
The -nographic option redirects the guest's ttyS0 to your console.
The purpose of 8xx_64.rom is the SCSI interface firmware, and it boots after the SGABIOS so that everything will be visible.
For QEMU help, press ctrl-a then hit h.

&lt;/pre&gt;

Good luck!</text>
    <sha1>74d722e56cd1017b70840e4078cd05372b4113f3</sha1>
  </revision>
  <revision>
    <id>744</id>
    <parentid>743</parentid>
    <timestamp>2012-08-23T10:17:30Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22523" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.0"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 FILE* kmsg = NULL;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 int usage = EX_OK;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; };
 struct nv param[] = {
   { "root=", NULL, NULL, 1 },      /* required; root device to boot */
   { "rootfs=", NULL, NULL, 1 },    /* required; root filesystem type */
   { "mountopt=", NULL, NULL, 0 },  /* optional; mount option ro or rw; default ro */
   { "init=", NULL, NULL, 0 },      /* optional; alt. init prgm; default /sbin/init */
   { "runlevel=", NULL, NULL, 0 },  /* optional; runlevel 0123456Ss; default 3 multiuser */
   { "console=", NULL, NULL, 0 }          /* optional; alt. console; e.g. ttyS0 */
 };
 enum { iroot, irootfs, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 kmsg = fopen("/dev/kmsg", "w");
 fprintf(kmsg, "foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   fprintf(kmsg, "Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 fprintf(kmsg, "Attempting mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 fprintf(kmsg, "Attempting mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 fprintf(kmsg, "Kernel cmdline size: %i\n", cmdline_size);
 fprintf(kmsg, "Kernel cmdline: \"%s\"\n", cmdline);

 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       fprintf(kmsg, "Kernel parameter %s: value missing.\n", param[i].n);
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults on non-required params, except for console */
 if( param[imountopt].v == NULL ) param[imountopt].v = "ro";
 if( param[iinit].v == NULL )     param[iinit].v = "/sbin/init";
 if( param[irunlevel].v == NULL ) param[irunlevel].v = "3";

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   fprintf(kmsg, "Using %s \"%s\"\n", param[i].n, param[i].v);
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( (param[i].req == 1) &amp;&amp; (param[i].v == NULL) ) {
     printf("Error: missing required kernel parameter: %s\n", param[i].n);
     usage = EX_USAGE;
   }
 }
 if( usage != EX_OK ) {
   printf("Aborting boot process. Missing required kernel parameter(s).\n");
   return usage;
 }
 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfs]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfs].v) == NULL ) {
   fprintf(kmsg, "%s \"%s\": filesystem type not available.\n",
	   param[irootfs].n, param[irootfs].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfs].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfs].v);
   else
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfs].v);
   if( access("/etc/hostid", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/hostid is present in initramfs.\n", param[irootfs].v);
   else
     fprintf(kmsg, "%s: /etc/hostid not present in initramfs.\n", param[irootfs].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   fprintf(kmsg, "% \"%\": invalid parameter value;\n"
		 "   use \"ro\" or \"rw\" (no quotes or spaces);\n"
		 "   defaulting to \"ro\".\n",
		 param[imountopt].n, param[imountopt].v
	  );
   mountflags = MS_RDONLY;
 }

 fprintf(kmsg, "Attempting %s %s mount %s /mnt.\n",
	 param[irootfs].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfs].v, mountflags, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "%s mounted successfully.\n", param[iroot].v);

 fprintf(kmsg, "Attempting mount --move /dev /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount --move /proc /mnt/proc\n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].v != NULL ) {
   fprintf(kmsg, "Console redirection to device %s requested.\n", param[iconsole].v);
   fprintf(kmsg, "Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
   close(0);
   /* expect only basename of device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   open(param[iconsole].v, O_RDWR);
   dup2(0, 1);
   dup2(0, 2);
   chdir("/");
 }

 fprintf(kmsg, "Execing: \"%s %s\" to boot mounted root system.\n",
	 param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 fclose(kmsg);
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  kmsg = fopen("/dev/kmsg", "w");
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  fclose(kmsg);
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
# note: root=, rootfstype, ro, rootwait are "legacy" kernel boot options and are not really being used here
#       so, they probably can be removed but are not hurting

# if you have errors using zfs and zpool commands on booted system with builtin modules, then
# upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries
# renamed like zpoolb, zfsb etc for builtin

# if you have boot problem, you might want to run in qemu's -nographic console mode:
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
# wait for the lilo prompt, it takes time to show up
boot: vm3.2.27b console=ttyS0
# ctrl-a h    for help
# ctrl-a c    for (QEMU) console

# BECAREFUL not to start qemu twice on the same ZFS guest
#  two simultaneous running qemu on the same ZFS will corrupt the pool
#  then it will NOT recover... you lose your whole installation!
# BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST!
# only use -nographic to see kernel problems then quit it...
# qemu or slackware is buggy with this it gets stuck right before you get the tty1 prompt.

# to use if=scsi, linux module sym53c8xx, may need to use the qemu option:
#       -option-rom 8xx_64.rom,bootindex=1
# download it here:
# http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
# extract 8xx_64.rom to /usr/share/qemu/

Then, at the lilo prompt, use kernel parameter: console=ttyS0     (do NOT say /dev/ttS0)
There is a delay before you see LILO so be patient. You should see full messages of kernel.
The purpose of sgabios is that it is the "serial graphics adapter" video BIOS that sends all its text mode I/O over ttyS0.
The -nographic option redirects the guest's ttyS0 to your console.
The purpose of 8xx_64.rom is the SCSI interface firmware, and it boots after the SGABIOS so that everything will be visible.
For QEMU help, press ctrl-a then hit h.

&lt;/pre&gt;

Good luck!</text>
    <sha1>50b17557c138926457ef558417d3ff344d1ce600</sha1>
  </revision>
  <revision>
    <id>745</id>
    <parentid>744</parentid>
    <timestamp>2012-08-23T10:35:58Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22575" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 FILE* kmsg = NULL;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 int usage = EX_OK;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; };
 struct nv param[] = {
   { "root=", NULL, NULL, 1 },      /* required; root device to boot */
   { "rootfstype=", NULL, NULL, 1 },    /* required; root filesystem type */
   { "mountopt=", NULL, NULL, 0 },  /* optional; mount option ro or rw; default ro */
   { "init=", NULL, NULL, 0 },      /* optional; alt. init prgm; default /sbin/init */
   { "runlevel=", NULL, NULL, 0 },  /* optional; runlevel 0123456Ss; default 3 multiuser */
   { "console=", NULL, NULL, 0 }          /* optional; alt. console; e.g. ttyS0 */
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 kmsg = fopen("/dev/kmsg", "w");
 fprintf(kmsg, "foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   fprintf(kmsg, "Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 fprintf(kmsg, "Attempting mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 fprintf(kmsg, "Attempting mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 fprintf(kmsg, "Kernel cmdline size: %i\n", cmdline_size);
 fprintf(kmsg, "Kernel cmdline: \"%s\"\n", cmdline);

 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       fprintf(kmsg, "Kernel parameter %s: value missing.\n", param[i].n);
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults on non-required params, except for console */
 if( param[imountopt].v == NULL ) param[imountopt].v = "ro";
 if( param[iinit].v == NULL )     param[iinit].v = "/sbin/init";
 if( param[irunlevel].v == NULL ) param[irunlevel].v = "3";

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   fprintf(kmsg, "Using %s \"%s\"\n", param[i].n, param[i].v);
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( (param[i].req == 1) &amp;&amp; (param[i].v == NULL) ) {
     printf("Error: missing required kernel parameter: %s\n", param[i].n);
     usage = EX_USAGE;
   }
 }
 if( usage != EX_OK ) {
   printf("Aborting boot process. Missing required kernel parameter(s).\n");
   return usage;
 }
 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   fprintf(kmsg, "%s \"%s\": filesystem type not available.\n",
	   param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);
   if( access("/etc/hostid", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   fprintf(kmsg, "% \"%\": invalid parameter value;\n"
		 "   use \"ro\" or \"rw\" (no quotes or spaces);\n"
		 "   defaulting to \"ro\".\n",
		 param[imountopt].n, param[imountopt].v
	  );
   mountflags = MS_RDONLY;
 }

 fprintf(kmsg, "Attempting %s %s mount %s /mnt.\n",
	 param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "%s mounted successfully.\n", param[iroot].v);

 fprintf(kmsg, "Attempting mount --move /dev /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount --move /proc /mnt/proc\n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].v != NULL ) {
   fprintf(kmsg, "Console redirection to device %s requested.\n", param[iconsole].v);
   fprintf(kmsg, "Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
   close(0);
   /* expect only basename of device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   open(param[iconsole].v, O_RDWR);
   dup2(0, 1);
   dup2(0, 2);
   chdir("/");
 }

 fprintf(kmsg, "Execing: \"%s %s\" to boot mounted root system.\n",
	 param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 fclose(kmsg);
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  kmsg = fopen("/dev/kmsg", "w");
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  fclose(kmsg);
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
# note: root=, rootfstype, ro, rootwait are "legacy" kernel boot options and are not really being used here
#       so, they probably can be removed but are not hurting

# if you have errors using zfs and zpool commands on booted system with builtin modules, then
# upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries
# renamed like zpoolb, zfsb etc for builtin

# if you have boot problem, you might want to run in qemu's -nographic console mode:
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
# wait for the lilo prompt, it takes time to show up
boot: vm3.2.27b console=ttyS0
# ctrl-a h    for help
# ctrl-a c    for (QEMU) console

# BECAREFUL not to start qemu twice on the same ZFS guest
#  two simultaneous running qemu on the same ZFS will corrupt the pool
#  then it will NOT recover... you lose your whole installation!
# BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST!
# only use -nographic to see kernel problems then quit it...
# qemu or slackware is buggy with this it gets stuck right before you get the tty1 prompt.

# to use if=scsi, linux module sym53c8xx, may need to use the qemu option:
#       -option-rom 8xx_64.rom,bootindex=1
# download it here:
# http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
# extract 8xx_64.rom to /usr/share/qemu/

Then, at the lilo prompt, use kernel parameter: console=ttyS0     (do NOT say /dev/ttS0)
There is a delay before you see LILO so be patient. You should see full messages of kernel.
The purpose of sgabios is that it is the "serial graphics adapter" video BIOS that sends all its text mode I/O over ttyS0.
The -nographic option redirects the guest's ttyS0 to your console.
The purpose of 8xx_64.rom is the SCSI interface firmware, and it boots after the SGABIOS so that everything will be visible.
For QEMU help, press ctrl-a then hit h.

&lt;/pre&gt;

Good luck!</text>
    <sha1>cda3945d8789bf2e09dfc85cde91233848de233b</sha1>
  </revision>
  <revision>
    <id>746</id>
    <parentid>745</parentid>
    <timestamp>2012-08-24T02:44:35Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23283" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 FILE* kmsg = NULL;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 int usage = EX_OK;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; };
 struct nv param[] = {
   { "root=", NULL, NULL, 1 },      /* required; root device to boot */
   { "rootfstype=", NULL, NULL, 1 },    /* required; root filesystem type */
   { "mountopt=", NULL, NULL, 0 },  /* optional; mount option ro or rw; default ro */
   { "init=", NULL, NULL, 0 },      /* optional; alt. init prgm; default /sbin/init */
   { "runlevel=", NULL, NULL, 0 },  /* optional; runlevel 0123456Ss; default 3 multiuser */
   { "console=", NULL, NULL, 0 }          /* optional; alt. console; e.g. ttyS0 */
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 kmsg = fopen("/dev/kmsg", "w");
 fprintf(kmsg, "foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   fprintf(kmsg, "Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 fprintf(kmsg, "Attempting mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 fprintf(kmsg, "Attempting mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 fprintf(kmsg, "Kernel cmdline size: %i\n", cmdline_size);
 fprintf(kmsg, "Kernel cmdline: \"%s\"\n", cmdline);

 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       fprintf(kmsg, "Kernel parameter %s: value missing.\n", param[i].n);
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults on non-required params, except for console */
 if( param[imountopt].v == NULL ) param[imountopt].v = "ro";
 if( param[iinit].v == NULL )     param[iinit].v = "/sbin/init";
 if( param[irunlevel].v == NULL ) param[irunlevel].v = "3";

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   fprintf(kmsg, "Using %s \"%s\"\n", param[i].n, param[i].v);
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( (param[i].req == 1) &amp;&amp; (param[i].v == NULL) ) {
     printf("Error: missing required kernel parameter: %s\n", param[i].n);
     usage = EX_USAGE;
   }
 }
 if( usage != EX_OK ) {
   printf("Aborting boot process. Missing required kernel parameter(s).\n");
   return usage;
 }
 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   fprintf(kmsg, "%s \"%s\": filesystem type not available.\n",
	   param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);
   if( access("/etc/hostid", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   fprintf(kmsg, "% \"%\": invalid parameter value;\n"
		 "   use \"ro\" or \"rw\" (no quotes or spaces);\n"
		 "   defaulting to \"ro\".\n",
		 param[imountopt].n, param[imountopt].v
	  );
   mountflags = MS_RDONLY;
 }

 fprintf(kmsg, "Attempting %s %s mount %s /mnt.\n",
	 param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "%s mounted successfully.\n", param[iroot].v);

 fprintf(kmsg, "Attempting mount --move /dev /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount --move /proc /mnt/proc\n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].v != NULL ) {
   fprintf(kmsg, "Console redirection to device %s requested.\n", param[iconsole].v);
   fprintf(kmsg, "Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
   close(0);
   /* expect only basename of device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   open(param[iconsole].v, O_RDWR);
   dup2(0, 1);
   dup2(0, 2);
   chdir("/");
 }

 fprintf(kmsg, "Execing: \"%s %s\" to boot mounted root system.\n",
	 param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 fclose(kmsg);
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  kmsg = fopen("/dev/kmsg", "w");
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  fclose(kmsg);
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevels "s1" (ttyS0) and "s2" (ttyS1) for serial console login support.

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0 runlevel=s1
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0).

When you are in qemu's serial graphics mode, the interface is a little different than in the normal graphical SQL-based mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.com used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>a3c541d323bd49c9cae2c79d0dce8ae4dc1d66fb</sha1>
  </revision>
  <revision>
    <id>747</id>
    <parentid>746</parentid>
    <timestamp>2012-08-24T02:55:37Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23418" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 FILE* kmsg = NULL;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 int usage = EX_OK;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; };
 struct nv param[] = {
   { "root=", NULL, NULL, 1 },      /* required; root device to boot */
   { "rootfstype=", NULL, NULL, 1 },    /* required; root filesystem type */
   { "mountopt=", NULL, NULL, 0 },  /* optional; mount option ro or rw; default ro */
   { "init=", NULL, NULL, 0 },      /* optional; alt. init prgm; default /sbin/init */
   { "runlevel=", NULL, NULL, 0 },  /* optional; runlevel 0123456Ss; default 3 multiuser */
   { "console=", NULL, NULL, 0 }          /* optional; alt. console; e.g. ttyS0 */
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 kmsg = fopen("/dev/kmsg", "w");
 fprintf(kmsg, "foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   fprintf(kmsg, "Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 fprintf(kmsg, "Attempting mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 fprintf(kmsg, "Attempting mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 fprintf(kmsg, "Kernel cmdline size: %i\n", cmdline_size);
 fprintf(kmsg, "Kernel cmdline: \"%s\"\n", cmdline);

 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       fprintf(kmsg, "Kernel parameter %s: value missing.\n", param[i].n);
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults on non-required params, except for console */
 if( param[imountopt].v == NULL ) param[imountopt].v = "ro";
 if( param[iinit].v == NULL )     param[iinit].v = "/sbin/init";
 if( param[irunlevel].v == NULL ) param[irunlevel].v = "3";

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   fprintf(kmsg, "Using %s \"%s\"\n", param[i].n, param[i].v);
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( (param[i].req == 1) &amp;&amp; (param[i].v == NULL) ) {
     printf("Error: missing required kernel parameter: %s\n", param[i].n);
     usage = EX_USAGE;
   }
 }
 if( usage != EX_OK ) {
   printf("Aborting boot process. Missing required kernel parameter(s).\n");
   return usage;
 }
 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   fprintf(kmsg, "%s \"%s\": filesystem type not available.\n",
	   param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);
   if( access("/etc/hostid", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   fprintf(kmsg, "% \"%\": invalid parameter value;\n"
		 "   use \"ro\" or \"rw\" (no quotes or spaces);\n"
		 "   defaulting to \"ro\".\n",
		 param[imountopt].n, param[imountopt].v
	  );
   mountflags = MS_RDONLY;
 }

 fprintf(kmsg, "Attempting %s %s mount %s /mnt.\n",
	 param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "%s mounted successfully.\n", param[iroot].v);

 fprintf(kmsg, "Attempting mount --move /dev /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount --move /proc /mnt/proc\n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].v != NULL ) {
   fprintf(kmsg, "Console redirection to device %s requested.\n", param[iconsole].v);
   fprintf(kmsg, "Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
   close(0);
   /* expect only basename of device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   open(param[iconsole].v, O_RDWR);
   dup2(0, 1);
   dup2(0, 2);
   chdir("/");
 }

 fprintf(kmsg, "Execing: \"%s %s\" to boot mounted root system.\n",
	 param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 fclose(kmsg);
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  kmsg = fopen("/dev/kmsg", "w");
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  fclose(kmsg);
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevels "s1" (ttyS0) and "s2" (ttyS1) for serial console login support:
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0 runlevel=s1
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0).

When you are in qemu's serial graphics mode, the interface is a little different than in the normal graphical SQL-based mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.com used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>b06632810720a919f16a0d15ec2521e5454af9d9</sha1>
  </revision>
  <revision>
    <id>748</id>
    <parentid>747</parentid>
    <timestamp>2012-08-24T02:57:16Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23471" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 FILE* kmsg = NULL;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 int usage = EX_OK;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; };
 struct nv param[] = {
   { "root=", NULL, NULL, 1 },      /* required; root device to boot */
   { "rootfstype=", NULL, NULL, 1 },    /* required; root filesystem type */
   { "mountopt=", NULL, NULL, 0 },  /* optional; mount option ro or rw; default ro */
   { "init=", NULL, NULL, 0 },      /* optional; alt. init prgm; default /sbin/init */
   { "runlevel=", NULL, NULL, 0 },  /* optional; runlevel 0123456Ss; default 3 multiuser */
   { "console=", NULL, NULL, 0 }          /* optional; alt. console; e.g. ttyS0 */
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 kmsg = fopen("/dev/kmsg", "w");
 fprintf(kmsg, "foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   fprintf(kmsg, "Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 fprintf(kmsg, "Attempting mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 fprintf(kmsg, "Attempting mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 fprintf(kmsg, "Kernel cmdline size: %i\n", cmdline_size);
 fprintf(kmsg, "Kernel cmdline: \"%s\"\n", cmdline);

 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       fprintf(kmsg, "Kernel parameter %s: value missing.\n", param[i].n);
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults on non-required params, except for console */
 if( param[imountopt].v == NULL ) param[imountopt].v = "ro";
 if( param[iinit].v == NULL )     param[iinit].v = "/sbin/init";
 if( param[irunlevel].v == NULL ) param[irunlevel].v = "3";

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   fprintf(kmsg, "Using %s \"%s\"\n", param[i].n, param[i].v);
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( (param[i].req == 1) &amp;&amp; (param[i].v == NULL) ) {
     printf("Error: missing required kernel parameter: %s\n", param[i].n);
     usage = EX_USAGE;
   }
 }
 if( usage != EX_OK ) {
   printf("Aborting boot process. Missing required kernel parameter(s).\n");
   return usage;
 }
 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   fprintf(kmsg, "%s \"%s\": filesystem type not available.\n",
	   param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);
   if( access("/etc/hostid", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   fprintf(kmsg, "% \"%\": invalid parameter value;\n"
		 "   use \"ro\" or \"rw\" (no quotes or spaces);\n"
		 "   defaulting to \"ro\".\n",
		 param[imountopt].n, param[imountopt].v
	  );
   mountflags = MS_RDONLY;
 }

 fprintf(kmsg, "Attempting %s %s mount %s /mnt.\n",
	 param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "%s mounted successfully.\n", param[iroot].v);

 fprintf(kmsg, "Attempting mount --move /dev /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount --move /proc /mnt/proc\n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].v != NULL ) {
   fprintf(kmsg, "Console redirection to device %s requested.\n", param[iconsole].v);
   fprintf(kmsg, "Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
   close(0);
   /* expect only basename of device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   open(param[iconsole].v, O_RDWR);
   dup2(0, 1);
   dup2(0, 2);
   chdir("/");
 }

 fprintf(kmsg, "Execing: \"%s %s\" to boot mounted root system.\n",
	 param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 fclose(kmsg);
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  kmsg = fopen("/dev/kmsg", "w");
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  fclose(kmsg);
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevels "s1" (ttyS0) and "s2" (ttyS1) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0 runlevel=s1
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0).

When you are in qemu's serial graphics mode, the interface is a little different than in the normal graphical SQL-based mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.com used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>098b3e6a225c78d5801ef89dd0dfb8f348b901e0</sha1>
  </revision>
  <revision>
    <id>749</id>
    <parentid>748</parentid>
    <timestamp>2012-08-24T03:32:59Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23682" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 FILE* kmsg = NULL;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 int usage = EX_OK;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; };
 struct nv param[] = {
   { "root=", NULL, NULL, 1 },      /* required; root device to boot */
   { "rootfstype=", NULL, NULL, 1 },    /* required; root filesystem type */
   { "mountopt=", NULL, NULL, 0 },  /* optional; mount option ro or rw; default ro */
   { "init=", NULL, NULL, 0 },      /* optional; alt. init prgm; default /sbin/init */
   { "runlevel=", NULL, NULL, 0 },  /* optional; runlevel 0123456Ss; default 3 multiuser */
   { "console=", NULL, NULL, 0 }          /* optional; alt. console; e.g. ttyS0 */
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 kmsg = fopen("/dev/kmsg", "w");
 fprintf(kmsg, "foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   fprintf(kmsg, "Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 fprintf(kmsg, "Attempting mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 fprintf(kmsg, "Attempting mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 fprintf(kmsg, "Kernel cmdline size: %i\n", cmdline_size);
 fprintf(kmsg, "Kernel cmdline: \"%s\"\n", cmdline);

 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       fprintf(kmsg, "Kernel parameter %s: value missing.\n", param[i].n);
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults on non-required params, except for console */
 if( param[imountopt].v == NULL ) param[imountopt].v = "ro";
 if( param[iinit].v == NULL )     param[iinit].v = "/sbin/init";
 if( param[irunlevel].v == NULL ) param[irunlevel].v = "3";

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   fprintf(kmsg, "Using %s \"%s\"\n", param[i].n, param[i].v);
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( (param[i].req == 1) &amp;&amp; (param[i].v == NULL) ) {
     printf("Error: missing required kernel parameter: %s\n", param[i].n);
     usage = EX_USAGE;
   }
 }
 if( usage != EX_OK ) {
   printf("Aborting boot process. Missing required kernel parameter(s).\n");
   return usage;
 }
 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   fprintf(kmsg, "%s \"%s\": filesystem type not available.\n",
	   param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);
   if( access("/etc/hostid", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   fprintf(kmsg, "% \"%\": invalid parameter value;\n"
		 "   use \"ro\" or \"rw\" (no quotes or spaces);\n"
		 "   defaulting to \"ro\".\n",
		 param[imountopt].n, param[imountopt].v
	  );
   mountflags = MS_RDONLY;
 }

 fprintf(kmsg, "Attempting %s %s mount %s /mnt.\n",
	 param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "%s mounted successfully.\n", param[iroot].v);

 fprintf(kmsg, "Attempting mount --move /dev /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount --move /proc /mnt/proc\n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].v != NULL ) {
   fprintf(kmsg, "Console redirection to device %s requested.\n", param[iconsole].v);
   fprintf(kmsg, "Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
   close(0);
   /* expect only basename of device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   open(param[iconsole].v, O_RDWR);
   dup2(0, 1);
   dup2(0, 2);
   chdir("/");
 }

 fprintf(kmsg, "Execing: \"%s %s\" to boot mounted root system.\n",
	 param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 fclose(kmsg);
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  kmsg = fopen("/dev/kmsg", "w");
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  fclose(kmsg);
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0 runlevel=s1
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0).

When you are in qemu's serial graphics mode, the interface is a little different than in the normal graphical SQL-based mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.com used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>f373dab8816d9958fa2938c422533b79514fbf48</sha1>
  </revision>
  <revision>
    <id>750</id>
    <parentid>749</parentid>
    <timestamp>2012-08-24T03:38:08Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="23723" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 FILE* kmsg = NULL;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 int usage = EX_OK;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; };
 struct nv param[] = {
   { "root=", NULL, NULL, 1 },      /* required; root device to boot */
   { "rootfstype=", NULL, NULL, 1 },    /* required; root filesystem type */
   { "mountopt=", NULL, NULL, 0 },  /* optional; mount option ro or rw; default ro */
   { "init=", NULL, NULL, 0 },      /* optional; alt. init prgm; default /sbin/init */
   { "runlevel=", NULL, NULL, 0 },  /* optional; runlevel 0123456Ss; default 3 multiuser */
   { "console=", NULL, NULL, 0 }          /* optional; alt. console; e.g. ttyS0 */
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 kmsg = fopen("/dev/kmsg", "w");
 fprintf(kmsg, "foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   fprintf(kmsg, "Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 fprintf(kmsg, "Attempting mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 fprintf(kmsg, "Attempting mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 } else {
  fprintf(kmsg, "Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 fprintf(kmsg, "Kernel cmdline size: %i\n", cmdline_size);
 fprintf(kmsg, "Kernel cmdline: \"%s\"\n", cmdline);

 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       fprintf(kmsg, "Kernel parameter %s: value missing.\n", param[i].n);
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults on non-required params, except for console */
 if( param[imountopt].v == NULL ) param[imountopt].v = "ro";
 if( param[iinit].v == NULL )     param[iinit].v = "/sbin/init";
 if( param[irunlevel].v == NULL ) param[irunlevel].v = "3";

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   fprintf(kmsg, "Using %s \"%s\"\n", param[i].n, param[i].v);
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   if( (param[i].req == 1) &amp;&amp; (param[i].v == NULL) ) {
     printf("Error: missing required kernel parameter: %s\n", param[i].n);
     usage = EX_USAGE;
   }
 }
 if( usage != EX_OK ) {
   printf("Aborting boot process. Missing required kernel parameter(s).\n");
   return usage;
 }
 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   fprintf(kmsg, "Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   fprintf(kmsg, "Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   fprintf(kmsg, "%s \"%s\": filesystem type not available.\n",
	   param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);
   if( access("/etc/hostid", F_OK) == 0 )
     fprintf(kmsg, "%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     fprintf(kmsg, "%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   fprintf(kmsg, "% \"%\": invalid parameter value;\n"
		 "   use \"ro\" or \"rw\" (no quotes or spaces);\n"
		 "   defaulting to \"ro\".\n",
		 param[imountopt].n, param[imountopt].v
	  );
   mountflags = MS_RDONLY;
 }

 fprintf(kmsg, "Attempting %s %s mount %s /mnt.\n",
	 param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "%s mounted successfully.\n", param[iroot].v);

 fprintf(kmsg, "Attempting mount --move /dev /mnt/dev\n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount --move /proc /mnt/proc\n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Beginning switch root procedure.\n");
 fprintf(kmsg, "Attempting chdir from / to /mnt\n");
 if( chdir("/mnt") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting mount-move . to /\n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  fprintf(kmsg, "time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chroot to .\n");
 if( chroot(".") != 0 ) {
  fprintf(kmsg, "time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 fprintf(kmsg, "Attempting chdir to /\n");
 if( chdir("/") != 0 ) {
  fprintf(kmsg, "time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 fprintf(kmsg, "Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].v != NULL ) {
   fprintf(kmsg, "Console redirection to device %s requested.\n", param[iconsole].v);
   fprintf(kmsg, "Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
   close(0);
   /* expect only basename of device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   open(param[iconsole].v, O_RDWR);
   dup2(0, 1);
   dup2(0, 2);
   chdir("/");
 }

 fprintf(kmsg, "Execing: \"%s %s\" to boot mounted root system.\n",
	 param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 fclose(kmsg);
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  kmsg = fopen("/dev/kmsg", "w");
  fprintf(kmsg, "time to panic: execl: %s\n", strerror(errno));
  fclose(kmsg);
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial graphics mode, the interface is a little different than in the normal graphical SQL-based mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.com used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>06380536e60bdc978c2803cb8b50dbe78ca2dba4</sha1>
  </revision>
  <revision>
    <id>751</id>
    <parentid>750</parentid>
    <timestamp>2012-08-24T11:42:16Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25559" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.8"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_LOCAL 1

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

void printk(char *fmt, ...) {
  FILE* f;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /***** variables
  *
  */
 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or local */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /***** program
  *
  */
 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc before dev since some devices
  * symlink into proc */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs as expected by an init program
  * and maybe required to mount zfs */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }
 /* it is assumed that all required devices are in devtmpfs
  * and if not, there will be boot problems
  *
  * if you need a more complex device setup, then you might need
  * udevd and run it with a larger full initrd package from your distro
  */

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_LOCAL; /* value src: local */
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT; /* value src: default */
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = "";
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness
  */

 /* param[iroot]: nothing to do, if user put bad device in then we fail */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 /* required, so should have value */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);
   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }


 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");

 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_LOCAL ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial graphics mode, the interface is a little different than in the normal graphical SQL-based mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.com used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>74622532a00318a0c865955f0d196a25d04d8ffe</sha1>
  </revision>
  <revision>
    <id>752</id>
    <parentid>751</parentid>
    <timestamp>2012-08-25T15:02:03Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28427" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate installation from the fully modular and working system. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.9"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = "";
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific informative checks */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink("/init") != 0 ) printk("unlink %s: %s\n", "/init", strerror(errno));
 else printk("/init %s", "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root ro rootfstype=zfs rootwait "
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.com used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>49f20524bd97095566011150cf01077535bb96ef</sha1>
  </revision>
  <revision>
    <id>779</id>
    <parentid>752</parentid>
    <timestamp>2012-09-03T18:33:43Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28438" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command
zpool set bootfs=zfs-root zfs-root
# this may help, but not really sure

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.10rc1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = "";
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific informative checks */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>c9beae8be04d64677d1e75ee24ac3b06e3dd9f11</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>Talk:Install Slackware Using A USB Flash Drive</title>
  <ns>1</ns>
  <id>292</id>
  <revision>
    <id>753</id>
    <timestamp>2012-08-28T06:50:37Z</timestamp>
    <contributor>
      <username>Sapta</username>
      <id>301</id>
    </contributor>
    <comment>Created page with "Hi,  I'm new to slackware. I tried installing it as given in the wiki page. But ran into trouble in the last stage.  First of all, fdisk -l shows sdb - 16 gb(usb size), sdb1 (..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1037" xml:space="preserve">Hi,

I'm new to slackware. I tried installing it as given in the wiki page. But ran into trouble in the last stage. 
First of all, fdisk -l shows sdb - 16 gb(usb size), sdb1 (4 gb) and sdb1p1 (similar size). What is sdb1p1? Which one do I mount? I decided to mount sdb1.

After mounting and running setup, I set up the targets \home, \usr etc. Then it says it has detected FAT/NTFS filesystem (the usb in all probability) and if I want to add that to fstab. I tried different things here. Since the usb is already mounted, I first tried answering no and going to install. Later I tried mounting sdb1 in flash at this step again and then running install. In both cases, when I select "install from hard disk partition" and select source partition as "/dev/sdb1" and then source path as "/slackware" or "/flash/slackware" or "slackware", it says "error mounting, should I continue". I tried using install option "pre-mounted directory" and gave "/flash/slackware" as the directory but it couldn't find the directory. What am I doing wrong?</text>
    <sha1>e58af921ae4d1cb842400f92373e4bbc7966acb6</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>X Windows: Remote X to Windows with Xming</title>
  <ns>0</ns>
  <id>293</id>
  <revision>
    <id>754</id>
    <timestamp>2012-08-29T15:12:05Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>CREATED!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1766" xml:space="preserve">1) Install Xming '''and''' Xming-fonts
  * Download from sourceforge.net/projects/xming[http://sourceforge.net/projects/xming/]

2) Add the Linux machine's DNS name(s) and IP address to the C:\Program Files\xming\X0.hosts file. File should contain:
    LinuxBox.mydomain.com
    LinuxBox
    192.168.1.25

3) Start Xming on your Windows machine '''(NOT XLaunch)'''

4) Start the connection:
Connect to the Linux machine via ssh/telnet/rlogin/whatever and run:
     DISPLAY=WINDOWS_IP:0;export DISPLAY;APPLICATION_YOU_WANT_TO_RUN
     
     EXAMPLE: DISPLAY=192.168.1.10:0;export DISPLAY;xterm


Minimize the telnet session, do not close it.  If you close it, your OV connection will close.

----

'''PROBLEMS'''

'''PROBLEM:''' "Xlib: connection to YOUR_IP refused by server"&lt;br&gt;
'''FIX:''' Check the Xming log, it probably contains "Xming.exe: client 4 rejected from IP YOUR_IP". If so, 
* close Xming
* Make sure that the DNS names and/or IPs are in the C:\Program Files\xming\X0.hosts file
* restart Xming
'''FIX2:''' If problem is not fixed, restart Xming with the -ac option.&lt;br&gt;

'''PROBLEM:''' Map starts but then I get a font error from OpenView.&lt;br&gt;
'''FIX:''' Install the Xming-fonts onto your Windows box.&lt;br&gt;

'''PROBLEM:''' When starting Xming, a Windows Security Alert pops up saying Windows Firewall has blocked this program.&lt;br&gt;
'''FIX:''' Change Windows Firewall setting to allow Xming.&lt;br&gt;
'''FIX2:''' Disable Windows Firewall by going to Services, setting Windows Firewall to MANUAL START and then stop the service.&lt;br&gt;

'''PROBLEM:''' Cannot connect to Xming and I have checked all of the above.&lt;br&gt;
'''FIX:''' When starting Xming as display 0, Windows Firewall does not complain. Check to see if Windows Firewall is blocking the connection.&lt;br&gt;</text>
    <sha1>7e0be231816b95339aa1de14e80a445bf4f28855</sha1>
  </revision>
  <revision>
    <id>755</id>
    <parentid>754</parentid>
    <timestamp>2012-08-29T15:14:36Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>FIXED: typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1782" xml:space="preserve">1) Install Xming '''and''' Xming-fonts
  * Download from sourceforge.net/projects/xming[http://sourceforge.net/projects/xming/]

2) Add the Linux machine's DNS name(s) and IP address to the C:\Program Files\xming\X0.hosts file. File should contain:
    LinuxBox.mydomain.com
    LinuxBox
    192.168.1.25

3) Start Xming on your Windows machine '''(NOT XLaunch)'''

4) Start the connection:
Connect to the Linux machine via ssh/telnet/rlogin/whatever and run:
     DISPLAY=WINDOWS_IP:0;export DISPLAY;APPLICATION_YOU_WANT_TO_RUN
     
     EXAMPLE: DISPLAY=192.168.1.10:0;export DISPLAY;xterm

5) Minimize the telnet session, do not close it.  If you close it, your X connections will close.&lt;br&gt;
&lt;br&gt;
&lt;br&gt;

----

'''PROBLEMS'''

'''PROBLEM:''' "Xlib: connection to YOUR_IP refused by server"&lt;br&gt;
'''FIX:''' Check the Xming log, it probably contains "Xming.exe: client 4 rejected from IP YOUR_IP". If so, 
* close Xming
* Make sure that the DNS names and/or IPs are in the C:\Program Files\xming\X0.hosts file
* restart Xming
'''FIX2:''' If problem is not fixed, restart Xming with the -ac option.&lt;br&gt;

'''PROBLEM:''' The application starts but then I get a font error(s).&lt;br&gt;
'''FIX:''' Install the Xming-fonts onto your Windows box.&lt;br&gt;

'''PROBLEM:''' When starting Xming, a Windows Security Alert pops up saying Windows Firewall has blocked this program.&lt;br&gt;
'''FIX:''' Change Windows Firewall setting to allow Xming.&lt;br&gt;
'''FIX2:''' Disable Windows Firewall by going to Services, setting Windows Firewall to MANUAL START and then stop the service.&lt;br&gt;

'''PROBLEM:''' Cannot connect to Xming and I have checked all of the above.&lt;br&gt;
'''FIX:''' When starting Xming as display 0, Windows Firewall does not complain. Check to see if Windows Firewall is blocking the connection.&lt;br&gt;</text>
    <sha1>bb4a9fb611a917dd06f27ccdbe27673f1773255a</sha1>
  </revision>
  <revision>
    <id>756</id>
    <parentid>755</parentid>
    <timestamp>2012-08-29T15:16:15Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>ADDED: Category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1808" xml:space="preserve">1) Install Xming '''and''' Xming-fonts
  * Download from sourceforge.net/projects/xming[http://sourceforge.net/projects/xming/]

2) Add the Linux machine's DNS name(s) and IP address to the C:\Program Files\xming\X0.hosts file. File should contain:
    LinuxBox.mydomain.com
    LinuxBox
    192.168.1.25

3) Start Xming on your Windows machine '''(NOT XLaunch)'''

4) Start the connection:
Connect to the Linux machine via ssh/telnet/rlogin/whatever and run:
     DISPLAY=WINDOWS_IP:0;export DISPLAY;APPLICATION_YOU_WANT_TO_RUN
     
     EXAMPLE: DISPLAY=192.168.1.10:0;export DISPLAY;xterm

5) Minimize the telnet session, do not close it.  If you close it, your X connections will close.&lt;br&gt;
&lt;br&gt;
&lt;br&gt;

----

'''PROBLEMS'''

'''PROBLEM:''' "Xlib: connection to YOUR_IP refused by server"&lt;br&gt;
'''FIX:''' Check the Xming log, it probably contains "Xming.exe: client 4 rejected from IP YOUR_IP". If so, 
* close Xming
* Make sure that the DNS names and/or IPs are in the C:\Program Files\xming\X0.hosts file
* restart Xming
'''FIX2:''' If problem is not fixed, restart Xming with the -ac option.&lt;br&gt;

'''PROBLEM:''' The application starts but then I get a font error(s).&lt;br&gt;
'''FIX:''' Install the Xming-fonts onto your Windows box.&lt;br&gt;

'''PROBLEM:''' When starting Xming, a Windows Security Alert pops up saying Windows Firewall has blocked this program.&lt;br&gt;
'''FIX:''' Change Windows Firewall setting to allow Xming.&lt;br&gt;
'''FIX2:''' Disable Windows Firewall by going to Services, setting Windows Firewall to MANUAL START and then stop the service.&lt;br&gt;

'''PROBLEM:''' Cannot connect to Xming and I have checked all of the above.&lt;br&gt;
'''FIX:''' When starting Xming as display 0, Windows Firewall does not complain. Check to see if Windows Firewall is blocking the connection.&lt;br&gt;


[[Category:Tutorials]]</text>
    <sha1>53be366e3535fee125d6ce95638423c824b47d79</sha1>
  </revision>
  <revision>
    <id>767</id>
    <parentid>756</parentid>
    <timestamp>2012-08-30T13:26:13Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>ADDED: Remote X over SSH</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2856" xml:space="preserve">===Plain Ol' Vanilla Remote X Session===

1) Install Xming '''and''' Xming-fonts
  * Download from sourceforge.net/projects/xming[http://sourceforge.net/projects/xming/]

2) Add the Linux machine's DNS name(s) and IP address to the C:\Program Files\xming\X0.hosts file. File should contain:
    LinuxBox.mydomain.com
    LinuxBox
    192.168.1.25

3) Start Xming on your Windows machine '''(NOT XLaunch)'''

4) Start the connection:
Connect to the Linux machine via ssh/telnet/rlogin/whatever and run:
     DISPLAY=WINDOWS_IP:0;export DISPLAY;APPLICATION_YOU_WANT_TO_RUN
     
     EXAMPLE: DISPLAY=192.168.1.10:0;export DISPLAY;xterm

5) Minimize the telnet session, do not close it.  If you close it, your X connections will close.&lt;br&gt;
&lt;br&gt;
&lt;br&gt;


----

===Remote X11 Over SSH===

1) Install Xming '''and''' Xming-fonts
  * Download from sourceforge.net/projects/xming[http://sourceforge.net/projects/xming/]

2) Add the Linux machine's DNS name(s) and IP address to the C:\Program Files\xming\X0.hosts file. File should contain:
    LinuxBox.mydomain.com
    LinuxBox
    192.168.1.25

3) Start Xming on your Windows machine '''(NOT XLaunch)'''

4) Install Putty (if it's not already installed).

   * Download from www.chiark.greenend.org.uk/~sgtatham/putty/

5) Open putty and fill in the “Host Name” box.

6) Ensure that SSH is checked.

7) Under Category &gt; Connection &gt; SSH &gt; X11 check the “Enable X11 forwarding” box.

8) Click the “Open” button to start the connection.

9) Log into the remote machine as you would do in a normal SSH session.

10) Start the X application from the command line, a window should open on your local machine with the application.

(It's a regular SSH session with putty but with X11 forwarding enabled.)

----

===PROBLEMS===

'''PROBLEM:''' "Xlib: connection to YOUR_IP refused by server"&lt;br&gt;
'''FIX:''' Check the Xming log, it probably contains "Xming.exe: client 4 rejected from IP YOUR_IP". If so, 
* close Xming
* Make sure that the DNS names and/or IPs are in the C:\Program Files\xming\X0.hosts file
* restart Xming
'''FIX2:''' If problem is not fixed, restart Xming with the -ac option.&lt;br&gt;

'''PROBLEM:''' The application starts but then I get a font error(s).&lt;br&gt;
'''FIX:''' Install the Xming-fonts onto your Windows box.&lt;br&gt;

'''PROBLEM:''' When starting Xming, a Windows Security Alert pops up saying Windows Firewall has blocked this program.&lt;br&gt;
'''FIX:''' Change Windows Firewall setting to allow Xming.&lt;br&gt;
'''FIX2:''' Disable Windows Firewall by going to Services, setting Windows Firewall to MANUAL START and then stop the service.&lt;br&gt;

'''PROBLEM:''' Cannot connect to Xming and I have checked all of the above.&lt;br&gt;
'''FIX:''' When starting Xming as display 0, Windows Firewall does not complain. Check to see if Windows Firewall is blocking the connection.&lt;br&gt;

[[Category:Tutorials]]</text>
    <sha1>fecd269b5f8f1214c862a96fd7ffa9379ac1edc9</sha1>
  </revision>
  <revision>
    <id>768</id>
    <parentid>767</parentid>
    <timestamp>2012-08-30T13:40:57Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>ADDED: Enable X11Forwarding to sshd_conf</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3251" xml:space="preserve">===Plain Ol' Vanilla Remote X Session===

1) Install Xming '''and''' Xming-fonts
  * Download from sourceforge.net/projects/xming[http://sourceforge.net/projects/xming/]

2) Add the Linux machine's DNS name(s) and IP address to the C:\Program Files\xming\X0.hosts file. File should contain:
    LinuxBox.mydomain.com
    LinuxBox
    192.168.1.25

3) Start Xming on your Windows machine '''(NOT XLaunch)'''

4) Start the connection:
Connect to the Linux machine via ssh/telnet/rlogin/whatever and run:
     DISPLAY=WINDOWS_IP:0;export DISPLAY;APPLICATION_YOU_WANT_TO_RUN &amp;
     
     EXAMPLE: DISPLAY=192.168.1.10:0;export DISPLAY;xterm &amp;

5) Minimize the SSH/telnet session, do not close it.  If you close it, your X connections will close.&lt;br&gt;
&lt;br&gt;
&lt;br&gt;


----

===Remote X11 Over SSH===
'''On the remote machine (Linux):'''&lt;br&gt;
1) Ensure that X11Forwarding is enabled in /etc/ssh/sshd_conf on the remote machine.

'''On the local machine (Windows):'''&lt;br&gt;
2) Install Xming '''and''' Xming-fonts
  * Download from sourceforge.net/projects/xming[http://sourceforge.net/projects/xming/]

3) Add the Linux machine's DNS name(s) and IP address to the C:\Program Files\xming\X0.hosts file. File should contain:
    LinuxBox.mydomain.com
    LinuxBox
    192.168.1.25

4) Start Xming on your Windows machine '''(NOT XLaunch)'''

5) Install Putty (if it's not already installed) onto your Windows machine.

   * Download from www.chiark.greenend.org.uk/~sgtatham/putty/[http://www.chiark.greenend.org.uk/~sgtatham/putty/]

6) Open putty and fill in the “Host Name” box.

7) Ensure that SSH is checked and that the port is correct (probably 22).

8) Under Category &gt; Connection &gt; SSH &gt; X11 check the “Enable X11 forwarding” box.

9) Click the “Open” button to start the connection.

10) Log into the remote machine as you would do in a normal SSH session.

11) Start the X application from the command line, a window should open on your local machine with the application.

12) Minimize the SSH session, do not close it.  If you close it, your X connections will close.

(It's a regular SSH session with putty but with X11 forwarding enabled.)

----

===PROBLEMS===

'''PROBLEM:''' "Xlib: connection to YOUR_IP refused by server"&lt;br&gt;
'''FIX:''' Check the Xming log, it probably contains "Xming.exe: client 4 rejected from IP YOUR_IP". If so, 
* close Xming
* Make sure that the DNS names and/or IPs are in the C:\Program Files\xming\X0.hosts file
* restart Xming
'''FIX2:''' If problem is not fixed, restart Xming with the -ac option.&lt;br&gt;

'''PROBLEM:''' The application starts but then I get a font error(s).&lt;br&gt;
'''FIX:''' Install the Xming-fonts onto your Windows box.&lt;br&gt;

'''PROBLEM:''' When starting Xming, a Windows Security Alert pops up saying Windows Firewall has blocked this program.&lt;br&gt;
'''FIX:''' Change Windows Firewall setting to allow Xming.&lt;br&gt;
'''FIX2:''' Disable Windows Firewall by going to Services, setting Windows Firewall to MANUAL START and then stop the service.&lt;br&gt;

'''PROBLEM:''' Cannot connect to Xming and I have checked all of the above.&lt;br&gt;
'''FIX:''' When starting Xming as display 0, Windows Firewall does not complain. Check to see if Windows Firewall is blocking the connection.&lt;br&gt;

[[Category:Tutorials]]</text>
    <sha1>fa1e51c63492a43c790198d98c1d625f663c57fe</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>DHCP Server: DNSMasq</title>
  <ns>0</ns>
  <id>294</id>
  <revision>
    <id>757</id>
    <timestamp>2012-08-29T16:07:31Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>CREATED!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1139" xml:space="preserve">Written from a Slackware 13.37 perspective.

To set up a DHCP server you can use the dchp package that is included with Slackware OR you can do it the easier way and use DNSMasq (also included with Slackware).

'''Assuming that you do not have DNSMasq installed'''

1) Install the official dnsmasq Slackware package either by pkgtool oe slackpkg.

2) Make DNSMasq start on boot:

     CHMOD 755 /etc/rc.d/rc.dnsmasq


At this point you will have a really cool little DNS on your box...

'''If you already had DNSMasq running on your box, start here'''

1) edit the /etc/dnsmasq.conf file:

     CHANGE: #dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
     TO: dhcp-range=192.168.1.200,192.168.1.239,12h  (using your correct IP range)

2) start/restart DNSMasq

     /etc/rc.d/rc.dnsmasq restart

You should now have a working DCHP server.

----
'''Persistent IPs'''

To assign IPs based on a device's MAC address, edit /etc/dnsmasq.conf and add the following line for every device (using the correct MAC and IP of course):

     dhcp-host=11:22:33:44:55:66,192.168.1.61

'''NOTE:''' The IP address should be OUTSIDE the DHCP pool.</text>
    <sha1>5c7c0248f48f15326855a44a3e7cb8b18f3665f8</sha1>
  </revision>
  <revision>
    <id>758</id>
    <parentid>757</parentid>
    <timestamp>2012-08-29T16:08:37Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>ADDED: Category</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1165" xml:space="preserve">Written from a Slackware 13.37 perspective.

To set up a DHCP server you can use the dchp package that is included with Slackware OR you can do it the easier way and use DNSMasq (also included with Slackware).

'''Assuming that you do not have DNSMasq installed'''

1) Install the official dnsmasq Slackware package either by pkgtool oe slackpkg.

2) Make DNSMasq start on boot:

     CHMOD 755 /etc/rc.d/rc.dnsmasq


At this point you will have a really cool little DNS on your box...

'''If you already had DNSMasq running on your box, start here'''

1) edit the /etc/dnsmasq.conf file:

     CHANGE: #dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
     TO: dhcp-range=192.168.1.200,192.168.1.239,12h  (using your correct IP range)

2) start/restart DNSMasq

     /etc/rc.d/rc.dnsmasq restart

You should now have a working DCHP server.

----
'''Persistent IPs'''

To assign IPs based on a device's MAC address, edit /etc/dnsmasq.conf and add the following line for every device (using the correct MAC and IP of course):

     dhcp-host=11:22:33:44:55:66,192.168.1.61

'''NOTE:''' The IP address should be OUTSIDE the DHCP pool.


[[Category: Tutorials]]</text>
    <sha1>9829dc95f23aec296fc8a935713fc5bcb63d7eab</sha1>
  </revision>
  <revision>
    <id>760</id>
    <parentid>758</parentid>
    <timestamp>2012-08-29T16:18:08Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>FIXED: typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1362" xml:space="preserve">Written from a Slackware 13.37 perspective.

To set up a DHCP server you can use the dchp package (that is included with Slackware)&lt;br&gt;
'''or'''&lt;br&gt;
you can do it the easier way and use DNSMasq (also included with Slackware).

'''Assuming that you do not have DNSMasq installed'''

1) Install the official dnsmasq Slackware package either by pkgtool or slackpkg.

2) Make DNSMasq start on boot:

     CHMOD 755 /etc/rc.d/rc.dnsmasq


At this point you will have a really cool little DNS on your box...

'''If you already had DNSMasq running on your box, start here'''

1) edit the /etc/dnsmasq.conf file:

     CHANGE: #dhcp-range=192.168.0.50,192.168.0.150,255.255.255.0,12h
     TO: dhcp-range=1ST_POOL_IP,LAST_POOL_IP,12h  (using your correct IP range)

1a) If your DNSMasq box isn't also your gateway router, tell your DHCP clients who is the default gateway:

     CHANGE: #dhcp-option=3,1.2.3.4
     TO: dhcp-option=3,YOUR_GATEWAY_IP

2) start/restart DNSMasq

     /etc/rc.d/rc.dnsmasq restart

You should now have a working DCHP server.

----
'''Persistent IPs'''

To assign IPs based on a device's MAC address, edit /etc/dnsmasq.conf and add the following line for every device (using the correct MAC and IP of course):

     dhcp-host=11:22:33:44:55:66,192.168.1.61

'''NOTE:''' The IP address should be OUTSIDE the DHCP pool.


[[Category: Tutorials]]</text>
    <sha1>8803ce1a95b81577985f3119f0dcbd5e32e530d1</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>DHCP Server: dhcpd</title>
  <ns>0</ns>
  <id>295</id>
  <revision>
    <id>759</id>
    <timestamp>2012-08-29T16:11:03Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>CREATED to match DCHP Server: DNSMasq</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="87" xml:space="preserve">NEEDS TO BE CREATED

You can look at [[DHCP Server: DNSMasq]]


[[Category: Tutorials]]</text>
    <sha1>a1aa167491f628128c0f524ac3a79656d4487744</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>X Windows: Remote X to Linux</title>
  <ns>0</ns>
  <id>296</id>
  <revision>
    <id>761</id>
    <timestamp>2012-08-29T19:25:29Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>CREATED!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1011" xml:space="preserve">'''NOTE:''' in the X11 world, the '''SERVER machine''' is the one listening for a connection (your desktop).&lt;br&gt;
'''NOTE:''' The '''CLIENT machine''' is the one initiating the connection (the remote machine).&lt;br&gt;
I know, it sounds backwards but, it is actually correct if you understand the X11 connection.&lt;br&gt;

----

1) Tell your X11 Server Linux box (your desktop) to accept X11 connections from the Client machines.&lt;br&gt;
* If it's a one time connection, just run the following from the command line&lt;br&gt;
or&lt;br&gt;
* You can add the following to .bashrc or .profile to make it permenant&lt;br&gt;

     xhost +144.45.254.150

2) Start the connection from the Client Linux machine (the remote machine)- Connect to the remote Linux machine via ssh/telnet/rlogin/whatever and run:

      DISPLAY=X11_SERVER_IP:0;export DISPLAY;APPLICATION_YOU_WANT_TO_RUN &amp;
      
      '''EXAMPLE:''' DISPLAY=192.168.1.10:0;export DISPLAY;xterm &amp;
      
      '''REMEMBER:''' ''The X11 server is your desktop.''


[[Category: Tutorials]]</text>
    <sha1>09cbe1e84dafe4d1775f7fa9d5c66f4d773cb8ba</sha1>
  </revision>
  <revision>
    <id>766</id>
    <parentid>761</parentid>
    <timestamp>2012-08-30T12:59:00Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>ADDED: X11 over SSH</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1845" xml:space="preserve">'''NOTE:''' In the X11 world, the '''SERVER machine''' is the one listening for a connection (the local machine (your desktop)).&lt;br&gt;
'''NOTE:''' The '''CLIENT machine''' is the one initiating the connection (the remote machine).&lt;br&gt;
I know, it sounds backwards but, it is actually correct if you understand the X11 connection.&lt;br&gt;


----
===Plain Ol' Vanilla X11 Remote Connection===

1) Tell your X11 server machine (your desktop) to accept X11 connections from the client machine.&lt;br&gt;
* If it's a one time connection, just run the following from the command line&lt;br&gt;
or&lt;br&gt;
* You can add the following to .bashrc or .profile to make it permanent&lt;br&gt;

     xhost +X11_SERVER_IP  (the '''remote''' machine)
     
     '''EXAMPLE:''' xhost +192.168.1.45

2) Start the connection from the Client Linux machine (the remote machine)- Connect to the remote Linux machine via ssh/telnet/rlogin/whatever and run:

      DISPLAY=X11_SERVER_IP:0;export DISPLAY;APPLICATION_YOU_WANT_TO_RUN &amp;
      
      '''EXAMPLE:''' DISPLAY=192.168.1.10:0;export DISPLAY;xterm &amp;
      
      '''REMEMBER:''' ''The X11 server is your desktop.''

----
===Remote X11 Over SSH===


1) ensure that X11Forwarding is enabled in /etc/ssh/ssh'''d'''_conf on the '''remote''' machine.

2) ensure that X11Forwarding is enabled in /etc/ssh/ssh_conf on the '''local''' machine.

3) open an X11 forwarded ssh session '''from the local machine to the remote machine''' (opposite of what you do for a 'vanilla' remote X connection):

     ssh -X USER@REMOTE_MACHINE 
     XAPPLICATION_YOU_WANT_TO_RUN
     
     '''EXAMPLE:'''
     ssh -X joe@192.168.1.45
     xterm &amp;

'''PROBLEMS'''&lt;br&gt;
'''PROBLEM:''' ssh connection is complaining about an “Invalid MIT-MAGIC-COOKIE”.&lt;br&gt;
'''FIX:''' start a less secure ssh session:

     ssh -Y USER@REMOTE_MACHINE


[[Category: Tutorials]]</text>
    <sha1>c2ae0e4b2885f20ce513da039dfcbac4a0e176ec</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>Perl Modules</title>
  <ns>0</ns>
  <id>129</id>
  <revision>
    <id>762</id>
    <parentid>155</parentid>
    <timestamp>2012-08-29T19:41:55Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>I originally created this page and things have changed slightly...</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1492" xml:space="preserve">[[Category:Tutorials]]
==Getting To The CPAN Prompt==
To administer your Perl modules you must use the CPAN prompt. To get to the CPAN prompt, &lt;b&gt;as root&lt;/b&gt; type:

::&lt;code&gt;perl -MCPAN -e shell&lt;/code&gt;

If this is the first time that you have entered the CPAN shell, you will be asked some set-up questions that will allow the shell to access CPAN's servers to get modules.  Just read the questions and answer them.

If you ever need to re-run the set-up again, enter the CPAN shell and then type:

::&lt;code&gt;o conf init&lt;/code&gt;


==Listing The Installed Modules==

'''Easy way'''
     instmodsh
     l (L)


'''Hard way'''
use this Perl program:

     #!/usr/bin/perl
     use ExtUtils::Installed;
     my $instmod = ExtUtils::Installed-&gt;new();
     foreach my $module ($instmod-&gt;modules())
     {
     my $version = $instmod-&gt;version($module) || "???";
     print "$module -- $version\n";
     }


==Installing New Modules==
From the CPAN shell prompt, type:

     install &amp;lt;Some::Module&amp;gt;


==Removing Modules==

A clean way is by using this Perl program:

     #!/usr/bin/perl -w
     use ExtUtils::Packlist;
     use ExtUtils::Installed;
     $ARGV[0] or die "Usage: $0 Module::Name\n";
     my $mod = $ARGV[0];
     my $inst = ExtUtils::Installed-&gt;new();
     foreach my $item (sort($inst-&gt;files($mod)))
     {
     print "removing $item\n";
     unlink $item;
     }
     my $packfile = $inst-&gt;packlist($mod)-&gt;packlist_file();
     print "removing $packfile\n";
     unlink $packfile;</text>
    <sha1>7109e17827390ccc6d5783d7824b90cba0e1b669</sha1>
  </revision>
  <revision>
    <id>763</id>
    <parentid>762</parentid>
    <timestamp>2012-08-29T19:43:08Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>/* Getting To The CPAN Prompt */  REMOVED perl MCPAN and ADDED cpan</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1475" xml:space="preserve">[[Category:Tutorials]]
==Getting To The CPAN Prompt==
To administer your Perl modules you must use the CPAN prompt. To get to the CPAN prompt, &lt;b&gt;as root&lt;/b&gt; type:

::&lt;code&gt;cpan&lt;/code&gt;

If this is the first time that you have entered the CPAN shell, you will be asked some set-up questions that will allow the shell to access CPAN's servers to get modules.  Just read the questions and answer them.

If you ever need to re-run the set-up again, enter the CPAN shell and then type:

::&lt;code&gt;o conf init&lt;/code&gt;

==Listing The Installed Modules==

'''Easy way'''
     instmodsh
     l (L)


'''Hard way'''
use this Perl program:

     #!/usr/bin/perl
     use ExtUtils::Installed;
     my $instmod = ExtUtils::Installed-&gt;new();
     foreach my $module ($instmod-&gt;modules())
     {
     my $version = $instmod-&gt;version($module) || "???";
     print "$module -- $version\n";
     }


==Installing New Modules==
From the CPAN shell prompt, type:

     install &amp;lt;Some::Module&amp;gt;


==Removing Modules==

A clean way is by using this Perl program:

     #!/usr/bin/perl -w
     use ExtUtils::Packlist;
     use ExtUtils::Installed;
     $ARGV[0] or die "Usage: $0 Module::Name\n";
     my $mod = $ARGV[0];
     my $inst = ExtUtils::Installed-&gt;new();
     foreach my $item (sort($inst-&gt;files($mod)))
     {
     print "removing $item\n";
     unlink $item;
     }
     my $packfile = $inst-&gt;packlist($mod)-&gt;packlist_file();
     print "removing $packfile\n";
     unlink $packfile;</text>
    <sha1>7c759926b25e3032bcdf2f6af7c7509b87199a1d</sha1>
  </revision>
  <revision>
    <id>764</id>
    <parentid>763</parentid>
    <timestamp>2012-08-29T19:46:23Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>ADDED: upgrade modules</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1593" xml:space="preserve">[[Category:Tutorials]]
==Getting To The CPAN Prompt==
To administer your Perl modules you must use the CPAN prompt. To get to the CPAN prompt, &lt;b&gt;as root&lt;/b&gt; type:

::&lt;code&gt;cpan&lt;/code&gt;

If this is the first time that you have entered the CPAN shell, you will be asked some set-up questions that will allow the shell to access CPAN's servers to get modules.  Just read the questions and answer them.

If you ever need to re-run the set-up again, enter the CPAN shell and then type:

::&lt;code&gt;o conf init&lt;/code&gt;

==Listing The Installed Modules==

'''Easy way'''
     instmodsh
     l (L)


'''Hard way'''
use this Perl program:

     #!/usr/bin/perl
     use ExtUtils::Installed;
     my $instmod = ExtUtils::Installed-&gt;new();
     foreach my $module ($instmod-&gt;modules())
     {
     my $version = $instmod-&gt;version($module) || "???";
     print "$module -- $version\n";
     }


==Installing New Modules==
From the CPAN shell prompt, type:

     install &amp;lt;Some::Module&amp;gt;


==Removing Modules==

A clean way is by using this Perl program:

     #!/usr/bin/perl -w
     use ExtUtils::Packlist;
     use ExtUtils::Installed;
     $ARGV[0] or die "Usage: $0 Module::Name\n";
     my $mod = $ARGV[0];
     my $inst = ExtUtils::Installed-&gt;new();
     foreach my $item (sort($inst-&gt;files($mod)))
     {
     print "removing $item\n";
     unlink $item;
     }
     my $packfile = $inst-&gt;packlist($mod)-&gt;packlist_file();
     print "removing $packfile\n";
     unlink $packfile;


==Upgrade Modules==

In the cpan prompt, type:

     upgrade MODULE::NAME to upgrade an individual module

'''or'''</text>
    <sha1>f1e89d29c3f2451d47e9575b90e1639e26fafb5c</sha1>
  </revision>
  <revision>
    <id>765</id>
    <parentid>764</parentid>
    <timestamp>2012-08-29T19:48:38Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>ADDED: upgrade modules</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1672" xml:space="preserve">[[Category:Tutorials]]
==Getting To The CPAN Prompt==
To administer your Perl modules you must use the CPAN prompt. To get to the CPAN prompt, &lt;b&gt;as root&lt;/b&gt; type:

::&lt;code&gt;cpan&lt;/code&gt;

If this is the first time that you have entered the CPAN shell, you will be asked some set-up questions that will allow the shell to access CPAN's servers to get modules.  Just read the questions and answer them.

If you ever need to re-run the set-up again, enter the CPAN shell and then type:

::&lt;code&gt;o conf init&lt;/code&gt;

==Listing The Installed Modules==
From the BASH prompt:

'''Easy way'''
     instmodsh
     l (L)


'''Hard way'''
use this Perl program:

     #!/usr/bin/perl
     use ExtUtils::Installed;
     my $instmod = ExtUtils::Installed-&gt;new();
     foreach my $module ($instmod-&gt;modules())
     {
     my $version = $instmod-&gt;version($module) || "???";
     print "$module -- $version\n";
     }


==Installing New Modules==
From the CPAN prompt, type:

     install &amp;lt;Some::Module&amp;gt;


==Removing Modules==

A clean way is by using this Perl program from the BASH prompt:

     #!/usr/bin/perl -w
     use ExtUtils::Packlist;
     use ExtUtils::Installed;
     $ARGV[0] or die "Usage: $0 Module::Name\n";
     my $mod = $ARGV[0];
     my $inst = ExtUtils::Installed-&gt;new();
     foreach my $item (sort($inst-&gt;files($mod)))
     {
     print "removing $item\n";
     unlink $item;
     }
     my $packfile = $inst-&gt;packlist($mod)-&gt;packlist_file();
     print "removing $packfile\n";
     unlink $packfile;


==Upgrade Modules==
From the CPAN prompt, type:

     upgrade MODULE::NAME (to upgrade an individual module)

'''or'''

     upgrade (to upgrade ALL modules)</text>
    <sha1>cad2d5601695462ad5bbbfa71233ea74b37c75d7</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>PPTP (Poptop)</title>
  <ns>0</ns>
  <id>297</id>
  <revision>
    <id>769</id>
    <timestamp>2012-08-30T14:38:02Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Moved from Pptp</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3300" xml:space="preserve">[[Category:Server]]
[[Category:Networking]]
[[Category:Tutorials]]

==(Poptop) pptpd Server Setup==

Here's what I did to get Poptop pptpd (1.3.4) running on my Slackware (13.37) box.

 1) Install the official Slackware ppp package using pkgtool or slackpkg.
 
 2) Install the ppptpd package from Slackbuilds.org using sbopkg.
 	***NOTE: The package name is NOT Poptop, it's pptpd***
 
 3) Edit /etc/pptpd.conf
 
 	ADD:
 		localip 10.7.0.1
 		remoteip 10.7.0.2-50
 	CHANGE:
 		option /etc/ppp/options.pptpd -&gt; option /etc/ppp/options
 
 4) Edit /etc/ppp/options
 	HERE IS A GOTCHA- The official Slackware ppp package (at the time of this writing) contains an error in the options
 	file. The pppd binary was compiled to look for the new ms-dns parameter but the option file has the old dns-addr
 	parameter.
 
 	CHANGE:
 	# dns-addr 192.168.1.1 -&gt; ms-dns 8.8.8.8 (or whatever your dns server is)
 
 5) Edit the /etc/ppp/chap-secrets file.
 	For some reason, the default Slackware package has 4 example entries in it that are not commented (jacco,*,sam,*)
 	delete these.  You don't want jacco or sam to have a free connection into your box...
 
 	ADD: one entry for each user you want to allow access.
 	Format is: CLIENT [tab] SERVER [tab] PASSWORD [tab] IP ADDRESS
 	Mine looks like this:
 
 	bob	*	"BobsPasswordIsStrong"	*
 	sue	*	"FluffyBunnies92"	*
 
 6) Finally to start pptpd, normally you would just execute 'pptpd &amp;' but being that I'm a good Slacker, I wrote an
 rc.pptpd script.
 	Create /etc/rc.d/rc.pptpd
 	contents:
 		#!/bin/sh
 		#
 		# /etc/rc.d/rc.pptpd
 		#
 		# Start/stop/restart the pptpd server.
 		#
 		# To make PopTop start automatically at boot, make this
 		# file executable:  chmod 755 /etc/rc.d/rc.pptpd
 		#
 		
 		pptpd_start() {
 		  if [ -x /usr/sbin/pptpd ]; then
 		    echo "Starting PopTop pptpd:  /usr/sbin/pptpd server.conf"
 		    /usr/sbin/pptpd &amp;
 		  fi
 		}
 		
 		pptpd_stop() {
 		  killall pptpd
 		}
 		
 		pptpd_restart() {
 		  pptpd_stop
 		  sleep 2
 		  pptpd_start
 		}
 		
 		case "$1" in
 		'start')
 		  pptpd_start
 		  ;;
 		'stop')
 		  pptpd_stop
 		  ;;
 		'restart')
 		  pptpd_restart
 		  ;;
 		*)
 		  # Default is "start", for backwards compatibility with previous
 		  # Slackware versions.  This may change to a 'usage' error someday.
 		  pptpd_start
 		esac
 
 
 7) Make it executable (and autobootable on start up)
 
 	chmod 755 /etc/rc.d/rc.pptpd
 
 To start it manually- /etc/rc.d/rc.pptpd start
 
 To be useful you next need to configure your firewall to forward and masquerade traffic from the vpn out to
 the world...
 
 8) Edit/create: /etc/rc.d/rc.firewall
 
 	ADD:
 		iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
 		iptables -A FORWARD -i ppp+ -j ACCEPT
 		iptables -A FORWARD -o ppp+ -j ACCEPT
 		iptables -A FORWARD -j ACCEPT
 		iptables -t nat -A POSTROUTING -s 10.7.0.0/24 -o ppp+ -j MASQUERADE
 
 9) Make it executable
 
 	chmod 755 /etc/rc.d/rc.firewall
 
 10) Flush the old firewall rules (forgetting to do this caused me all sorts of grief (Thanks mancha))
 
 	iptables -F
 
 11) Execute the new firewall rules
 
 	/etc/rc.d/rc.firewall
 
 If you and I haven't made any mistakes, you should now have pptp (server) and router working on your box.

==pptp Client Setup==

Needs to be added.</text>
    <sha1>a28dd0fdb696a708217fbb99c929d401a1f060b9</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>Pptp</title>
  <ns>0</ns>
  <id>285</id>
  <revision>
    <id>770</id>
    <parentid>725</parentid>
    <timestamp>2012-08-30T14:38:48Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Moved to PPPTP (Poptop)</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>NTPD</title>
  <ns>0</ns>
  <id>126</id>
  <revision>
    <id>771</id>
    <parentid>149</parentid>
    <timestamp>2012-08-30T14:52:37Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Moved to NTPD</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
  <revision>
    <id>772</id>
    <parentid>771</parentid>
    <timestamp>2012-08-30T15:01:26Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Undo revision 771 by [[Special:Contributions/Arfon|Arfon]] ([[User talk:Arfon|talk]]) - Removed 2007 stuff, fixed typos</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1916" xml:space="preserve">
== Automating the time synchronization ==
You have two choices for automatic time updating, you can run ntpd all the time as a background process or you can have it run once in awhile (if you are tight on system resources).

'''Running ntpd all the time'''&lt;br&gt;
::Just enable rc.ntpd script:
::::&lt;code&gt;chmod +x /etc/rc.d/rc.ntpd&lt;/code&gt;
::After the script is enabled you probably will want ntpd to start immediately so, can either restart the system or manually start ntpd with:
::::&lt;code&gt;/etc/rc.d/rc.ntpd start&lt;/code&gt;

'''Running ntpd once in awhile'''&lt;br&gt;
::You have many choices but the two best ones are:
:::1) Set up a cron job
:::2) Set up a /etc/rc.d/rc.local entry and update the time on start-up only.
::Either way, you need to add the following commands into your cron job or rc.local script:
::::&lt;code&gt;ntpdate pool.ntp.org&lt;/code&gt; &lt;---(updates the time)
::::&lt;code&gt;hwclock --systohc&lt;/code&gt; &lt;------(saves the time to the hardware clock)
&lt;br&gt;
&lt;br&gt;

==Manually updating the time==
Issue the following commands:
::::&lt;code&gt;ntpdate pool.ntp.org&lt;/code&gt;
::::&lt;code&gt;hwclock --systohc&lt;/code&gt;
&lt;br&gt;
&lt;br&gt;

==Choosing the right time server==
On ntp.org you will find a complete list with the right time server for you.
Let's say you live in germany, then you will choose &lt;code&gt;de.pool.ntp.org&lt;/code&gt;. A complete List is available at http://support.ntp.org/bin/view/Servers/NTPPoolServers
&lt;br&gt;
&lt;br&gt;

==DST changes==
If your time is off due to DST changes, you must update the &lt;code&gt;/etc/localtime&lt;/code&gt; file.  You should be able to find a correct file on the internet and just replace the old &lt;code&gt;/etc/localtime&lt;/code&gt; file.
&lt;br&gt;
&lt;br&gt;

==PROBLEMS==
'''PROBLEM:''' "Unable to contact time server:" error with KDE's Time Control Module.&lt;br&gt;
'''FIX:''' Make sure ntpd is NOT running.  If ntpd is running, manual ntp and KDE ntp updates will return errors due to ntpd having control of the ntp port.


[[Category:Tutorials]]</text>
    <sha1>53bc989820cf8bcf52ec176733c416e6da5fae64</sha1>
  </revision>
  <revision>
    <id>773</id>
    <parentid>772</parentid>
    <timestamp>2012-08-30T15:04:19Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>Arfon moved page [[Ntpd]] to [[NTPD - temp]]: Fixing page name</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1916" xml:space="preserve">
== Automating the time synchronization ==
You have two choices for automatic time updating, you can run ntpd all the time as a background process or you can have it run once in awhile (if you are tight on system resources).

'''Running ntpd all the time'''&lt;br&gt;
::Just enable rc.ntpd script:
::::&lt;code&gt;chmod +x /etc/rc.d/rc.ntpd&lt;/code&gt;
::After the script is enabled you probably will want ntpd to start immediately so, can either restart the system or manually start ntpd with:
::::&lt;code&gt;/etc/rc.d/rc.ntpd start&lt;/code&gt;

'''Running ntpd once in awhile'''&lt;br&gt;
::You have many choices but the two best ones are:
:::1) Set up a cron job
:::2) Set up a /etc/rc.d/rc.local entry and update the time on start-up only.
::Either way, you need to add the following commands into your cron job or rc.local script:
::::&lt;code&gt;ntpdate pool.ntp.org&lt;/code&gt; &lt;---(updates the time)
::::&lt;code&gt;hwclock --systohc&lt;/code&gt; &lt;------(saves the time to the hardware clock)
&lt;br&gt;
&lt;br&gt;

==Manually updating the time==
Issue the following commands:
::::&lt;code&gt;ntpdate pool.ntp.org&lt;/code&gt;
::::&lt;code&gt;hwclock --systohc&lt;/code&gt;
&lt;br&gt;
&lt;br&gt;

==Choosing the right time server==
On ntp.org you will find a complete list with the right time server for you.
Let's say you live in germany, then you will choose &lt;code&gt;de.pool.ntp.org&lt;/code&gt;. A complete List is available at http://support.ntp.org/bin/view/Servers/NTPPoolServers
&lt;br&gt;
&lt;br&gt;

==DST changes==
If your time is off due to DST changes, you must update the &lt;code&gt;/etc/localtime&lt;/code&gt; file.  You should be able to find a correct file on the internet and just replace the old &lt;code&gt;/etc/localtime&lt;/code&gt; file.
&lt;br&gt;
&lt;br&gt;

==PROBLEMS==
'''PROBLEM:''' "Unable to contact time server:" error with KDE's Time Control Module.&lt;br&gt;
'''FIX:''' Make sure ntpd is NOT running.  If ntpd is running, manual ntp and KDE ntp updates will return errors due to ntpd having control of the ntp port.


[[Category:Tutorials]]</text>
    <sha1>53bc989820cf8bcf52ec176733c416e6da5fae64</sha1>
  </revision>
  <revision>
    <id>775</id>
    <parentid>773</parentid>
    <timestamp>2012-08-30T15:04:37Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>Arfon moved page [[NTPD - temp]] to [[NTPD]]: Fixing page name</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1916" xml:space="preserve">
== Automating the time synchronization ==
You have two choices for automatic time updating, you can run ntpd all the time as a background process or you can have it run once in awhile (if you are tight on system resources).

'''Running ntpd all the time'''&lt;br&gt;
::Just enable rc.ntpd script:
::::&lt;code&gt;chmod +x /etc/rc.d/rc.ntpd&lt;/code&gt;
::After the script is enabled you probably will want ntpd to start immediately so, can either restart the system or manually start ntpd with:
::::&lt;code&gt;/etc/rc.d/rc.ntpd start&lt;/code&gt;

'''Running ntpd once in awhile'''&lt;br&gt;
::You have many choices but the two best ones are:
:::1) Set up a cron job
:::2) Set up a /etc/rc.d/rc.local entry and update the time on start-up only.
::Either way, you need to add the following commands into your cron job or rc.local script:
::::&lt;code&gt;ntpdate pool.ntp.org&lt;/code&gt; &lt;---(updates the time)
::::&lt;code&gt;hwclock --systohc&lt;/code&gt; &lt;------(saves the time to the hardware clock)
&lt;br&gt;
&lt;br&gt;

==Manually updating the time==
Issue the following commands:
::::&lt;code&gt;ntpdate pool.ntp.org&lt;/code&gt;
::::&lt;code&gt;hwclock --systohc&lt;/code&gt;
&lt;br&gt;
&lt;br&gt;

==Choosing the right time server==
On ntp.org you will find a complete list with the right time server for you.
Let's say you live in germany, then you will choose &lt;code&gt;de.pool.ntp.org&lt;/code&gt;. A complete List is available at http://support.ntp.org/bin/view/Servers/NTPPoolServers
&lt;br&gt;
&lt;br&gt;

==DST changes==
If your time is off due to DST changes, you must update the &lt;code&gt;/etc/localtime&lt;/code&gt; file.  You should be able to find a correct file on the internet and just replace the old &lt;code&gt;/etc/localtime&lt;/code&gt; file.
&lt;br&gt;
&lt;br&gt;

==PROBLEMS==
'''PROBLEM:''' "Unable to contact time server:" error with KDE's Time Control Module.&lt;br&gt;
'''FIX:''' Make sure ntpd is NOT running.  If ntpd is running, manual ntp and KDE ntp updates will return errors due to ntpd having control of the ntp port.


[[Category:Tutorials]]</text>
    <sha1>53bc989820cf8bcf52ec176733c416e6da5fae64</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>Ntpd</title>
  <ns>0</ns>
  <id>298</id>
  <revision>
    <id>774</id>
    <timestamp>2012-08-30T15:04:19Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Arfon moved page [[Ntpd]] to [[NTPD - temp]]: Fixing page name</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="25" xml:space="preserve">#REDIRECT [[NTPD - temp]]</text>
    <sha1>491e8c735247530ec62d34ff181f2e4b450f17b8</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>NTPD - temp</title>
  <ns>0</ns>
  <id>299</id>
  <revision>
    <id>776</id>
    <timestamp>2012-08-30T15:04:37Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>Arfon moved page [[NTPD - temp]] to [[NTPD]]: Fixing page name</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="18" xml:space="preserve">#REDIRECT [[NTPD]]</text>
    <sha1>8014faa7f0f3239ddb9979a4ed92940829869303</sha1>
  </revision>
</page>
<page arvcontinue="20120818184438|733">
  <title>Network Configuration</title>
  <ns>0</ns>
  <id>300</id>
  <revision>
    <id>777</id>
    <timestamp>2012-08-30T18:38:57Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <comment>CREATED!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1236" xml:space="preserve">==See Your Current Network Configuration==

   ifconfig

   /sbin/ifconfig (if you are not root)


==Network Reconfiguration - Temporary Changes==

ifconfig is the command to make changes to your networking.

     ifconfig (shows the current interface configuration)
     
     ifconfig eth0 up (brings eth0 interface up)
     
     ifconfig eth1 down (takes eth1 interface down)
     
     ifconfig eth0 192.168.1.5 netmask 255.255.255.0 up (brings eth0 up with an IP of 192.168.1.5)
     
     ifconfig eth0:1 192.168.2.15 netmask 255.255.255.0 (adds a secondary IP address of 192.168.2.15 to eth0)


==Network Reconfiguration - Permanent Changes==
'''ETH0'''&lt;br&gt;
If you need to change your '''eth0''' configuration after an install, use netconfig

     netconfig

'''OTHER INTERFACES'''&lt;br&gt;
To reconfigure other network devices, you need to edit the /etc/rc.d/rc.inet1.conf files by hand. The file is very easy to figure out.

     vi /etc/rc.d/rc.inet1.conf


==Make changes take effect immediately==
To make the network changes immediately active:

     /etc/rc.d/rc.inet1 restart  (restarts all interfaces)
     /etc/rc.d/rc.inet1 eth0_restart  (restarts eth0)
     /etc/rc.d/rc.inet1 eth1_restart  (restarts eth1)
     ...etc...</text>
    <sha1>15fb224a6d1728e9cf308c9b33560a145c12d58e</sha1>
  </revision>
  <revision>
    <id>778</id>
    <parentid>777</parentid>
    <timestamp>2012-08-30T18:40:34Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>Forgot to add Category AGAIN!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1262" xml:space="preserve">==See Your Current Network Configuration==

   ifconfig

   /sbin/ifconfig (if you are not root)


==Network Reconfiguration - Temporary Changes==

ifconfig is the command to make changes to your networking.

     ifconfig (shows the current interface configuration)
     
     ifconfig eth0 up (brings eth0 interface up)
     
     ifconfig eth1 down (takes eth1 interface down)
     
     ifconfig eth0 192.168.1.5 netmask 255.255.255.0 up (brings eth0 up with an IP of 192.168.1.5)
     
     ifconfig eth0:1 192.168.2.15 netmask 255.255.255.0 (adds a secondary IP address of 192.168.2.15 to eth0)


==Network Reconfiguration - Permanent Changes==
'''ETH0'''&lt;br&gt;
If you need to change your '''eth0''' configuration after an install, use netconfig

     netconfig

'''OTHER INTERFACES'''&lt;br&gt;
To reconfigure other network devices, you need to edit the /etc/rc.d/rc.inet1.conf files by hand. The file is very easy to figure out.

     vi /etc/rc.d/rc.inet1.conf


==Make changes take effect immediately==
To make the network changes immediately active:

     /etc/rc.d/rc.inet1 restart  (restarts all interfaces)
     /etc/rc.d/rc.inet1 eth0_restart  (restarts eth0)
     /etc/rc.d/rc.inet1 eth1_restart  (restarts eth1)
     ...etc...


[[Category: Tutorials]]</text>
    <sha1>8b12afb0dc6ed769f9cea3587f2a622e9a4f6158</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>ZFS root</title>
  <ns>0</ns>
  <id>290</id>
  <revision>
    <id>783</id>
    <parentid>782</parentid>
    <timestamp>2012-09-09T04:06:47Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="54107" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at
[http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device.

Note: On a real ZFS installation, users will typically want to use the ZFS mirror or raidz virtual device (vdev) types for reliability against hard drive failures. For example, a good configuration might be to use a USB memory stick (and a backup stick) for /boot that is plugged into an on-motherboard "Type A" USB connector. Then, use four whole hard drives in a raidz2 vdev as the initial storage space in the root zpool. At a later time, to add more storage space, additional whole four-drive raidz2 vdevs of the same size could be added to the zpool. It is recommended to only add the same vdev type (disk, mirror, or raidz|1|2|3) and size to a zpool since zfs stripes across the vdevs, and vdevs of different types/sizes do not stripe together optimally. After adding a vdev to your zpool, you might need to copy the new /etc/zfs/zpool.cache to your initrd-tree or initramfs-source (and rebuild/reinstall them) if you are using the cachefile to import your zpool. Using mirror vdevs would be similar to a raid10. Using 4-disk raidz2 vdevs would give the same storage space as raid10 while fully reliable against any double-disk failure; however, the raidz2 parity calculations results in higher CPU usage and/or lower performance. Because raidz vdevs cannot be grown by adding hard drives to them, and vdevs in a zpool are striped, it is important with ZFS to decide what type and size of vdev will be used in a zpool as the units of add-on storage space; it could be difficult to alter this decision later. Finally, on a real installation with raidz, data scrub should be scheduled to actively search for "latent defects" on the hard drives so that unknown read/write errors do not become known later during a disk swap/rebuild and result in the zpool becoming faulted (lost).

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on:

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "zpool import -f zfs-root", "mount zfs-root", and then "exit" to continue booting onto zfs-root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set, and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as readonly property changes. Note: if you use mountpoint=legacy, then you do not need to make the following changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts of run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>b840f3f890c141b5f30533b03f357c079d70ed95</sha1>
  </revision>
  <revision>
    <id>792</id>
    <parentid>783</parentid>
    <timestamp>2012-09-14T06:50:06Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="54618" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at
[http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device.

Note: On a real ZFS installation, users will typically want to use the ZFS mirror or raidz virtual device (vdev) types for reliability against hard drive failures. For example, a good configuration might be to use a USB memory stick (and a backup stick) for /boot that is plugged into an on-motherboard "Type A" USB connector. Then, use four whole hard drives in a raidz2 vdev as the initial storage space in the root zpool. At a later time, to add more storage space, additional whole four-drive raidz2 vdevs of the same size could be added to the zpool. It is recommended to only add the same vdev type (disk, mirror, or raidz|1|2|3) and size to a zpool since zfs stripes across the vdevs, and vdevs of different types/sizes do not stripe together optimally. After adding a vdev to your zpool, you might need to copy the new /etc/zfs/zpool.cache to your initrd-tree or initramfs-source (and rebuild/reinstall them) if you are using the cachefile to import your zpool. Using mirror vdevs would be similar to a raid10. Using 4-disk raidz2 vdevs would give the same storage space as raid10 while fully reliable against any double-disk failure; however, the raidz2 parity calculations results in higher CPU usage and/or lower performance. Because raidz vdevs cannot be grown by adding hard drives to them, and vdevs in a zpool are striped, it is important with ZFS to decide what type and size of vdev will be used in a zpool as the units of add-on storage space; it could be difficult to alter this decision later. Finally, on a real installation with raidz, data scrub should be scheduled to actively search for "latent defects" on the hard drives so that unknown read/write errors do not become known later during a disk swap/rebuild and result in the zpool becoming faulted (lost).

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on:

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "zpool import -f zfs-root", "mount zfs-root", and then "exit" to continue booting onto zfs-root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set, and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as readonly property changes. Note: if you use mountpoint=legacy, then you do not need to make the following changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts to run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

An alternative to using /etc/fastboot is to make the file &lt;code&gt;/sbin/fsck.zfs&lt;/code&gt; that always just "does nothing successfully":
&lt;pre&gt;
#!/bin/sh
exec /usr/bin/true
&lt;/pre&gt;
This fsck helper has the advantage that you do not need to alter &lt;code&gt;rc.S&lt;/code&gt; as much, or at all if you use zfs property &lt;code&gt;mountpoint=legacy&lt;/code&gt; and the regular &lt;code&gt;mount&lt;/code&gt; command on your zfs-root. With these ideas, no slackware /etc/rc.d/* files really need editing, but it is up to you how you want to experiment.

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>e8ad383f860374ce018bd4fe1b883bfd9aa3c58a</sha1>
  </revision>
  <revision>
    <id>793</id>
    <parentid>792</parentid>
    <timestamp>2012-09-14T07:59:36Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="54749" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at
[http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device.

Note: On a real ZFS installation, users will typically want to use the ZFS mirror or raidz virtual device (vdev) types for reliability against hard drive failures. For example, a good configuration might be to use a USB memory stick (and a backup stick) for /boot that is plugged into an on-motherboard "Type A" USB connector. Then, use four whole hard drives in a raidz2 vdev as the initial storage space in the root zpool. At a later time, to add more storage space, additional whole four-drive raidz2 vdevs of the same size could be added to the zpool. It is recommended to only add the same vdev type (disk, mirror, or raidz|1|2|3) and size to a zpool since zfs stripes across the vdevs, and vdevs of different types/sizes do not stripe together optimally. After adding a vdev to your zpool, you might need to copy the new /etc/zfs/zpool.cache to your initrd-tree or initramfs-source (and rebuild/reinstall them) if you are using the cachefile to import your zpool. Using mirror vdevs would be similar to a raid10. Using 4-disk raidz2 vdevs would give the same storage space as raid10 while fully reliable against any double-disk failure; however, the raidz2 parity calculations results in higher CPU usage and/or lower performance. Because raidz vdevs cannot be grown by adding hard drives to them, and vdevs in a zpool are striped, it is important with ZFS to decide what type and size of vdev will be used in a zpool as the units of add-on storage space; it could be difficult to alter this decision later. Finally, on a real installation with raidz, data scrub should be scheduled to actively search for "latent defects" on the hard drives so that unknown read/write errors do not become known later during a disk swap/rebuild and result in the zpool becoming faulted (lost).

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:

&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;

When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on and sync disks.

To avoid the requirement to import the zfs-root pool at startup, keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:

&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;

A zfs fs will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:

&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;

If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):

&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;

This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:

&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:

&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:

&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:

&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).

&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;

These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted.

Mount some special mounts before chroot:

&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:

&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel.

&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:

&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:

&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on:

Setup mkinitrd:

&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit.
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it).
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt.
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time. ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by a system call, the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system.


Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsibe for configuring your block devices and mount your root at /mnt and then booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;

This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short name. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands and startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually "zpool import -f zfs-root", "mount zfs-root", and then "exit" to continue booting onto zfs-root.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid. In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the system call sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"), import only the pool for the root fs with mountpoint=none and readonly=on properties set, and while it is not mounted:
&lt;pre&gt;
(on installer or initrd rescue shell)
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
zfs set readonly=off zfs-root
mount zfs-pool
cp /etc/zfs/zpool.cache-initrd /mnt/etc/zfs/
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;

Now, doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to "remount" rw or ro as readonly property changes. Note: if you use mountpoint=legacy, then you do not need to make the following changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6
&lt;pre&gt;
# comment out the line
#    /bin/mount -v -n -o remount,ro /
#add the line
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;


For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts to run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

An alternative to using /etc/fastboot is to make the file &lt;code&gt;/sbin/fsck.zfs&lt;/code&gt; that always just "does nothing successfully":
&lt;pre&gt;
#!/bin/sh
exec /bin/true
&lt;/pre&gt;
Or, it can be:
&lt;pre&gt;
#!/bin/sh
exit 0
&lt;/pre&gt;
Or, you just do (LOL!):
&lt;pre&gt;
ln -s /bin/true /sbin/fsck.zfs
&lt;/pre&gt;
Got the idea, right!

This fsck helper has the advantage that you do not need to alter &lt;code&gt;rc.S&lt;/code&gt; as much, or at all if you use zfs property &lt;code&gt;mountpoint=legacy&lt;/code&gt; and the regular &lt;code&gt;mount&lt;/code&gt; command on your zfs-root. With these ideas, no slackware /etc/rc.d/* files really need editing, but it is up to you how you want to experiment.

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>0c9821e46f48699d0f8535063aa83bcfc1095f13</sha1>
  </revision>
  <revision>
    <id>795</id>
    <parentid>793</parentid>
    <timestamp>2012-09-16T08:07:20Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="58520" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at
[http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device.

Note: On a real ZFS installation, users will typically want to use the ZFS mirror or raidz virtual device (vdev) types for reliability against hard drive failures. For example, a good configuration might be to use a USB memory stick (and a backup stick) for /boot that is plugged into an on-motherboard "Type A" USB connector. Then, use four whole hard drives in a raidz2 vdev as the initial storage space in the root zpool. At a later time, to add more storage space, additional whole four-drive raidz2 vdevs of the same size could be added to the zpool. It is recommended to only add the same vdev type (disk, mirror, or raidz|1|2|3) and size to a zpool since zfs stripes across the vdevs, and vdevs of different types/sizes do not stripe together optimally. After adding a vdev to your zpool, you might need to copy the new /etc/zfs/zpool.cache to your initrd-tree or initramfs-source (and rebuild/reinstall them) if you are using the cachefile to import your zpool. Using mirror vdevs would be similar to a raid10. Using 4-disk raidz2 vdevs would give the same storage space as raid10 while fully reliable against any double-disk failure; however, the raidz2 parity calculations results in higher CPU usage and/or lower performance. Because raidz vdevs cannot be grown by adding hard drives to them, and vdevs in a zpool are striped, it is important with ZFS to decide what type and size of vdev will be used in a zpool as the units of add-on storage space; it could be difficult to alter this decision later. Finally, on a real installation with raidz, data scrub should be scheduled to actively search for "latent defects" on the hard drives so that unknown read/write errors do not become known later during a disk swap/rebuild and result in the zpool becoming faulted (lost).

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

You can also use "legacy" for the mountpoint and the management of mounting and unmounting the pool will be expected to be done using the regular "mount" and "umount" commands:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;
Later in the wiki, it is shown how to mount using "zfs mount" for mountpoint=none, and regular "mount" for mountpoint=legacy. Using mountpoint=legacy is probably the preferred setting for the zfs-root because you can use the normal mount and umount commands and do no have to change slackware /etc/rc.d/* scripts much, if any. The normal slackware scripts handle a root filesystem's mounting and remounting using the normal mount command.

On creation, the zpool zfs-pool is "imported" and has a zpool status that can be viewed:
&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;
When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on or remount read-only and sync disks.

To avoid the requirement to import the zfs-root pool at startup, you can keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:
&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;
A warning about the zpool.cache file: Having /etc/zfs/zpool.cache present at zfs module load or module init time can be unsafe if the device names in /dev have changed since the last boot. Especially dangerous is if two hard drives have swapped names, like /dev/sda and /dev/sdb have swapped names. It is safer to not have a zpool.cache file on the system at boot and zfs module load/init time to guard against the possibility that the cache file is no longer correct. This wiki will try to show how you can use zpool.cache to import your pool if the regular zpool import command seems to always require you to force it. This wiki will also show how to not need a zpool.cache file to import normally.

A zfs filesystem will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:
&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; then the options for the mount command for ro or rw mounting will work as normal also and override whatever the readonly property is set to. The readonly property does serve as a default.

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;
If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;
This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:
&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:
&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:
&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:
&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).
&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:
&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;
These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted. Although the fstab option for fs_passno is 0 and indicates that root (/) should not be fsck, this fs_passno option in fstab is ignored during system startup for / in rc.S because rc.S explicity runs "fsck /" which does not look at options inside fstab. Fsck doesn't work on a zfs fs, and we will deal with that problem in a moment (see below).

Mount some special mounts before chroot:
&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:
&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel:
&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:
&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:
&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on...

Setup mkinitrd:
&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit:
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it):
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt:
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage (NAS) where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time (that requires a "cluster" fs). ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system. The hostid can also be passed to the SPL module with the module parameter &lt;code&gt;spl.spl_hostid=0xHHHHHHHH&lt;/code&gt; where the Hs are a hexadecimal hostid value and this overrides any /etc/hostid or hostname/IP-based hostid value.

Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsible for configuring your block devices, mounting root at /mnt, and booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;
This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short hostname. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;
We want to make sure the default is to mount readonly, then it mounts using defaults from /etc/fstab inside the initrd.

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands at startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines. Using zpool import/export is safer than using a zpool.cache, so we try to setup that way preferably.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually do:
&lt;pre&gt;
zpool import -f zfs-root
mount zfs-root
exit
&lt;/pre&gt;
This will force import, overriding the conflict that zfs thinks may be happening. Next is mount. After this, exit to let the init script continue on to boot the system normally.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid (the SPL module actually tries to run the hostid command to get this value or it uses the spl.spl_hostid value that is given to it). In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the function sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"):
&lt;pre&gt;
(on installer or initrd rescue shell)
zpool import zfs-root
zfs set readonly=off zfs-root
mount zfs-root
cp /etc/zfs/zpool.cache /mnt/etc/zfs/zpool.cache-initrd
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;
Words of caution, again: Doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people. As will be spammed all over this wiki, using zpool.cache is not recommended if you can avoid it because it is potentially unsafe for your pool.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to remount rw or ro as readonly property changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# before: echo "Unmounting local file systems."
# add lines:
  rm -f /etc/zfs/zpool.cache
  echo "Removed /etc/zfs/zpool.cache"
&lt;/pre&gt;
Remove /etc/zfs/zpool.cache on shutdown. This is recommended because if it is present when you import a pool, it might use this old cache to determine the device filenames in the pool, which may have changed filenames since the last boot, especially the non-persistent /dev/sd* device filenames. It is safest to avoid any usage of the zpool.cache file at boot in initramfs, zfs module load, and at zpool import of other pools.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# comment out the line:
#    /bin/mount -v -n -o remount,ro /
# add the line:
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;
This attempts to export even though it cannot return success for the root pool. The attempt is still recorded in the zpool history, and even though it fails the pool may actually be marked as exported (not sure).

For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts to run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

An alternative to using /etc/fastboot is to make the file &lt;code&gt;/sbin/fsck.zfs&lt;/code&gt; that always just "does nothing successfully":
&lt;pre&gt;
#!/bin/sh
exec /bin/true
&lt;/pre&gt;
Or, it can be:
&lt;pre&gt;
#!/bin/sh
exit 0
&lt;/pre&gt;
Or, just do:
&lt;pre&gt;
ln -s /bin/true /sbin/fsck.zfs
&lt;/pre&gt;
This fsck helper has the advantage that you do not need to alter &lt;code&gt;rc.S&lt;/code&gt; as much, or at all if you use zfs property &lt;code&gt;mountpoint=legacy&lt;/code&gt; and the regular &lt;code&gt;mount&lt;/code&gt; command on your zfs-root. With these ideas, no slackware /etc/rc.d/* files really need editing, but it is up to you how you want to experiment. I prefer to use &lt;code&gt;mountpoint=legacy&lt;/code&gt; and edit just the initrd init script as above, and edit rc.6 to remove /etc/zfs/zpool.cache and try to export.

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>9f4c0b96e8e35300283c1a87033731e84a8ac4db</sha1>
  </revision>
  <revision>
    <id>796</id>
    <parentid>795</parentid>
    <timestamp>2012-09-16T09:58:56Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="58521" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc10) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc2. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc10.tar.gz and zfs-0.6.0-rc10.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at
[http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp spl-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc10_3.2.27-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
cp zfs-0.6.0rc10_3.2.27-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory. ZFS supports creating complex data storage configurations such as pools (similar to a volume group) backed by one or more of various kinds of virtual devices (similar to disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device.

Note: On a real ZFS installation, users will typically want to use the ZFS mirror or raidz virtual device (vdev) types for reliability against hard drive failures. For example, a good configuration might be to use a USB memory stick (and a backup stick) for /boot that is plugged into an on-motherboard "Type A" USB connector. Then, use four whole hard drives in a raidz2 vdev as the initial storage space in the root zpool. At a later time, to add more storage space, additional whole four-drive raidz2 vdevs of the same size could be added to the zpool. It is recommended to only add the same vdev type (disk, mirror, or raidz|1|2|3) and size to a zpool since zfs stripes across the vdevs, and vdevs of different types/sizes do not stripe together optimally. After adding a vdev to your zpool, you might need to copy the new /etc/zfs/zpool.cache to your initrd-tree or initramfs-source (and rebuild/reinstall them) if you are using the cachefile to import your zpool. Using mirror vdevs would be similar to a raid10. Using 4-disk raidz2 vdevs would give the same storage space as raid10 while fully reliable against any double-disk failure; however, the raidz2 parity calculations results in higher CPU usage and/or lower performance. Because raidz vdevs cannot be grown by adding hard drives to them, and vdevs in a zpool are striped, it is important with ZFS to decide what type and size of vdev will be used in a zpool as the units of add-on storage space; it could be difficult to alter this decision later. Finally, on a real installation with raidz, data scrub should be scheduled to actively search for "latent defects" on the hard drives so that unknown read/write errors do not become known later during a disk swap/rebuild and result in the zpool becoming faulted (lost).

&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc10_3.2.27-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning (numbers are in MiB):
  0 to   4: unused
  4 to 516: /dev/sda1 512MiB, type 8300
516 to 520: unused
520 to -96: /dev/sda2, type bf01
&lt;/pre&gt;

The -96 means to count from the end of the disk so that 96MiB will remain unused at the end of the disk.

Create a zpool called zfs-root:

&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

You can also use "legacy" for the mountpoint and the management of mounting and unmounting the pool will be expected to be done using the regular "mount" and "umount" commands:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;
Later in the wiki, it is shown how to mount using "zfs mount" for mountpoint=none, and regular "mount" for mountpoint=legacy. Using mountpoint=legacy is probably the preferred setting for the zfs-root because you can use the normal mount and umount commands and do not have to change slackware /etc/rc.d/* scripts much, if any. The normal slackware scripts handle a root filesystem's mounting and remounting using the normal mount command.

On creation, the zpool zfs-root is "imported" and has a zpool status that can be viewed:
&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;
When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on or remount read-only and sync disks.

To avoid the requirement to import the zfs-root pool at startup, you can keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:
&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;
A warning about the zpool.cache file: Having /etc/zfs/zpool.cache present at zfs module load or module init time can be unsafe if the device names in /dev have changed since the last boot. Especially dangerous is if two hard drives have swapped names, like /dev/sda and /dev/sdb have swapped names. It is safer to not have a zpool.cache file on the system at boot and zfs module load/init time to guard against the possibility that the cache file is no longer correct. This wiki will try to show how you can use zpool.cache to import your pool if the regular zpool import command seems to always require you to force it. This wiki will also show how to not need a zpool.cache file to import normally.

A zfs filesystem will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:
&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; then the options for the mount command for ro or rw mounting will work as normal also and override whatever the readonly property is set to. The readonly property does serve as a default.

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;
If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;
This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:
&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:
&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:
&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:
&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).
&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:
&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;
These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted. Although the fstab option for fs_passno is 0 and indicates that root (/) should not be fsck, this fs_passno option in fstab is ignored during system startup for / in rc.S because rc.S explicity runs "fsck /" which does not look at options inside fstab. Fsck doesn't work on a zfs fs, and we will deal with that problem in a moment (see below).

Mount some special mounts before chroot:
&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:
&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel:
&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:
&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:
&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on...

Setup mkinitrd:
&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit:
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it):
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt:
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage (NAS) where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time (that requires a "cluster" fs). ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system. The hostid can also be passed to the SPL module with the module parameter &lt;code&gt;spl.spl_hostid=0xHHHHHHHH&lt;/code&gt; where the Hs are a hexadecimal hostid value and this overrides any /etc/hostid or hostname/IP-based hostid value.

Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsible for configuring your block devices, mounting root at /mnt, and booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;
This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short hostname. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;
We want to make sure the default is to mount readonly, then it mounts using defaults from /etc/fstab inside the initrd.

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands at startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines. Using zpool import/export is safer than using a zpool.cache, so we try to setup that way preferably.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually do:
&lt;pre&gt;
zpool import -f zfs-root
mount zfs-root
exit
&lt;/pre&gt;
This will force import, overriding the conflict that zfs thinks may be happening. Next is mount. After this, exit to let the init script continue on to boot the system normally.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid (the SPL module actually tries to run the hostid command to get this value or it uses the spl.spl_hostid value that is given to it). In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the function sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"):
&lt;pre&gt;
(on installer or initrd rescue shell)
zpool import zfs-root
zfs set readonly=off zfs-root
mount zfs-root
cp /etc/zfs/zpool.cache /mnt/etc/zfs/zpool.cache-initrd
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;
Words of caution, again: Doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people. As will be spammed all over this wiki, using zpool.cache is not recommended if you can avoid it because it is potentially unsafe for your pool.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to remount rw or ro as readonly property changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# before: echo "Unmounting local file systems."
# add lines:
  rm -f /etc/zfs/zpool.cache
  echo "Removed /etc/zfs/zpool.cache"
&lt;/pre&gt;
Remove /etc/zfs/zpool.cache on shutdown. This is recommended because if it is present when you import a pool, it might use this old cache to determine the device filenames in the pool, which may have changed filenames since the last boot, especially the non-persistent /dev/sd* device filenames. It is safest to avoid any usage of the zpool.cache file at boot in initramfs, zfs module load, and at zpool import of other pools.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# comment out the line:
#    /bin/mount -v -n -o remount,ro /
# add the line:
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;
This attempts to export even though it cannot return success for the root pool. The attempt is still recorded in the zpool history, and even though it fails the pool may actually be marked as exported (not sure).

For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts to run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

An alternative to using /etc/fastboot is to make the file &lt;code&gt;/sbin/fsck.zfs&lt;/code&gt; that always just "does nothing successfully":
&lt;pre&gt;
#!/bin/sh
exec /bin/true
&lt;/pre&gt;
Or, it can be:
&lt;pre&gt;
#!/bin/sh
exit 0
&lt;/pre&gt;
Or, just do:
&lt;pre&gt;
ln -s /bin/true /sbin/fsck.zfs
&lt;/pre&gt;
This fsck helper has the advantage that you do not need to alter &lt;code&gt;rc.S&lt;/code&gt; as much, or at all if you use zfs property &lt;code&gt;mountpoint=legacy&lt;/code&gt; and the regular &lt;code&gt;mount&lt;/code&gt; command on your zfs-root. With these ideas, no slackware /etc/rc.d/* files really need editing, but it is up to you how you want to experiment. I prefer to use &lt;code&gt;mountpoint=legacy&lt;/code&gt; and edit just the initrd init script as above, and edit rc.6 to remove /etc/zfs/zpool.cache and try to export.

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.27, if .27 is new kernel upgrade; you currently run on old, maybe .26)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.27
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>9d378ee353c4edefee1b852b230e5ff817581cd5</sha1>
  </revision>
  <revision>
    <id>797</id>
    <parentid>796</parentid>
    <timestamp>2012-09-19T08:42:03Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="60887" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc11) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc4. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc11.tar.gz and zfs-0.6.0-rc11.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at
[http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc11_3.2.28-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
cp spl-0.6.0rc11_3.2.28-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc11_3.2.28-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
cp zfs-0.6.0rc11_3.2.28-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory.

ZFS supports creating complex data storage configurations in data storage pools (similar to a LVM volume group) backed by one or more virtual devices (similar to physical disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device.

On a real ZFS installation, users will typically want to use the ZFS mirror or raidz virtual device (vdev) types for reliability against hard drive failures. For example, a good configuration might be to use a USB memory stick (and a backup stick) for /boot that is plugged into an on-motherboard "Type A" USB connector. Then, use four whole hard drives in a raidz2 vdev as the initial storage space in the root zpool. At a later time, to add more storage space, additional whole four-drive raidz2 vdevs of the same size could be added to the zpool. It is recommended to only add the same vdev type (disk, mirror, or raidz|1|2|3) and size to a zpool since zfs stripes across the vdevs, and vdevs of different types/sizes do not stripe together optimally. After adding a vdev to your zpool, you might need to copy the new /etc/zfs/zpool.cache to your initrd-tree or initramfs-source (and rebuild/reinstall them) if you are using the cachefile to import your zpool. Using mirror vdevs would be similar to a raid10. Using 4-disk raidz2 vdevs would give the same storage space as raid10 while fully reliable against any double-disk failure; however, the raidz2 parity calculations results in higher CPU usage and/or lower performance. Because raidz vdevs cannot be grown by adding hard drives to them, and vdevs in a zpool are striped, it is important with ZFS to decide what type and size of vdev will be used in a zpool as the units of add-on storage space; it could be difficult to alter this decision later. Finally, on a real installation with raidz, data scrub should be scheduled to actively search for "latent defects" on the hard drives so that unknown read/write errors do not become known later during a disk swap/rebuild and result in the zpool becoming faulted (lost).

If you decide to test raidz in qemu, consider making the qemu disk files on different physical disks on your host to avoid putting all the stress onto a single disk on your host. The raidz qemu disks that are all on a single physical hard drive will cause poor performance and stress on the disk due to the large amount of seek operations to access the stripes/columns in the raidz. Again, we'll keep it simple in this wiki and just make a root zpool that is just holding a single qemu disk that you've given to qemu to avoid stress on the host hard drive. But, if you really want to test raidz, you can do it by just making more qemu disks (with incremented index=X number) and making your zpool a raidz; there's no technical restriction here on the kind of vdevs in your root zpool.

Make "slackzfs" guest, and boot it into the slackware installer to begin installation:
&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning:
Part. #    Size        Partition Type           Partition Name
           4.0 MiB     free space
   1       512.0 MiB   Linux filesystem         boot
           4.0 MiB     free space
   2       9.4 GiB     Solaris /usr &amp; Mac ZFS   root
           96.0 MiB    free space
&lt;/pre&gt;
The free space is left as a recommendation. The free space has potential uses for data recovery techniques, changing boot configuration, accomodating a replacement disk that is slightly smaller, and avoiding the end of the disk where GPT and other disk labels may need to claim space at the end of a drive to hold metadata. The "partition name" can be blank or any arbitrary name you'd like to give them.

If you are going to test a ZFS mirror or raidz configuration, then you can repeat this same partitioning on each disk. For example, for a four-disk raidz2 with /dev/sd[abcd] you might do:
&lt;pre&gt;
sgdisk -R /dev/sdb /dev/sda
sgdisk -G /dev/sdb
sgdisk -R /dev/sdc /dev/sda
sgdisk -G /dev/sdc
sgdisk -R /dev/sdd /dev/sda
sgdisk -G /dev/sdd
&lt;/pre&gt;
Then, you could use the boot partitions /dev/sd[abcd]1 in a mdadm raid1 as your boot device:
&lt;pre&gt;
mdadm --create /dev/md0 -l 1 -n 4 /dev/sd[abcd]1
&lt;/pre&gt;
In this configuration, /dev/md0 is your 4-way mirror /boot device and is used as explained in the slackware [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/README_RAID.TXT README_RAID.TXT]. The /dev/sd[abcd]2 would be given to ZFS for the raidz2 (instead of to mdadm raid). This is only an example and there are many possible configurations, including using whole un-partitioned disks; however, we will continue in this wiki with a simpler configuration with /dev/sda1 as a non-raid /boot device and /dev/sda2 in a non-raidz/non-mirror zpool.

Create a zpool called zfs-root:
&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

You can also use "legacy" for the mountpoint and the management of mounting and unmounting the pool will be expected to be done using the regular "mount" and "umount" commands:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;
Later in the wiki, it is shown how to mount using "zfs mount" for mountpoint=none, and regular "mount" for mountpoint=legacy. Using mountpoint=legacy is probably the preferred setting for the zfs-root because you can use the normal mount and umount commands and do not have to change slackware /etc/rc.d/* scripts much, if any. The normal slackware scripts handle a root filesystem's mounting and remounting using the normal mount command.

On creation, the zpool zfs-root is "imported" and has a zpool status that can be viewed:
&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;
When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on or remount read-only and sync disks.

To avoid the requirement to import the zfs-root pool at startup, you can keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:
&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;
A warning about the zpool.cache file: Having /etc/zfs/zpool.cache present at zfs module load or module init time can be unsafe if the device names in /dev have changed since the last boot. Especially dangerous is if two hard drives have swapped names, like /dev/sda and /dev/sdb have swapped names. It is safer to not have a zpool.cache file on the system at boot and zfs module load/init time to guard against the possibility that the cache file is no longer correct. This wiki will try to show how you can use zpool.cache to import your pool if the regular zpool import command seems to always require you to force it. This wiki will also show how to not need a zpool.cache file to import normally.

A zfs filesystem will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:
&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; then the options for the mount command for ro or rw mounting will work as normal also and override whatever the readonly property is set to. The readonly property does serve as a default.

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;
If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;
This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:
&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:
&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:
&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:
&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).
&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:
&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;
These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted. Although the fstab option for fs_passno is 0 and indicates that root (/) should not be fsck, this fs_passno option in fstab is ignored during system startup for / in rc.S because rc.S explicity runs "fsck /" which does not look at options inside fstab. Fsck doesn't work on a zfs fs, and we will deal with that problem in a moment (see below).

Mount some special mounts before chroot:
&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:
&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel:
&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:
&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:
&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on...

Setup mkinitrd:
&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit:
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it):
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt:
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage (NAS) where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time (that requires a "cluster" fs). ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system. The hostid can also be passed to the SPL module with the module parameter &lt;code&gt;spl.spl_hostid=0xHHHHHHHH&lt;/code&gt; where the Hs are a hexadecimal hostid value and this overrides any /etc/hostid or hostname/IP-based hostid value.

Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsible for configuring your block devices, mounting root at /mnt, and booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;
This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short hostname. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;
We want to make sure the default is to mount readonly, then it mounts using defaults from /etc/fstab inside the initrd.

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands at startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines. Using zpool import/export is safer than using a zpool.cache, so we try to setup that way preferably.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually do:
&lt;pre&gt;
zpool import -f zfs-root
mount zfs-root
exit
&lt;/pre&gt;
This will force import, overriding the conflict that zfs thinks may be happening. Next is mount. After this, exit to let the init script continue on to boot the system normally.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid (the SPL module actually tries to run the hostid command to get this value or it uses the spl.spl_hostid value that is given to it). In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the function sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"):
&lt;pre&gt;
(on installer or initrd rescue shell)
zpool import zfs-root
zfs set readonly=off zfs-root
mount zfs-root
cp /etc/zfs/zpool.cache /mnt/etc/zfs/zpool.cache-initrd
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;
Words of caution, again: Doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people. As will be spammed all over this wiki, using zpool.cache is not recommended if you can avoid it because it is potentially unsafe for your pool.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to remount rw or ro as readonly property changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# before: echo "Unmounting local file systems."
# add lines:
  rm -f /etc/zfs/zpool.cache
  echo "Removed /etc/zfs/zpool.cache"
&lt;/pre&gt;
Remove /etc/zfs/zpool.cache on shutdown. This is recommended because if it is present when you import a pool, it might use this old cache to determine the device filenames in the pool, which may have changed filenames since the last boot, especially the non-persistent /dev/sd* device filenames. It is safest to avoid any usage of the zpool.cache file at boot in initramfs, zfs module load, and at zpool import of other pools.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# comment out the line:
#    /bin/mount -v -n -o remount,ro /
# add the line:
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;
This attempts to export even though it cannot return success for the root pool. The attempt is still recorded in the zpool history, and even though it fails the pool may actually be marked as exported (not sure).

For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts to run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

An alternative to using /etc/fastboot is to make the file &lt;code&gt;/sbin/fsck.zfs&lt;/code&gt; that always just "does nothing successfully":
&lt;pre&gt;
#!/bin/sh
exec /bin/true
&lt;/pre&gt;
Or, it can be:
&lt;pre&gt;
#!/bin/sh
exit 0
&lt;/pre&gt;
Or, just do:
&lt;pre&gt;
ln -s /bin/true /sbin/fsck.zfs
&lt;/pre&gt;
This fsck helper has the advantage that you do not need to alter &lt;code&gt;rc.S&lt;/code&gt; as much, or at all if you use zfs property &lt;code&gt;mountpoint=legacy&lt;/code&gt; and the regular &lt;code&gt;mount&lt;/code&gt; command on your zfs-root. With these ideas, no slackware /etc/rc.d/* files really need editing, but it is up to you how you want to experiment. I prefer to use &lt;code&gt;mountpoint=legacy&lt;/code&gt; and edit just the initrd init script as above, and edit rc.6 to remove /etc/zfs/zpool.cache and try to export.

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;

In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.28, if .28 is new kernel upgrade; you currently run on old, maybe .27)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.28
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>8223c1c539c32e62271f4b0b19d37eac2ceaf3fb</sha1>
  </revision>
  <revision>
    <id>802</id>
    <parentid>797</parentid>
    <timestamp>2012-09-24T08:39:14Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="62687" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc11) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc4. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc11.tar.gz and zfs-0.6.0-rc11.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at
[http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc11_3.2.28-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
cp spl-0.6.0rc11_3.2.28-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc11_3.2.28-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
cp zfs-0.6.0rc11_3.2.28-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory.

ZFS supports creating complex data storage configurations in data storage pools (similar to a LVM volume group) backed by one or more virtual devices (similar to physical disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device.

On a real ZFS installation, users will typically want to use the ZFS mirror or raidz virtual device (vdev) types for reliability against hard drive failures. For example, a good configuration might be to use a USB memory stick (and a backup stick) for /boot that is plugged into an on-motherboard "Type A" USB connector. Then, use four whole hard drives in a raidz2 vdev as the initial storage space in the root zpool. At a later time, to add more storage space, additional whole four-drive raidz2 vdevs of the same size could be added to the zpool. It is recommended to only add the same vdev type (disk, mirror, or raidz|1|2|3) and size to a zpool since zfs stripes across the vdevs, and vdevs of different types/sizes do not stripe together optimally. After adding a vdev to your zpool, you might need to copy the new /etc/zfs/zpool.cache to your initrd-tree or initramfs-source (and rebuild/reinstall them) if you are using the cachefile to import your zpool. Using mirror vdevs would be similar to a raid10. Using 4-disk raidz2 vdevs would give the same storage space as raid10 while fully reliable against any double-disk failure; however, the raidz2 parity calculations results in higher CPU usage and/or lower performance. Because raidz vdevs cannot be grown by adding hard drives to them, and vdevs in a zpool are striped, it is important with ZFS to decide what type and size of vdev will be used in a zpool as the units of add-on storage space; it could be difficult to alter this decision later. Finally, on a real installation with raidz, data scrub should be scheduled to actively search for "latent defects" on the hard drives so that unknown read/write errors do not become known later during a disk swap/rebuild and result in the zpool becoming faulted (lost).

If you decide to test raidz in qemu, consider making the qemu disk files on different physical disks on your host to avoid putting all the stress onto a single disk on your host. The raidz qemu disks that are all on a single physical hard drive will cause poor performance and stress on the disk due to the large amount of seek operations to access the stripes/columns in the raidz. Again, we'll keep it simple in this wiki and just make a root zpool that is just holding a single qemu disk that you've given to qemu to avoid stress on the host hard drive. But, if you really want to test raidz, you can do it by just making more qemu disks (with incremented index=X number) and making your zpool a raidz; there's no technical restriction here on the kind of vdevs in your root zpool.

Make "slackzfs" guest, and boot it into the slackware installer to begin installation:
&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning:
Part. #    Size        Partition Type           Partition Name
           4.0 MiB     free space
   1       512.0 MiB   Linux filesystem         boot
           4.0 MiB     free space
   2       9.4 GiB     Solaris /usr &amp; Mac ZFS   root
           96.0 MiB    free space
&lt;/pre&gt;
The free space is left as a recommendation. The free space has potential uses for data recovery techniques, changing boot configuration, accomodating a replacement disk that is slightly smaller, and avoiding the end of the disk where GPT and other disk labels may need to claim space at the end of a drive to hold metadata. The "partition name" can be blank or any arbitrary name you'd like to give them.

If you are going to test a ZFS mirror or raidz configuration, then you can repeat this same partitioning on each disk. For example, for a four-disk raidz2 with /dev/sd[abcd] you might do:
&lt;pre&gt;
sgdisk -R /dev/sdb /dev/sda
sgdisk -G /dev/sdb
sgdisk -R /dev/sdc /dev/sda
sgdisk -G /dev/sdc
sgdisk -R /dev/sdd /dev/sda
sgdisk -G /dev/sdd
&lt;/pre&gt;
Then, you could use the boot partitions /dev/sd[abcd]1 in a mdadm raid1 as your boot device:
&lt;pre&gt;
mdadm --create /dev/md0 -l 1 -n 4 /dev/sd[abcd]1
&lt;/pre&gt;
In this configuration, /dev/md0 is your 4-way mirror /boot device and is used as explained in the slackware [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/README_RAID.TXT README_RAID.TXT]. The /dev/sd[abcd]2 would be given to ZFS for the raidz2 (instead of to mdadm raid). This is only an example and there are many possible configurations, including using whole un-partitioned disks; however, we will continue in this wiki with a simpler configuration with /dev/sda1 as a non-raid /boot device and /dev/sda2 in a non-raidz/non-mirror zpool.

Create a zpool called zfs-root:
&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

You can also use "legacy" for the mountpoint and the management of mounting and unmounting the pool will be expected to be done using the regular "mount" and "umount" commands:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;
Later in the wiki, it is shown how to mount using "zfs mount" for mountpoint=none, and regular "mount" for mountpoint=legacy. Using mountpoint=legacy is probably the preferred setting for the zfs-root because you can use the normal mount and umount commands and do not have to change slackware /etc/rc.d/* scripts much, if any. The normal slackware scripts handle a root filesystem's mounting and remounting using the normal mount command.

On creation, the zpool zfs-root is "imported" and has a zpool status that can be viewed:
&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;
When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on or remount read-only and sync disks.

To avoid the requirement to import the zfs-root pool at startup, you can keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:
&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;
A warning about the zpool.cache file: Having /etc/zfs/zpool.cache present at zfs module load or module init time can be unsafe if the device names in /dev have changed since the last boot. Especially dangerous is if two hard drives have swapped names, like /dev/sda and /dev/sdb have swapped names. It is safer to not have a zpool.cache file on the system at boot and zfs module load/init time to guard against the possibility that the cache file is no longer correct. This wiki will try to show how you can use zpool.cache to import your pool if the regular zpool import command seems to always require you to force it. This wiki will also show how to not need a zpool.cache file to import normally.

A zfs filesystem will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:
&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; then the options for the mount command for ro or rw mounting will work as normal also and override whatever the readonly property is set to. The readonly property does serve as a default.

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;
If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;
This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:
&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:
&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:
&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:
&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).
&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:
&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;
These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted. Although the fstab option for fs_passno is 0 and indicates that root (/) should not be fsck, this fs_passno option in fstab is ignored during system startup for / in rc.S because rc.S explicity runs "fsck /" which does not look at options inside fstab. Fsck doesn't work on a zfs fs, and we will deal with that problem in a moment (see below).

Mount some special mounts before chroot:
&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:
&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel:
&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:
&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:
&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on...

Setup mkinitrd:
&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit:
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it):
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt:
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage (NAS) where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time (that requires a "cluster" fs). ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system. The hostid can also be passed to the SPL module with the module parameter &lt;code&gt;spl.spl_hostid=0xHHHHHHHH&lt;/code&gt; where the Hs are a hexadecimal hostid value and this overrides any /etc/hostid or hostname/IP-based hostid value.

Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsible for configuring your block devices, mounting root at /mnt, and booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;
This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short hostname. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;
We want to make sure the default is to mount readonly, then it mounts using defaults from /etc/fstab inside the initrd.

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands at startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines. Using zpool import/export is safer than using a zpool.cache, so we try to setup that way preferably.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually do:
&lt;pre&gt;
zpool import -f zfs-root
mount zfs-root
exit
&lt;/pre&gt;
This will force import, overriding the conflict that zfs thinks may be happening. Next is mount. After this, exit to let the init script continue on to boot the system normally.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid (the SPL module actually tries to run the hostid command to get this value or it uses the spl.spl_hostid value that is given to it). In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the function sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"):
&lt;pre&gt;
(on installer or initrd rescue shell)
zpool import zfs-root
zfs set readonly=off zfs-root
mount zfs-root
cp /etc/zfs/zpool.cache /mnt/etc/zfs/zpool.cache-initrd
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;
Words of caution, again: Doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people. As will be spammed all over this wiki, using zpool.cache is not recommended if you can avoid it because it is potentially unsafe for your pool.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to remount rw or ro as readonly property changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# before: echo "Unmounting local file systems."
# add lines:
  rm -f /etc/zfs/zpool.cache
  echo "Removed /etc/zfs/zpool.cache"
&lt;/pre&gt;
Remove /etc/zfs/zpool.cache on shutdown. This is recommended because if it is present when you import a pool, it might use this old cache to determine the device filenames in the pool, which may have changed filenames since the last boot, especially the non-persistent /dev/sd* device filenames. It is safest to avoid any usage of the zpool.cache file at boot in initramfs, zfs module load, and at zpool import of other pools.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# comment out the line:
#    /bin/mount -v -n -o remount,ro /
# add the line:
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;
This attempts to export even though it cannot return success for the root pool. The attempt is still recorded in the zpool history, and even though it fails the pool may actually be marked as exported (not sure).

For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts to run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

An alternative to using /etc/fastboot is to make the file &lt;code&gt;/sbin/fsck.zfs&lt;/code&gt; that always just "does nothing successfully":
&lt;pre&gt;
#!/bin/sh
exec /bin/true
&lt;/pre&gt;
Or, it can be:
&lt;pre&gt;
#!/bin/sh
exit 0
&lt;/pre&gt;
Or, just do:
&lt;pre&gt;
ln -s /bin/true /sbin/fsck.zfs
&lt;/pre&gt;
This fsck helper has the advantage that you do not need to alter &lt;code&gt;rc.S&lt;/code&gt; as much, or at all if you use zfs property &lt;code&gt;mountpoint=legacy&lt;/code&gt; and the regular &lt;code&gt;mount&lt;/code&gt; command on your zfs-root. With these ideas, no slackware /etc/rc.d/* files really need editing, but it is up to you how you want to experiment. I prefer to use &lt;code&gt;mountpoint=legacy&lt;/code&gt; and edit just the initrd init script as above, and edit rc.6 to remove /etc/zfs/zpool.cache and try to export.

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;
In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

An alternative rescue shell on the initrd can be started as follows:
&lt;pre&gt;
boot: vmlinuz rdinit=/bin/sh
&lt;/pre&gt;
This puts you into a sh shell inside the initrd, and the normal /init script is not run at all. In this shell, you can fix problems and then attempt to start the system normally as follows:
&lt;pre&gt;
exec /init
&lt;/pre&gt;
This runs the normal rdinit program, "execing" it so that it takes process ID (PID) 1 of your sh shell, which is the required PID for the init program.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd could fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, then you may want to use &lt;code&gt;readonly=off&lt;/code&gt; and use the options to the &lt;code&gt;mount&lt;/code&gt; command to control ro|rw mounting. With &lt;code&gt;mountpoint=legacy&lt;/code&gt; and &lt;code&gt;readonly=on&lt;/code&gt; used together, there can be a contradiction between how the kernel actually mounts zfs-root (ro according to the readonly property) and how the userspace mount command and /etc/mtab attempt to mount the zfs-root (if you give &lt;code&gt;-o rw&lt;/code&gt;). The kernel might actually mount ro, even when you have told the mount command to mount rw. The /etc/mtab can erroneously report rw, while the kernel's /proc/mounts file reports the actual mount as ro. Again, the two methods of mounting a zfs fs, either "legacy" &lt;code&gt;mount&lt;/code&gt; command or by using the &lt;code&gt;zfs set mountpoint&lt;/code&gt; can conflict with each other on the mode of mounting. If you create a zfs filesystem under zfs-root, like &lt;code&gt;zfs create "zfs-root/movies"&lt;/code&gt; and then try to mount it, it may have inherited &lt;code&gt;mountpoint=legacy&lt;/code&gt; and &lt;code&gt;readonly=on&lt;/code&gt; from zfs-root, and it may mount ro even if you use the rw mount option: in this case, you have to do another command &lt;code&gt;mount -o remount,rw "zfs-root/movies"&lt;/code&gt; to make it actually switch to rw (kind of weird!).

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.28, if .28 is new kernel upgrade; you currently run on old, maybe .27)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.28
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>b69bab17357d2637a89a69670f8d69d582742e68</sha1>
  </revision>
  <revision>
    <id>803</id>
    <parentid>802</parentid>
    <timestamp>2012-09-24T14:44:46Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="63265" xml:space="preserve">[[Category:Tutorials]]
If you have heard about the ZFS filesystem and you're curious to try it out, then you can try it on slackware64, thanks to the ZFSonLinux.org project!

In this article, an example is shown of how to install slackware64 14.0 onto a ZFS root filesystem (zfs-root) inside a QEMU virtual machine for testing purposes. It is recommended that you install qemu and learn how to use it to test a ZFS installation before you decide to use it on real hardware. A slackbuild for qemu can be found on slackbuilds.org. If you have a processor that supports Intel VT-x or AMD AMD-V virtualization acceleration (try modprobe kvm-intel or modprobe kvm-amd), then use the slackbuild for qemu-kvm.

This article isn't going to go into any detail on actually using ZFS or what kinds of installation options and settings might be optimal. This article just presents an example of how to get started with ZFS on slackware.

At this time of writing, ZFSonLinux is at "release candidate" (version 0.6.0-rc11) development stage, and many issues can occur. See the ZFSonLinux.org web site and the issues tracker for an idea about the current issues. There is also an irc channel on irc.freenode.net, #zfsonlinux, for discussion of issues and help.

Although not required, it is helpful to keep a local mirror of slackware64 on your system. Having a local mirror makes it easier to upgrade to slackware64-current or to patches/* in a release. To help manage your own local slackware mirror and generate your own CD and DVD slackware installers, see http://alien.slackbook.org/blog/local-slackware-mirror/.

In this article, we use a slackware64-current DVD image file as the qemu cdrom device media for the installation of the slackware guest. This was tested at slackware64-current = slackware64 14.0rc4. You can obtain a slackware DVD image using a torrent, buy the DVD from slackware.com, or generate your own DVD image file using the mirror script. For an actual DVD, you can pass your DVD device (e.g., /dev/sr0) as the qemu cdrom device. For a DVD image file, pass the image file as the qemu cdrom device.

The ZFSonLinux packages are not included in slackware at this time. There are two packages involved: spl and zfs. The first, spl, is "Solaris Porting Layer" and must be installed on the system before zfs can be compiled. The source code tarballs for these are at ZFSonLinux.org. At this time of writing, they are spl-0.6.0-rc11.tar.gz and zfs-0.6.0-rc11.tar.gz.

At this point, it is assumed you have qemu installed, have obtained a slackware64-current/14.0 DVD, and have downloaded spl and zfs tarballs to your host system. The first step now is, if your host is not slackware64-current/14.0 (the same as the guest will be), then you need to create a minimal development slackware64 guest system in qemu for just the purpose of compiling and packaging the spl and zfs slackware packages and transferring a copy of these packages back onto your host system to use later to install onto zfs during the slackware install process.

From this point onward, instructions become a bit terse and mostly limited to examples of the commands you might use to complete tasks. You are encouraged to examine what each command does by reading the command's man pages. For example, the command "man qemu" can show you most of what you need to know about running qemu on the command line.

So, here's an example of how you might build the spl and zfs packages, starting in your home directory:

&lt;pre&gt;
(on host)
cd ~
mkdir qemu
cd qemu
mkdir slackdevel
cd slackdevel
mkdir packages
cp ~/spl-*.tar.gz packages
cp ~/zfs-*.tar.gz packages
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

When you need to change boot to cd or disk, try changing "order=dc" or hitting F12 at boot prompt and select the CD/DVD boot option.

Note: The support for booting drives using if=scsi is not included with current versions of qemu. Booting scsi requires the 8xx_64.rom option-rom, which can be downloaded at
[http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip LSI.com]. Unzip it, and then:
&lt;pre&gt;
cp 8xx_64.rom /usr/share/qemu
# then run qemu-kvm with additional command line option: -option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;

Qemu should boot into the install-dvd, and now perform a very ordinary slackware64 install onto /dev/sda. Install d package set and most others, but package sets x, kde, xfce not really needed.

First note: examples here use tools from the gptfdisk package (gdisk, sgdisk, cgdisk) to partition the disk with GUID partition table (GPT) format. GPT might not be too familiar to everyone, who mostly have only used MBR partitions with fdisk. In the slackware installations this author has tested in qemu, using GPT partitions has caused no problems with lilo or other tools used in slackware. GPT disk labels support creating up to 128 partitions and support disks larger than 2TB (the limit of MBR fdisk). LILO installs into the first 440 bytes on /dev/sda, inside a GPT "protective MBR" that serves to provide compatibility with MBR bootloaders like lilo. LILO uses LBA32 sector addressing and can see all 512-byte sectors inside the first 2TB of a disk. So long as the /boot partition is within the first 2TB of a disk, lilo can work on a disk larger than 2TB. Unlike the common default of fdisk to start the first partition at sector 63, which is not aligned with the 4KiB sector size of Advanced Format hard disks, gdisk's default is to start partitions at 2048 sector (1MiB) boundaries which are also 4KiB aligned. Using gdisk GPT works on all disks and is compatible with using Advanced Format hard disks larger than 2TB. More information about GPT disk label format can be found on wikipedia.org. For those that have used grub instead of lilo, grub installation is different with GPT than with MBR, and grub requires a GPT partition of type grub-bios or 0xEF02 "BIOS Boot Partition" of about 8MiB where it can install it's additional bootloader stages because grub cannot embed in sectors 1-62 on GPT where GPT keeps it's partition tables. On MBR, sectors 1-62 were normally reserved space for bootloaders to keep a 2nd stage.

For this purpose of development guest, just create a simple 1-partition system, /dev/sda1, and do a simple slackware install on it. Don't bother with swap or separate /boot unless you want to:

&lt;pre&gt;
(on install-dvd)
cgdisk /dev/sda
setup
reboot
&lt;/pre&gt;

When this simple development guest boots, login as root, and continue:

&lt;pre&gt;
(on qemu guest)
cd ~
mkdir packages
mount hostpackages -t 9p -o trans=virtio packages
echo --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share &gt; configure-options
mkdir src
cd src

mkdir install
tar xvzf ~/packages/spl-*.tar.gz
cd spl-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../spl-0.6.0rc11_3.2.28-x86_64-1root.txz)
cd ..
rm -r install
installpkg spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
cp spl-0.6.0rc11_3.2.28-x86_64-1root.txz ~/packages

mkdir install
tar xvzf ~/packages/zfs-*.tar.gz
cd zfs-*
./configure $( cat ~/configure-options )
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-&lt;version&gt;_&lt;kernel_version&gt;-x86_64-&lt;build_id&gt;.txz
(e.g., makepkg ../zfs-0.6.0rc11_3.2.28-x86_64-1root.txz)
cd ..
rm -r install
installpkg zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
cp zfs-0.6.0rc11_3.2.28-x86_64-1root.txz ~/packages
&lt;/pre&gt;

At this point spl and zfs packages are copied back to the host in the packages directory. Also, spl and zfs are installed in this simple development guest, so one could begin to experiment with zfs pools and datasets but while the root fs is whatever you made it during setup (probably the default, ext4). This development guest isn't really needed anymore, so it can be deleted:

&lt;pre&gt;
halt
(exit qemu: ctrl-alt-2 then enter quit at QEMU command prompt)

(on host)
rm disk1.raw dvd.iso
mv packages ..
cd ..
rmdir slackdevel
&lt;/pre&gt;

Now that we have the spl and zfs packages on the host, it is possible to copy them into your local slackware64 mirror and then generate your own install DVD image that includes them. For example, change to the directory that contains the slackware README files, and create a "addon" directory and copy the spl and zfs slackware packages into there. Then, generate the DVD image using a command such as $( ./mirror-slackware-current.sh -i ) from where you have this script configured to maintain your local mirror. We can also just continue to access them inside the installer using qemu's virtfs option. When you are going to do a real installation onto real hardware, you need to generate and burn your own DVD that includes the packages.

It is time to begin the installation of slackware64 on a ZFS root, assuming either you have regenerated dvd.iso with zfs packages in addon/* or we access the zfs packages while in the installer using qemu's virtfs to the host's packages directory.

ZFS supports creating complex data storage configurations in data storage pools (similar to a LVM volume group) backed by one or more virtual devices (similar to physical disks and raid arrays) and containing one or more datasets (similar to mounted filesystems, logical volume devices, or snapshots). But here, we keep it simple and will install on just a single disk device.

On a real ZFS installation, users will typically want to use the ZFS mirror or raidz virtual device (vdev) types for reliability against hard drive failures. For example, a good configuration might be to use a USB memory stick (and a backup stick) for /boot that is plugged into an on-motherboard "Type A" USB connector. Then, use four whole hard drives in a raidz2 vdev as the initial storage space in the root zpool. At a later time, to add more storage space, additional whole four-drive raidz2 vdevs of the same size could be added to the zpool. It is recommended to only add the same vdev type (disk, mirror, or raidz|1|2|3) and size to a zpool since zfs stripes across the vdevs, and vdevs of different types/sizes do not stripe together optimally. After adding a vdev to your zpool, you might need to copy the new /etc/zfs/zpool.cache to your initrd-tree or initramfs-source (and rebuild/reinstall them) if you are using the cachefile to import your zpool. Using mirror vdevs would be similar to a raid10. Using 4-disk raidz2 vdevs would give the same storage space as raid10 while fully reliable against any double-disk failure; however, the raidz2 parity calculations results in higher CPU usage and/or lower performance. Because raidz vdevs cannot be grown by adding hard drives to them, and vdevs in a zpool are striped, it is important with ZFS to decide what type and size of vdev will be used in a zpool as the units of add-on storage space; it could be difficult to alter this decision later. Finally, on a real installation with raidz, data scrub should be scheduled to actively search for "latent defects" on the hard drives so that unknown read/write errors do not become known later during a disk swap/rebuild and result in the zpool becoming faulted (lost).

If you decide to test raidz in qemu, consider making the qemu disk files on different physical disks on your host to avoid putting all the stress onto a single disk on your host. The raidz qemu disks that are all on a single physical hard drive will cause poor performance and stress on the disk due to the large amount of seek operations to access the stripes/columns in the raidz. Again, we'll keep it simple in this wiki and just make a root zpool that is just holding a single qemu disk that you've given to qemu to avoid stress on the host hard drive. But, if you really want to test raidz, you can do it by just making more qemu disks (with incremented index=X number) and making your zpool a raidz; there's no technical restriction here on the kind of vdevs in your root zpool.

Make "slackzfs" guest, and boot it into the slackware installer to begin installation:
&lt;pre&gt;
(on host)
mkdir slackzfs
mv packages slackzfs/
cd slackzfs
qemu-img create disk1.raw 10G
ln -s ~/slackware64-current-install-dvd.iso dvd.iso
qemu-kvm \
 -option-rom 8xx_64.rom,bootindex=1 \
 -no-quit \
 -no-shutdown \
 -boot order=cd,menu=on \
 -m 2G \
 -cpu host \
 -smp sockets=1,cores=4 \
 -net nic,model=e1000 -net user \
 -cdrom dvd.iso \
 -drive format=raw,media=disk,cache=none,aio=native,if=scsi,index=0,file=disk1.raw \
 -virtfs local,path=./packages/,security_model=none,mount_tag=hostpackages
&lt;/pre&gt;

The install-dvd should boot, and then begin installation steps on the installer command line:

&lt;pre&gt;
(on install-dvd)
# mount the install-dvd
mkdir /dvd
mount /dev/sr0 /dvd

# install coreutils, which provides the "hostid" command needed to load the spl module
installpkg /dvd/slackware64/a/coreutils-8.17-x86_64-1.txz

# install kmod package which includes "depmod" command and others
installpkg /dvd/slackware64/a/kmod-9-x86_64-2.txz
depmod

# install the full kernel modules so you can load 9p filesystem and use it if you want
# .. you might keep the zfs modules packages off the dvd and use a plain slack dvd
installpkg /dvd/slackware64/a/kernel-modules-*.txz
depmod

# install bash and libtermcap because udev rules in zfs use bash scripts
installpkg /dvd/slackware64/a/bash-*.txz
installpkg /dvd/slackware64/l/libtermcap-*.txz

# install spl and zfs that you have copied into the mirror before running the DVD creation
installpkg /dvd/addon/spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
installpkg /dvd/addon/zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod

#Or:
mkdir /packages
find /lib/modules/ | grep 9p
lsmod
# check that 9p modules load, mainly 9pnet_virtio
modprobe 9pnet_virtio
mount hostpackages -t 9p -o trans=virtio /packages
installpkg /packages/spl-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
installpkg /packages/zfs-0.6.0rc11_3.2.28-x86_64-1root.txz
depmod
modprobe zfs
&lt;/pre&gt;

Now zfs tools: "zpool" and "zfs" should work in the live installer.
On the installer, there can be trouble seeing man pages, so install:

&lt;pre&gt;
installpkg /dvd/slackware64/ap/man-*.txz
installpkg /dvd/slackware64/ap/groff-*.txz
installpkg /dvd/slackware64/a/less-*.txz
export MANPATH=/usr/man:/usr/share/man
&lt;/pre&gt;

The manual pages should be readable:

&lt;pre&gt;
man zpool
man zfs
&lt;/pre&gt;

After seeing the man pages, we should be fully ready to continue to setup on ZFS.

&lt;pre&gt;
(still on install-dvd)
ls -l /dev/sd*
&lt;/pre&gt;

Make sure the disk devices you expect are there. We'll use sda and make boot (/boot on /dev/sda1) and root (/ on /dev/sda2) partitions.

First, some background info: A ZFS filesystem is not supported by lilo as the filesystem containing /boot, which holds lilo's 2nd stage and the linux kernel files. The on-disk format of a ZFS filesystem is often a complex raid configuration where even if lilo understood ZFS it would likely require /boot to reside in only certain simple ZFS configurations to be plainly readable to lilo. As things are, a linux root installed in a partition with ZFS filesystem needs /boot to be on another partition with a filesystem that lilo understands, such as ext4 fs. In addition, because the spl and zfs modules are not built into the kernel, and the zfs startup requires some configuration to mount the zfs root, an initial ram/root filesystem (initrd) is needed. The initrd is a gzip compressed cpio archive file that contains a small linux root operating system that is decompressed into a ramfs block device at boot up and takes initial control of the system. The initrd contains an init script that configures devices in devtmpfs mounted at /dev. For example, if using mdadm, lvm, luks, losetup, and now zfs, this init script runs all the commands to create or start these devices (one of which is the root device), mounts the root device, and then transfers system control to the init script in the mounted root filesystem. The ramfs-based root environment on the booted install-dvd or booted initrd image (in rescue command line) are small slackware installations that exist only in ram and are temporary, but while inside them you can install, upgrade, and remove slackware packages inside them using the regular package management tools; this allows you access to any kernel modules and programs as needed inside these ramfs root. Packages can be installed, upgraded, or removed permanantly in the initrd image file to manage the programs and modules required during the initrd boot stage. Also from within these ramfs initial root environments, once the root device is mounted, chroot can be used to work on the mounted root system as if it were booted; this allows one to fix problems that are occuring in the root fs init scripts that cause normal booting to fail, or to install a kernel and/or modules etc. Now on to partitioning:

&lt;pre&gt;
cgdisk /dev/sda
&lt;/pre&gt;

Here, cgdisk looks just like cfdisk, but it makes GPT partitions.

Make a partition for /boot that is about 512MiB of whatever partition type you like (8300 "Linux filesystem" is fine), or make it type bf07 "Solaris Reserved 1" if you want ZFS to maybe see the disk as if it was given as a whole disk to ZFS. Make a second partition using the remaining space with partition type bf01 "Solaris ZFS". Currently, when ZFSonLinux is given a whole disk device like /dev/sdb to use, it will automatically GPT partition it with a bf01 partition #1 that is the whole disk except a small 8MiB type bf07 partition #9 at the end of the disk (/dev/sdb1 and /dev/sb9). The small 8MiB type bf07 partition #9 is most likely reserved for use by bootloaders, like lilo, to have a /boot or other boot-related files kept there. For example, you might have /dev/sda that is totally non-ZFS for booting and /dev/sdb passed to ZFS whole where it automatically partitions sdb, but you can just use one disk here and make partitions. Let's use type 8300 for /boot to be sure nothing is confused:

&lt;pre&gt;
We'll continue with this partitioning:
Part. #    Size        Partition Type           Partition Name
           4.0 MiB     free space
   1       512.0 MiB   Linux filesystem         boot
           4.0 MiB     free space
   2       9.4 GiB     Solaris /usr &amp; Mac ZFS   root
           96.0 MiB    free space
&lt;/pre&gt;
The free space is left as a recommendation. The free space has potential uses for data recovery techniques, changing boot configuration, accomodating a replacement disk that is slightly smaller, and avoiding the end of the disk where GPT and other disk labels may need to claim space at the end of a drive to hold metadata. The "partition name" can be blank or any arbitrary name you'd like to give them.

If you are going to test a ZFS mirror or raidz configuration, then you can repeat this same partitioning on each disk. For example, for a four-disk raidz2 with /dev/sd[abcd] you might do:
&lt;pre&gt;
sgdisk -R /dev/sdb /dev/sda
sgdisk -G /dev/sdb
sgdisk -R /dev/sdc /dev/sda
sgdisk -G /dev/sdc
sgdisk -R /dev/sdd /dev/sda
sgdisk -G /dev/sdd
&lt;/pre&gt;
Then, you could use the boot partitions /dev/sd[abcd]1 in a mdadm raid1 as your boot device:
&lt;pre&gt;
mdadm --create /dev/md0 -l 1 -n 4 /dev/sd[abcd]1
&lt;/pre&gt;
In this configuration, /dev/md0 is your 4-way mirror /boot device and is used as explained in the slackware [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/README_RAID.TXT README_RAID.TXT]. The /dev/sd[abcd]2 would be given to ZFS for the raidz2 (instead of to mdadm raid). This is only an example and there are many possible configurations, including using whole un-partitioned disks; however, we will continue in this wiki with a simpler configuration with /dev/sda1 as a non-raid /boot device and /dev/sda2 in a non-raidz/non-mirror zpool.

Create a zpool called zfs-root:
&lt;pre&gt;
zpool create -m none zfs-root /dev/sda2
&lt;/pre&gt;

A zpool created like this, the normal way, is a kernel-internal block device that contains already a zfs filesystem. There is normally no entry in /dev for this device. However, it can still be referenced as a mountable device similar to how devtmpfs, proc, and sysfs are also kernel-internal mountable block devices. The -m option told zpool not to automatically mount it anywhere, and without -m the default is to always automatically mount to /zfs-root. These kinds of details are explained better elsewhere. For this situation, we do not want it automounted.

Because a zpool itself is a useable zfs fs, it has a full set of zfs "properties" to set options about the filesystem, perhaps similar to tune2fs. The "mountpoint=&lt;some place to mount&gt;" is one such property. We want it set to the special value "none":

&lt;pre&gt;
zfs get mountpoint zfs-root
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

You can also use "legacy" for the mountpoint and the management of mounting and unmounting the pool will be expected to be done using the regular "mount" and "umount" commands:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;
Later in the wiki, it is shown how to mount using "zfs mount" for mountpoint=none, and regular "mount" for mountpoint=legacy. Using mountpoint=legacy is probably the preferred setting for the zfs-root because you can use the normal mount and umount commands and do not have to change slackware /etc/rc.d/* scripts much, if any. The normal slackware scripts handle a root filesystem's mounting and remounting using the normal mount command.

On creation, the zpool zfs-root is "imported" and has a zpool status that can be viewed:
&lt;pre&gt;
zpool status zfs-root

zpool export zfs-root
zpool status zfs-root
# Now there is no status.

zpool import zfs-root
# Now it is back.
&lt;/pre&gt;
When a zpool is imported, it has it's current configuration cached in a file /etc/zfs/zpool.cache. When a zpool is exported, then it's entries in the cache file are removed and the cache file is deleted if it becomes empty. So long as the zfs kernel modules see this cache file and valid cache data inside it, ZFS considers the described zpools in the cache file to be valid as imported zpools. If the zpool.cache file is present at the time the zfs modules are loaded, then there is no further need to use the import and export zpool commands at system startup and shutdown. With root on a zfs, it is not possible to export the pool that root is on, but this is not a problem. At shutdown, the safe procedure will be to set the zfs-root property readonly=on or remount read-only and sync disks.

To avoid the requirement to import the zfs-root pool at startup, you can keep a copy of the zpool.cache file to later copy onto the initrd image to read at modules load time to have the pool reactivated without need to issue the zpool import command:
&lt;pre&gt;
cp /etc/zfs/zpool.cache /etc/zfs/zpool.cache-initrd
&lt;/pre&gt;
A warning about the zpool.cache file: Having /etc/zfs/zpool.cache present at zfs module load or module init time can be unsafe if the device names in /dev have changed since the last boot. Especially dangerous is if two hard drives have swapped names, like /dev/sda and /dev/sdb have swapped names. It is safer to not have a zpool.cache file on the system at boot and zfs module load/init time to guard against the possibility that the cache file is no longer correct. This wiki will try to show how you can use zpool.cache to import your pool if the regular zpool import command seems to always require you to force it. This wiki will also show how to not need a zpool.cache file to import normally.

A zfs filesystem will not normally allow you to mount over any files. The mountpoint is expected to be an empty directory. Remove any junk files inside the installer's /mnt because zfs won't mount over any files:

&lt;pre&gt;
rm /mnt/README
&lt;/pre&gt;

The directory /mnt is where the slackware setup expects you to mount your root for installation.

Controlling whether a zfs fs is to be mounted read-only or read-write is best managed by setting the readonly property while it is not yet mounted:
&lt;pre&gt;
zfs set readonly=on zfs-root
zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; then the options for the mount command for ro or rw mounting will work as normal also and override whatever the readonly property is set to. The readonly property does serve as a default.

Slackware expects root to be mounted readonly when /etc/rc.d/rc.S runs during normal startup, so later this is used to satisfy slackware's expectation to avoid rc.S complaining.

The zfs-root can be mounted and unmounted in two different ways:
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
zfs set mountpoint=none zfs-root
# or
mount zfs-root -t zfs /mnt
umount /mnt
&lt;/pre&gt;
If it is already mounted and you want to change it to mount somewhere else, it is best to transition it to unmounted first, then mount it in the new place.

The mount options &lt;code&gt;-o ro, -o rw, -o remount,ro, and -o remount,rw &lt;/code&gt; can also be used and will override the &lt;code&gt;readonly=on|off&lt;/code&gt; property without altering the property value. This can be confusing until you are familiar with how the two methods of mounting interact. When &lt;code&gt;mountpoint=legacy&lt;/code&gt; is set, zfs expects the regular mount and umount commands to be used to mount and unmount the dataset with the assistance of the mount.zfs helper. For now, we will continue with &lt;code&gt;mountpoint=none&lt;/code&gt;, but using legacy is also a good option.

Now, let's continue some, and mount to /mnt using the current &lt;code&gt;readonly=off&lt;/code&gt; setting (rw mount):
&lt;pre&gt;
zfs set mountpoint=/mnt zfs-root
&lt;/pre&gt;
This method of mounting will show the most detailed mount options in /etc/mtab. They are the mount options that zfs thinks are proper, and they are probably what should be kept in /etc/fstab for zfs-root until we know better.

&lt;pre&gt;
cat /etc/mtab &gt;&gt; /etc/fstab
&lt;/pre&gt;

Now edit /etc/fstab to make sure it looks right, and remove the "rw" mount option, because we want to let it use a default for that, which will come from how we set the readonly= property most of the time. Unmount again:
&lt;pre&gt;
zfs set mountpoint=none zfs-root
&lt;/pre&gt;

Mount again, now using all options from /etc/fstab:
&lt;pre&gt;
mount zfs-root
&lt;/pre&gt;

It should be mounted at /mnt, and touch /mnt/t should allow you to make the file t. Then rm it: rm /mnt/t
For installation, we want to make sure it is mounted read-write. After installation, it should mount readonly inside the initrd.

Sometimes there can be problems using the mount command, and then you can try it with the -i option:
&lt;pre&gt;
 mount -i zfs-root
 mount -i zfs-root -t zfs /mnt
&lt;/pre&gt;
but, you should not have to use -i. When using -i makes it work, it performs an "internal-only" mount and does not use any mount.&lt;fstype&gt; helper scripts that might be on the system. You can use &lt;code&gt;mountpoint=legacy"&lt;/code&gt; to avoid this small problem if you are preferring to use the regular mount and umount commands on your zfs-root.

Setup the /boot device:
&lt;pre&gt;
mkfs.ext4 /dev/sda1
mkdir /mnt/boot
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

We have both root and boot mounted where the slackware installer expects them. Unmount the dvd so setup can find it normally:
&lt;pre&gt;
umount /dev/sr0
setup
&lt;/pre&gt;

In the setup, skip straight to TARGET selection for the root device, but the setup doesn't see or understand the zfs-root, so it is not listed. This does not matter because we have mounted it already. Just skip down to a slot that say to continue, and continue on with setup. Because TARGET is skipped, you may not see the ADDITIONAL prompt (or if so, skip it too) where normally you give /dev/sda1 and have it mounted as /boot. This is also okay because we have mounted /mnt/boot already.
Because we did not give TARGET the root device or say what device /boot is on, the lilo installation will fail, or you can skip it. Otherwise, this installation process is normal.

&lt;pre&gt;
# Finish installation and exit setup, but do NOT reboot!
# There is still a lot to do before rebooting.
umount /dev/sr0
&lt;/pre&gt;

At this point, it is assumed that the setup has completed installing into /mnt. Congrats! You've installed slackware into a ZFS root!

The next steps are to prepare to use "chroot /mnt" and finish up the configuration on the installed root system and then be able to reboot onto the completed installation. Before doing chroot, copy some files from the setup environment into /mnt.

Copy the current installer /etc/fstab for later use inside the initrd. This fstab is what is proper inside the initrd, except remove option "rw" (if not done already).
&lt;pre&gt;
cp /etc/fstab /mnt/etc/fstab.initrd
&lt;/pre&gt;

The fstab.initrd will look like:
&lt;pre&gt;
 proc /proc proc defaults 0 0
 zfs-root /mnt zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
&lt;/pre&gt;

In the initrd, we want zfs-root to mount to /mnt.

Create /mnt/etc/fstab:
&lt;pre&gt;
cat /etc/mtab &gt;&gt; /mnt/etc/fstab
vi /mnt/etc/fstab
&lt;/pre&gt;

Using vi started above, edit /mnt/etc/fstab and make it have lines such as:
&lt;pre&gt;
 zfs-root / zfs defaults,atime,dev,exec,suid,xattr,nomand,zfsutil 0 0
 /dev/sda1 /boot ext4 defaults 0 2
&lt;/pre&gt;
These two lines in &lt;code&gt;/mnt/etc/fstab&lt;/code&gt; are how the mounts should be looking when root is booted. Although the fstab option for fs_passno is 0 and indicates that root (/) should not be fsck, this fs_passno option in fstab is ignored during system startup for / in rc.S because rc.S explicity runs "fsck /" which does not look at options inside fstab. Fsck doesn't work on a zfs fs, and we will deal with that problem in a moment (see below).

Mount some special mounts before chroot:
&lt;pre&gt;
mount -t devtmpfs none /mnt/dev
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
&lt;/pre&gt;

Make sure /boot is mounted:

&lt;pre&gt;
mount /dev/sda1 /mnt/boot
&lt;/pre&gt;

If you had mounted a 9p fs share to access spl and zfs packages, then unmount that now:
umount /packages

Ready, now:
&lt;pre&gt;
chroot /mnt
&lt;/pre&gt;

At this point, you should be on the installed system, and now try to configure mkinitrd and lilo. First, switch to use the generic kernel:
&lt;pre&gt;
cd /boot
rm System.map config vmlinuz
ln -s System.map-gen* System.map
ln -s config-gen* config
ln -s vmlinuz-gen* vmlinuz
&lt;/pre&gt;

We installed spl and zfs inside the live ramfs install-dvd environment, but not yet have we installed them into the root system:
&lt;pre&gt;
mount /dev/sr0 /mnt/cdrom
depmod
installpkg /mnt/cdrom/addon/spl-*.txz
depmod
installpkg /mnt/cdrom/addon/zfs-*.txz
depmod
&lt;/pre&gt;

If instead, you used a 9p share to access the spl and zfs packages, then repeat that procedure here to install them onto the root system.

Setup lilo: edit /etc/lilo.conf so it is like:
&lt;pre&gt;
  lba32
  append = " vt.default_utf8=1"
  boot = /dev/sda
  message = /boot/boot_message.txt
  prompt
  timeout = 1200
  change-rules
   reset
  vga = normal
  image = /boot/vmlinuz
   label = vmlinuz
   initrd = /boot/initrd.gz
   root = /dev/ram0
   read-write
# alternatively, the root and read-write lines
# can be this one line of kernel parameters:
#  addappend = " root=/dev/ram0 rw "
&lt;/pre&gt;

A note about initrd: The /boot/initrd.gz is a gzipped cpio archive containing a minimal BusyBox-based slackware root system that is sourced from /boot/initrd-tree. The commands "mkinitrd" and "mkinitrd -F" generates /boot/initrd-tree and /boot/initrd.gz. When using a initrd, the initial root device is normally set to root=/dev/ram0 (a ramfs block device) and allowed read-write. The kernel refers to devices in terms of "major" and "minor" numbers, and the ram0 device is assigned the block device major 1 and minor 0. This ram0 major/minor is written in hexadecimal as 0x0100 (256 in decimal). This hexademical number makes an appearance in /boot/initrd-tree/int where it runs: "echo 0x0100 &gt; /proc/sys/kernel/real-root-dev". Echoing a device code to real-root-dev is part of a deprecated initrd mechanism, but is probably harmless to leave alone as slackware has it unless you know otherwise. More information about how initrd works can be found in:
&lt;pre&gt;
/usr/src/linux/Documentation/devices.txt (info about major:minor device numbers)
/usr/src/linux/Documentation/initrd.txt  (mostly obsolete info on old initrd)
/usr/src/linux/Documentation/filesystems/ramfs-rootfs-initramfs.txt (current info on new initrd, called initramfs)
&lt;/pre&gt;
Advanced note about initrd: Slackware's mkinitrd package does not use the "pivot_root" command as documented in "initrd.txt", but instead uses "switch_root" provided by a project called BusyBox. The switch_root command changes the effective root filesystem from the initrd (unpacked in rootfs at /) to the new root filesystem (zfs-root mounted at /mnt); it overmounts rootfs / with zfs-root /mnt. The switch_root works as follows: delete everything in rootfs / (one filesystem only) that held initrd to free up ram memory, then use mount, chroot, and chdir to make the effective root change. In concept (as a shell script), the command "exec switch_root /mnt $INIT $RUNLEVEL" is performed as follows:
&lt;pre&gt;
 find / -xdev | xargs rm -rf
 cd "$1"
 shift
 mount --move . /
 exec chroot . "$@"
&lt;/pre&gt;
Here, typically INIT=/sbin/init RUNLEVEL=3. The 'exec' causes switch_root to take the place of the parent process having PID=1. In system calls, the switch_root looks similar to this:
&lt;pre&gt;
chdir("/mnt");
/* &lt;insert code to unlink/rmdir all initrd files/directories
 *  installed in rootfs / without crossing filesystems &gt; */
mount(".", "/", NULL, MS_MOVE, NULL);
chroot(".");
chdir("/");
execl("/sbin/init", "3", (char*) NULL );
&lt;/pre&gt;
The kernel's rootfs / that contained initrd is never actually unmounted (it can't be) because it is built into the kernel and always exists as at least a tiny ramfs or tmpfs, so you can continue to see it in /proc/mounts. When you give lilo root=/dev/ram0 (a ramfs device), the kernel will actually use the internal rootfs, which is an instance of a tmpfs (if your kernel config includes tmpfs) or ramfs. The rootfs that is a tmpfs can by default use up to half of system ram. If rootfs is a ramfs, it can use up to almost all of system ram until the system panics. Typically, tmpfs is built into the kernel, and so depending on how much ram your computer has, the initrd-tree can probably be up to about half that size.

Quite a lot of notes... now to continue on...

Setup mkinitrd:
&lt;pre&gt;
cp /etc/mkinitrd.conf.sample /etc/mkinitrd.conf
vi /etc/mkinitrd.conf
&lt;/pre&gt;

Edit it to look like this (other defaults should be ok):
&lt;pre&gt;
 MODULE_LIST="sym53c8xx:ext4:e1000:zfs:9p:9pnet_virtio"
 ROOTDEV="zfs-root"
 ROOTFS="zfs"
#Module sym53c8xx is the driver for qemu's if=scsi drive device.
#Module ext4 for /boot.
#Module e1000 for eth0 net device.
#Module zfs for ZFSonLinux.
#Modules 9p and 9pnet_virtio for mounting qemu -virtfs mount_tag.
&lt;/pre&gt;

These 9p modules could be useful from the rescue command line inside the initrd to get needed files that are on the host.

All dependent modules will also be included automatically into /boot/initrd-tree, which is packaged as /boot/initrd.gz. For example, to see the dependent modules of zfs:
&lt;pre&gt;
modprobe --show-depends zfs
&lt;/pre&gt;

All listed modules will also be in the initrd. Now, make a /boot/initrd-tree that we can begin to look at and edit:
&lt;pre&gt;
mkinitrd
&lt;/pre&gt;

Create an empty /etc/mtab or else zpool import fails (zfs expects /etc/mtab to exists already, it won't make it):
&lt;pre&gt;
touch /boot/initrd-tree/etc/mtab
&lt;/pre&gt;

Copy in the fstab.initrd that was made earlier while on the installer. This provides all the mount options for a simple "mount zfs-root" onto /mnt:
&lt;pre&gt;
cp /etc/fstab.initrd /boot/initrd-tree/etc/fstab
&lt;/pre&gt;

More package installing! This time into an alternate root, the root of the initrd, /boot/initrd-tree. This is how you can put whatever packages you like into your initrd. These installations work independent of your normal installations. You can install, upgrade, and remove packages using an altroot:

If spl and zfs are on your customized dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/spl-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/addon/zfs-*.txz
&lt;/pre&gt;
Otherwise, repeat same procedure but you mount your 9p mount_tag and get them installed.

More regular packages from the dvd:
&lt;pre&gt;
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/kmod-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/coreutils-*.txz
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/gptfdisk-*.txz

# A bash script is in /boot/initrd-tree/lib/udev/, so we need it or udev rules have problems:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/a/bash-*.txz
# Bash needs this:
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/l/libtermcap-*.txz

# Install net-tools to ensure that /etc/HOSTNAME, /etc/hosts, and potentially, /etc/hostid are handled proper.
installpkg --root /boot/initrd-tree /mnt/cdrom/slackware64/n/net-tools-*.txz
&lt;/pre&gt;

When ZFS has to import a zpool while the initrd is running (this can be avoided by not exporting and keeping /etc/zfs/zpool.cache inside the initrd), ZFS will refuse to import a pool if it thinks that the pool may be in use by another system. ZFS was designed for network attached storage (NAS) where multiple hosts might have access to the same disks but ZFS cannot support two hosts importing and using a ZFS pool at the same time (that requires a "cluster" fs). ZFS checks a value called "hostid" to determine this kind of conflict, and it can be a tricky issue with an initrd boot process. The value of hostid is returned by the gethostid() function or the hostid command. This function will return the hostid from /etc/hostid if that file exists and has a valid id in it, or else if the file doesn't exist it obtains a hostid number based on the hostname and ip address assigned to hostname found in /etc/hosts or in DNS. If the hostid trying to import a pool is not the same as the hostid that imported it last time, ZFS will not import the pool unless "zpool import -f zfs-root" is used to force the import. This force option is not recommended to use, so it is best to configure your initrd with matching /etc/HOSTNAME and /etc/hosts as on the root installation and ensure what your system looks like on the initrd matches the booted root system. The hostid can also be passed to the SPL module with the module parameter &lt;code&gt;spl.spl_hostid=0xHHHHHHHH&lt;/code&gt; where the Hs are a hexadecimal hostid value and this overrides any /etc/hostid or hostname/IP-based hostid value.

Edit /boot/initrd-tree/init (this is the main system startup script on the initrd, responsible for configuring your block devices, mounting root at /mnt, and booting root):

Inside init, right near the top of the file after the PATH= line, add this:
&lt;pre&gt;
/bin/hostname -F /etc/HOSTNAME
/bin/hostname $( /bin/hostname -s )
#/sbin/chhostid 13371400
# you can make your hostid whatever, but this didn't work right with ZFS, so it is commented out
&lt;/pre&gt;
This sets the name reported by the hostname command (the default is "darkstar") to be what is contained in /etc/HOSTNAME. The hostname is modified in the next line to be the short hostname. These lines will help ZFS to properly identify your host when importing pools.

Inside init, right after it runs "mdadm" commands as used for raid setup, we like it to setup ZFS, so add:
&lt;pre&gt;
/sbin/zpool import zfs-root
/sbin/zfs set readonly=on zfs-root
mount zfs-root
&lt;/pre&gt;
We want to make sure the default is to mount readonly, then it mounts using defaults from /etc/fstab inside the initrd.

Inside init, close to the bottom, where it "Switch to real root partition", comment out 1 line that normally does the mount:
&lt;pre&gt;
# mount -o ro -t $ROOTFS $ROOTDEV /mnt
&lt;/pre&gt;
We have already mounted zfs-root, and we don't want to use any mount options because we should be using a properly set /etc/fstab inside the initrd for the zfs-root mount options onto /mnt.

During a normal startup we want a readonly mount.

Note: we are going to setup with using "zpool import" and "zpool export" commands at startup and shutdown. But later, you can experiment having /etc/zfs/zpool.cache stored in the initrd and commenting out the zpool import/export lines. Using zpool import/export is safer than using a zpool.cache, so we try to setup that way preferably.

As mentioned, the zpool import command may sometimes fail, and give the message: "pool may be in use from another system". This is nothing serious in this test situation. When this happens, zfs-root will not get mounted to /mnt and the init script will detect this and drop you into a rescue command line where you may manually do:
&lt;pre&gt;
zpool import -f zfs-root
mount zfs-root
exit
&lt;/pre&gt;
This will force import, overriding the conflict that zfs thinks may be happening. Next is mount. After this, exit to let the init script continue on to boot the system normally.

To avoid this problem we copy some files in (assuming you first edit /etc/HOSTNAME to hold the hostname you like to see on your command prompts, and edited /etc/hosts to have hostname on your loopback or other local ip address):
&lt;pre&gt;
cp /etc/HOSTNAME /etc/hosts /boot/initrd-tree/etc
&lt;/pre&gt;
The value reported by the hostid command is what ZFS sees as your hostid (the SPL module actually tries to run the hostid command to get this value or it uses the spl.spl_hostid value that is given to it). In this setup so far, the value is based on the ip assigned to your hostname. If your hostname is on the line in /etc/hosts for ip address 192.168.13.37, then your hostid will be hex numbers C0.A8.0D.25 rearranged as A8C0250D (pairs of bytes are swapped). This is a ip-based hostid value, a 32bit hexadecimal number. The hostid has to be the same each boot or import will need a -f option to force it. Simply setting the hostid using the function sethostid() which writes a /etc/hostid file doesn't seem to agree with ZFS and you'd have to force the import, so this setup now assumes that you do not have or have deleted /etc/hostid.

You can sometimes see what has been happening to a zpool by using the command "zpool history -li zfs-root" to see a log of commands.

Once again, you can do away with the import and export commands by trying to have /etc/zfs/zpool.cache inside your initrd. To create zpool.cache, while on the installer or in the rescue shell of the initrd (at lilo "boot: vmlinuz rescue"):
&lt;pre&gt;
(on installer or initrd rescue shell)
zpool import zfs-root
zfs set readonly=off zfs-root
mount zfs-root
cp /etc/zfs/zpool.cache /mnt/etc/zfs/zpool.cache-initrd
cp /mnt/etc/zfs/zpool.cache-initrd /mnt/boot/initrd-tree/etc/zfs/zpool.cache
umount /mnt
zfs set readonly=on zfs-root
#mount zfs-root
#exit (to continue boot process onto rootfs mounted at /mnt)
&lt;/pre&gt;
Words of caution, again: Doing this zpool.cache approach is not necessary, and some talk suggests this is deprecated or discouraged. Although /etc/hostid setup fails to import without -f option, ip-based (hosts|dns) hostid works on booting and import works without -f option and may be the more proper way to do shutdown and startup rather than using a cache file which could become invalid and cause a problem that is difficult to understand. The contents and exact function of the cache file are not well understood by many people. As will be spammed all over this wiki, using zpool.cache is not recommended if you can avoid it because it is potentially unsafe for your pool.

Save /boot/initrd-tree/init and quit vi.

Now, edit /etc/rc.d/rc.S and rc.6 to understand how to remount rw or ro as readonly property changes:

In /etc/rc.d/rc.S:
&lt;pre&gt;
# comment out the line
#    /sbin/mount -w -v -n -o remount /
#add the line
     /sbin/zfs set readonly=off zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6:
&lt;pre&gt;
# before: echo "Unmounting local file systems."
# add lines:
  rm -f /etc/zfs/zpool.cache
  echo "Removed /etc/zfs/zpool.cache"
&lt;/pre&gt;
Remove /etc/zfs/zpool.cache on shutdown. This is recommended because if it is present when you import a pool, it might use this old cache to determine the device filenames in the pool, which may have changed filenames since the last boot, especially the non-persistent /dev/sd* device filenames. It is safest to avoid any usage of the zpool.cache file at boot in initramfs, zfs module load, and at zpool import of other pools.

It is also possible to prevent &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; from ever being created by using the zfs module option 'spa_config_path=' to tell the zfs module not to use any zpool.cache file (a blank filename). To set this zfs module option, do the following:
&lt;pre&gt;
echo options zfs spa_config_path= &gt; /etc/modprobe.d/zfs.conf
cp -a /etc/modprobe.d /boot/initrd-tree/etc
&lt;/pre&gt;
If zfs is built into the kernel (see [http://slackwiki.com/ZFS_root_%28builtin%29 ZFS root (builtin)]), then this zfs module option is set as a kernel parameter: &lt;code&gt;zfs.spa_config_path=&lt;/code&gt;

In /etc/rc.d/rc.6:
&lt;pre&gt;
# comment out the line:
#    /bin/mount -v -n -o remount,ro /
# add the line:
     /sbin/zfs set readonly=on zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, you do not need to make the above change.

In /etc/rc.d/rc.6, near the bottom just before poweroff|reboot, add the following block of lines:
&lt;pre&gt;
########################
# Try to export zfs-root
/sbin/zpool export zfs-root
if [ $? -gt 0 ] ; then
 echo "ZFS export failed."
 echo "Notice: if root fs is busy, then this is normal fail."
else
 echo "ZFS export successful."
 echo "Warning: successful export is abnormal for root fs."
fi
/bin/sleep 5
########################
&lt;/pre&gt;
This attempts to export even though it cannot return success for the root pool. The attempt is still recorded in the zpool history, and even though it fails the pool may actually be marked as exported (not sure).

For ZFS, you cannot run fsck on it. It doesn't support that kind of filesystem check. The rc.S script will complain a lot in many places about not being able to run fsck on the zfs-root. To disable all attempts to run fsck, we can simply create a file that acts as a flag in /etc/rc.d/rc.S to tell it to skip fsck:
&lt;pre&gt;
touch /etc/fastboot
&lt;/pre&gt;

This fastboot file is normally a run-once temporary file, and it is deleted near the bottom inside rc.S. Edit rc.S and stop it from deleting /etc/fastboot. We would like it to always skip all fsck. Edit /etc/rc.d/rc.S, and find the "rm" of fastboot, and do not have it removed!

An alternative to using /etc/fastboot is to make the file &lt;code&gt;/sbin/fsck.zfs&lt;/code&gt; that always just "does nothing successfully":
&lt;pre&gt;
#!/bin/sh
exec /bin/true
&lt;/pre&gt;
Or, it can be:
&lt;pre&gt;
#!/bin/sh
exit 0
&lt;/pre&gt;
Or, just do:
&lt;pre&gt;
ln -s /bin/true /sbin/fsck.zfs
&lt;/pre&gt;
This fsck helper has the advantage that you do not need to alter &lt;code&gt;rc.S&lt;/code&gt; as much, or at all if you use zfs property &lt;code&gt;mountpoint=legacy&lt;/code&gt; and the regular &lt;code&gt;mount&lt;/code&gt; command on your zfs-root. With these ideas, no slackware /etc/rc.d/* files really need editing, but it is up to you how you want to experiment. I prefer to use &lt;code&gt;mountpoint=legacy&lt;/code&gt; and edit just the initrd init script as above, and edit rc.6 to remove /etc/zfs/zpool.cache and try to export.

We are getting close, and have finished all editing, so make /boot/initrd.gz and install lilo:
&lt;pre&gt;
mkinitrd -F
lilo
&lt;/pre&gt;

We finished! All that's left to do is clean up.

Exit the chroot.
&lt;pre&gt;
exit
&lt;/pre&gt;
Try to umount everything:
&lt;pre&gt;
umount /mnt/proc
umount /mnt/sys
umount /mnt/dev
umount /mnt/boot
umount /mnt/mnt/cdrom
umount /mnt/root/packages
umount /mnt
zpool export zfs-root
&lt;/pre&gt;

Note, that export stops a pool and frees devices, while import binds devices and starts a pool. It is somewhat like mdadm -A -s and mdadm -S -s, while /etc/zfs/zpool.cache might be somewhat like mdadm -E -s &gt; /etc/mdadm.conf.

&lt;pre&gt;
# Remove the DVD or change boot order
reboot
&lt;/pre&gt;

When you reboot, if all is good, you are booting properly onto a slackware installed on a ZFS root! Congrats!

If this seems to go badly, and this might happen if the import fails as explained some before, then you will be on the initrd's rescue command line just before the part in init where it wants to mount zfs-root and switch_root to boot up. In this case, you typically got commands like these to do:

If you get dumped to rescue because zpool import will not work and requires -f (force), then:
&lt;pre&gt;
 zpool import -f zfs-root
 zpool export    zfs-root
 zpool import    zfs-root
 mount zfs-root
 exit
&lt;/pre&gt;
This can happen if hostname, hostid, or uname changes.

If you get into a jam and need to boot into the initrd and skip zpool import etc, use the lilo prompt (or, boot the install-dvd):
&lt;pre&gt;
boot: vmlinuz rescue
&lt;/pre&gt;
In the rescue mode of the initrd, after you have mounted your zfs-root as readonly=on to /mnt, then "exit" to continue booting.

An alternative rescue shell on the initrd can be started as follows:
&lt;pre&gt;
boot: vmlinuz rdinit=/bin/sh
&lt;/pre&gt;
This puts you into a sh shell inside the initrd, and the normal /init script is not run at all. In this shell, you can fix problems and then attempt to start the system normally as follows:
&lt;pre&gt;
exec /init
&lt;/pre&gt;
This runs the normal rdinit program, "execing" it so that it takes process ID (PID) 1 of your sh shell, which is the required PID for the init program.

In other emergency command lines, you might need to run the lines at the end of init starting from: &lt;code&gt;udevadm info --cleanup-db; udevadm control --exit&lt;/code&gt;
If you don't run those udevadm commands, two runs of udevd could fight each other and it is slow; you have to wait 2 minutes twice for timeouts (4 minutes).
The last line in init is run like: &lt;code&gt;exec switch_root /mnt /sbin/init 1&lt;/code&gt;

Warning: the switch_root command is kind of dangerous, so read the manual page about it. From what I can tell, everything except the new root "/mnt" is deleted, so you are giving a command that says what NOT to delete! Make sure nothing got mounted outside of "/mnt" before you run it. However, the deletes should not cross filesystems, but only delete the contents of initramfs.

Also, in rescue command line or anytime you have finished making changes and are about to reboot in some abnormal situation, first run:
&lt;pre&gt;
zfs set readonly=on zfs-root
&lt;/pre&gt;
If you are using &lt;code&gt;mountpoint=legacy&lt;/code&gt; for zfs-root, then you may want to use &lt;code&gt;readonly=off&lt;/code&gt; and use the options to the &lt;code&gt;mount&lt;/code&gt; command to control ro|rw mounting. With &lt;code&gt;mountpoint=legacy&lt;/code&gt; and &lt;code&gt;readonly=on&lt;/code&gt; used together, there can be a contradiction between how the kernel actually mounts zfs-root (ro according to the readonly property) and how the userspace mount command and /etc/mtab attempt to mount the zfs-root (if you give &lt;code&gt;-o rw&lt;/code&gt;). The kernel might actually mount ro, even when you have told the mount command to mount rw. The /etc/mtab can erroneously report rw, while the kernel's /proc/mounts file reports the actual mount as ro. Again, the two methods of mounting a zfs fs, either "legacy" &lt;code&gt;mount&lt;/code&gt; command or by using the &lt;code&gt;zfs set mountpoint&lt;/code&gt; can conflict with each other on the mode of mounting. If you create a zfs filesystem under zfs-root, like &lt;code&gt;zfs create "zfs-root/movies"&lt;/code&gt; and then try to mount it, it may have inherited &lt;code&gt;mountpoint=legacy&lt;/code&gt; and &lt;code&gt;readonly=on&lt;/code&gt; from zfs-root, and it may mount ro even if you use the rw mount option: in this case, you have to do another command &lt;code&gt;mount -o remount,rw "zfs-root/movies"&lt;/code&gt; to make it actually switch to rw (kind of weird!).

A bug in unpatched grep 2.13 build 1, found slackware 14.0rc1, causes problems when processing files stored on ZFS but rarely shows problems on other filesystems; the bug does not handle sparse files on zfs and btrfs correctly and results in chaos with slackpkg, compiling kernel modules, and possibly many other things. You must downgrade grep to 2.12 or use the patched grep 2.13 build 2 in slackware 14.0rc2 or later.

----
Upgrading:

From time to time you will want to upgrade the kernel to the new kernel in slackware64-current or in patches/. This will also necessitate a rebuild and reinstall or upgrade of spl and zfs. Below is an example of when both kernel and spl/zfs are being upgraded, to give an idea of the process:

Using slackpkg, that is configured to use your local slackware mirror is a good option but you can also configure it to use a remote mirror.

&lt;pre&gt;
slackpkg upgrade-all
&lt;/pre&gt;
Assume slackpkg just upgraded your kernel, kernel-modules, kernel-headers, and kernel-source.

Note: the first time you try to run on kernel-generic, setup kernel-huge in lilo as 2nd choice. Huge has all the hard drive controllers builtin, but generic has them all as modules. For example, run "modinfo mptsas" to see module options (maybe you have a LSISAS1068) for your hard drive controller. Add file /etc/modprobe.d/mptsas.conf to set options you want with a line: options mptsas ... Do this for all the device driver modules for your hardware. Do this setup while you are on the huge kernel, then setup to reboot to generic. Include all these modules you need into mkinitrd.conf MODULES_LIST. Check that /boot/initrd-tree/etc/modprobe.d/ has a copy of your customized module conf files because it is on the initrd where the modules will load and use the conf files. mkinitrd probably copies all /etc/modprobe.d/* files into the initrd-tree, but check it. Pay attention to /etc/modprobe.d/README and /lib/modprobe.d/* /lib/modprobe.d/* maybe not copied to initrd-tree but you might want to copy some of it into your initrd-tree yourself to use them.


Check that upgraded kernel-source is symlinked to /usr/src/linux (zfs build looks here). SPL/ZFS modules will install to the kernel version in /lib/modules/&lt;/usr/src/linux kernel version&gt;
&lt;pre&gt;
cd /usr/local/src
tar xvzf ~/spl-*.tar.gz
tar xvzf ~/zfs-*.tar.gz

###### upgrade spl 1st
mkdir install
cd spl-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod &lt;new kernel version&gt;     (e.g. depmod 3.2.28, if .28 is new kernel upgrade; you currently run on old, maybe .27)
# this builds the module dependencies in /lib/modules/&lt;new kernel version&gt;
###### upgrade zfs 2nd
mkdir install
cd zfs-*
./configure --prefix=/ --libexecdir=/usr/libexec --libdir=/lib64 --includedir=/usr/include --datarootdir=/usr/share
make
make install DESTDIR=/usr/local/src/install
cd ../install
makepkg ../zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
cd ..
rm -r install
upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
depmod 3.2.28
####### upgrade spl/zfs inside altroot /boot/initrd-tree
ROOT=/boot/initrd-tree upgradepkg spl-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
ROOT=/boot/initrd-tree upgradepkg zfs-&lt;version&gt;rcX_&lt;kernel version&gt;-x86_64-Xroot.txz
# note: ROOT is an environment variable, not a command line option to upgradepkg!
# note: do not worry about depmod inside initrd-tree, mkinitrd -F actually installs the modules
# note: this upgrade here is really to just upgrade the command line tools zpool, zfs etc
####### rebuild /boot/initrd.gz and reinstall lilo
vi /etc/mkinitrd.conf
# temporarily set KERNEL_VERSION to new version, but you are still running on old version
mkinitrd -F
lilo
vi /etc/mkinitrd.conf
# you can set KERNEL_VERSION back to $(uname -r) now
reboot
&lt;/pre&gt;

After reboot you can remove any old /lib/modules/&lt;old kernel version&gt; directory.

----
More about /etc/hostid. If you want to experiment changing your /etc/hostid file and seeing if you can use it and make zpool import work normally, here is a tool that might be helpful:
&lt;pre&gt;
/* software product name: foobarz-chhostid.c
 * suggested binary name: chhostid
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_CHHOSTID_VERSION "1.0.5"
#include &lt;sys/socket.h&gt;
#include &lt;netinet/in.h&gt;
#include &lt;arpa/inet.h&gt;
#include &lt;stdio.h&gt;
#include &lt;endian.h&gt;
#include &lt;string.h&gt;
#include &lt;errno.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sysexits.h&gt;
/* note: if include stdlib then sethostid fails even with _BSD_SOURCE defined */

long swapbytes(long abcd) {
  long badc;
  unsigned char addr_a;
  unsigned char addr_b;
  unsigned char addr_c;
  unsigned char addr_d;
  addr_a = (unsigned char) (abcd &gt;&gt; 24);
  addr_b = (unsigned char) (abcd &gt;&gt; 16);
  addr_c = (unsigned char) (abcd &gt;&gt;  8);
  addr_d = (unsigned char) (abcd);
  return badc = ( (addr_b &lt;&lt; 24) | (addr_a &lt;&lt; 16) | (addr_d &lt;&lt; 8) | addr_c );
}

int main(int argc, char* argv[])
{
 long newhostid;
 struct in_addr addr;
 char* invalidchar;

 /*********** check command line */
 if(!( ((argc==3) &amp;&amp; ( (strcmp(argv[1],"-h")==0) ||
                       (strcmp(argv[1],"-i")==0) ||
                       (strcmp(argv[1],"-l")==0) )) ||
       ((argc==2) &amp;&amp; ( (strcmp(argv[1],"-s")==0) ))
     )
   ) {
                 /*01234567890123456789012345678901234567890123456789012345678901234567890123456789*/
  fprintf(stderr, "foobarz-chhostid, version %s. License: BSD.\n", FOOBARZ_CHHOSTID_VERSION);
  fprintf(stderr, "foobarz-chhostid, (c) 2012, foobarz; all rights reserved.\n");
  fprintf(stderr, "descr: %s change system hostid (in /etc/hostid).\n", argv[0]);
  fprintf(stderr, "usage: %s -h &lt;new hostid&gt;\n"
                  "        Change system hostid to &lt;new hostid&gt;;\n"
                  "        &lt;new hostid&gt; must be 32bit 8-digit hex number xxxxxxxx, each x in 0-f|F.\n"
                  "        The ip corresponding to &lt;new hostid&gt; is also listed for reference only.\n", argv[0]);
  fprintf(stderr, "usage: %s -i &lt;dotted ip address&gt;\n"
                  "        Change system hostid to hostid corresponding to &lt;dotted ip address&gt;.\n", argv[0]);
  fprintf(stderr, "usage: %s -l &lt;dotted ip address&gt;\n"
                  "        List hostid corresponding to &lt;dotted ip address&gt;;\n"
                  "        no change to system hostid.\n", argv[0]);
  fprintf(stderr, "usage: %s -s\n"
                  "        List current system hostid and corresponding ip address;\n"
                  "        no change to system hostid.\n", argv[0]);
  return EX_USAGE;
 }

 /*********** -h &lt;hostid&gt; */
 if( strcmp(argv[1],"-h") == 0 ) {
  if(strlen(argv[2]) != 8) { fprintf(stderr, "new hostid must be 8-digit hex number xxxxxxxx, each x in 0-f|F\n"); return EX_USAGE; }

  newhostid = strtol(argv[2],&amp;invalidchar,16);
  if( newhostid==LONG_MIN ) { perror("strtol (underflow)"); return EX_USAGE; }
  if( newhostid==LONG_MAX ) { perror("strtol (overflow)"); return EX_USAGE; }
  if(*invalidchar != '\0') { fprintf(stderr, "invalid hex number %c; must be in 0-f|F\n", *invalidchar); return EX_USAGE; }

  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));
 }

 /*********** -i or -l, then find hostid for &lt;dotted ip address&gt; */
 if( (strcmp(argv[1],"-i") == 0) || (strcmp(argv[1],"-l") == 0) ) {
  if( inet_aton(argv[2], &amp;addr) == 0 ) { fprintf(stderr, "inet_aton: invalid dotted ip address: %s\n", argv[2]); return EX_USAGE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get hostid by swapping bytes of ip a.b.c.d */
  newhostid = swapbytes(ntohl(addr.s_addr));
 }

 /*********** -i &lt;dotted ip address&gt; */
 if( strcmp(argv[1],"-i") == 0 ) {
  if( sethostid(newhostid) != 0 ) {
   perror("sethostid");
   if( errno == EPERM ) return EX_NOPERM;
   return EX_UNAVAILABLE;
  }
  printf("System hostid changed.\n");
 }

 /*********** -l &lt;dotted ip address&gt; */
 if(strcmp(argv[1],"-l") == 0 ) {
   printf("Listing hostid for ip. (no changes)\n");
 }

 /*********** -s */
 if(strcmp(argv[1],"-s") == 0 ) {
   /* see if /etc/hostid exists and print info */
   if( access("/etc/hostid", F_OK) != 0 ) {
     printf("Notice: /etc/hostid does not exist.\n");
     perror("Reason");
     printf("System hostid derived from ip of hostname found in hosts file or dns.\n");
   } else {
     printf("Notice: /etc/hostid exists.\n"
            "System hostid is obtained from hostid file.\n");
   }

  errno=0;
  newhostid = gethostid();
  if(errno!=0) { perror("gethostid"); return EX_UNAVAILABLE; }

  /* hostid is a byte-swapped ip like b.a.d.c */
  /* get ip by swapping to correct order a.b.c.d and save into in_addr struct */
  addr.s_addr = htonl(swapbytes(newhostid));

  printf("Listing current system hostid. (no changes)\n");
 }

 /*********** print info and return */
 printf("ip dot: %s\n", inet_ntoa(addr) );
 printf("ip hex: %.8x\n", ntohl(addr.s_addr) );
 printf("hostid: %.8x\n", newhostid );
 return EX_OK;
}
&lt;/pre&gt;
----
Now available! "ZFS root (builtin)" wiki (aka "ZFS root, part II"):
http://slackwiki.com/ZFS_root_(builtin)
It is now possible to build the modules and a small initramfs into your kernel to have a fully-contained and bootable ZFS root kernel from a simple lilo entry. Good luck!</text>
    <sha1>a552a5e8d00ffd26453f69c6801f2dd23d0f6f44</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>ZFS root (builtin)</title>
  <ns>0</ns>
  <id>291</id>
  <revision>
    <id>784</id>
    <parentid>779</parentid>
    <timestamp>2012-09-09T04:31:02Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="28906" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command

# You might think to set bootfs property like this:
#  zpool set bootfs=zfs-root zfs-root
# however, this will result in ZFS placing many restrictions on zfs-root as per how that option
#  is used on Solaris systems:
#  * zfs-root must be VTOC (SMI) label, not GPT (EFI) label
#  * zfs-root can only contain 1 vdev: either a plain disk, or a mirror
# so, do not set that property!
# If bootfs is set, you would find that you cannot add vdevs to your zfs-root.
# If it is set already, then unset it like this:
#  zpool set bootfs= zfs-root

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

#define FOOBARZ_INIT_VERSION "1.0.10rc1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

/* Your initramfs-source should contain the following
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 */

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
 };
 enum { iroot, irootfstype, imountopt, iinit, irunlevel, iconsole, ilastparam };

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = "";
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific informative checks */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

gcc --static init.c -o init
strip init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>5f0baa89e97746676b8d8d5b0d3f04066ae4282b</sha1>
  </revision>
  <revision>
    <id>785</id>
    <parentid>784</parentid>
    <timestamp>2012-09-11T03:41:19Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="34310" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
# use legacy so zfs will not expect zfs mount, but instead expect standard mount for this fs
# edit /etc/rc.d/rc.S and rc.6 to use regular "mount" commands, remove "zfs" commands
# edit rc.6 and remove or comment out zfs export command

# You might think to set bootfs property like this:
#  zpool set bootfs=zfs-root zfs-root
# however, this will result in ZFS placing many restrictions on zfs-root as per how that option
#  is used on Solaris systems:
#  * zfs-root must be VTOC (SMI) label, not GPT (EFI) label
#  * zfs-root can only contain 1 vdev: either a plain disk, or a mirror
# so, do not set that property!
# If bootfs is set, you would find that you cannot add vdevs to your zfs-root.
# If it is set already, then unset it like this:
#  zpool set bootfs= zfs-root

mkdir /boot/initramfs-source
# this will hold some files for rootfs inside kernel

cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  #  make usre you made this directory or the kernel build fails
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  #  for qemu if=scsi -option-rom 8xx_64.rom,bootindex=1  hard disks
  # buildin any hard drive controllers etc that you need
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # /boot may use this ext4 fs
make prepare scripts
# this make command is what the spl and zfs copy-builtin scripts expect to be done before they are run

cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

### move zfs and spl modules inside kernel source to be at end of drivers:
### the order builtin modules init is the order they link into the kernel
### and we need zfs to init after all hard drive controllers
### zfs is more like a device driver layer over the lower-level hba drivers

cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF

### move complete

cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS


### prepare contents of initramfs
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4

# this should be enough device nodes initially
# once devtmpfs mounts over /dev, a lot more is available in it by default

cat &gt; /init &lt;&lt;"EOF" &lt;some initial program PID=1 for the system to start on&gt; EOF
# an initramfs-source/init program is required to mount and boot a root linux system
# the common way to make /init is using busybox with files like this:
#    /bin/busybox
#    /bin/ash -&gt; busybox
#    /bin/sh -&gt; busybox
#    # run busybox to see what other "applets" can be symlinked to it
#    # when busybox is run as a different symlinked applet name, it runs the applet
#    /init
#    # init is ash script, see slackware's /boot/initrd-tree/init for example
#    Inside this script:
#      1) parse kernel parameters passed into it and set variables based on them
#      2) start udevd and trigger rules for block devices to setup initial /dev devices
#      3) load kernel modules and keyboard map
#      4) run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
#         (any udev rules for them should do more /dev setup in the background)
#      5) mount the root filesystem read-only at /mnt
#      6) stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh
#      7) shutdown udevd so it can be restarted by root system when booted
#      8) mount --move {proc,sys,run,dev} to under /mnt
#      9) run: exec switch_root /mnt /sbin/init $RUNLEVEL
#    The slackware mkinitrd package is fully configured busybox installation
#      for an extern file initramfs initrd.gz image outside the kernel.
#    It could be changed to be inside the kernel easily by just using initrd-tree
#      as target of INITRAMFS_SOURCE in the kernel config and removing initrd in lilo.

# Because the zfs modules are builtin, we really don't need busybox and the whole
# mkinitrd package. All we need to do is mount the zfs that is already imported
# because the zpool.cache is present in rootfs when the zfs module initializes, and
# then we do the switch root procedure to boot up on the mounted system.
# udevd rules will still be run when the root system starts udevd.

# So, let's make a simple /init c program that will be all that we really need:
cat &gt; init.c &lt;&lt;"EOF"
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}

EOF
## end of rootfs /init

# If foobarz-init is updated, you can find the latest version at:
# https://github.com/foobarz/foobarz-init

# The foobarz-init program can be compiled two ways as of v1.1.1:
# First, the simple compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:

gcc --static init.c -o init
strip init

# The second way to compile it adds support for zpool_import so that you do not have to include a /etc/zfs/zpool.cache file, but instead
# would add a kernel parameter: zpool_import_name=zfs-root, or zpool_import_guid=&lt;guid of zfs-root&gt;.
# You can import the root pool with a different name by also using zpool_import_newname=rpool.
# However you import, kernel param root=&lt;your root pool name or newname&gt; needs to be given also.
# The zpool_import only imports, it does not mount. What to mount is still told using root= and rootfstype=.
#
# If the import is not working, zpool_import_force=1 can be used to force it.
#
# This second way also requires you to install libtirpc first. Now here is an example gcc line:

gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc

strip init
cp init /boot/initramfs-source/init

## build and install kernel
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line.

Notes on the spl and zfs packages to install: If you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>2781c3acba1637fdb4b0413de5f50a5e944a7612</sha1>
  </revision>
  <revision>
    <id>786</id>
    <parentid>785</parentid>
    <timestamp>2012-09-12T03:44:07Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38988" xml:space="preserve">[[Category:Tutorials]]
The first "ZFS root" wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zfs export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.27b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an eariler stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;/code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Note: the zpool_import support requires that you install [http://sourceforge.net/projects/libtirpc/ libtirpc] first.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Congrats! If this works, you can select the "vm3.2.27b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>98a9e7ada0c67ded5d64fa1da2623ce88334e2de</sha1>
  </revision>
  <revision>
    <id>787</id>
    <parentid>786</parentid>
    <timestamp>2012-09-12T03:47:29Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39020" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS at your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternatve kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zfs export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.27b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an eariler stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;/code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Note: the zpool_import support requires that you install [http://sourceforge.net/projects/libtirpc/ libtirpc] first.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Congrats! If this works, you can select the "vm3.2.27b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console of booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>2312365a575698f07510de837b1d409fce053bb5</sha1>
  </revision>
  <revision>
    <id>788</id>
    <parentid>787</parentid>
    <timestamp>2012-09-12T07:24:49Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39022" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zfs export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.27b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an eariler stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Note: the zpool_import support requires that you install [http://sourceforge.net/projects/libtirpc/ libtirpc] first.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Congrats! If this works, you can select the "vm3.2.27b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>51c62d7bee8d99df3dce64fb7dd67968d071fdf9</sha1>
  </revision>
  <revision>
    <id>789</id>
    <parentid>788</parentid>
    <timestamp>2012-09-12T19:57:57Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39918" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zfs export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.27b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an eariler stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Congrats! If this works, you can select the "vm3.2.27b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>ffa83d5e54949551d9bb2a74f798941a8d627adf</sha1>
  </revision>
  <revision>
    <id>790</id>
    <parentid>789</parentid>
    <timestamp>2012-09-12T22:31:37Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="40589" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zfs export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.27b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an eariler stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Congrats! If this works, you can select the "vm3.2.27b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>5d2793d13874cfbec7f2bba565efaada233c30ba</sha1>
  </revision>
  <revision>
    <id>791</id>
    <parentid>790</parentid>
    <timestamp>2012-09-12T22:50:19Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41193" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zfs export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.27b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an eariler stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;zfs_config.h&lt;/code&gt; can be found in the kernel source when you have installed the builtin spl/zfs configuration; for example at &lt;code&gt;/usr/src/linux-3.2.27b/zfs_config.h&lt;/code&gt;. If you currently have installed the modular spl/zfs configuration, &lt;code&gt;zfs_config.h&lt;/code&gt; is found where the zfs module headers are installed; for example at &lt;code&gt;/usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h&lt;/code&gt;. Wherever it is, &lt;code&gt;-include&lt;/code&gt; it as shown in the example gcc line above. zfs_config.h seems misplaced because it would seem that using libzfs shouldn't depend on modules header files.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;

Congrats! If this works, you can select the "vm3.2.27b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>5fd81aa60eef8f863fcbcd7b88acd908d845bd66</sha1>
  </revision>
  <revision>
    <id>794</id>
    <parentid>791</parentid>
    <timestamp>2012-09-14T14:29:31Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="41768" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zpool export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.27 /usr/src/linux-3.2.27b
rm -r install
cd /usr/src/linux-3.2.27b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.27b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc10.tar.gz
mkdir install
cd spl-0.6.0-rc10
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.27b \
    --with-linux-obj=/usr/src/linux-3.2.27b \
    --with-spl=/root/src/spl-0.6.0-rc10
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.27b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc10_3.2.27b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.27b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.27b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.27b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.27b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.27b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an earlier stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;zfs_config.h&lt;/code&gt; can be found in the kernel source when you have installed the builtin spl/zfs configuration; for example at &lt;code&gt;/usr/src/linux-3.2.27b/zfs_config.h&lt;/code&gt;. If you currently have installed the modular spl/zfs configuration, &lt;code&gt;zfs_config.h&lt;/code&gt; is found where the zfs module headers are installed; for example at &lt;code&gt;/usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h&lt;/code&gt;. Wherever it is, &lt;code&gt;-include&lt;/code&gt; it as shown in the example gcc line above. zfs_config.h seems misplaced because it would seem that using libzfs shouldn't depend on modules header files.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.27b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.27b
cp System.map /boot/System.map-vm3.2.27b
# add new lilo menu entry for vm3.2.27b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.27b
   label = vm3.2.27b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;
Note: If &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; is not included in addappend, then during boot SPL module will attempt to read /etc/hostid or run a user-space helper to write the &lt;code&gt;hostid&lt;/code&gt; into &lt;code&gt;/proc/sys/kernel/spl/hostid&lt;/code&gt;. Reading /etc/hostid fails unless you use foobarz-chhostid and make the file and copy it into /boot/initramfs-source/etc/hostid. The helper will fail because no &lt;code&gt;sh&lt;/code&gt; shell and no &lt;code&gt;hostid&lt;/code&gt; command are installed in the initramfs. The default hostid becomes 0xffffffff, which is considered an invalid hostid.

Congrats! If this works, you can select the "vm3.2.27b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc10_3.2.27b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.27b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>312c5aed942f06c568d1cf9e6f5674693073767d</sha1>
  </revision>
  <revision>
    <id>798</id>
    <parentid>794</parentid>
    <timestamp>2012-09-19T10:49:36Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42822" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zpool export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.28 /usr/src/linux-3.2.28b
rm -r install
cd /usr/src/linux-3.2.28b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.28b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc11.tar.gz
mkdir install
cd spl-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.28b \
    --with-linux-obj=/usr/src/linux-3.2.28b
wget https://raw.github.com/zfsonlinux/spl/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.28b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc11_3.2.28b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc11.tar.gz
mkdir install
cd spl-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.28b \
    --with-linux-obj=/usr/src/linux-3.2.28b \
    --with-spl=/root/src/spl-0.6.0-rc11
wget https://raw.github.com/zfsonlinux/zfs/master/copy-builtin
chmod +x copy-builtin
./copy-builtin /usr/src/linux-3.2.28b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc11_3.2.28b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.28b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.28b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.28b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.28b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.28b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

It is time to pause for a moment here and talk about zpool.cache: Using it is actually dangerous. We are not using udev and it's persistent block device filenames (/dev/disk/by-*), but are using the default kernel block device names (/dev/sd*) in devtmpfs. Device names for a hard drive in /dev can potentially change on boot depending on disk controller initialization order and disk drive response time. Adding another disk controller or hard disk on a controller can result in device name assignment changes to all the hard disks. A zpool.cache file holds all the zfs_member device filenames /dev/sd* for a pool configuration, but the zpool.cache configuration will be incorrect if device filenames have been changed or swapped around and this could result in a faulted pool that may or may not be recoverable. Using zpool.cache to import pools at boot, even with udev persistent device filenames, is potentially destructive if devices have been changed around. The proper thing to do is zpool_import and do not include zpool.cache in the initramfs.

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an earlier stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc11/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/zfs-0.6.0-rc11/3.2.28/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;zfs_config.h&lt;/code&gt; can be found in the kernel source when you have installed the builtin spl/zfs configuration; for example at &lt;code&gt;/usr/src/linux-3.2.28b/zfs_config.h&lt;/code&gt;. If you currently have installed the modular spl/zfs configuration, &lt;code&gt;zfs_config.h&lt;/code&gt; is found where the zfs module headers are installed; for example at &lt;code&gt;/usr/src/zfs-0.6.0-rc11/3.2.28/zfs_config.h&lt;/code&gt;. Wherever it is, &lt;code&gt;-include&lt;/code&gt; it as shown in the example gcc line above. zfs_config.h seems misplaced because it would seem that using libzfs shouldn't depend on modules header files.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.28b
cp System.map /boot/System.map-vm3.2.28b
# add new lilo menu entry for vm3.2.28b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.28b
   label = vm3.2.28b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;
Note: If &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; is not included in addappend, then during boot SPL module will attempt to read /etc/hostid or run a user-space helper to write the &lt;code&gt;hostid&lt;/code&gt; into &lt;code&gt;/proc/sys/kernel/spl/hostid&lt;/code&gt;. Reading /etc/hostid fails unless you use foobarz-chhostid and make the file and copy it into /boot/initramfs-source/etc/hostid. The helper will fail because no &lt;code&gt;sh&lt;/code&gt; shell and no &lt;code&gt;hostid&lt;/code&gt; command are installed in the initramfs. The default hostid becomes 0xffffffff, which is considered an invalid hostid.

Congrats! If this works, you can select the "vm3.2.28b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc11_3.2.28b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.28b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>aef6529f2ca0f2592a21cd771dc178a812552485</sha1>
  </revision>
  <revision>
    <id>799</id>
    <parentid>798</parentid>
    <timestamp>2012-09-19T13:26:56Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42888" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zpool export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.28 /usr/src/linux-3.2.28b
rm -r install
cd /usr/src/linux-3.2.28b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.28b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc11.tar.gz
mkdir install
cd spl-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.28b \
    --with-linux-obj=/usr/src/linux-3.2.28b
./copy-builtin /usr/src/linux-3.2.28b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc11_3.2.28b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc11.tar.gz
mkdir install
cd zfs-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.28b \
    --with-linux-obj=/usr/src/linux-3.2.28b \
    --with-spl=/root/src/spl-0.6.0-rc11
    --with-spl-obj=/root/src/spl-0.6.0-rc11
./copy-builtin /usr/src/linux-3.2.28b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc11_3.2.28b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we can move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers. This move is &lt;bold&gt;optional&lt;/bold&gt; and you can skip doing this and everything will probably work fine, but it is shown here how to move the modules to under drivers in case you prefer them there:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.28b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.28b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.28b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.28b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.28b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

It is time to pause for a moment here and talk about zpool.cache: Using it is actually dangerous. We are not using udev and it's persistent block device filenames (/dev/disk/by-*), but are using the default kernel block device names (/dev/sd*) in devtmpfs. Device names for a hard drive in /dev can potentially change on boot depending on disk controller initialization order and disk drive response time. Adding another disk controller or hard disk on a controller can result in device name assignment changes to all the hard disks. A zpool.cache file holds all the zfs_member device filenames /dev/sd* for a pool configuration, but the zpool.cache configuration will be incorrect if device filenames have been changed or swapped around and this could result in a faulted pool that may or may not be recoverable. Using zpool.cache to import pools at boot, even with udev persistent device filenames, is potentially destructive if devices have been changed around. The proper thing to do is zpool_import and do not include zpool.cache in the initramfs.

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an earlier stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc11/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/linux-3.2.28b/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;zfs_config.h&lt;/code&gt; can be found in the kernel source when you have installed the builtin spl/zfs configuration; for example at &lt;code&gt;/usr/src/linux-3.2.28b/zfs_config.h&lt;/code&gt;. If you currently have installed the modular spl/zfs configuration, &lt;code&gt;zfs_config.h&lt;/code&gt; is found where the zfs module headers are installed; for example at &lt;code&gt;/usr/src/zfs-0.6.0-rc11/3.2.28/zfs_config.h&lt;/code&gt;. Wherever it is, &lt;code&gt;-include&lt;/code&gt; it as shown in the example gcc line above. zfs_config.h seems misplaced because it would seem that using libzfs shouldn't depend on modules header files.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.28b
cp System.map /boot/System.map-vm3.2.28b
# add new lilo menu entry for vm3.2.28b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.28b
   label = vm3.2.28b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;
Note: If &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; is not included in addappend, then during boot SPL module will attempt to read /etc/hostid or run a user-space helper to write the &lt;code&gt;hostid&lt;/code&gt; into &lt;code&gt;/proc/sys/kernel/spl/hostid&lt;/code&gt;. Reading /etc/hostid fails unless you use foobarz-chhostid and make the file and copy it into /boot/initramfs-source/etc/hostid. The helper will fail because no &lt;code&gt;sh&lt;/code&gt; shell and no &lt;code&gt;hostid&lt;/code&gt; command are installed in the initramfs. The default hostid becomes 0xffffffff, which is considered an invalid hostid.

Congrats! If this works, you can select the "vm3.2.28b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc11_3.2.28b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.28b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>8a22a71d66f1e40dc618031f34f97ac80c355170</sha1>
  </revision>
  <revision>
    <id>800</id>
    <parentid>799</parentid>
    <timestamp>2012-09-19T13:28:18Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="42882" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zpool export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.28 /usr/src/linux-3.2.28b
rm -r install
cd /usr/src/linux-3.2.28b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.28b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc11.tar.gz
mkdir install
cd spl-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.28b \
    --with-linux-obj=/usr/src/linux-3.2.28b
./copy-builtin /usr/src/linux-3.2.28b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc11_3.2.28b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc11.tar.gz
mkdir install
cd zfs-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.28b \
    --with-linux-obj=/usr/src/linux-3.2.28b \
    --with-spl=/root/src/spl-0.6.0-rc11
    --with-spl-obj=/root/src/spl-0.6.0-rc11
./copy-builtin /usr/src/linux-3.2.28b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc11_3.2.28b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we can move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers. This move is &lt;b&gt;optional&lt;/b&gt; and you can skip doing this and everything will probably work fine, but it is shown here how to move the modules to under drivers in case you prefer them there:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.28b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.28b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.28b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.28b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.28b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

It is time to pause for a moment here and talk about zpool.cache: Using it is actually dangerous. We are not using udev and it's persistent block device filenames (/dev/disk/by-*), but are using the default kernel block device names (/dev/sd*) in devtmpfs. Device names for a hard drive in /dev can potentially change on boot depending on disk controller initialization order and disk drive response time. Adding another disk controller or hard disk on a controller can result in device name assignment changes to all the hard disks. A zpool.cache file holds all the zfs_member device filenames /dev/sd* for a pool configuration, but the zpool.cache configuration will be incorrect if device filenames have been changed or swapped around and this could result in a faulted pool that may or may not be recoverable. Using zpool.cache to import pools at boot, even with udev persistent device filenames, is potentially destructive if devices have been changed around. The proper thing to do is zpool_import and do not include zpool.cache in the initramfs.

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an earlier stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * and this program compiled to /boot/initramfs-source/init
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.1"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc11/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { "root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { "mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { "zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { "zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	printk("zpool_import: searching for pool.\n");
	pools = zpool_search_import(libzfs, &amp;iargs);
	if( (pools == NULL) || nvlist_empty(pools) )
		printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
	else {
		printk("zpool_import: getting pool information.\n");
		pool = nvlist_next_nvpair(pools, pool);
		printk("zpool_import: getting pool configuration.\n");
		nvpair_value_nvlist(pool, &amp;config);
		printk("zpool_import: attempting pool import.\n");
		if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
			printk("zpool_import: import failed.\n");
			printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
			printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
		} else  printk("zpool_import: import successful.\n");
	}
	printk("zpool_import: fini libzfs.\n");
	libzfs_fini(libzfs);
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/linux-3.2.28b/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;zfs_config.h&lt;/code&gt; can be found in the kernel source when you have installed the builtin spl/zfs configuration; for example at &lt;code&gt;/usr/src/linux-3.2.28b/zfs_config.h&lt;/code&gt;. If you currently have installed the modular spl/zfs configuration, &lt;code&gt;zfs_config.h&lt;/code&gt; is found where the zfs module headers are installed; for example at &lt;code&gt;/usr/src/zfs-0.6.0-rc11/3.2.28/zfs_config.h&lt;/code&gt;. Wherever it is, &lt;code&gt;-include&lt;/code&gt; it as shown in the example gcc line above. zfs_config.h seems misplaced because it would seem that using libzfs shouldn't depend on modules header files.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.28b
cp System.map /boot/System.map-vm3.2.28b
# add new lilo menu entry for vm3.2.28b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.28b
   label = vm3.2.28b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;
Note: If &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; is not included in addappend, then during boot SPL module will attempt to read /etc/hostid or run a user-space helper to write the &lt;code&gt;hostid&lt;/code&gt; into &lt;code&gt;/proc/sys/kernel/spl/hostid&lt;/code&gt;. Reading /etc/hostid fails unless you use foobarz-chhostid and make the file and copy it into /boot/initramfs-source/etc/hostid. The helper will fail because no &lt;code&gt;sh&lt;/code&gt; shell and no &lt;code&gt;hostid&lt;/code&gt; command are installed in the initramfs. The default hostid becomes 0xffffffff, which is considered an invalid hostid.

Congrats! If this works, you can select the "vm3.2.28b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc11_3.2.28b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.28b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>8b8bc64cc0f21702f52778f3f0adc6a121b60c0c</sha1>
  </revision>
  <revision>
    <id>801</id>
    <parentid>800</parentid>
    <timestamp>2012-09-22T09:30:40Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43126" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zpool export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.28 /usr/src/linux-3.2.28b
rm -r install
cd /usr/src/linux-3.2.28b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.28b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc11.tar.gz
mkdir install
cd spl-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.28b \
    --with-linux-obj=/usr/src/linux-3.2.28b
./copy-builtin /usr/src/linux-3.2.28b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc11_3.2.28b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc11.tar.gz
mkdir install
cd zfs-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.28b \
    --with-linux-obj=/usr/src/linux-3.2.28b \
    --with-spl=/root/src/spl-0.6.0-rc11
    --with-spl-obj=/root/src/spl-0.6.0-rc11
./copy-builtin /usr/src/linux-3.2.28b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc11_3.2.28b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we can move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers. This move is &lt;b&gt;optional&lt;/b&gt; and you can skip doing this and everything will probably work fine, but it is shown here how to move the modules to under drivers in case you prefer them there:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.28b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.28b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.28b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.28b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.28b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache

It is time to pause for a moment here and talk about zpool.cache: Using it is actually dangerous. We are not using udev and it's persistent block device filenames (/dev/disk/by-*), but are using the default kernel block device names (/dev/sd*) in devtmpfs. Device names for a hard drive in /dev can potentially change on boot depending on disk controller initialization order and disk drive response time. Adding another disk controller or hard disk on a controller can result in device name assignment changes to all the hard disks. A zpool.cache file holds all the zfs_member device filenames /dev/sd* for a pool configuration, but the zpool.cache configuration will be incorrect if device filenames have been changed or swapped around and this could result in a faulted pool that may or may not be recoverable. Using zpool.cache to import pools at boot, even with udev persistent device filenames, is potentially destructive if devices have been changed around. The proper thing to do is zpool_import and do not include zpool.cache in the initramfs.

# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an earlier stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * Copy this compiled program to /boot/initramfs-source/init
 * If not named /init, then use rdinit=/othername kernel parameter.
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.2"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.28/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { " root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { " rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { " mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { " zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults for params not given on cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	if( libzfs != NULL ) {
		printk("zpool_import: searching for pool.\n");
		pools = zpool_search_import(libzfs, &amp;iargs);
		if( (pools == NULL) || nvlist_empty(pools) )
			printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
		else {
			printk("zpool_import: getting pool information.\n");
			pool = nvlist_next_nvpair(pools, pool);
			printk("zpool_import: getting pool configuration.\n");
			nvpair_value_nvlist(pool, &amp;config);
			printk("zpool_import: attempting pool import.\n");
			if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
				printk("zpool_import: import failed.\n");
				printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
				printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
			} else  printk("zpool_import: import successful.\n");
		}
		printk("zpool_import: fini libzfs.\n");
		libzfs_fini(libzfs);
	} else {
		printk("zpool_import: unable to initialize libzfs.\n");
	}
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/linux-3.2.28b/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;zfs_config.h&lt;/code&gt; can be found in the kernel source when you have installed the builtin spl/zfs configuration; for example at &lt;code&gt;/usr/src/linux-3.2.28b/zfs_config.h&lt;/code&gt;. If you currently have installed the modular spl/zfs configuration, &lt;code&gt;zfs_config.h&lt;/code&gt; is found where the zfs module headers are installed; for example at &lt;code&gt;/usr/src/zfs-0.6.0-rc11/3.2.28/zfs_config.h&lt;/code&gt;. Wherever it is, &lt;code&gt;-include&lt;/code&gt; it as shown in the example gcc line above. zfs_config.h seems misplaced because it would seem that using libzfs shouldn't depend on modules header files.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.28b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.28b
cp System.map /boot/System.map-vm3.2.28b
# add new lilo menu entry for vm3.2.28b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.28b
   label = vm3.2.28b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;
Note: If &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; is not included in addappend, then during boot SPL module will attempt to read /etc/hostid or run a user-space helper to write the &lt;code&gt;hostid&lt;/code&gt; into &lt;code&gt;/proc/sys/kernel/spl/hostid&lt;/code&gt;. Reading /etc/hostid fails unless you use foobarz-chhostid and make the file and copy it into /boot/initramfs-source/etc/hostid. The helper will fail because no &lt;code&gt;sh&lt;/code&gt; shell and no &lt;code&gt;hostid&lt;/code&gt; command are installed in the initramfs. The default hostid becomes 0xffffffff, which is considered an invalid hostid.

Congrats! If this works, you can select the "vm3.2.28b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc11_3.2.28b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.28b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>0f6ed16f04a4bfe2223c1622e7fdb328dc7ae7ad</sha1>
  </revision>
  <revision>
    <id>804</id>
    <parentid>801</parentid>
    <timestamp>2012-09-24T20:08:44Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43201" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zpool export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.29 /usr/src/linux-3.2.29b
rm -r install
cd /usr/src/linux-3.2.29b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.29b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc11.tar.gz
mkdir install
cd spl-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.29b \
    --with-linux-obj=/usr/src/linux-3.2.29b
./copy-builtin /usr/src/linux-3.2.29b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc11_3.2.29b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc11.tar.gz
mkdir install
cd zfs-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.29b \
    --with-linux-obj=/usr/src/linux-3.2.29b \
    --with-spl=/root/src/spl-0.6.0-rc11
    --with-spl-obj=/root/src/spl-0.6.0-rc11
./copy-builtin /usr/src/linux-3.2.29b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc11_3.2.29b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we can move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers. This move is &lt;b&gt;optional&lt;/b&gt; and you can skip doing this and everything will probably work fine, but it is shown here how to move the modules to under drivers in case you prefer them there:
&lt;pre&gt;
cd /usr/src/linux-3.2.29b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.29b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.29b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.29b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.29b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.29b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.29b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
&lt;/pre&gt;
It is time to pause for a moment here and talk about zpool.cache: Using it is actually dangerous. We are not using udev and it's persistent block device filenames (/dev/disk/by-*), but are using the default kernel block device names (/dev/sd*) in devtmpfs. Device names for a hard drive in /dev can potentially change on boot depending on disk controller initialization order and disk drive response time. Adding another disk controller or hard disk on a controller can result in device name assignment changes to all the hard disks. A zpool.cache file holds all the zfs_member device filenames /dev/sd* for a pool configuration, but the zpool.cache configuration will be incorrect if device filenames have been changed or swapped around and this could result in a faulted pool that may or may not be recoverable. Using zpool.cache to import pools at boot, even with udev persistent device filenames, is potentially destructive if devices have been changed around. The proper thing to do is zpool_import and do not include zpool.cache in the initramfs.

Now, let's continue making some files in the initramfs-source:
&lt;pre&gt;
# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an earlier stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * Copy this compiled program to /boot/initramfs-source/init
 * If not named /init, then use rdinit=/othername kernel parameter.
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.2"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.29/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { " root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { " rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { " mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { " zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults for params not given on cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	if( libzfs != NULL ) {
		printk("zpool_import: searching for pool.\n");
		pools = zpool_search_import(libzfs, &amp;iargs);
		if( (pools == NULL) || nvlist_empty(pools) )
			printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
		else {
			printk("zpool_import: getting pool information.\n");
			pool = nvlist_next_nvpair(pools, pool);
			printk("zpool_import: getting pool configuration.\n");
			nvpair_value_nvlist(pool, &amp;config);
			printk("zpool_import: attempting pool import.\n");
			if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
				printk("zpool_import: import failed.\n");
				printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
				printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
			} else  printk("zpool_import: import successful.\n");
		}
		printk("zpool_import: fini libzfs.\n");
		libzfs_fini(libzfs);
	} else {
		printk("zpool_import: unable to initialize libzfs.\n");
	}
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/linux-3.2.29b/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;zfs_config.h&lt;/code&gt; can be found in the kernel source when you have installed the builtin spl/zfs configuration; for example at &lt;code&gt;/usr/src/linux-3.2.29b/zfs_config.h&lt;/code&gt;. If you currently have installed the modular spl/zfs configuration, &lt;code&gt;zfs_config.h&lt;/code&gt; is found where the zfs module headers are installed; for example at &lt;code&gt;/usr/src/zfs-0.6.0-rc11/3.2.29/zfs_config.h&lt;/code&gt;. Wherever it is, &lt;code&gt;-include&lt;/code&gt; it as shown in the example gcc line above. zfs_config.h seems misplaced because it would seem that using libzfs shouldn't depend on modules header files.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.29b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.29b
cp System.map /boot/System.map-vm3.2.29b
# add new lilo menu entry for vm3.2.29b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.29b
   label = vm3.2.29b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;
Note: If &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; is not included in addappend, then during boot SPL module will attempt to read /etc/hostid or run a user-space helper to write the &lt;code&gt;hostid&lt;/code&gt; into &lt;code&gt;/proc/sys/kernel/spl/hostid&lt;/code&gt;. Reading /etc/hostid fails unless you use foobarz-chhostid and make the file and copy it into /boot/initramfs-source/etc/hostid. The helper will fail because no &lt;code&gt;sh&lt;/code&gt; shell and no &lt;code&gt;hostid&lt;/code&gt; command are installed in the initramfs. The default hostid becomes 0xffffffff, which is considered an invalid hostid.

Congrats! If this works, you can select the "vm3.2.29b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc11_3.2.29b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.29b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>67bc5a2aa63fd57ce3be00a67015d0e628141caa</sha1>
  </revision>
  <revision>
    <id>805</id>
    <parentid>804</parentid>
    <timestamp>2012-09-25T12:12:38Z</timestamp>
    <contributor>
      <username>Foobarz</username>
      <id>298</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="43319" xml:space="preserve">[[Category:Tutorials]]
The first [http://slackwiki.com/ZFS_root "ZFS root"] wiki explains the details of running ZFS as your root filesystem by using a fully modular generic kernel approach. Now, I can share how it can be done with the SPL and ZFS modules built into the kernel. This procedure is just an example and can use some fine tuning, but here goes:

The steps below are to create a kernel with SPL and ZFS modules builtin. This kernel will be installed as an alternative kernel to boot in lilo, and it will have a separate kernel installation from the fully modular and working system kernel. This will allow testing the builtin kernel while able to boot back onto a working modular ZFS system. We start this procedure assuming you are on a working fully modular ZFS install as in the "ZFS root" wiki.

Use mountpoint=legacy so that zfs will not expect &lt;code&gt;zfs mount&lt;/code&gt;, but instead expect standard &lt;code&gt;mount&lt;/code&gt; for mounting zfs-root:
&lt;pre&gt;
zfs set mountpoint=legacy zfs-root
&lt;/pre&gt;

Edit &lt;code&gt;/etc/rc.d/rc.S&lt;/code&gt; and &lt;code&gt;rc.6&lt;/code&gt; to use regular &lt;code&gt;mount&lt;/code&gt; commands, remove &lt;code&gt;zfs&lt;/code&gt; commands. Edit &lt;code&gt;rc.6&lt;/code&gt; and remove or comment out &lt;code&gt;zpool export&lt;/code&gt; command. These edits undo changes made in the "ZFS root" wiki, but it shows the two different ways of mounting a zfs filesystem.

You &lt;i&gt;might&lt;/i&gt; think to set &lt;code&gt;bootfs&lt;/code&gt; property like this:
&lt;pre&gt;
zpool set bootfs=zfs-root zfs-root
&lt;/pre&gt;
However, this will result in ZFS placing many restrictions on zfs-root as per how that option is used on Solaris systems:
&lt;ol&gt;
&lt;li&gt; zfs-root must be VTOC (SMI) label, not GPT (EFI) label&lt;/li&gt;
&lt;li&gt; zfs-root can only contain 1 vdev: either a plain disk, or a mirror&lt;/li&gt;
&lt;/ol&gt;
So, do &lt;b&gt;NOT&lt;/b&gt; set that property! If &lt;code&gt;bootfs&lt;/code&gt; is set, you would find that you cannot add vdevs to your zfs-root. If it is set already, then unset it like this:
&lt;pre&gt;
zpool set bootfs= zfs-root
&lt;/pre&gt;

Make a directory to store files to be inside the initramfs:
&lt;pre&gt;
mkdir /boot/initramfs-source
&lt;/pre&gt;
This directory will hold some files for the initial rootfs inside the kernel. Your &lt;code&gt;/boot&lt;/code&gt; should be on a small ext4 partition or on a mounted USB stick that you use to boot.

Extract the slackware kernel-source package to obtain a copy of the kernel source, and make an initial kernel config for it:
&lt;pre&gt;
cd ~
mkdir src
cd src
tar xvzf /mnt/cdrom/slackware64/k/kernel-source-*.txz
mv usr/src/linux-3.2.29 /usr/src/linux-3.2.29b
rm -r install
cd /usr/src/linux-3.2.29b
make menuconfig
  General setup-&gt;Local version - append to kernel release = b
  General setup-&gt;Default hostname                         = slackzfs
  General setup-&gt;Initramfs source files(s)                = /boot/initramfs-source
  Device Drivers-&gt;SCSI device support-&gt;SCSI low-level drivers-&gt; &lt;*&gt; SYM53C8XX Version 2 SCSI support
  File systems -&gt; &lt;*&gt; The Extended 4 (ext4) filesystem
  # build in any hard drive controllers and filesystems that you need for booting
  # then save the config
make prepare scripts
&lt;/pre&gt;
The kernel source has been set to have a "Local version" &lt;code&gt;b&lt;/code&gt;. This will result in modules installed to &lt;code&gt;/lib/modules/3.2.29b&lt;/code&gt; and keeps this kernel's source and modules seperate from slackware's kernel-generic package installation. The &lt;code&gt;make prepare scripts&lt;/code&gt; command readies the kernel source as needed before we can install a copy of spl and zfs modules into the kernel source tree.

Now proceed to configure and copy spl and zfs into the kernel source tree:
&lt;pre&gt;
cd ~/src
tar xvzf ~/spl-0.6.0-rc11.tar.gz
mkdir install
cd spl-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.29b \
    --with-linux-obj=/usr/src/linux-3.2.29b
./copy-builtin /usr/src/linux-3.2.29b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../spl-0.6.0rc11_3.2.29b-x86_64-1root.txz
cd ..
rm -r install

tar xvzf ~/zfs-0.6.0-rc11.tar.gz
mkdir install
cd zfs-0.6.0-rc11
./configure \
    --prefix=/ \
    --libdir=/lib64 \
    --includedir=/usr/include \
    --datarootdir=/usr/share \
    --enable-linux-builtin=yes \
    --with-linux=/usr/src/linux-3.2.29b \
    --with-linux-obj=/usr/src/linux-3.2.29b \
    --with-spl=/root/src/spl-0.6.0-rc11
    --with-spl-obj=/root/src/spl-0.6.0-rc11
./copy-builtin /usr/src/linux-3.2.29b
make
make install DESTDIR=~/src/install
cd ~/src/install
makepkg ../zfs-0.6.0rc11_3.2.29b-x86_64-1root.txz
cd ..
rm -r install
&lt;/pre&gt;
At this point, the &lt;code&gt;copy-builtin&lt;/code&gt; scripts have installed the configured spl and zfs modules source into the kernel source. The regular &lt;code&gt;make menuconfig&lt;/code&gt; in the kernel source should now show options for spl and zfs in the kernel config.

As of this writing, the copy-builtin script places the spl and zfs modules into the kernel source in places where the modules may not initialize in the best order, &lt;i&gt;after&lt;/i&gt; all lower-level storage drivers are initialized. If spl and zfs initialize too soon, there is a chance they may not be able to see all of the storage devices. The order of initialization (as seen in dmesg) of modules that are builtin to the kernel is the order that the modules are linked into the kernel during kernel compilation. The order of link depends on where the module source files are located in the kernel source tree. To ensure that spl and zfs will initialize after all hardware drivers, we can move them into the &lt;code&gt;drivers&lt;/code&gt; tree and after all other drivers. This move is &lt;b&gt;optional&lt;/b&gt; and you can skip doing this and everything will probably work fine, but it is shown here how to move the modules to under drivers in case you prefer them there:
&lt;pre&gt;
cd /usr/src/linux-3.2.29b
mkdir drivers/zfsonlinux
mv spl drivers/zfsonlinux
vi Kconfig
  # remove references to spl
vi Makefile
  # remove references to spl

cd /usr/src/linux-3.2.29b/fs
mv zfs ../drivers/zfsonlinux
vi Kconfig
  # remove references to zfs
vi Makefile
  # remove references to zfs

cd /usr/src/linux-3.2.29b/drivers
vi Kconfig
  )# add line at end of menu, before "endmenu":
  )source "drivers/zfsonlinux/Kconfig"
  )endmenu

cd /usr/src/linux-3.2.29b/drivers
vi Makefile
  )# add line at very end of file:
  )obj-$(CONFIG_ZFSONLINUX) += zfsonlinux/

cd /usr/src/linux-3.2.29b/drivers/zfsonlinux
cat &gt; Kconfig &lt;&lt;"EOF"
menuconfig ZFSONLINUX
	tristate "ZFSonLinux support"

if ZFSONLINUX

source "drivers/zfsonlinux/spl/Kconifg"

source "drivers/zfsonlinux/zfs/Kconifg"

endif
EOF

cd /usr/src/linux-3.2.29b/zfsonlinux
cat &gt; Makefile &lt;&lt;"EOF"
obj-$(CONFIG_SPL) += spl/
obj-$(CONFIG_ZFS) += zfs/
EOF
&lt;/pre&gt;
This completes the move of the spl and zfs modules in the kernel source tree to be under &lt;code&gt;drivers/zfsonlinux&lt;/code&gt;.

Now, in kernel configuration, you can build in the modules as follows:
&lt;pre&gt;
cd /usr/src/linux-3.2.29b
make menuconfig
   Device Drivers -&gt;
    &lt;*&gt; ZFSonLinux support -&gt;
      &lt;*&gt; Solaris Porting Layer (SPL)
      &lt;*&gt;     ZFS
&lt;/pre&gt;

In the kernel config, we set &lt;code&gt;/boot/initramfs-source&lt;/code&gt; as source location of the contents to be linked into kernel's builtin initramfs (rootfs). Now, we create some files that are needed to be in the initramfs:
&lt;pre&gt;
cd /boot/initramfs-source

# make standard directories
mkdir -p proc dev sys mnt bin sbin etc/zfs

# zfs seems to want mtab present, even if empty
touch etc/mtab

# if zpool.cache file can be read by zfs at module init, it imports the pools in the cache
cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
&lt;/pre&gt;
It is time to pause for a moment here and talk about zpool.cache: Using it is actually dangerous. We are not using udev and it's persistent block device filenames (/dev/disk/by-*), but are using the default kernel block device names (/dev/sd*) in devtmpfs. Device names for a hard drive in /dev can potentially change on boot depending on disk controller initialization order and disk drive response time. Adding another disk controller or hard disk on a controller can result in device name assignment changes to all the hard disks. A zpool.cache file holds all the zfs_member device filenames /dev/sd* for a pool configuration, but the zpool.cache configuration will be incorrect if device filenames have been changed or swapped around and this could result in a faulted pool that may or may not be recoverable. Using zpool.cache to import pools at boot, even with udev persistent device filenames, is potentially destructive if devices have been changed around. The proper thing to do is zpool_import and do not include zpool.cache in the initramfs.

Now, let's continue making some files in the initramfs-source:
&lt;pre&gt;
# make initial console device node; otherwise, there is a problem at startup:
# "Warning: unable to open an initial console" and you'd have problems with console and tty login
# making these nodes from within /init is not early enough to avoid problem
mknod dev/console c 5 1   # system console

# make memory device kmsg to "printk" kernel messages
# we can write to this file to send out messages
mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer

# recommended loop0 device to mount fs images
mknod dev/loop0   b 7 0

# make initial virtual terminal devices
mknod dev/tty     c 5 0   # current tty
mknod dev/tty0    c 4 0   # current virtual term
mknod dev/tty1    c 4 1   # login virtual term 1 (F1)

# make alternative console=ttyS0 standard 8250/16550 UART serial port devices
#   useful with kernel parameter console=ttyS0
#          with qemu -nographic -option-rom sgabios.bin,bootindex=0
mknod dev/ttyS0   c 4 64  # COM1
mknod dev/ttyS1   c 4 65  # COM2
mknod dev/ttyS2   c 4 66  # COM3
mknod dev/ttyS3   c 4 67  $ COM4
&lt;/pre&gt;
This should be enough device nodes initially in the initramfs. Once devtmpfs mounts over /dev inside initramfs, a lot more devices are available in it by default.

The initramfs needs an &lt;code&gt;/init&lt;/code&gt; program that will be run automatically by the kernel as process id 1, the first program to run on the system. This program's task is to mount a root filesystem, switch it to be the new root (/), and then exec the init (&lt;code&gt;/sbin/init&lt;/code&gt;) program that is on the new root so that the new root system is booted.

The common way to make /init is using busybox with files like these in /boot/initrd-tree or /boot/initramfs-source:
&lt;pre&gt;
bin/busybox
bin/ash -&gt; busybox
bin/sh -&gt; busybox
# run busybox to see what other "applets" can be symlinked to it
# when busybox is run as a different symlinked applet name, it runs as the applet
init
# init can be an ash script, see slackware's /boot/initrd-tree/init for example
&lt;/pre&gt;

For example, as an ash script, slackware's init does the following:
&lt;ol&gt;
 &lt;li&gt;parse kernel parameters passed into it and set variables based on them&lt;/li&gt;
 &lt;li&gt;start udevd and trigger rules for block devices to setup initial /dev devices&lt;/li&gt;
 &lt;li&gt;load kernel modules and keyboard map&lt;/li&gt;
 &lt;li&gt;run mdadm, cryptsetup, lvm, zpool/zfs to setup more devices
     (any udev rules for them should do more /dev setup in the background)&lt;/li&gt;
 &lt;li&gt;mount the root filesystem read-only at /mnt&lt;/li&gt;
 &lt;li&gt;stat /mnt/sbin/init, and if not executable run a rescue shell /bin/sh&lt;/li&gt;
 &lt;li&gt;shutdown udevd so it can be restarted by root system when booted&lt;/li&gt;
 &lt;li&gt;mount --move {proc,sys,run,dev} to under /mnt&lt;/li&gt;
 &lt;li&gt;run: exec switch_root /mnt /sbin/init $RUNLEVEL&lt;/li&gt;
&lt;/ol&gt;

The slackware mkinitrd package is a fully configured BusyBox installation that makes an external initramfs image file, initrd.gz, that is passed to the kernel by the bootloader (lilo). It could be changed to be internal to the kernel by just using initrd-tree as the CONFIG_INITRAMFS_SOURCE in the kernel config and removing initrd in the lilo.conf.

The main purpose of most initramfs/initrd is to load and configure kernel modules and devices needed to mount a root filesystem. Because the spl/zfs modules are builtin, there isn't really a lot that needs to be done by an initramfs. What remains to be done is import the zfs-root pool, mount it, and exec the system /sbin/init. The kernel's "legacy" parameters &lt;code&gt;root=&lt;/code&gt; and &lt;code&gt;rootfstype=&lt;/code&gt; that are able to directly boot a root disk do not work with ZFS at this time because ZFS pools always need to be imported before it is possible to mount and boot on them. The automatic import that ZFS can do by using a cachefile (/etc/zfs/zpool.cache) stored in initramfs still does not work with the legacy boot parameters because at an earlier stage of the boot process, the kernel ignores a rootfs that does not contain an &lt;code&gt;/init&lt;/code&gt; program, and/or the device type of an imported pool is not the device types recognized by the legacy boot as valid root devices.

You could just continue to use slackware's mkinitrd package as in the "ZFS root" wiki and it works the same whether the modules are builtin or not. But, by building the spl/zfs modules in, aren't we really wanting to get rid of using the mkinitrd/initrd.gz? We'd like to have a kernel with everything in it to boot, and use a simple lilo image entry that has no initrd.

We can do this, and not use the mkinitrd package, but we still need to finish our own initramfs &lt;code&gt;/init&lt;/code&gt; program to import, mount, switch root, and boot. Save the following c program to "foobarz-init.c":
&lt;pre&gt;
/* software product name: foobarz-init.c
 * suggested binary name: /init (in initramfs-source, rootfs)
 * license              : BSD
 * license text:
Copyright (c) 2012, foobarz
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
    * Redistributions of source code must retain the above copyright
      notice, this list of conditions and the following disclaimer.
    * Redistributions in binary form must reproduce the above copyright
      notice, this list of conditions and the following disclaimer in the
      documentation and/or other materials provided with the distribution.
    * Neither the name of the &lt;organization&gt; nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL &lt;COPYRIGHT HOLDER&gt; BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
*/

/* Your initramfs-source should contain the following
 *
 * cd /boot/initramfs-source
 * mkdir -p proc dev sys mnt bin sbin etc/zfs
 * touch etc/mtab
 * cp /etc/zfs/zpool.cache-initrd etc/zfs/zpool.cache
 * # zpool.cache is optional - zpool_import_ kernel params can be used instead
 * #  see below for details on using zpool_import
 * mknod dev/console c 5 1   # system console
 * mknod dev/kmsg    c 1 11  # lines printed to kmsg enter kernel messages buffer
 * mknod dev/loop0   b 7 0
 * mknod dev/tty     c 5 0   # current tty
 * mknod dev/tty0    c 4 0   # current virtual term
 * mknod dev/tty1    c 4 1   # login virtual term 1 (F1)
 * mknod dev/ttyS0   c 4 64  # COM1
 * mknod dev/ttyS1   c 4 65  # COM2
 * mknod dev/ttyS2   c 4 66  # COM3
 * mknod dev/ttyS3   c 4 67  $ COM4
 *
 * Copy this compiled program to /boot/initramfs-source/init
 * If not named /init, then use rdinit=/othername kernel parameter.
 *
 * Set kernel config option
 *  CONFIG_INITRAMFS_SOURCE=/boot/initramfs-source
 * to build the initramfs into your kernel image
 *  that also has builtin drivers (spl and zfs, etc).
 */

#define FOOBARZ_INIT_VERSION "1.1.2"
#define _BSD_SOURCE
#include &lt;stdio.h&gt;
#include &lt;stdarg.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;fcntl.h&gt;
#include &lt;unistd.h&gt;
#include &lt;sys/mount.h&gt;
#include &lt;sysexits.h&gt;
#include &lt;errno.h&gt;
#include &lt;string.h&gt;
/* support for zpool import
 *
 * If -DINCLUDE_ZPOOL_IMPORT, then support to import a zpool is
 * enabled in the program. Enabling it will add many dependencies to the
 * compile and link; for example:
 *
 * gcc -static -DINCLUDE_ZPOOL_IMPORT \
 *    foobarz-init.c -include /usr/src/zfs-0.6.0-rc10/3.2.29/zfs_config.h \
 *   -o init \
 *   -I /usr/include/libspl -I /usr/include/libzfs \
 *   -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
 *   -I /usr/include/tirpc \
 *   -ltirpc
 *
 * Note that libtirpc is a drop-in replacement for the SunRPC functions that
 * used to be in glibc. No additional includes are needed, just the gcc -I and -l
 * options for tirpc.
 *
 * Otherwise, with -UINCLUDE_ZPOOL_IMPORT, the compile is just:
 * gcc -static foobarz-init.c -o init
 */
#if defined(INCLUDE_ZPOOL_IMPORT)
#include &lt;libzfs.h&gt;
#else
#include &lt;sys/types.h&gt;
#include &lt;sys/stat.h&gt;
#endif

#define PARAM_REQ_NO 0
#define PARAM_REQ_YES 1
#define PARAM_SRC_DEFAULT 0
#define PARAM_SRC_CMDLINE 1

void printk(char *fmt, ...) {
  FILE* f;
  int fd;
  va_list args;

  f = fopen("/dev/kmsg", "w");
  va_start(args, fmt);
  vfprintf(f, fmt, args);
  va_end(args);
  fflush(f);
  fclose(f);
  /* avoid flooding kmsg and having msgs suppressed; 20msgs/sec */
  usleep(50000);
}

int main(int argc, char* argv[]) {
 /*** variables */

 int i;
 int   fd = 0; /* file descriptor */
 unsigned long mountflags;

 /* kernel command line */
 off_t cmdline_size;
 char* cmdline; /* to be malloc 4096B */
 char* cmdline_end;
 char* temp_end;
 char* src_msg; /* default or cmdline */
 int flag_param_missing = 0;

 /* use to hold contents of a misc /proc/&lt;file&gt; */
 char* miscproc_buff; /* to be malloc 4096B */
 off_t miscproc_size;

 /* note about environ, argv, and kernel cmdline for init:
  *   environ is not defined for init
  *   only argv[0] is set for init
  *   kernel command line parameters are accessed
  *   at /proc/cmdline
  */

 /* kernel parameters expected to be name=value */
 /* do not use quotes or spaces in parameters   */
 /* you can add more params somwhere after root= */
 struct nv { char* n; char* v; char* v_end; int req; int src; };
 struct nv param[] = {
   { " root=",       NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { " rootfstype=", NULL, NULL, PARAM_REQ_YES, PARAM_SRC_DEFAULT },
   { " mountopt=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " init=",       NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " runlevel=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " console=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#if defined(INCLUDE_ZPOOL_IMPORT)
   ,
   { " zpool_import_name=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_guid=",    NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_newname=", NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT },
   { " zpool_import_force=",   NULL, NULL, PARAM_REQ_NO , PARAM_SRC_DEFAULT }
#endif
 };
 enum {
	 iroot,
	 irootfstype,
	 imountopt,
	 iinit,
	 irunlevel,
	 iconsole,
#if defined(INCLUDE_ZPOOL_IMPORT)
	 izpool_import_name,
	 izpool_import_guid,
	 izpool_import_newname,
	 izpool_import_force,
#endif
	 ilastparam
 };

#if defined(INCLUDE_ZPOOL_IMPORT)
 libzfs_handle_t* libzfs = NULL;
 importargs_t iargs = { 0 };
 nvlist_t* pools = NULL;
 nvpair_t* pool = NULL;
 nvlist_t* config = NULL;
#endif

 /*** program */

 printk("foobarz-init, version %s: booting initramfs.\n", FOOBARZ_INIT_VERSION);

 cmdline       = (char*) malloc(4096);
 miscproc_buff = (char*) malloc(4096);
 if( (cmdline == NULL) || (miscproc_buff == NULL) ) {
   printk("Unable to allocate buffer memory: malloc: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }

 /* mount proc /proc
  *  note: some /dev devices symlink into /proc
  *  proc contains info about processes, including cmdline etc. */
 printk("Attempting cmd: mount proc /proc\n");
 if( mount("proc", "/proc", "proc", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount proc successful.\n");
 }

 /* mount devtmpfs /dev
  *  note: This simple init program works if your root device is made from devices
  *  that are available by default in devtmpfs, such as /dev/sd*
  *
  *  For zfs, your root zfs pool should be created with default device nodes and
  *  then it should be mountable by this simple init program.
  *
  *  udev may be needed to configure device nodes and symlinks required
  *  to access a root device configuration made with such nodes and symlinks.
  *  If you need udevd, you can include it into your initramfs-source and
  *  modify this program to run it before attempting to mount your root device.
  *  However, if udevd is needed, a significant number of userspace programs may also be
  *  required by rules in /lib/udev/. You could install busybox + udev (about 5MB) or
  *  coreutils + util-linux + bash + udev (about 25MB) into initramfs-source. But, at that
  *  point you'd have ash or bash and many tools that are easier to use than this
  *  simple init program; it would then be easy to have /init as #!/bin/&lt;b&gt;ash script. */
 printk("Attempting cmd: mount devtmpfs /dev\n");
 if( mount("devtmpfs", "/dev", "devtmpfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount devtmpfs successful.\n");
 }

 /* mount sysfs /sys
  *  note: some kernel modules try to access /sys with userspace helpers to echo values into /sys variables;
  *  such modules expect a minimal userspace that contains coreutils or busybox */
 printk("Attempting cmd: mount sysfs /sys\n");
 if( mount("sysfs", "/sys", "sysfs", 0, NULL) != 0 ) {
   printk("time to panic: mount: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 } else {
   printk("Mount sysfs successful.\n");
 }

 /* process kernel command line */
 fd = open("/proc/cmdline", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 /* note, on /proc fs:
  *       lseek likely always returns error
  *       stat likely always returns st_size = 0
  *   so determining size of /proc file means just reading it;
  *   you have to read /proc files according to their documented
  *   maximum sizes; this is probably for performance reasons */
 cmdline_size = read(fd, cmdline, 4095);
 if( cmdline_size == -1 ) {
   printk("Failed to read /proc/cmdline: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);

 /* cmdline may be newline + null terminated, but make it null + null */
 cmdline[cmdline_size] = '\0';
 if( cmdline[cmdline_size-1] == '\n' ) {
   cmdline[cmdline_size-1] = '\0';
   cmdline_size--;
   cmdline_end = cmdline + cmdline_size;
 }
 printk("Kernel cmdline size: %i\n", cmdline_size);
 printk("Kernel cmdline: \"%s\"\n", cmdline);

 /* find v and v_end of values in cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   param[i].v = strstr(cmdline, param[i].n);
   if( param[i].v != NULL ) {
     param[i].src = PARAM_SRC_CMDLINE;
     while( *(param[i].v) != '=' ) param[i].v++;
     param[i].v++;
     temp_end = param[i].v;
     while( !( (*temp_end == ' ') ||
               (*temp_end == '\n') ||
               (temp_end == cmdline_end)
	     ) ) temp_end++;
     if( temp_end == param[i].v ) {
       printk("Kernel parameter %s: value missing.\n", param[i].n);
       param[i].v = NULL;
     } else param[i].v_end = temp_end;
   }
 }

 /* set defaults for params not given on cmdline */
 for( i=iroot; i&lt;ilastparam; i++ ) {
   /* terminate value strings */
   if( param[i].v_end != NULL ) *(param[i].v_end) = '\0';
   /* set defaults if no value on cmdline */
   if( param[i].v == NULL ) {
     param[i].src = PARAM_SRC_DEFAULT;
     if( param[i].req == PARAM_REQ_YES ) flag_param_missing = 1;
     switch(i) {
       case iroot      : param[i].v = "&lt;missing required param&gt;" ; break;
       case irootfstype: param[i].v = "&lt;missing required param&gt;" ; break;
       case imountopt  : param[i].v = "ro"        ; break;
       case iinit      : param[i].v = "/sbin/init"; break;
       case irunlevel  : param[i].v = "3"         ; break;
       case iconsole   : param[i].v = "console"   ; break;
       default         : param[i].v = NULL;
     }
   }
   if(param[i].src == PARAM_SRC_DEFAULT) src_msg = "default";
   else src_msg = "cmdline";
   printk("Using %s \"%s\" (source: %s)\n", param[i].n, param[i].v, src_msg);
 }

 if( flag_param_missing ) {
   printk("Aborting boot process: missing required kernel parameter(s).\n");
   return EX_USAGE;
 }

 /* generic nv pair kernel cmdline processing finished
  *  now, examine specific params for defaults and correctness */

 /* param[irootfstype]: can be checked against /proc/filesystems: */
 fd = open("/proc/filesystems", O_RDONLY);
 if( fd == -1 ) {
   printk("Cannot open /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 miscproc_size = read(fd, miscproc_buff, 4095);
 if( miscproc_size == -1 ) {
   printk("Failed to read /proc/filesystems: %s\n", strerror(errno));
   return EX_UNAVAILABLE;
 }
 close(fd);
 if( strstr(miscproc_buff, param[irootfstype].v) == NULL ) {
   printk("%s \"%s\": filesystem type not available.\n", param[irootfstype].n, param[irootfstype].v);
   return EX_UNAVAILABLE;
 }

 /* zfs-specific */
 if( strcmp(param[irootfstype].v, "zfs") == 0 ) {
   if( access("/etc/zfs/zpool.cache", F_OK) == 0 )
     printk("rootfstype=%s: /etc/zfs/zpool.cache is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/zfs/zpool.cache not present in initramfs.\n", param[irootfstype].v);

   if( access("/etc/hostid", F_OK) == 0 )
     printk("rootfstype=%s: /etc/hostid is present in initramfs.\n", param[irootfstype].v);
   else
     printk("rootfstype=%s: /etc/hostid not present in initramfs.\n", param[irootfstype].v);

#if defined(INCLUDE_ZPOOL_IMPORT)
   /* zpool import */
   if( (param[izpool_import_name].v != NULL) || (param[izpool_import_guid].v != NULL) ) {
	printk("zpool_import: import requested.\n");
	if( (param[izpool_import_name].v != NULL) &amp;&amp; (param[izpool_import_guid].v != NULL) ) {
		printk("zpool_import: given both pool name and guid; using guid.\n");
		param[izpool_import_name].v = NULL;
	}
	if( param[izpool_import_name].v != NULL )
		printk("zpool_import: pool name: %s\n", param[izpool_import_name].v );
	else
		printk("zpool_import: pool guid: %s\n", param[izpool_import_guid].v );

	iargs.path = NULL;
	iargs.paths = 0;
	iargs.poolname = param[izpool_import_name].v;
	if( param[izpool_import_guid].v != NULL )
		iargs.guid = strtoull(param[izpool_import_guid].v, NULL, 10);
	else
		iargs.guid = 0;
	iargs.cachefile = NULL;
	if( (param[izpool_import_force].v != NULL) &amp;&amp; (strcmp(param[izpool_import_force].v, "1") == 0) ) {
		iargs.can_be_active = 1;
		printk("zpool_import: import forced.\n");
	} else {
		iargs.can_be_active = 0;
		printk("zpool_import: import not forced.\n");
	}
	iargs.unique = 1;
	iargs.exists = 1;

	printk("zpool_import: init libzfs.\n");
	libzfs = libzfs_init();
	if( libzfs != NULL ) {
		printk("zpool_import: searching for pool.\n");
		pools = zpool_search_import(libzfs, &amp;iargs);
		if( (pools == NULL) || nvlist_empty(pools) )
			printk("zpool_import: pool not available for import, or already imported by cachefile.\n");
		else {
			printk("zpool_import: getting pool information.\n");
			pool = nvlist_next_nvpair(pools, pool);
			printk("zpool_import: getting pool configuration.\n");
			nvpair_value_nvlist(pool, &amp;config);
			printk("zpool_import: attempting pool import.\n");
			if( zpool_import(libzfs, config, param[izpool_import_newname].v, NULL) != 0 ) {
				printk("zpool_import: import failed.\n");
				printk("zpool_import: error description: %s\n", libzfs_error_description(libzfs) );
				printk("zpool_import: error action: %s\n", libzfs_error_action(libzfs) );
			} else  printk("zpool_import: import successful.\n");
		}
		printk("zpool_import: fini libzfs.\n");
		libzfs_fini(libzfs);
	} else {
		printk("zpool_import: unable to initialize libzfs.\n");
	}
   }
#endif /* zpool_import */
 }

 if(      strcmp(param[imountopt].v, "ro") == 0 ) mountflags = MS_RDONLY;
 else if( strcmp(param[imountopt].v, "rw") == 0 ) mountflags = 0;
 else {
   printk("%s \"%s\": invalid parameter value; defaulting to \"ro\".\n", param[imountopt].n, param[imountopt].v);
   mountflags = MS_RDONLY;
 }

 /* param[iroot]: nothing to check; if user gives bad root=device then mount fails */

 /* try to mount root=device at /mnt
  *
  * note: for zfs, if a copy of /etc/zfs/zpool.cache (when pool is imported) is put in initramfs-source, then
  * the zfs module can read it and automatically import the pools described in the cache file; the imported
  * pools can be available to mount here if they were created using standard device names, otherwise
  * udevd may be required to run before mounting the pool */
 printk("Attempting cmd: mount -t %s -o %s %s /mnt.\n", param[irootfstype].v, param[imountopt].v, param[iroot].v);
 if( mount(param[iroot].v, "/mnt", param[irootfstype].v, mountflags, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("%s mounted successfully.\n", param[iroot].v);

 /* check to see if the mounted root filesystem has an executable init program */
 chdir("/mnt");
 if( access(param[iinit].v+1, X_OK) != 0 ) {
   chdir("/");
   printk("access X_OK: %s\n", strerror(errno));
   printk("The init program /mnt/%s is not present or not executable.\n", param[iinit].v+1);
   printk("Aborting boot process: no init program.\n");
   printk("Unmounting %s.\n", param[iroot].v);
   if( umount("/mnt") == -1 ) {
     printk("umount: %s\n", strerror(errno));
     printk("Failed to umount %s.\n", param[iroot].v);
   } else printk("Successfully unmounted %s.\n", param[iroot].v);
   return EX_UNAVAILABLE;
 }
 chdir("/");
 printk("Init program /mnt/%s is present and executable.\n", param[iinit].v+1);

 /* switch the root / from initramfs to the mounted new root device at /mnt.
  *
  * note: after this switch, it is not possible to access the initramfs files anymore,
  * yet they consume ram memory unless they are deleted here before switching.
  * Any programs that are run after clearing the initramfs and switching root must exist on the new root.
  * This program may safely delete itself (/init) since it is already in ram and executing.
  * If you have installed additional files and programs in initramfs that consume significant ram,
  * then you need to insert additional code here to delete those files (carefully). */

 /* delete files off of initramfs to free ram memory */
 printk("Freeing memory from initramfs...\n");
 if( unlink(argv[0]) != 0 ) printk("unlink %s: %s\n", argv[0], strerror(errno));
 else printk("%s %s", argv[0], "deleted from initramfs.\n");

 /* switch root */
 printk("Beginning switch root procedure.\n");

 printk("(1) Attempting cmd: mount --move /dev /mnt/dev \n");
 if( mount("/dev", "/mnt/dev", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(2) Attempting cmd: mount --move /proc /mnt/proc \n");
 if( mount("/proc", "/mnt/proc", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(3) Attempting cmd: mount --move /sys /mnt/sys \n");
 if( mount("/sys", "/mnt/sys", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(4) Attempting cmd: chdir /mnt \n");
 if( chdir("/mnt") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(5) Attempting cmd: mount --move . / \n");
 if( mount(".", "/", NULL, MS_MOVE, NULL) != 0 ) {
  printk("time to panic: mount: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(6) Attempting cmd: chroot . \n");
 if( chroot(".") != 0 ) {
  printk("time to panic: chroot: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }

 printk("(7) Attempting cmd: chdir / \n");
 if( chdir("/") != 0 ) {
  printk("time to panic: chdir: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
 printk("Completed switch root procedure.\n");

 /* check for "console=" kernel parameter and switch
  *  stdin, stdout, and stderr to named console device
  */
 if( param[iconsole].src == PARAM_SRC_CMDLINE ) {
   printk("Console redirection to device %s requested.\n", param[iconsole].v);
   /* expect only basename of console device (e.g., ttyS0), so chdir /dev */
   chdir("/dev");
   if( access(param[iconsole].v, F_OK ) == 0 ) {
     printk("Opening stdin, stdout, and stderr on %s.\n", param[iconsole].v);
     close(0);
     open(param[iconsole].v, O_RDWR);
     dup2(0, 1);
     dup2(0, 2);
   } else {
     printk("access F_OK: %s\n", strerror(errno));
     printk("Could not access device: %s!\n", param[iconsole].v);
     printk("Console redirection to device %s aborted!\n", param[iconsole].v);
   }
   chdir("/");
 }

 printk("Execing: \"%s %s\" to boot mounted root system.\n", param[iinit].v, param[irunlevel].v);

 /* free resources held to this point */
 free(cmdline);
 free(miscproc_buff);

 if( execl(param[iinit].v, param[irunlevel].v, (char *) NULL ) != 0 ) {
  printk("time to panic: execl: %s\n", strerror(errno));
  return EX_UNAVAILABLE;
 }
}
&lt;/pre&gt;

If foobarz-init is updated, you can find the latest version at [https://github.com/foobarz/foobarz-init github].

The foobarz-init program can be compiled two ways as of v1.1.1. First, the simpler compile that does not support zpool_import but does support importing pools using a /etc/zfs/zpool.cache file in the initramfs:
&lt;pre&gt;
gcc --static init.c -o init
strip init
&lt;/pre&gt;

The second way to compile it adds support for zpool_import so that you do not have to include a &lt;code&gt;/etc/zfs/zpool.cache&lt;/code&gt; file in the initramfs:
&lt;pre&gt;
gcc -static -DINCLUDE_ZPOOL_IMPORT \
     foobarz-init.c -include /usr/src/linux-3.2.29b/zfs_config.h \
    -o init \
    -I /usr/include/libspl -I /usr/include/libzfs \
    -lzfs -lnvpair -lzpool -luutil -luuid -lrt -lz -lm -lpthread \
    -I /usr/include/tirpc \
    -ltirpc
strip init
&lt;/pre&gt;
Dependencies required before you can compile this second way:
&lt;ul&gt;
&lt;li&gt; Install [http://sourceforge.net/projects/libtirpc/ libtirpc]. The glibc package has removed the RPC-related functions from the static libc. The libtirpc is the new replacement as a separate library. You can make your own libtirpc package and install it to resolve these RPC-related functions. Without this, the compile fails because it cannot find many "xdr" functions.&lt;/li&gt;
&lt;li&gt; Reinstall the [ftp://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/a/util-linux/ util-linux] package with static libraries enabled. Edit the &lt;code&gt;util-linux.SlackBuild&lt;/code&gt; and remove the line &lt;code&gt;--disable-static&lt;/code&gt;, then build it and use upgradepkg to install the new package. This resolves linking static to libuuid.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;zfs_config.h&lt;/code&gt; can be found in the kernel source when you have installed the builtin spl/zfs configuration; for example at &lt;code&gt;/usr/src/linux-3.2.29b/zfs_config.h&lt;/code&gt;. If you currently have installed the modular spl/zfs configuration, &lt;code&gt;zfs_config.h&lt;/code&gt; is found where the zfs module headers are installed; for example at &lt;code&gt;/usr/src/zfs-0.6.0-rc11/3.2.29/zfs_config.h&lt;/code&gt;. Wherever it is, &lt;code&gt;-include&lt;/code&gt; it as shown in the example gcc line above. zfs_config.h seems misplaced because it would seem that using libzfs shouldn't depend on modules header files.&lt;/li&gt;
&lt;li&gt;You may need to install the spl and zfs packages configured for --enable-linux-builtin=yes before compiling and linking to libzfs to make sure you are using the version of libzfs intended for builtin modules in case a difference between the two configurations exists. Currently, there seems to be no difference in the libzfs for either modular or builtin modules, but later there could be at least a small difference for detection of modules to load or builtin already. You may see a message that the ZFS modules stack load failed, but it can be ignored since the modules are builtin; this is just libzfs trying to load the modules even though they are builtin.&lt;/li&gt;
&lt;/ul&gt;
With these dependencies, you can probably compile static with the zpool_import support. The exact location of "zfs_config.h" may vary depending on your zfs and kernel versions, so adjust accordingly.

Read the foobarz-init source code to see how it uses kernel parameters. The params &lt;code&gt;root&lt;/code&gt; and &lt;code&gt;rootfstype&lt;/code&gt; are always required to tell init what root pool name to mount and the filesystem type (e.g. zfs).

For the zpool_import support: &lt;code&gt;zpool_import_name=poolname&lt;/code&gt;, or &lt;code&gt;zpool_import_guid=&lt;guid of a pool&gt;&lt;/code&gt; tells what pool to import. You can also import the pool with a new different name by also using &lt;code&gt;zpool_import_newname=newpoolname&lt;/code&gt;. If the import is not working, &lt;code&gt;zpool_import_force=1&lt;/code&gt; can be used to force import even if ZFS thinks the pool may be in use by another system.

However you import the pool, either using zpool.cache or zpool_import support, the kernel param &lt;code&gt;root=&lt;your poolname or newpoolname&gt;&lt;/code&gt; and &lt;code&gt;rootfstype=zfs&lt;/code&gt; needs to be given also. The zpool_import only imports, it does not say what to mount. What to mount is still told using root= and rootfstype=.

Now copy the compiled static program into the initramfs:
&lt;pre&gt;
cp init /boot/initramfs-source/init
&lt;/pre&gt;

Build and install kernel:
&lt;pre&gt;
cd /usr/src/linux-3.2.29b
make -j8
make -j8 modules_install
cp arch/x86/boot/bzImage /boot/vm3.2.29b
cp System.map /boot/System.map-vm3.2.29b
# add new lilo menu entry for vm3.2.29b kernel
vi /etc/lilo.conf
  image = /boot/vm3.2.29b
   label = vm3.2.29b
   addappend = " spl.spl_hostid=0x007f0100 zfs.spa_config_path=/etc/zfs/zpool.cache root=zfs-root rootfstype=zfs"
lilo
reboot
&lt;/pre&gt;
Note: If &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; is not included in addappend, then during boot SPL module will attempt to read &lt;code&gt;/etc/hostid&lt;/code&gt; or else run a user-space helper to write the &lt;code&gt;hostid&lt;/code&gt; into &lt;code&gt;/proc/sys/kernel/spl/hostid&lt;/code&gt;. Reading &lt;code&gt;/etc/hostid&lt;/code&gt; fails unless you use [https://github.com/foobarz/foobarz-chhostid foobarz-chhostid] to make the file and copy it to &lt;code&gt;/boot/initramfs-source/etc/hostid&lt;/code&gt; then run the steps above again. The helper will fail because no &lt;code&gt;sh&lt;/code&gt; shell and no &lt;code&gt;hostid&lt;/code&gt; command are installed in the initramfs. The default hostid becomes 0xffffffff, which is considered an invalid hostid.

Congrats! If this works, you can select the "vm3.2.29b" lilo entry to boot. If you are using the zpool_import support in the init program, you need to add at least the &lt;code&gt;zpool_import_name=zfs-root&lt;/code&gt; param to the addappend line in lilo.conf.

Notes on kernel params (lilo append and addappend lines): root= and rootfstype= are used by both foorbarz-init and mkinitrd. The "ro" param is not used by foobarz-init, so instead use: mountopt=ro|rw. See "modinfo spl" and "modinfo zfs" to see all of the options those modules can take on the kernel command line. Notice the &lt;code&gt;spl.spl_hostid=0x007f0100&lt;/code&gt; param that works around the hostid mismatch problem while trying to import a pool; this param and hostname/ip set to use local loopback 127.0.0.1 in etc/hosts etc/HOSTNAME in initramfs will work most of the time, and if not the pool import needs to be forced.

Notes on the spl and zfs packages to install: &lt;i&gt;If&lt;/i&gt; you have errors using zfs and zpool commands on booted system with builtin modules, then upgrade/switch to the 0.6.0rc11_3.2.29b builds, or you can make a custom package with the binaries renamed like zpoolb, zfsb etc for builtin.

----
Using qemu's -nographic serial console (/usr/share/qemu/sgabios.bin): If you have a boot problem, you might want to run in qemu's -nographic console mode:

First, edit /etc/inittab, and uncomment the line for local serial ports runlevel "s1" (ttyS0) for serial console login support. This is done in the guest (host does not need this):
&lt;pre&gt;
# Local serial lines:
s1:12345:respawn:/sbin/agetty -L ttyS0 38400 linux
#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100
#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100
&lt;/pre&gt;
Second, edit /etc/securetty, and uncomment ttyS0 line:
&lt;pre&gt;
ttyS0
#ttyS1
# ...
&lt;/pre&gt;
You cannot login on ttyS0 without this change even though you get the login prompt!

Then, run qemu such as:
&lt;pre&gt;
qemu-kvm &lt;all regular options&gt; -nographic -option-rom sgabios.bin,bootindex=0
&lt;/pre&gt;
Wait for the lilo prompt, it may take several seconds show up in this mode.

In the lilo menu, select your kernel image with builtin spl/zfs, and use kernel params such as:
&lt;pre&gt;
boot: vm3.2.29b console=ttyS0
&lt;/pre&gt;
At the lilo prompt, use kernel parameter: console=ttyS0 (do NOT say /dev/ttS0). Passing runlevel=s1 does not appear to be necessary.

When you are in qemu's serial mode, the interface is a little different than in the normal graphical mode: use keypresses:
&lt;pre&gt;
ctrl-a h    # for help
ctrl-a c    # toggle access to (QEMU) console / back to emulation
&lt;/pre&gt;
If you cannot get a login: prompt, try ctrl-a c, then do (QEMU) sendkey ctrl-alt-delete. This will reboot cleanly back to lilo, then you can do (QEMU) quit.

Once you login to the guest, the terminal size needs adjustment. On your host, in another xterm sized the same as your guest console terminal, get the size of the terminal:
&lt;pre&gt;
echo $LINES
echo $COLUMNS
&lt;/pre&gt;
Now, back in the guest terminal of same size:
&lt;pre&gt;
export LINES &lt;lines&gt;
export COLUMNS &lt;columns&gt;
stty cols $COLUMNS rows $LINES
exec bash
reset
&lt;/pre&gt;
So, you set the environment variables and also set them with stty. Then, restart bash (exec, or else it is a child shell process).

BECAREFUL not to start qemu twice on the same ZFS guest! Two simultaneous running qemu on the same ZFS will corrupt the pool and it will NOT recover - you lose your whole installation! Before running qemu, check ps -A, look for an already running qemu process incase it somehow entered into the background!

BECAREFUL when using -nographic ttyS0 that you are not doing commands on the HOST! Only use -nographic to see kernel problems. Use regular console if booting is working normally.

To use the qemu -drive if=scsi option, the linux module sym53c8xx should be loaded in the guest. You may need to use the qemu option:
&lt;pre&gt;
-option-rom 8xx_64.rom,bootindex=1
&lt;/pre&gt;
The file 8xx_64.rom used to be inside qemu, but in new versions it is missing. You can download it:
&lt;pre&gt;
wget http://www.lsi.com/downloads/Public/Host%20Bus%20Adapters/Host%20Bus%20Adapters%20Common%20Files/lsi_bios.zip
&lt;/pre&gt;
Extract the zip and place 8xx_64.rom in /usr/share/qemu/.

Good luck!</text>
    <sha1>7fbba332770064d8ef7e24af8063bb956ae3fbac</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Install Slackware Using A USB Flash Drive</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>806</id>
    <parentid>490</parentid>
    <timestamp>2012-09-30T11:20:26Z</timestamp>
    <contributor>
      <username>Dont stop me</username>
      <id>303</id>
    </contributor>
    <minor/>
    <comment>Updated installation source selection. The old option did not accept the iso9960 partition system.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2923" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is, and mount the device to some location:

 mkdir flash &amp;&amp; mount /dev/sdX1 flash

When installing, choose "Install from a Slackware CD or DVD" then select the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed.

Other than that, installation process should be no different than when installing from a DVD.</text>
    <sha1>452db266e52c791170aaf3dae4e2df319fa8e3fe</sha1>
  </revision>
  <revision>
    <id>808</id>
    <parentid>806</parentid>
    <timestamp>2012-09-30T11:45:05Z</timestamp>
    <contributor>
      <username>Dont stop me</username>
      <id>303</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2958" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is, and mount the device to some location:

 mkdir flash &amp;&amp; mount /dev/sdX1 flash

When installing, choose "Install from a Slackware CD or DVD" then select the "manual" option and after that the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed.

Other than that, installation process should be no different than when installing from a DVD.</text>
    <sha1>7296c22ba5c734226979e0c3d6b39bcdfa844b5c</sha1>
  </revision>
  <revision>
    <id>830</id>
    <parentid>808</parentid>
    <timestamp>2013-03-09T21:03:54Z</timestamp>
    <contributor>
      <username>Enjoying life</username>
      <id>317</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3390" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is, and mount the device to some location:

 mkdir flash &amp;&amp; mount /dev/sdX1 flash

When installing, choose "Install from a Slackware CD or DVD" then select the "manual" option and after that the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed.

Other than that, installation process should be no different than when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit and /slackware64 for 64 bit.</text>
    <sha1>075e538b8a13fa5362b134c6a97038d5b6c54a8d</sha1>
  </revision>
  <revision>
    <id>831</id>
    <parentid>830</parentid>
    <timestamp>2013-03-09T21:19:59Z</timestamp>
    <contributor>
      <username>Enjoying life</username>
      <id>317</id>
    </contributor>
    <comment>/* Install with Unetbootin */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3450" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is, and mount the device to some location:

 mkdir flash &amp;&amp; mount /dev/sdX1 flash

When installing, choose "Install from a Slackware CD or DVD" then select the "manual" option and after that the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed.

Other than that, installation process should be no different than when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit and /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>bbb4dd1068a3dd5e69ec5a188725cb62a2d70bed</sha1>
  </revision>
  <revision>
    <id>832</id>
    <parentid>831</parentid>
    <timestamp>2013-03-09T21:25:05Z</timestamp>
    <contributor>
      <username>Enjoying life</username>
      <id>317</id>
    </contributor>
    <comment>/* Install with Unetbootin */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3449" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is, and mount the device to some location:

 mkdir flash &amp;&amp; mount /dev/sdX1 flash

When installing, choose "Install from a Slackware CD or DVD" then select the "manual" option and after that the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed.

Other than that, installation process should be no different than when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>c9f9679dd77c787ef202647ab84dffcf4f67b55c</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Talk:Install Slackware Using A USB Flash Drive</title>
  <ns>1</ns>
  <id>292</id>
  <revision>
    <id>807</id>
    <parentid>753</parentid>
    <timestamp>2012-09-30T11:26:28Z</timestamp>
    <contributor>
      <username>Dont stop me</username>
      <id>303</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1355" xml:space="preserve">Hi,

I'm new to slackware. I tried installing it as given in the wiki page. But ran into trouble in the last stage. 
First of all, fdisk -l shows sdb - 16 gb(usb size), sdb1 (4 gb) and sdb1p1 (similar size). What is sdb1p1? Which one do I mount? I decided to mount sdb1.

After mounting and running setup, I set up the targets \home, \usr etc. Then it says it has detected FAT/NTFS filesystem (the usb in all probability) and if I want to add that to fstab. I tried different things here. Since the usb is already mounted, I first tried answering no and going to install. Later I tried mounting sdb1 in flash at this step again and then running install. In both cases, when I select "install from hard disk partition" and select source partition as "/dev/sdb1" and then source path as "/slackware" or "/flash/slackware" or "slackware", it says "error mounting, should I continue". I tried using install option "pre-mounted directory" and gave "/flash/slackware" as the directory but it couldn't find the directory. What am I doing wrong?

Hi,

I had the same issue.

You have to select "Install from a Slackware CD or DVD" then select custom. Enter the device path ex. /dev/sdb1. Installatin should proceed as normal.
The reason for this is that installing from hard disks option does not support iso9660 filesystem.

Hope this helps,

Best wishes,
Zoltan</text>
    <sha1>1f36476721c558e6474d1b27699d917b82e8bfa5</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Customizing Bash Prompt</title>
  <ns>0</ns>
  <id>77</id>
  <revision>
    <id>809</id>
    <parentid>727</parentid>
    <timestamp>2012-12-03T07:01:42Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4794" xml:space="preserve">[[Category:Tips]]

Originally posted by 
http://www.compelitepc.com

There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@compelitepc.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[sales@compelitepc.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes.</text>
    <sha1>d20b8af9f15e0be3116889676dd7e3b933235c7c</sha1>
  </revision>
  <revision>
    <id>810</id>
    <parentid>809</parentid>
    <timestamp>2012-12-03T07:02:13Z</timestamp>
    <contributor>
      <username>Supyrow</username>
      <id>196</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4812" xml:space="preserve">[[Category:Tips]]

Originally posted by 
http://www.compelitepc.com
Look under HOWTOs

There are allot of white papers on customizing the bash prompt. This one is of course different... by a small margin. It starts by mapping out colors from "\033" or "ESC" commands into text commands for better reading, modifying or if you change your background and have a transparent terminal running and need to change colors again with out having to remember or look up the color codes.

&lt;pre&gt; 
#.bashrc 
DULL=0
BRIGHT=1
FG_BLACK=30
FG_RED=31
FG_GREEN=32
FG_YELLOW=33
FG_BLUE=34
FG_VIOLET=35
FG_CYAN=36
FG_WHITE=37
FG_NULL=00
BG_BLACK=40
BG_RED=41
BG_GREEN=42
BG_YELLOW=43
BG_BLUE=44
BG_VIOLET=45
BG_CYAN=46
BG_WHITE=47
BG_NULL=00

ESC="\033"
NORMAL="\[$ESC[m\]"
RESET="\[$ESC[${DULL};${FG_WHITE};${BG_NULL}m\]"
BLACK="\[$ESC[${DULL};${FG_BLACK}m\]"
RED="\[$ESC[${DULL};${FG_RED}m\]"
GREEN="\[$ESC[${DULL};${FG_GREEN}m\]"
YELLOW="\[$ESC[${DULL};${FG_YELLOW}m\]"
BLUE="\[$ESC[${DULL};${FG_BLUE}m\]"
VIOLET="\[$ESC[${DULL};${FG_VIOLET}m\]"
CYAN="\[$ESC[${DULL};${FG_CYAN}m\]"
WHITE="\[$ESC[${DULL};${FG_WHITE}m\]"
BRIGHT_BLACK="\[$ESC[${BRIGHT};${FG_BLACK}m\]"
BRIGHT_RED="\[$ESC[${BRIGHT};${FG_RED}m\]"
BRIGHT_GREEN="\[$ESC[${BRIGHT};${FG_GREEN}m\]"
BRIGHT_YELLOW="\[$ESC[${BRIGHT};${FG_YELLOW}m\]"
BRIGHT_BLUE="\[$ESC[${BRIGHT};${FG_BLUE}m\]"
BRIGHT_VIOLET="\[$ESC[${BRIGHT};${FG_VIOLET}m\]"
BRIGHT_CYAN="\[$ESC[${BRIGHT};${FG_CYAN}m\]"
BRIGHT_WHITE="\[$ESC[${BRIGHT};${BG_WHITE}m\]"
REV_CYAN="\[$ESC[${DULL};${BG_WHITE};${BG_CYAN}m\]"
REV_RED="\[$ESC[${DULL};${FG_YELLOW}; ${BG_RED}m\]"

PROMPT_COMMAND='export ERR=$?'
&lt;/pre&gt;

If you happen to use Eterm or other advanced terminal its possible you need a ".bash_profile" here is one you can use if you don't have one.

&lt;pre&gt;
#.bash_profile
source .bashrc
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi 
#End Script
&lt;/pre&gt;

Lets put it to work: I personally would comment out my currently working ##"PS1=" and put it below it in case you need to change it back for some reason.

&lt;pre&gt;
PS1="${GREEN}YOUR COMPANY NAME HERE${BRIGHT_YELLOW}[${YELLOW}\u@compelitepc.com${BRIGHT_YELLOW}]\n
${BRIGHT_CYAN}[${CYAN}\t${BRIGHT_CYAN}]${BRIGHT_VIOLET}[${VIOLET}\$(lsMB)${BRIGHT_VIOLET} |
${VIOLET}\$(lsMiB)${BRIGHT_VIOLET}]${BRIGHT_YELLOW}[${YELLOW}\w${BRIGHT_YELLOW}]\n
${BRIGHT_YELLOW}[${YELLOW}\!${BRIGHT_YELLOW}]${BRIGHT_CYAN} %&gt; ${RESET}"
&lt;/pre&gt;

Should look like this minus the colors:

&lt;pre&gt;
YOUR COMPANY NAME HERE[sales@compelitepc.com]
[13:57:23][590.478 MB|563.316 MiB][/media/cdrom]
[503] %&gt; 
&lt;/pre&gt;

Note: the [503] is the history line number for those who cant remember what they typed or want to input something from the far past.

Now... To get the sum of files in current working directory, I made two files which do the summing. "lsMB" and "lsMiB" which on my system are both located in ~/bin as executable. Here is lsMB:

&lt;pre&gt;
#!/bin/bash
#lsMB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1024 \nquit" | bc)
   suffix="kB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1048576 \nquit" | bc)
   suffix="MB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize=$(echo -e "scale=3 \n$TotalBytes/1073741824 \nquit" | bc)
   suffix="GB"
fi
fi
fi
fi
echo -n "$TotalSize $suffix"
#End Script
&lt;/pre&gt;

Finally, this is the lsMiB executable file located in "~/bin" This has the modification for the conversion to KiB, MiB &amp; GiB one could further the code to handle TiB easily by doing some research on it... Try wiki!

&lt;pre&gt;
#!/bin/bash
#lsMiB free for anyone who wishes to use and implement it, just please show your work. ;)
let TotalBytes=0
for Bytes in $(ls -l -a | grep "^-" | awk '{ print $5 }')
do
   let TotalBytes=$TotalBytes+$Bytes
done
if [ $TotalBytes -lt 1024 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes \nquit" | bc)
   suffix2="B"
else if [ $TotalBytes -lt 1048576 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1024*.976 \nquit" | bc)
   suffix2="KiB"
else if [ $TotalBytes -lt 1073741824 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1048576*.954 \nquit" | bc)
   suffix2="MiB"
else if [ $TotalBytes -lt 1099511627776 ]; then
   TotalSize2=$(echo -e "scale=3 \n$TotalBytes/1073741824*.931 \nquit" | bc)
   suffix2="GiB"
fi
fi
fi
fi
echo -n "$TotalSize2 $suffix2"
#End Script
&lt;/pre&gt;

One would be able to see the changes if 1) Restart the Terminal or 2) type:&lt;pre&gt;$ source ~/.bashrc&lt;/pre&gt; and you will instantly see the changes.</text>
    <sha1>1fd5e221f851d3ef500c06f733ebd654a40d89b4</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>User:Funnyhodge</title>
  <ns>2</ns>
  <id>302</id>
  <revision>
    <id>813</id>
    <timestamp>2012-12-06T16:33:13Z</timestamp>
    <contributor>
      <username>Funnyhodge</username>
      <id>310</id>
    </contributor>
    <comment>Funnyhodge moved page [[User:Funnyhodge]] to [[User:Data control and optimization]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="48" xml:space="preserve">#REDIRECT [[User:Data control and optimization]]</text>
    <sha1>cfc116e75f114452877a7f9861bf44444e48b73b</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Google Earth</title>
  <ns>0</ns>
  <id>96</id>
  <revision>
    <id>814</id>
    <parentid>118</parentid>
    <timestamp>2012-12-17T06:58:24Z</timestamp>
    <contributor>
      <username>Tonyguards</username>
      <id>311</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1813" xml:space="preserve">[[Category:Tips]]

You can download Google Earth from http://earth.google.com/

You have to set the .bin file that you download to be executatable, and then run it, to install.

&lt;pre&gt;
chmod a+x GoogleEarthLinux.bin
./GoogleEarthLinux.bin
&lt;/pre&gt;

By default it installs itself in /opt/google-earth/ .  It offers to make a link from /usr/local/bin/googleearth to the right executable, I recommend allowing it to do this.

Once it is done, to run it you just type "googleearth" in an xterm (X must be running).  You can make the appropriate desktop icon or menu item depending on what window manager you are using.

If the splash screen shows up for some amount of time, and then all of X (the entire graphical environment) crashes (if you have graphical login set up, it will give you a login screen again, otherwise you will go back to the console), some people have found this to be solved by downloading the libGL.so library.  It should be put in the /opt/google-earth/ directory:

(as root)
&lt;pre&gt;
cd /opt/google-earth/
wget http://librarian.launchpad.net/7037027/libGL.so.1 -O libGL.so.1
&lt;/pre&gt;

Some places on the web also refer to downloading it from http://www.ground-impact.com/libGL.so.1.2 .  Here are links to a few discussions of the issue:

http://www.linuxquestions.org/questions/slackware-14/google-earth-crashes-x-598569/?s=3ff14bc2cdec277267c5547b7dee84d9
http://forum.mandriva.com/viewtopic.php?t=71691&amp;highlight=googleearth

'''Performance Issue with Google Earth:'''
&lt;pre&gt;
if google earth is slow in slackware Linux, check whether DRI is enabled or not, if Direct Rendering is enabled then
disable "Atmosphere" effect from View menu -&gt; [x] Atmosphere for smoother functioning of the graphics in Google Earth window.
&lt;/pre&gt;

[http://littletods.com/en/content/4-perlengkapan-bayi Perlengkapan Bayi]</text>
    <sha1>e42469ddba16aab8f8ba64b7fc0c4d3eeda9d731</sha1>
  </revision>
  <revision>
    <id>815</id>
    <parentid>814</parentid>
    <timestamp>2012-12-17T07:02:19Z</timestamp>
    <contributor>
      <username>Tonyguards</username>
      <id>311</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1971" xml:space="preserve">[[Category:Tips]]

You can download Google Earth from http://earth.google.com/

You have to set the .bin file that you download to be executatable, and then run it, to install.

&lt;pre&gt;
chmod a+x GoogleEarthLinux.bin
./GoogleEarthLinux.bin
&lt;/pre&gt;

By default it installs itself in /opt/google-earth/ .  It offers to make a link from /usr/local/bin/googleearth to the right executable, I recommend allowing it to do this.

Once it is done, to run it you just type "googleearth" in an xterm (X must be running).  You can make the appropriate desktop icon or menu item depending on what window manager you are using.

If the splash screen shows up for some amount of time, and then all of X (the entire graphical environment) crashes (if you have graphical login set up, it will give you a login screen again, otherwise you will go back to the console), some people have found this to be solved by downloading the libGL.so library.  It should be put in the /opt/google-earth/ directory:

(as root)
&lt;pre&gt;
cd /opt/google-earth/
wget http://librarian.launchpad.net/7037027/libGL.so.1 -O libGL.so.1
&lt;/pre&gt;

Some places on the web also refer to downloading it from http://www.ground-impact.com/libGL.so.1.2 .  Here are links to a few discussions of the issue:

http://www.linuxquestions.org/questions/slackware-14/google-earth-crashes-x-598569/?s=3ff14bc2cdec277267c5547b7dee84d9
http://forum.mandriva.com/viewtopic.php?t=71691&amp;highlight=googleearth

'''Performance Issue with Google Earth:'''
&lt;pre&gt;
if google earth is slow in slackware Linux, check whether DRI is enabled or not, if Direct Rendering is enabled then
disable "Atmosphere" effect from View menu -&gt; [x] Atmosphere for smoother functioning of the graphics in Google Earth window.
&lt;/pre&gt;

* [http://littletods.com/en/content/4-perlengkapan-bayi Perlengkapan Bayi]
* [http://www.doxapest.co.id/index.php/pest-control-dan-anti-rayap Anti Rayap]
* [http://saranasukses.com/outsourcing-indonesia.html Outsourcing Indonesia]</text>
    <sha1>a77066b87b7a9b18bf269ec8c0adfdb48114043f</sha1>
  </revision>
  <revision>
    <id>816</id>
    <parentid>815</parentid>
    <timestamp>2012-12-17T15:20:26Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Tonyguards|Tonyguards]] ([[User talk:Tonyguards|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1739" xml:space="preserve">[[Category:Tips]]

You can download Google Earth from http://earth.google.com/

You have to set the .bin file that you download to be executatable, and then run it, to install.

&lt;pre&gt;
chmod a+x GoogleEarthLinux.bin
./GoogleEarthLinux.bin
&lt;/pre&gt;

By default it installs itself in /opt/google-earth/ .  It offers to make a link from /usr/local/bin/googleearth to the right executable, I recommend allowing it to do this.

Once it is done, to run it you just type "googleearth" in an xterm (X must be running).  You can make the appropriate desktop icon or menu item depending on what window manager you are using.

If the splash screen shows up for some amount of time, and then all of X (the entire graphical environment) crashes (if you have graphical login set up, it will give you a login screen again, otherwise you will go back to the console), some people have found this to be solved by downloading the libGL.so library.  It should be put in the /opt/google-earth/ directory:

(as root)
&lt;pre&gt;
cd /opt/google-earth/
wget http://librarian.launchpad.net/7037027/libGL.so.1 -O libGL.so.1
&lt;/pre&gt;

Some places on the web also refer to downloading it from http://www.ground-impact.com/libGL.so.1.2 .  Here are links to a few discussions of the issue:

http://www.linuxquestions.org/questions/slackware-14/google-earth-crashes-x-598569/?s=3ff14bc2cdec277267c5547b7dee84d9
http://forum.mandriva.com/viewtopic.php?t=71691&amp;highlight=googleearth

'''Performance Issue with Google Earth:'''
&lt;pre&gt;
if google earth is slow in slackware Linux, check whether DRI is enabled or not, if Direct Rendering is enabled then
disable "Atmosphere" effect from View menu -&gt; [x] Atmosphere for smoother functioning of the graphics in Google Earth window.
&lt;/pre&gt;</text>
    <sha1>b2ad930a00343e4563141b3261b42c4da4d45198</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Multilib</title>
  <ns>0</ns>
  <id>228</id>
  <revision>
    <id>817</id>
    <parentid>396</parentid>
    <timestamp>2012-12-18T07:22:32Z</timestamp>
    <contributor>
      <username>RonaldCole</username>
      <id>312</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="799" xml:space="preserve">There's a good tutorial (and packages) on how to set up multilib support (32-bit programs on Slackware64) at
[http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib AlienBOB's site]. You'd do well to go there next.

''However'', as that's not complete and clear on all points, here are some details:

==Binary display drivers==

You need to reinstall binary drivers. ATI and Nvidia driver packages contain both 64bit and 32bit libraries to be maximally useful on a 64bit multilib OS. However, the slackbuild scripts available at slackbuilds.org are not up to this task, so if you already installed 64-bit binary drivers from slackbuilds.org, you should remove these and then use ATI's or Nvidia's driver installer.


[[Category:Tutorials]]
&lt;nowiki&gt;http://essaywritingservice.co/&lt;/nowiki&gt;</text>
    <sha1>941870259c0bdf1e9a7c14aea5a46377abfe2fb8</sha1>
  </revision>
  <revision>
    <id>818</id>
    <parentid>817</parentid>
    <timestamp>2012-12-18T13:58:01Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/RonaldCole|RonaldCole]] ([[User talk:RonaldCole|talk]]) to last revision by [[User:Merge-delete|Merge-delete]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="751" xml:space="preserve">There's a good tutorial (and packages) on how to set up multilib support (32-bit programs on Slackware64) at
[http://alien.slackbook.org/dokuwiki/doku.php?id=slackware:multilib AlienBOB's site]. You'd do well to go there next.

''However'', as that's not complete and clear on all points, here are some details:

==Binary display drivers==

You need to reinstall binary drivers. ATI and Nvidia driver packages contain both 64bit and 32bit libraries to be maximally useful on a 64bit multilib OS. However, the slackbuild scripts available at slackbuilds.org are not up to this task, so if you already installed 64-bit binary drivers from slackbuilds.org, you should remove these and then use ATI's or Nvidia's driver installer.


[[Category:Tutorials]]</text>
    <sha1>c1907982c750d717ec701e87c90a4923a26cebc4</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Resource Limits</title>
  <ns>0</ns>
  <id>31</id>
  <revision>
    <id>819</id>
    <parentid>48</parentid>
    <timestamp>2013-01-02T01:35:09Z</timestamp>
    <contributor>
      <username>Beder</username>
      <id>313</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2574" xml:space="preserve">= Purpose =

This page does not attempt to explain the different types of system resource limits or when it is (or is not) appropriate to change them; see '''man ulimit''' and [[http://google.com Google]] for that discussion.

However, some users run into problems with the linux kernel's default limit settings, so we'll attempt to explain how to modify them to suit special needs.

= Overview =

The default settings provided by the kernel are sane values for most multi-user machines.  Issuing the command '''ulimit -Hn''' should show the following:
 user@host:~$ ulimit -Hn
 1024
and '''ulimit -n''' should show this:
 user@host:~$ ulimit -n
 1024

The first command shows the hard limit set by the kernel, and the second command shows the soft limit set by the user.  An unprivileged user can increase the soft limit (up to the hard limit value), and he is also able to lower the hard limit (but then is unable to increase it, as an unprivileged user cannot raise the hard limit at all).

There are some situations which might require a larger hard limit for users, and the obvious "solution" is to add a line in /etc/profile to increase it.  However, this will not work, because normal users cannot increase their hard limits (as indicated above).

= Solution =

To increase the hard limits for users, you will need to create '''/etc/initscript''' and place appropriate commands inside it.  The easiest way is to copy the file '''/sbin/initscript.sample''' to '''/etc/initscript''' and edit the copy, but you are certainly free to "roll your own." 

Using the following '''/etc/initscript''' file:

 PATH=/bin:/sbin:/usr/bin:/usr/sbin
 export PATH
 
 # Increase the hardlimit for open files
 ulimit -Hn 4096
 
 # Execute the program.
 eval exec "$4"

You should get the following after a reboot:
 user@host:~$ ulimit -Hn
 4096
 
 user@host:~$ ulimit -n
 1024

Notice that the hardlimit is now 4096 (as specified in /etc/initscript), but the softlimit is still 1024.  In other words, you will still need to use /etc/profile (or some other shell init file - see below for recommendation) to raise the desired users' softlimits.  With some creative scripting, you can be more selective about which users have what limits.

Rather than editing the system /etc/profile, it's recommended to create a custom file in /etc/profile.d and make it executable.  This way, you don't have to worry about trying to merge your changes to /etc/profile when doing Slackware upgrades to new versions.

= Other Resources =

* '''man initscript'''
* '''man ulimit'''

[[Category:Tutorials]]</text>
    <sha1>2d43ea3b4bae0ff7f88322bb72cb7a05cb60d7a7</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>User talk:Beder</title>
  <ns>3</ns>
  <id>303</id>
  <revision>
    <id>820</id>
    <timestamp>2013-01-02T02:27:45Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Thanks!</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="53" xml:space="preserve">Thanks for the fix in Resource_Limits :-)  --rworkman</text>
    <sha1>fb496efcf83ed92f260c9b273d4c7095d0e8ffc1</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>PPPoE</title>
  <ns>0</ns>
  <id>79</id>
  <revision>
    <id>821</id>
    <parentid>101</parentid>
    <timestamp>2013-01-30T10:05:31Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <minor/>
    <comment>/* Connecting With PPPoE */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="655" xml:space="preserve">[[Category:Tutorials]]

== Setting Up PPPoE ==

As root, run '''pppoe-setup'''. Answer the questions.

'''GOTCHA:''' on the last question, answer ''1 STAND ALONE''.


== Connecting With PPPoE ==

As root, run '''pppoe-start'''.


You should now be connected.


PROBLEM: It reports connected but, I can't get to the internet.

FIX: It's probably screwed up your routing table.
::route del default
::route add default dev ppp0
Your connection should be working now.

To make this process automatic at bootup, add the following lines at the end of file /etc/rc.d/rc.local:

::pppoe-start
::route del default
::route add default dev ppp0 

and then reboot...</text>
    <sha1>25e0a7cbc22693deca6dafe7e94f286a0e7702ed</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Administration (General)</title>
  <ns>0</ns>
  <id>38</id>
  <revision>
    <id>822</id>
    <parentid>59</parentid>
    <timestamp>2013-01-30T10:17:26Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <minor/>
    <comment>/* Hostname */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="882" xml:space="preserve">== Hostname ==

You can change a Slackware box's &lt;code&gt;hostname&lt;/code&gt; by two methods:

1) Edit &lt;code&gt;/etc/HOSTNAME&lt;/code&gt;

2) Use the hostname command-

:On any running Linux system you can change its hostname with the command ‘hostname‘.

::'''&lt;code&gt;#hostname&lt;/code&gt;''' without any parameter it will output the current hostname of the system.

::'''&lt;code&gt;hostname –fd&lt;/code&gt;''' will output the fully qualified domain name (or FQDN) of the system.

::'''&lt;code&gt;hostname NEW_NAME&lt;/code&gt;''' will set the hostname of the system to NEW_NAME. This is active right away and will remain like that until the system will be rebooted (because at system boot it will set this from some particular file configurations - see bellow how to set this permanently). You will most probably need to exit the current shell in order to see the change in your shell prompt.


[[Category:Tutorials]]</text>
    <sha1>15f71235cf0120da5310e2fa7d0a72e772ff727c</sha1>
  </revision>
  <revision>
    <id>823</id>
    <parentid>822</parentid>
    <timestamp>2013-01-30T10:20:50Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <minor/>
    <comment>/* Hostname */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="881" xml:space="preserve">== Hostname ==

You can change a Slackware box's &lt;code&gt;hostname&lt;/code&gt; by two methods:

1) Edit &lt;code&gt;/etc/HOSTNAME&lt;/code&gt;

2) Use the hostname command-

:On any running Linux system you can change its hostname with the command ‘hostname‘.

::'''&lt;code&gt;#hostname&lt;/code&gt;''' without any parameter it will output the current hostname of the system.

::'''&lt;code&gt;hostname –f&lt;/code&gt;''' will output the fully qualified domain name (or FQDN) of the system.

::'''&lt;code&gt;hostname NEW_NAME&lt;/code&gt;''' will set the hostname of the system to NEW_NAME. This is active right away and will remain like that until the system will be rebooted (because at system boot it will set this from some particular file configurations - see bellow how to set this permanently). You will most probably need to exit the current shell in order to see the change in your shell prompt.


[[Category:Tutorials]]</text>
    <sha1>ba6f2735593a2a56d569d3d8e7a183ddb5bcd52a</sha1>
  </revision>
  <revision>
    <id>824</id>
    <parentid>823</parentid>
    <timestamp>2013-01-30T10:21:16Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <minor/>
    <comment>/* Hostname */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="880" xml:space="preserve">== Hostname ==

You can change a Slackware box's &lt;code&gt;hostname&lt;/code&gt; by two methods:

1) Edit &lt;code&gt;/etc/HOSTNAME&lt;/code&gt;

2) Use the hostname command-

:On any running Linux system you can change its hostname with the command ‘hostname‘.

::'''&lt;code&gt;hostname&lt;/code&gt;''' without any parameter it will output the current hostname of the system.

::'''&lt;code&gt;hostname –f&lt;/code&gt;''' will output the fully qualified domain name (or FQDN) of the system.

::'''&lt;code&gt;hostname NEW_NAME&lt;/code&gt;''' will set the hostname of the system to NEW_NAME. This is active right away and will remain like that until the system will be rebooted (because at system boot it will set this from some particular file configurations - see bellow how to set this permanently). You will most probably need to exit the current shell in order to see the change in your shell prompt.


[[Category:Tutorials]]</text>
    <sha1>dbbd7f1ec5351c8142a2b3f065e90cdb56f069dd</sha1>
  </revision>
  <revision>
    <id>825</id>
    <parentid>824</parentid>
    <timestamp>2013-01-30T10:23:16Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="864" xml:space="preserve">== Hostname ==

You can change a Slackware box's &lt;code&gt;hostname&lt;/code&gt; by two methods:

1) Edit &lt;code&gt;/etc/HOSTNAME&lt;/code&gt;

2) Use the hostname command-

:On any running Linux system you can change its hostname with the command ‘hostname‘.

::'''&lt;code&gt;hostname&lt;/code&gt;''' without any parameter it will output the current hostname of the system.

::'''&lt;code&gt;hostname –f&lt;/code&gt;''' will output the fully qualified domain name (or FQDN) of the system.

::'''&lt;code&gt;hostname NEW_NAME&lt;/code&gt;''' will set the hostname of the system to NEW_NAME. This is active right away and will remain so  until the system is rebooted (because at system boot it sets this from some particular file configuration - see bellow how to set this permanently). You will most probably need to exit the current shell in order to see the change in your shell prompt.


[[Category:Tutorials]]</text>
    <sha1>061d901ee9b0931b19d33ba77e47ad324912d7de</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>User:Gutrus gutrus</title>
  <ns>2</ns>
  <id>304</id>
  <revision>
    <id>826</id>
    <timestamp>2013-01-30T10:25:42Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <comment>Created page with "Buon giorno!   LOL!"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19" xml:space="preserve">Buon giorno! 

LOL!</text>
    <sha1>ad3a41aa0e6dd716a038b5cfc70874f2fd44b312</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Fstab</title>
  <ns>0</ns>
  <id>94</id>
  <revision>
    <id>827</id>
    <parentid>474</parentid>
    <timestamp>2013-01-30T10:33:23Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <minor/>
    <comment>/* Syntax */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3913" xml:space="preserve">The /etc/fstab file tells the system how and where to mount filesystems by default.

==Syntax==
The syntax of the file is this:

&lt;table cellspacing="10"&gt;
&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;MAN PAGE-ese:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;FS_SPEC&lt;/td&gt;
&lt;td align="center"&gt;FS_FILE&lt;/td&gt;
&lt;td align="center"&gt;FS_VFSTYPE&lt;/td&gt;
&lt;td align="center"&gt;FS_MNTOPS&lt;/td&gt;
&lt;td align="center"&gt;FS_FREQ&lt;/td&gt;
&lt;td align="center"&gt;FS_PASSNO&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;IN ENGLISH:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;DEVICE&lt;/td&gt;
&lt;td align="center"&gt;MOUNT_POINT&lt;/td&gt;
&lt;td align="center"&gt;FILESYSTEM&lt;/td&gt;
&lt;td align="center"&gt;OPTIONS&lt;/td&gt;
&lt;td align="center"&gt;DUMP&lt;/td&gt;
&lt;td align="center"&gt;FSCK_ORDER&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;EXAMPLE:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;/dev/hdb1&lt;/td&gt;
&lt;td align="center"&gt;/mnt/windows&lt;/td&gt;
&lt;td align="center"&gt;vfat&lt;/td&gt;
&lt;td align="center"&gt;defaults&lt;/td&gt;
&lt;td align="center"&gt;0&lt;/td&gt;
&lt;td align="center"&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;

==Field Descriptions==
FS_SPEC (DEVICE) - the device or remote filesystem to be mounted.

FS_FILE (MOUNT_POINT) - the mount point for the filesystem. &lt;i&gt;NOTE: For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces these can be escaped as `\040'.&lt;/i&gt;

FS_VFSTYPE (FILESYSTEM)-  the type of the filesystem. As of Slackware 10.2, the FILE_SYSTEM choices are:
:auto, adfs, affs, autofs, coda, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xfs, xiafs and possibly others.
&lt;i&gt;NOTE: for swap-able and portable devices (e.g. memory sticks and CDROMs), &lt;code&gt;auto&lt;/code&gt; is the best choice because it allows the computer to determine the correct filesystem.&lt;/i&gt;

FS_MNTOPS (OPTION) - the (comma seperated) mount options. See the MOUNT command's MAN PAGE for the options because there are MANY!
The most commonly used options are:&lt;br&gt;
:noauto - do not mount this device/partition automatically on boot-up.
:ro - mount this device/partition READ-ONLY (e.g. CDROM).
:owner - Only allow the owner to mount and un-mount this device/partition.
:users - Allow any user to mount or unmount this device/partition.


FS_FREQ (DUMP) - used for these filesystems by the dump command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. For the most part, this should be "0" (zero).

FS_PASSNO (FSCK_ORDER) - used by the fsck program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

==Benefits Of fstab Entries==
Once you have a device in the fstab, mounting become VERY easy.  Instead of having to:
:&lt;code&gt;mount -t iso9660 /dev/hdb1 /mnt/cdrom&lt;/code&gt;
every time you want to use the CDROM, you can just type:
:&lt;code&gt;mount /mnt/cdrom&lt;/code&gt;
IF you have the entry in your fstab.


==Useful Examples==
CDROM:&lt;br&gt;
:/dev/hdc1 /mnt/cdrom auto noauto,ro,owner,users 0 0

[[USB Memory Stick]]:&lt;br&gt;
:/dev/sda1 /mnt/memstick auto noauto,owner,users 0 0&lt;br&gt;
(make sure to &lt;code&gt;mkdir /mnt/memstick&lt;/code&gt; after changing your /etc/fstab).

[[External USB Drive / NTFS partition]]
:/dev/sdd1        /media/1T        ntfs-3g     auto  0   0
(/dev/sdd1 is your external USB hard drive and /media/1T is destination folder)


Note: For changing who can access the filesystem on NON-Native linux formats see [[Permissions and Umasks]] and [[Windows Partitions]]

[[Category:Tutorials]]</text>
    <sha1>9aba1696e5162486953abe55fc6db8eaa31676af</sha1>
  </revision>
  <revision>
    <id>828</id>
    <parentid>827</parentid>
    <timestamp>2013-01-30T10:37:11Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <minor/>
    <comment>/* Useful Examples */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3916" xml:space="preserve">The /etc/fstab file tells the system how and where to mount filesystems by default.

==Syntax==
The syntax of the file is this:

&lt;table cellspacing="10"&gt;
&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;MAN PAGE-ese:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;FS_SPEC&lt;/td&gt;
&lt;td align="center"&gt;FS_FILE&lt;/td&gt;
&lt;td align="center"&gt;FS_VFSTYPE&lt;/td&gt;
&lt;td align="center"&gt;FS_MNTOPS&lt;/td&gt;
&lt;td align="center"&gt;FS_FREQ&lt;/td&gt;
&lt;td align="center"&gt;FS_PASSNO&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;IN ENGLISH:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;DEVICE&lt;/td&gt;
&lt;td align="center"&gt;MOUNT_POINT&lt;/td&gt;
&lt;td align="center"&gt;FILESYSTEM&lt;/td&gt;
&lt;td align="center"&gt;OPTIONS&lt;/td&gt;
&lt;td align="center"&gt;DUMP&lt;/td&gt;
&lt;td align="center"&gt;FSCK_ORDER&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;EXAMPLE:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;/dev/hdb1&lt;/td&gt;
&lt;td align="center"&gt;/mnt/windows&lt;/td&gt;
&lt;td align="center"&gt;vfat&lt;/td&gt;
&lt;td align="center"&gt;defaults&lt;/td&gt;
&lt;td align="center"&gt;0&lt;/td&gt;
&lt;td align="center"&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;

==Field Descriptions==
FS_SPEC (DEVICE) - the device or remote filesystem to be mounted.

FS_FILE (MOUNT_POINT) - the mount point for the filesystem. &lt;i&gt;NOTE: For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces these can be escaped as `\040'.&lt;/i&gt;

FS_VFSTYPE (FILESYSTEM)-  the type of the filesystem. As of Slackware 10.2, the FILE_SYSTEM choices are:
:auto, adfs, affs, autofs, coda, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xfs, xiafs and possibly others.
&lt;i&gt;NOTE: for swap-able and portable devices (e.g. memory sticks and CDROMs), &lt;code&gt;auto&lt;/code&gt; is the best choice because it allows the computer to determine the correct filesystem.&lt;/i&gt;

FS_MNTOPS (OPTION) - the (comma seperated) mount options. See the MOUNT command's MAN PAGE for the options because there are MANY!
The most commonly used options are:&lt;br&gt;
:noauto - do not mount this device/partition automatically on boot-up.
:ro - mount this device/partition READ-ONLY (e.g. CDROM).
:owner - Only allow the owner to mount and un-mount this device/partition.
:users - Allow any user to mount or unmount this device/partition.


FS_FREQ (DUMP) - used for these filesystems by the dump command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. For the most part, this should be "0" (zero).

FS_PASSNO (FSCK_ORDER) - used by the fsck program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

==Benefits Of fstab Entries==
Once you have a device in the fstab, mounting become VERY easy.  Instead of having to:
:&lt;code&gt;mount -t iso9660 /dev/hdb1 /mnt/cdrom&lt;/code&gt;
every time you want to use the CDROM, you can just type:
:&lt;code&gt;mount /mnt/cdrom&lt;/code&gt;
IF you have the entry in your fstab.


==Useful Examples==
CDROM/DVD:&lt;br&gt;
:/dev/sr0 /media/dvd auto noauto,ro,owner,users 0 0

[[USB Memory Stick]]:&lt;br&gt;
:/dev/sda1 /mnt/memstick auto noauto,owner,users 0 0&lt;br&gt;
(make sure to &lt;code&gt;mkdir /mnt/memstick&lt;/code&gt; after changing your /etc/fstab).

[[External USB Drive / NTFS partition]]
:/dev/sdd1        /media/1T        ntfs-3g     auto  0   0
(/dev/sdd1 is your external USB hard drive and /media/1T is destination folder)


Note: For changing who can access the filesystem on NON-Native linux formats see [[Permissions and Umasks]] and [[Windows Partitions]]

[[Category:Tutorials]]</text>
    <sha1>6e35d61dd81a976dc89b65dc14be829114b99510</sha1>
  </revision>
  <revision>
    <id>829</id>
    <parentid>828</parentid>
    <timestamp>2013-01-30T10:38:23Z</timestamp>
    <contributor>
      <username>Gutrus gutrus</username>
      <id>315</id>
    </contributor>
    <minor/>
    <comment>/* Useful Examples */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3925" xml:space="preserve">The /etc/fstab file tells the system how and where to mount filesystems by default.

==Syntax==
The syntax of the file is this:

&lt;table cellspacing="10"&gt;
&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;MAN PAGE-ese:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;FS_SPEC&lt;/td&gt;
&lt;td align="center"&gt;FS_FILE&lt;/td&gt;
&lt;td align="center"&gt;FS_VFSTYPE&lt;/td&gt;
&lt;td align="center"&gt;FS_MNTOPS&lt;/td&gt;
&lt;td align="center"&gt;FS_FREQ&lt;/td&gt;
&lt;td align="center"&gt;FS_PASSNO&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;IN ENGLISH:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;DEVICE&lt;/td&gt;
&lt;td align="center"&gt;MOUNT_POINT&lt;/td&gt;
&lt;td align="center"&gt;FILESYSTEM&lt;/td&gt;
&lt;td align="center"&gt;OPTIONS&lt;/td&gt;
&lt;td align="center"&gt;DUMP&lt;/td&gt;
&lt;td align="center"&gt;FSCK_ORDER&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td align="right"&gt;&lt;b&gt;EXAMPLE:&lt;/b&gt;&lt;/td&gt;
&lt;td align="center"&gt;/dev/hdb1&lt;/td&gt;
&lt;td align="center"&gt;/mnt/windows&lt;/td&gt;
&lt;td align="center"&gt;vfat&lt;/td&gt;
&lt;td align="center"&gt;defaults&lt;/td&gt;
&lt;td align="center"&gt;0&lt;/td&gt;
&lt;td align="center"&gt;1&lt;/td&gt;
&lt;/tr&gt;
&lt;/table&gt;

==Field Descriptions==
FS_SPEC (DEVICE) - the device or remote filesystem to be mounted.

FS_FILE (MOUNT_POINT) - the mount point for the filesystem. &lt;i&gt;NOTE: For swap partitions, this field should be specified as `none'. If the name of the mount point contains spaces these can be escaped as `\040'.&lt;/i&gt;

FS_VFSTYPE (FILESYSTEM)-  the type of the filesystem. As of Slackware 10.2, the FILE_SYSTEM choices are:
:auto, adfs, affs, autofs, coda, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, nfs4, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xfs, xiafs and possibly others.
&lt;i&gt;NOTE: for swap-able and portable devices (e.g. memory sticks and CDROMs), &lt;code&gt;auto&lt;/code&gt; is the best choice because it allows the computer to determine the correct filesystem.&lt;/i&gt;

FS_MNTOPS (OPTION) - the (comma seperated) mount options. See the MOUNT command's MAN PAGE for the options because there are MANY!
The most commonly used options are:&lt;br&gt;
:noauto - do not mount this device/partition automatically on boot-up.
:ro - mount this device/partition READ-ONLY (e.g. CDROM).
:owner - Only allow the owner to mount and un-mount this device/partition.
:users - Allow any user to mount or unmount this device/partition.


FS_FREQ (DUMP) - used for these filesystems by the dump command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. For the most part, this should be "0" (zero).

FS_PASSNO (FSCK_ORDER) - used by the fsck program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

==Benefits Of fstab Entries==
Once you have a device in the fstab, mounting become VERY easy.  Instead of having to:
:&lt;code&gt;mount -t iso9660 /dev/hdb1 /mnt/cdrom&lt;/code&gt;
every time you want to use the CDROM, you can just type:
:&lt;code&gt;mount /mnt/cdrom&lt;/code&gt;
IF you have the entry in your fstab.


==Useful Examples==
CDROM/DVD:&lt;br&gt;
:/dev/sr0  /media/dvd  auto  noauto,ro,owner,users  0  0

[[USB Memory Stick]]:&lt;br&gt;
:/dev/sda1  /mnt/memstick  auto  noauto,owner,users  0 0&lt;br&gt;
(make sure to &lt;code&gt;mkdir /mnt/memstick&lt;/code&gt; after changing your /etc/fstab).

[[External USB Drive / NTFS partition]]
:/dev/sdd1        /media/1T        ntfs-3g     auto  0   0
(/dev/sdd1 is your external USB hard drive and /media/1T is destination folder)


Note: For changing who can access the filesystem on NON-Native linux formats see [[Permissions and Umasks]] and [[Windows Partitions]]

[[Category:Tutorials]]</text>
    <sha1>148ed47ea90ed940ac89ac3cc4f3b00642d36722</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>PDF Printing</title>
  <ns>0</ns>
  <id>208</id>
  <revision>
    <id>833</id>
    <parentid>296</parentid>
    <timestamp>2013-03-15T16:23:37Z</timestamp>
    <contributor>
      <username>Allend</username>
      <id>75</id>
    </contributor>
    <comment>/* PDF Printing */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5986" xml:space="preserve">[[Category:Tips]]
== PDF Printing ==

While many applications offer exporting output to portable document format (PDF) files, many others do not.
It is easy to add a virtual PDF printer to CUPS by installing the cups-pdf package that is available at http://www.slackbuilds.org

This works well for single documents, but if you print multiple documents that are parsed as having the same name then the older documents will be overwritten.
A solution to this is to run a script that watches for the creation of the PDF document in the spool directory (/var/spool/cups-pdf/&lt;username&gt; by default) and then moves the document to another directory (USERS_DIR). The script below (watch_for_spooled_pdf.sh kept in /home/xx/pdf_printing) also prepends a date and time string to keep the document names unique.
A user xx should start this script as a background process i.e. /home/xx/pdf_printing/watch_for_spooled_pdf.sh &amp;

&lt;pre&gt;
#!/bin/sh

# Script to watch for creation of .pdf files by CUPS-PDF in spool directory
#  and move to users directory prepending the creation date and time.
#
# This script uses the -m option to inotifywait and should never exit.

SPOOL_DIR=/var/spool/cups-pdf/xx/
USERS_DIR=/home/xx/Desktop/PDF_Files/

inotifywait  -mq --timefmt '%Y%m%d %H%M%S' --format '%T %f' \
  -e close_write $SPOOL_DIR \
  | while read date time file; do
      mv $SPOOL_DIR${file} $USERS_DIR${date}${time}_${file}
    done
&lt;/pre&gt;

What if printed PDF documents should be combined into one large PDF document?
A user could move the files to be combined to a new subdirectory and then run the script (combine.sh) shown below.
This script creates a single PDF document with bookmark entries to each of the individual documents using the facilities in the pdfpages and hyperref packages of LaTeX. The page order is in the order of creation date and time.
 
&lt;pre&gt;
#!/bin/bash

# Script to combine .pdf files into a single bookmarked .pdf file
# Intended to be run from within a directory containing files to be concatenated.
# The directory name is accepted as a parameter

# If the directory name has been passed, then make it the working directory.
if [[ $1 ]]; then cd $1; fi

# Filename for the .tex file that will be processed using pdflatex
OUTFILE=$PWD/out2.tex
# Starting values for bookmark creation
BKMK_TEXT=Contents
BKMK_ANCHOR=Beginning
BKMK_LEVEL=0
# Variable containing ASCII code for centre dot character
CENTREDOT=$(echo -e "\xB7")

# Function to sanitise filenames by:
#  Changing space characters to underscore characters
#  and changing all but last period characters to centre dot (0xB7)
#  Necessary for \includepdf to parse filenames correctly
sanitise_filenames () {
for FILENAME in *.[Pp][Dd][Ff] ; do
  PREFIX=${FILENAME%.*}
  SUFFIX=${FILENAME##*.}
  NEWPREFIX=${PREFIX// /_}
  NEWPREFIX=${NEWPREFIX//./$CENTREDOT}
  if [ "$PREFIX" != "$NEWPREFIX" ]; then
    mv "$FILENAME" "$NEWPREFIX.$SUFFIX"
  fi
done
return
}

# Function to create a bookmark entry
do_bookmark_entry () {
  BKMK_TEXT=${FILENAME%.*}
  BKMK_TEXT=${BKMK_TEXT:15}
  #  NB. Need to substitute 'space' for 'underscore' to be valid bookmark text.
  BKMK_TEXT=${BKMK_TEXT//_/ }
  # Create a unique anchor point based on date and time prepended to filename
  BKMK_ANCHOR=${FILENAME:0:14}
  echo "\pdfbookmark["$BKMK_LEVEL"]{"$BKMK_TEXT"}{"$BKMK_ANCHOR"}" &gt;&gt; $OUTFILE
return
}

# Function to add all pdf files in current directory to the output file
add_pdf_files () {
for FILENAME in *.[Pp][Dd][Ff] ; do
  do_bookmark_entry
  echo "\includepdf[pages=-,fitpaper]{"$PWD"/"$FILENAME"}" &gt;&gt; $OUTFILE
done
return
}

echo "\documentclass{article}" &gt; $OUTFILE
echo "\usepackage{pdfpages}" &gt;&gt; $OUTFILE
echo "\usepackage[bookmarks,bookmarksopen,bookmarksopenlevel=1,pdfpagelayout={SinglePage},pdfview={Fit}]{hyperref}" &gt;&gt; $OUTFILE

echo "\begin{document}" &gt;&gt; $OUTFILE
echo "\pdfbookmark["$BKMK_LEVEL"]{"$BKMK_TEXT"}{"$BKMK_ANCHOR"}" &gt;&gt; $OUTFILE

sanitise_filenames
(( BKMK_LEVEL++ ))
for FNAME in * ; do
  if [ -d $FNAME ]; then
    FILENAME=$FNAME
    do_bookmark_entry
    cd $FNAME
    (( BKMK_LEVEL++ ))
    sanitise_filenames
    add_pdf_files
    (( BKMK_LEVEL-- ))
    cd ..
  elif [ -f $FNAME ] &amp;&amp; [[ ${FNAME##*.} == [Pp][Dd][Ff] ]] ; then
    FILENAME=$FNAME
    do_bookmark_entry
    echo "\includepdf[pages=-,fitpaper]{"$PWD"/"$FILENAME"}" &gt;&gt; $OUTFILE
  fi
done

echo "\end{document}" &gt;&gt; $OUTFILE

# Now process the .tex file
# Do a second run so that bookmark entries are resolved
pdflatex $OUTFILE; pdflatex $OUTFILE
wait

# Rename the created .pdf file
mv ${OUTFILE%.*}.pdf $(date +%Y%m%d%H%M%S)_All.pdf

# Cleanup files left by pdflatex processing
rm ${OUTFILE%.*}*

# Cleanup trigger file if this script has been started from watch_for_combine_start.sh script
if [ -f combine.start ]; then rm combine.start; fi

# Remove this script
rm $0
&lt;/pre&gt;

As a convenience, the user could also have a second background process running the script (watch_for_combine_start.sh) shown below. This script watches for the creation of a 'trigger' file (combine.start) in the directory tree and then executes the 'combine.sh' script shown above. This is useful in a network environment, so that a Windows user manipulating the files via a Samba share can create the combined PDF file without having to log in to the Slackware Linux server.

&lt;pre&gt;
#!/bin/sh

# Script to watch for creation of a trigger file in a directory tree.
#  This event causes another script to be copied into the tree subdirectory and run.
#  The tree subdirectory name is passed as a parameter.
#
# This script should never exit

WATCH_DIR=/home/xx/Desktop/PDF_Files
TRIGGER_FILE=combine.start
SCRIPT_FILE=/home/xx/pdf_printing/combine.sh

inotifywait  -mqr --timefmt '%Y%m%d %H%M%S' --format '%T %w %f' \
  -e close_write $WATCH_DIR \
  | while read date time path file; do
      if [ ${file} == $TRIGGER_FILE ]; then
        cp $SCRIPT_FILE ${path}
        sh ${path}/$(basename $SCRIPT_FILE) ${path} &gt; /dev/null &amp;
      fi
    done
&lt;/pre&gt;</text>
    <sha1>6ffc3b41174059d3b99e668e4e3e2bf4665fe2cc</sha1>
  </revision>
</page>
<page arvcontinue="20120909040647|783">
  <title>Links</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>834</id>
    <parentid>516</parentid>
    <timestamp>2013-03-27T14:14:22Z</timestamp>
    <contributor>
      <username>Graf</username>
      <id>318</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4134" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* [http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ Slackware FAQ by] [[User:juhl|juhl]] (Jesper Juhl)
* [http://www.nielshorn.net/slackware/slack_versions.php A complete overview of all Slackware versions] by Niels Horn
* [http://www.slackbook.org Updated version of the slackware book]
* [http://www.slackware.com/getslack Extensive listing of Slackware mirrors]
* [http://www.linuxquestions.org/questions/slackware-14/ Slackware forum] on LinuxQuestions.org
* [http://slackbuilds.org/ slackbuilds.org - Build scripts for additional software]
* [http://sbopkg.org sbopkg.org] - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* [http://gitorious.org/sbopkg-slackware-queues Build queues for all Slackware packages from SlackBuilds.org]
* [http://slackworld.berlios.de/ The Slack World page on berlios]
* [http://slacky.eu European Slackware community]
* [http://slackware.linux.or.id Indonesian Slackware Community] - by [[User:Willysr|Willysr]]
* [http://open-eslack.org/ Spanish Slackware community]
* [http://www.slack-world.com Iranian Slackware Community]
* [http://www.slackware.ru Russian Slackware Community]
* [http://www.slackware.su Russian Slackware forum and articles]
* http://jtgzmanager.sf.net/  A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.

==Free packages==
* [http://connie.slackware.com/~alien/slackbuilds/ Eric Hameleers' packages] [http://slackware.org.uk/people/alien/slackbuilds/ mirror] 
* [http://rlworkman.net/pkgs/ rworkman's packages] [http://slackware.org.uk/people/rlworkman/ mirror] 
* [http://www.nielshorn.net/slackware/slack_pkg.php Niels Horn's packages]
* http://www.linuxpackages.net/
* [http://repository.slacky.eu/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware

==SlackBuild Repositories==
* [http://slackbuilds.org The SlackBuilds.org Project]
* [http://www.slackware.com/~alien/slackbuilds/ Eric "Alien" Hameleer's SlackBuilds]
* [http://slackware.org.uk/people/rlworkman/sources/ rworkman's SlackBuilds]

==Live CD's based on Slackware==
* [http://porteus.org/ Porteus] - A fast, portable and modular live CD/USB, originally started as a community remix of Slax
* [http://www.imagineos.com.br/ ImagineOS] (formerly GoblinX)
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://open-eslack.org/wiki/ A Spanish Slackware Wiki]
* [http://www.slackware.ru/wiki/ 1 Russian Slackware Wiki]
* [http://wiki.slackware.su 2 Russian Slackware Wiki]

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for stable and current

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs</text>
    <sha1>0a3b42bd606c449ebbd2d3f1162b957a877af9a4</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>User:AndDT</title>
  <ns>2</ns>
  <id>305</id>
  <revision>
    <id>835</id>
    <timestamp>2013-03-30T14:46:41Z</timestamp>
    <contributor>
      <username>AndDT</username>
      <id>319</id>
    </contributor>
    <comment>Created page with "Slackware user :) First met Slackware 20120328 Schoolguy, learning in the lastest, 11th form in Technical Lyceum KPI in Kyiv  * Real Name: Andrew Tkalia * IRC Nickname: AndDT ..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="331" xml:space="preserve">Slackware user :) First met Slackware 20120328
Schoolguy, learning in the lastest, 11th form in Technical Lyceum KPI in Kyiv

* Real Name: Andrew Tkalia
* IRC Nickname: AndDT
* E-Mail: anddt@anddt.us.to
* My homepage: http://anddt.us.to/
* My blog: http://anddt.us.to/blog/
* My package collection: ftp://anddt.us.to:2111/packages/</text>
    <sha1>890334faba79b90ed16a2dd1c029a06fbabe967f</sha1>
  </revision>
  <revision>
    <id>836</id>
    <parentid>835</parentid>
    <timestamp>2013-03-30T14:47:50Z</timestamp>
    <contributor>
      <username>AndDT</username>
      <id>319</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="333" xml:space="preserve">Slackware user :) First met Slackware 20120328.

Schoolguy, learning in the lastest, 11th form in Technical Lyceum KPI in Kyiv

* Real Name: Andrew Tkalia
* IRC Nickname: AndDT
* E-Mail: anddt@anddt.us.to
* My homepage: http://anddt.us.to/
* My blog: http://anddt.us.to/blog/
* My package collection: ftp://anddt.us.to:2111/packages/</text>
    <sha1>7c127a337ab85671e9dc32fb49050417a8b59476</sha1>
  </revision>
  <revision>
    <id>837</id>
    <parentid>836</parentid>
    <timestamp>2013-03-30T14:50:16Z</timestamp>
    <contributor>
      <username>AndDT</username>
      <id>319</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="468" xml:space="preserve">Slackware user :) First met Slackware 20120328.

Schoolguy, learning in the lastest, 11th form in Technical Lyceum KPI in Kyiv.

I have an amateur server (my notebook) at anddt.us.to with lighttpd, exim, vsftpd, php, postgresql ...etc

I am systemd and Oracle hater :)

* Real Name: Andrew
* IRC Nickname: AndDT
* E-Mail: anddt@anddt.us.to
* My homepage: http://anddt.us.to/
* My blog: http://anddt.us.to/blog/
* My package collection: ftp://anddt.us.to:2111/packages/</text>
    <sha1>221fb8d56c12caba217724cd911046866bb421d2</sha1>
  </revision>
  <revision>
    <id>838</id>
    <parentid>837</parentid>
    <timestamp>2013-03-30T17:56:55Z</timestamp>
    <contributor>
      <username>AndDT</username>
      <id>319</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="524" xml:space="preserve">Slackware user :) First met Slackware 20120328.

Schoolguy, learning in the lastest, 11th form in Technical Lyceum KPI in Kyiv.

I have an amateur server (my notebook) at anddt.us.to with lighttpd, exim, vsftpd, php, postgresql ...etc

I am systemd and Oracle hater :)

* Real Name: Andrew
* IRC Nickname: AndDT
* E-Mail: anddt@anddt.us.to
* My homepage: http://anddt.us.to/
* My blog: http://anddt.us.to/blog/
* My package collection: ftp://anddt.us.to:2111/packages/
* My SlackBuilds: https://github.com/AndDT/SlackBuilds/</text>
    <sha1>3257d67c475309c2849ee4f6c8b014d5426005fd</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>User:Alisonken1</title>
  <ns>2</ns>
  <id>242</id>
  <revision>
    <id>839</id>
    <parentid>499</parentid>
    <timestamp>2013-05-21T20:16:53Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="207" xml:space="preserve">* Real name: Ken Roberts
* IRC Nickname: alisonken1
* IRC aliasses: alisonken1home, alisonken1lap1, alisonken1lap2, alisonken1lap3
* Slackware mirror that I maintain: http://slackware.dreamhost.com/slackware</text>
    <sha1>1a94777e91bd7319b577e085a61ced347c4fceab</sha1>
  </revision>
  <revision>
    <id>840</id>
    <parentid>839</parentid>
    <timestamp>2013-05-21T20:17:24Z</timestamp>
    <contributor>
      <username>Alisonken1</username>
      <id>38</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="207" xml:space="preserve">* Real name: Ken Roberts
* IRC Nickname: alisonken1
* IRC aliases:  alisonken1home, alisonken1lap1, alisonken1lap2, alisonken1lap3
* Slackware mirror that I maintain: http://slackware.dreamhost.com/slackware</text>
    <sha1>dc180f8ae3c21de5f22fbca2734cf3aa5e920ca7</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>841</id>
    <parentid>619</parentid>
    <timestamp>2013-05-21T20:43:40Z</timestamp>
    <contributor>
      <username>Clientkill</username>
      <id>323</id>
    </contributor>
    <comment>Added me</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1536" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Adioe3|adioe3]]
* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[User:Clientkill|Clientkill]]
* [[USer:codermaniac|codermaniac]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|dchmelik]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:Erik|erik]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[User:natex|natex]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>0e8a8a478be01f338c81f4a15e3ea9b0f908e62a</sha1>
  </revision>
  <revision>
    <id>867</id>
    <parentid>841</parentid>
    <timestamp>2013-11-19T13:07:15Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1534" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Adioe3|adioe3]]
* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[User:Clientkill|Clientkill]]
* [[USer:codermaniac|codermaniac]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|darwin]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:Erik|erik]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[User:natex|natex]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>457fb63209b1bbfe674c7942b61f7c196ab4eeaa</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>User:Clientkill</title>
  <ns>2</ns>
  <id>306</id>
  <revision>
    <id>842</id>
    <timestamp>2013-05-21T20:44:52Z</timestamp>
    <contributor>
      <username>Clientkill</username>
      <id>323</id>
    </contributor>
    <comment>Created page with "Hello slackers,  I'm Clientkill. I'm relatively new to slack, but have been using Linux for a while now.  I'm on ##slackware and ot almost always, feel free to chat!"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="165" xml:space="preserve">Hello slackers, 
I'm Clientkill.
I'm relatively new to slack, but have been using Linux for a while now. 
I'm on ##slackware and ot almost always, feel free to chat!</text>
    <sha1>d9b2dfc6f342b18f2a9e6f8603bd9e52f7eed3b1</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>Install Slackware Using A USB Flash Drive</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>843</id>
    <parentid>832</parentid>
    <timestamp>2013-05-24T11:19:10Z</timestamp>
    <contributor>
      <username>Donallen</username>
      <id>324</id>
    </contributor>
    <comment>/* Installation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3297" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Using isohybrid ==

At this point you should have a Slackware ISO lying on your hard disk

Make it hybrid:

 isohybrid slackware-13.1-install-dvd.iso

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is. When installing, choose "Install from a Slackware CD or DVD". Then select the "manual" option, then the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed as when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>4254ea3ea2e393c0c26d93d3cae4f5055e55136c</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>DVB</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>849</id>
    <parentid>309</parentid>
    <timestamp>2013-09-13T02:50:43Z</timestamp>
    <contributor>
      <username>Domtheo</username>
      <id>331</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10291" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.
[http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta], [http://www.propertykita.com/rumah.html Rumah Dijual di Bandung], [http://www.propertykita.com/rumah.html Rumah Dijual di Bekasi]

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps
Eventually, my SlackBuild will be hosted here http://slackbuilds.rlworkman.net/CONTRIB/linuxtv-dvb-apps/ (thanks to robw810).

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>375959fb3151b8fa90b552b54c8d36ae0020e6e8</sha1>
  </revision>
  <revision>
    <id>852</id>
    <parentid>849</parentid>
    <timestamp>2013-09-29T20:09:59Z</timestamp>
    <contributor>
      <username>Eflags</username>
      <id>334</id>
    </contributor>
    <comment>Undo revision 849 by [[Special:Contributions/Domtheo|Domtheo]] ([[User talk:Domtheo|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9981" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps
Eventually, my SlackBuild will be hosted here http://slackbuilds.rlworkman.net/CONTRIB/linuxtv-dvb-apps/ (thanks to robw810).

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>75a8ff975f95ea3d57850216885694a0868a88d1</sha1>
  </revision>
  <revision>
    <id>854</id>
    <parentid>852</parentid>
    <timestamp>2013-09-30T03:39:53Z</timestamp>
    <contributor>
      <username>Domtheo</username>
      <id>331</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10291" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.
[http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta], [http://www.propertykita.com/rumah.html Rumah Dijual di Bandung], [http://www.propertykita.com/rumah.html Rumah Dijual di Bekasi]

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps
Eventually, my SlackBuild will be hosted here http://slackbuilds.rlworkman.net/CONTRIB/linuxtv-dvb-apps/ (thanks to robw810).

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>375959fb3151b8fa90b552b54c8d36ae0020e6e8</sha1>
  </revision>
  <revision>
    <id>864</id>
    <parentid>854</parentid>
    <timestamp>2013-10-31T09:29:40Z</timestamp>
    <contributor>
      <username>Domtheo</username>
      <id>331</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10249" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.
[http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta], [http://www.awanirentcar.com Sewa mobil jakarta], [http://kiosauto.com Aksesoris mobil]

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps
Eventually, my SlackBuild will be hosted here http://slackbuilds.rlworkman.net/CONTRIB/linuxtv-dvb-apps/ (thanks to robw810).

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>4de2c210a93130ec0cd38e6f5ec77aa0b646a3f8</sha1>
  </revision>
  <revision>
    <id>869</id>
    <parentid>864</parentid>
    <timestamp>2013-11-21T01:11:04Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Fucking spammers</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10095" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps
Eventually, my SlackBuild will be hosted here http://slackbuilds.rlworkman.net/CONTRIB/linuxtv-dvb-apps/ (thanks to robw810).

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>fbb716c6aac147fce659760032518fbd49689f32</sha1>
  </revision>
  <revision>
    <id>870</id>
    <parentid>869</parentid>
    <timestamp>2013-11-21T01:11:25Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>/* DVB Apps */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9969" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>fe886615a3a8aa6d826160d0692e37bc649c08a4</sha1>
  </revision>
  <revision>
    <id>872</id>
    <parentid>870</parentid>
    <timestamp>2013-11-25T03:22:15Z</timestamp>
    <contributor>
      <username>Kunaguers</username>
      <id>343</id>
    </contributor>
    <comment>Undo revision 869 by [[Special:Contributions/Rworkman|Rworkman]] ([[User talk:Rworkman|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10123" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.
[http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta], [http://www.awanirentcar.com Sewa mobil jakarta], [http://kiosauto.com Aksesoris mobil]

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>f3c4f9c7eec44a0e934172de3c5ed5b9fbbd03e5</sha1>
  </revision>
  <revision>
    <id>874</id>
    <parentid>872</parentid>
    <timestamp>2014-01-01T02:51:46Z</timestamp>
    <contributor>
      <username>Count Zero</username>
      <id>346</id>
    </contributor>
    <comment>Undo revision 872 by [[Special:Contributions/Kunaguers|Kunaguers]] ([[User talk:Kunaguers|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9969" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>fe886615a3a8aa6d826160d0692e37bc649c08a4</sha1>
  </revision>
  <revision>
    <id>875</id>
    <parentid>874</parentid>
    <timestamp>2014-01-01T02:53:07Z</timestamp>
    <contributor>
      <username>Count Zero</username>
      <id>346</id>
    </contributor>
    <comment>Removing a piece of spam I missed on first undo.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9855" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>ec6559520878aab1714f2b78351def4e6c009ce3</sha1>
  </revision>
  <revision>
    <id>879</id>
    <parentid>875</parentid>
    <timestamp>2014-01-02T04:13:17Z</timestamp>
    <contributor>
      <username>Kunaguers</username>
      <id>343</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10123" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.
[http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta], [http://www.awanirentcar.com Sewa mobil jakarta], [http://kiosauto.com Aksesoris mobil]

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>f3c4f9c7eec44a0e934172de3c5ed5b9fbbd03e5</sha1>
  </revision>
  <revision>
    <id>891</id>
    <parentid>879</parentid>
    <timestamp>2014-01-07T05:14:11Z</timestamp>
    <contributor>
      <username>Count Zero</username>
      <id>346</id>
    </contributor>
    <comment>Undo revision 879 by [[Special:Contributions/Kunaguers|Kunaguers]] ([[User talk:Kunaguers|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9855" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>ec6559520878aab1714f2b78351def4e6c009ce3</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>SlackBuild Scripts</title>
  <ns>0</ns>
  <id>15</id>
  <revision>
    <id>850</id>
    <parentid>592</parentid>
    <timestamp>2013-09-13T02:56:35Z</timestamp>
    <contributor>
      <username>Domtheo</username>
      <id>331</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3183" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other [http://www.optimaweb.co.id/jasa-seo Jasa seo Profesional]
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:
[http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi], [http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta]

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.
[http://www.propertykita.com/rumah.html Rumah Dijual di Depok], [http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta]

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>72db4bd0a5698b21a972d7384f89e08bdcacebeb</sha1>
  </revision>
  <revision>
    <id>851</id>
    <parentid>850</parentid>
    <timestamp>2013-09-29T20:08:32Z</timestamp>
    <contributor>
      <username>Eflags</username>
      <id>334</id>
    </contributor>
    <comment>Reverting vandalism</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2881" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5efc3844c6e55de198f33a7ed5009d1bd1cf0049</sha1>
  </revision>
  <revision>
    <id>853</id>
    <parentid>851</parentid>
    <timestamp>2013-09-30T03:39:27Z</timestamp>
    <contributor>
      <username>Domtheo</username>
      <id>331</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3233" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other [http://www.optimaweb.co.id/jasa-seo Jasa seo Profesional]
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:
[http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi], [http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.awanirentcar.com Sewa Mobil Jakarta]

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.
[http://www.propertykita.com/rumah.html Rumah Dijual di Depok], [http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta]

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>e2e0cdc16d8ab1376bd8787f3a34f95686042909</sha1>
  </revision>
  <revision>
    <id>865</id>
    <parentid>853</parentid>
    <timestamp>2013-11-15T16:01:15Z</timestamp>
    <contributor>
      <username>Willysr</username>
      <id>341</id>
    </contributor>
    <comment>Undo revision 853 by [[Special:Contributions/Domtheo|Domtheo]] ([[User talk:Domtheo|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2881" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5efc3844c6e55de198f33a7ed5009d1bd1cf0049</sha1>
  </revision>
  <revision>
    <id>866</id>
    <parentid>865</parentid>
    <timestamp>2013-11-18T03:36:30Z</timestamp>
    <contributor>
      <username>Domtheo</username>
      <id>331</id>
    </contributor>
    <minor/>
    <comment>Undo revision 865 by [[Special:Contributions/Willysr|Willysr]] ([[User talk:Willysr|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3233" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other [http://www.optimaweb.co.id/jasa-seo Jasa seo Profesional]
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:
[http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi], [http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.awanirentcar.com Sewa Mobil Jakarta]

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.
[http://www.propertykita.com/rumah.html Rumah Dijual di Depok], [http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta]

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>e2e0cdc16d8ab1376bd8787f3a34f95686042909</sha1>
  </revision>
  <revision>
    <id>868</id>
    <parentid>866</parentid>
    <timestamp>2013-11-21T00:58:37Z</timestamp>
    <contributor>
      <username>Willysr</username>
      <id>341</id>
    </contributor>
    <comment>Undo revision 866 by [[Special:Contributions/Domtheo|Domtheo]] ([[User talk:Domtheo|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2881" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5efc3844c6e55de198f33a7ed5009d1bd1cf0049</sha1>
  </revision>
  <revision>
    <id>871</id>
    <parentid>868</parentid>
    <timestamp>2013-11-25T03:21:39Z</timestamp>
    <contributor>
      <username>Kunaguers</username>
      <id>343</id>
    </contributor>
    <comment>Undo revision 868 by [[Special:Contributions/Willysr|Willysr]] ([[User talk:Willysr|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3233" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other [http://www.optimaweb.co.id/jasa-seo Jasa seo Profesional]
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:
[http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi], [http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.awanirentcar.com Sewa Mobil Jakarta]

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.
[http://www.propertykita.com/rumah.html Rumah Dijual di Depok], [http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta]

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>e2e0cdc16d8ab1376bd8787f3a34f95686042909</sha1>
  </revision>
  <revision>
    <id>873</id>
    <parentid>871</parentid>
    <timestamp>2013-12-31T01:06:47Z</timestamp>
    <contributor>
      <username>Count Zero</username>
      <id>346</id>
    </contributor>
    <comment>Undo revision 871 by [[Special:Contributions/Kunaguers|Kunaguers]] ([[User talk:Kunaguers|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2881" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5efc3844c6e55de198f33a7ed5009d1bd1cf0049</sha1>
  </revision>
  <revision>
    <id>878</id>
    <parentid>873</parentid>
    <timestamp>2014-01-02T04:13:00Z</timestamp>
    <contributor>
      <username>Kunaguers</username>
      <id>343</id>
    </contributor>
    <minor/>
    <comment>Undo revision 873 by [[Special:Contributions/Count Zero|Count Zero]] ([[User talk:Count Zero|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3233" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other [http://www.optimaweb.co.id/jasa-seo Jasa seo Profesional]
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:
[http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi], [http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.awanirentcar.com Sewa Mobil Jakarta]

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.
[http://www.propertykita.com/rumah.html Rumah Dijual di Depok], [http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta]

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>e2e0cdc16d8ab1376bd8787f3a34f95686042909</sha1>
  </revision>
  <revision>
    <id>892</id>
    <parentid>878</parentid>
    <timestamp>2014-01-07T05:15:03Z</timestamp>
    <contributor>
      <username>Count Zero</username>
      <id>346</id>
    </contributor>
    <comment>Undo revision 878 by [[Special:Contributions/Kunaguers|Kunaguers]] ([[User talk:Kunaguers|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2881" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5efc3844c6e55de198f33a7ed5009d1bd1cf0049</sha1>
  </revision>
  <revision>
    <id>893</id>
    <parentid>892</parentid>
    <timestamp>2014-01-10T13:30:58Z</timestamp>
    <contributor>
      <username>Kath16</username>
      <id>348</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3021" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]] [http://samsvaginalmeshlawsuitblog.wordpress.com/ Sam's Vaginal Mesh Lawsuit Blog]
[http://samsvaginalmeshlawsuitblog.webs.com/ Sam's Blog]


[[Category:Tutorials]]</text>
    <sha1>7747e0cdffd0b97b6095851322cf91a12a75ec3f</sha1>
  </revision>
  <revision>
    <id>894</id>
    <parentid>893</parentid>
    <timestamp>2014-01-20T03:46:21Z</timestamp>
    <contributor>
      <username>Domtheos</username>
      <id>350</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3233" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other [http://www.optimaweb.co.id/jasa-seo Jasa seo Profesional]
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:
[http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi], [http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.awanirentcar.com Sewa Mobil Jakarta]

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.
[http://www.propertykita.com/rumah.html Rumah Dijual di Depok], [http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta]

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>e2e0cdc16d8ab1376bd8787f3a34f95686042909</sha1>
  </revision>
  <revision>
    <id>895</id>
    <parentid>894</parentid>
    <timestamp>2014-01-20T06:52:35Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Domtheos|Domtheos]] ([[User talk:Domtheos|talk]]) to last revision by [[User:Kath16|Kath16]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3021" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]] [http://samsvaginalmeshlawsuitblog.wordpress.com/ Sam's Vaginal Mesh Lawsuit Blog]
[http://samsvaginalmeshlawsuitblog.webs.com/ Sam's Blog]


[[Category:Tutorials]]</text>
    <sha1>7747e0cdffd0b97b6095851322cf91a12a75ec3f</sha1>
  </revision>
  <revision>
    <id>896</id>
    <parentid>895</parentid>
    <timestamp>2014-01-20T06:55:19Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Die in a fire, spammer.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2881" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5efc3844c6e55de198f33a7ed5009d1bd1cf0049</sha1>
  </revision>
  <revision>
    <id>897</id>
    <parentid>896</parentid>
    <timestamp>2014-01-23T03:00:18Z</timestamp>
    <contributor>
      <username>Sinyorita</username>
      <id>351</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3233" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other [http://www.optimaweb.co.id/jasa-seo Jasa seo Profesional]
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:
[http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi], [http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.awanirentcar.com Sewa Mobil Jakarta]

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.
[http://www.propertykita.com/rumah.html Rumah Dijual di Depok], [http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta]

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>e2e0cdc16d8ab1376bd8787f3a34f95686042909</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>Links</title>
  <ns>0</ns>
  <id>3</id>
  <revision>
    <id>859</id>
    <parentid>834</parentid>
    <timestamp>2013-10-18T11:19:40Z</timestamp>
    <contributor>
      <username>Lystor</username>
      <id>337</id>
    </contributor>
    <comment>Add  Slackware Packages Search</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4206" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* [http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ Slackware FAQ by] [[User:juhl|juhl]] (Jesper Juhl)
* [http://www.nielshorn.net/slackware/slack_versions.php A complete overview of all Slackware versions] by Niels Horn
* [http://www.slackbook.org Updated version of the slackware book]
* [http://www.slackware.com/getslack Extensive listing of Slackware mirrors]
* [http://www.linuxquestions.org/questions/slackware-14/ Slackware forum] on LinuxQuestions.org
* [http://slackbuilds.org/ slackbuilds.org - Build scripts for additional software]
* [http://sbopkg.org sbopkg.org] - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* [http://gitorious.org/sbopkg-slackware-queues Build queues for all Slackware packages from SlackBuilds.org]
* [http://slackworld.berlios.de/ The Slack World page on berlios]
* [http://slacky.eu European Slackware community]
* [http://slackware.linux.or.id Indonesian Slackware Community] - by [[User:Willysr|Willysr]]
* [http://open-eslack.org/ Spanish Slackware community]
* [http://www.slack-world.com Iranian Slackware Community]
* [http://www.slackware.ru Russian Slackware Community]
* [http://www.slackware.su Russian Slackware forum and articles]
* http://jtgzmanager.sf.net/  A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.

==Free packages==
* [http://connie.slackware.com/~alien/slackbuilds/ Eric Hameleers' packages] [http://slackware.org.uk/people/alien/slackbuilds/ mirror] 
* [http://rlworkman.net/pkgs/ rworkman's packages] [http://slackware.org.uk/people/rlworkman/ mirror] 
* [http://www.nielshorn.net/slackware/slack_pkg.php Niels Horn's packages]
* http://www.linuxpackages.net/
* [http://repository.slacky.eu/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware

==SlackBuild Repositories==
* [http://slackbuilds.org The SlackBuilds.org Project]
* [http://www.slackware.com/~alien/slackbuilds/ Eric "Alien" Hameleer's SlackBuilds]
* [http://slackware.org.uk/people/rlworkman/sources/ rworkman's SlackBuilds]

==Live CD's based on Slackware==
* [http://porteus.org/ Porteus] - A fast, portable and modular live CD/USB, originally started as a community remix of Slax
* [http://www.imagineos.com.br/ ImagineOS] (formerly GoblinX)
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://open-eslack.org/wiki/ A Spanish Slackware Wiki]
* [http://www.slackware.ru/wiki/ 1 Russian Slackware Wiki]
* [http://wiki.slackware.su 2 Russian Slackware Wiki]

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for stable and current

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Slackware Packages Search==
* http://pkgs.org
* http://slackfind.net

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs</text>
    <sha1>d6bd07b475300082ddda4ef5bdda25b287663603</sha1>
  </revision>
  <revision>
    <id>860</id>
    <parentid>859</parentid>
    <timestamp>2013-10-22T15:10:22Z</timestamp>
    <contributor>
      <username>Alienbob</username>
      <id>9</id>
    </contributor>
    <minor/>
    <comment>/* SlackBuild Repositories */ Spell my name correctly.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4209" xml:space="preserve">[[Category:Information]]

==Slackware Links==
* http://www.slackware.com - the home of Slackware
* [http://www.chaosbits.net/Articles/Historical/SlackwareFAQ/ Slackware FAQ by] [[User:juhl|juhl]] (Jesper Juhl)
* [http://www.nielshorn.net/slackware/slack_versions.php A complete overview of all Slackware versions] by Niels Horn
* [http://www.slackbook.org Updated version of the slackware book]
* [http://www.slackware.com/getslack Extensive listing of Slackware mirrors]
* [http://www.linuxquestions.org/questions/slackware-14/ Slackware forum] on LinuxQuestions.org
* [http://slackbuilds.org/ slackbuilds.org - Build scripts for additional software]
* [http://sbopkg.org sbopkg.org] - Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org repository
* [http://gitorious.org/sbopkg-slackware-queues Build queues for all Slackware packages from SlackBuilds.org]
* [http://slackworld.berlios.de/ The Slack World page on berlios]
* [http://slacky.eu European Slackware community]
* [http://slackware.linux.or.id Indonesian Slackware Community] - by [[User:Willysr|Willysr]]
* [http://open-eslack.org/ Spanish Slackware community]
* [http://www.slack-world.com Iranian Slackware Community]
* [http://www.slackware.ru Russian Slackware Community]
* [http://www.slackware.su Russian Slackware forum and articles]
* http://jtgzmanager.sf.net/  A new frontend to pkgtools built with Qt4 C++ libs - by Alexandre Arnt
* http://slackbot.sourceforge.net - Buildsystem and buildtools for Slackware
* http://buildpkg.berlios.de/ - buildpkg: a Slackware package building utility.

==Free packages==
* [http://connie.slackware.com/~alien/slackbuilds/ Eric Hameleers' packages] [http://slackware.org.uk/people/alien/slackbuilds/ mirror] 
* [http://rlworkman.net/pkgs/ rworkman's packages] [http://slackware.org.uk/people/rlworkman/ mirror] 
* [http://www.nielshorn.net/slackware/slack_pkg.php Niels Horn's packages]
* http://www.linuxpackages.net/
* [http://repository.slacky.eu/ Slacky.eu] Italian Slackware site
* [http://slacke17.sourceforge.net/ SlackE17] A distribution of Enlightenment DR17 for Slackware

==SlackBuild Repositories==
* [http://slackbuilds.org The SlackBuilds.org Project]
* [http://www.slackware.com/~alien/slackbuilds/ Eric "AlienBOB" Hameleers' SlackBuilds]
* [http://slackware.org.uk/people/rlworkman/sources/ rworkman's SlackBuilds]

==Live CD's based on Slackware==
* [http://porteus.org/ Porteus] - A fast, portable and modular live CD/USB, originally started as a community remix of Slax
* [http://www.imagineos.com.br/ ImagineOS] (formerly GoblinX)
* [http://mutagenix.org Mutagenix] A basic rescue CD and a Freerock GNOME based desktop CD
* [http://www.slax.org Slax Homepage]
* [http://slampp.abangadek.com SLAMPP Homepage]

==Other Wikis==
* [http://alien.slackbook.org/ Alien Bob's Wiki]
* [http://www.slackforum.de/wiki/ A German Slackware Wiki]
* [http://open-eslack.org/wiki/ A Spanish Slackware Wiki]
* [http://www.slackware.ru/wiki/ 1 Russian Slackware Wiki]
* [http://wiki.slackware.su 2 Russian Slackware Wiki]

==RSS Feeds==
* http://dev.slackware.it/rss/ - RSS feeds for stable Slackware release and -current ChangeLog
* http://slackbuilds.org/mirror/rss/ - ChangeLog RSS feeds for stable and current

==Slack==
* http://www.subgenius.com - The [[Church of the SubGenius]]: the source of the term "Slack"
* http://www.modemac.com/x-day - X-Day
* http://en.wikipedia.org/wiki/Church_of_the_SubGenius - Wikipedia entry

==Slackware Packages Search==
* http://pkgs.org
* http://slackfind.net

==General Links==
* http://freshmeat.net - large index of Unix and cross-platform software and themes
* http://sourceforge.net - large repository of Open Source code and applications
* http://developer.berlios.de - another Open Source repository - ideal if you want subversion hosting for your project
* http://art.gnome.org - gnome-desktop themes and backgrounds
* http://www.gnome-look.org - eyecandy for your gnome-desktop
* http://www.kde-look.org - eyecandy for your KDE desktop
* http://www.kde-apps.org - Applications and addons for KDE
* http://kerneltrap.org - Kernel talk
* http://urbanmyth.org/microcode/ - The latest microcode for your Intel CPUs</text>
    <sha1>ef193e8001401a80986eff7a16d7aea18b2ab06b</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>UX32VD</title>
  <ns>0</ns>
  <id>313</id>
  <revision>
    <id>877</id>
    <timestamp>2014-01-01T13:28:01Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>Created page with "[[Category:Hardware]] ==Slackware on an ASUS UX32VD==  Linux Kernel 3.10.x  &lt;pre&gt; -&gt; Processor type and features Processor family (X) Core 2/newer Xeon &lt;/pre&gt;  '''SATA:''':&lt;pr..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4003" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==

Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; SMBus Control Method Interface
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;M&gt; AST server chips
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==</text>
    <sha1>d4ad19902fff19c7a7e6f2c1dece4a7108d2f94b</sha1>
  </revision>
  <revision>
    <id>880</id>
    <parentid>877</parentid>
    <timestamp>2014-01-02T12:27:29Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>/* Slackware on an ASUS UX32VD */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4029" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; SMBus Control Method Interface
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;M&gt; AST server chips
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==</text>
    <sha1>024c2322016b962ca27505e79d551ffeac9de296</sha1>
  </revision>
  <revision>
    <id>881</id>
    <parentid>880</parentid>
    <timestamp>2014-01-02T12:29:59Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5867" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; SMBus Control Method Interface
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;M&gt; AST server chips
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==</text>
    <sha1>a917980bba2edb4016e4baf8e02123a4e2711ba4</sha1>
  </revision>
  <revision>
    <id>882</id>
    <parentid>881</parentid>
    <timestamp>2014-01-02T12:32:00Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5920" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; SMBus Control Method Interface
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;M&gt; AST server chips
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]</text>
    <sha1>fb7765ccbc643e87e5e72991b46d180c7222e992</sha1>
  </revision>
  <revision>
    <id>883</id>
    <parentid>882</parentid>
    <timestamp>2014-01-02T14:42:57Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6041" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; SMBus Control Method Interface
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;M&gt; AST server chips
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Ambient Light Sensor==


==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>c024aac87cc3f47e3c2310c3c75c1f863c6cccda</sha1>
  </revision>
  <revision>
    <id>884</id>
    <parentid>883</parentid>
    <timestamp>2014-01-02T15:06:12Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>/* Ambient Light Sensor */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6420" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; SMBus Control Method Interface
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;M&gt; AST server chips
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>97f8aab444a8c552313c889bd7c4ab26de6de03c</sha1>
  </revision>
  <revision>
    <id>885</id>
    <parentid>884</parentid>
    <timestamp>2014-01-02T15:09:02Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>/* Hardware */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7061" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; SMBus Control Method Interface
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;M&gt; AST server chips
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>ec8275c7332d0e8e1a7bb720e61dd1421dd97135</sha1>
  </revision>
  <revision>
    <id>886</id>
    <parentid>885</parentid>
    <timestamp>2014-01-02T15:10:48Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>/* Kernel Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7040" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; SMBus Control Method Interface
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>6e7513519a152775f24afd197491ce19d9782b38</sha1>
  </revision>
  <revision>
    <id>887</id>
    <parentid>886</parentid>
    <timestamp>2014-01-02T15:16:38Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>/* Kernel Configuration */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7064" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>1cd6974fc6b768063255e0ddf4582e9baf51848d</sha1>
  </revision>
  <revision>
    <id>889</id>
    <parentid>887</parentid>
    <timestamp>2014-01-04T18:04:32Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7673" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Touchpad==
&lt;pre&gt;
Section "InputClass"
      Identifier "Synaptics Touchpad"
      Driver "synaptics"
      MatchISTouchpad "on"
      MatchDriver "synaptics"
#      MatchDevice Path "/dev/input/event*"
#      Option "FastTaps" "1"
      Option "ClickPad"         "true"
      Option "HorizTwoFingerScroll" "on"
      Option "EmulateMidButtonTime" "0"
      Option "SoftButtonAreas"  "50% 0 82% 0 0 0 0 0"
      Option "CircularScrolling"          "on"
      Option "CircScrollTrigger"          "1"
      Option "FingerLow" "6"
      Option "FingerHigh" "13"
      Option "SHMConfig" "on"
EndSection
&lt;/pre&gt;

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>4d4a274120e300f4d075285cc5590fb25075f4fd</sha1>
  </revision>
  <revision>
    <id>890</id>
    <parentid>889</parentid>
    <timestamp>2014-01-04T18:05:12Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>/* Touchpad */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7713" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;*&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Touchpad==
/etc/X11/xorg.conf.d/50-synaptics.conf 
&lt;pre&gt;
Section "InputClass"
      Identifier "Synaptics Touchpad"
      Driver "synaptics"
      MatchISTouchpad "on"
      MatchDriver "synaptics"
#      MatchDevice Path "/dev/input/event*"
#      Option "FastTaps" "1"
      Option "ClickPad"         "true"
      Option "HorizTwoFingerScroll" "on"
      Option "EmulateMidButtonTime" "0"
      Option "SoftButtonAreas"  "50% 0 82% 0 0 0 0 0"
      Option "CircularScrolling"          "on"
      Option "CircScrollTrigger"          "1"
      Option "FingerLow" "6"
      Option "FingerHigh" "13"
      Option "SHMConfig" "on"
EndSection
&lt;/pre&gt;

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>2a9b936db2b802d0655292e688da10a0f1dfae10</sha1>
  </revision>
</page>
<page arvcontinue="20130330144641|835">
  <title>EeePC 1215N</title>
  <ns>0</ns>
  <id>314</id>
  <revision>
    <id>888</id>
    <timestamp>2014-01-03T14:59:13Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>Created page with "[[Category:Hardware]] ==Slackware on an ASUS eeepc 1215N ==  '''Ethernet:'''  - Kernel version 2.6.x &lt;pre&gt; Device Drivers ---&gt;   [ x ] Network Device Support ---&gt;     [ x ] Et..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="950" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

'''Ethernet:'''

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

'''Wifi:''' 

The wireless card has two controller solutions

Proprietary driver:

The Broadcom STA driver can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].

or

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
&lt;/pre&gt;</text>
    <sha1>ae6cce8cbe28a5b76c56f8eb6449ebf6b0dba4f8</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>DVB</title>
  <ns>0</ns>
  <id>81</id>
  <revision>
    <id>898</id>
    <parentid>891</parentid>
    <timestamp>2014-01-23T03:00:32Z</timestamp>
    <contributor>
      <username>Sinyorita</username>
      <id>351</id>
    </contributor>
    <minor/>
    <comment>Undo revision 891 by [[Special:Contributions/Count Zero|Count Zero]] ([[User talk:Count Zero|talk]])</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10123" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.
[http://www.propertykita.com/rumah.html Rumah Dijual di Jakarta], [http://www.awanirentcar.com Sewa mobil jakarta], [http://kiosauto.com Aksesoris mobil]

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
[http://www.optimaweb.co.id/jasa-seo Jasa seo Jakarta], [http://www.optimaweb.co.id/jasa-seo Jasa seo Bergaransi]
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>f3c4f9c7eec44a0e934172de3c5ed5b9fbbd03e5</sha1>
  </revision>
  <revision>
    <id>901</id>
    <parentid>898</parentid>
    <timestamp>2014-03-15T16:31:34Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Sinyorita|Sinyorita]] ([[User talk:Sinyorita|talk]]) to last revision by [[User:Count Zero|Count Zero]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9855" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
I've been a big fan of tv tuner cards for almost as long as I've been in to computers.  As soon as my dad bought an HDTV, I knew I had to have it, and the first chance I had was to buy the ATI HDTV Wonder card for my computer.  Sure, the picture can be bad sometimes because you are grabbing the signal out of the air with an unamplified antenna, but it is well worth it.  When I finally decided to make the jump to Linux a few months ago, I researched ahead of time if it was possible to use my card in Linux, and to my surprise I could.  Let me note that it did take me a few months of on and off work to get it running since I was pretty much learning Linux from scratch along the way.  The biggest pitfalls I ran in to was the lack of a complete HOWTO to lead me through the steps from start to finish and the lack of a large DVB/HDTV user community to ask for help when I ran in to trouble.  I hope that this tutorial gets rid of those two pitfalls and lets you get your HDTV card working without any trouble.

==Kernel Configuration ==
I'm not sure which kernel exactly began including the necesary modules for the ATI HDTV Wonder card, but I do know that kernel versions 2.6.15 and up have them.  In order to use the ATI HDTV Wonder, you need to enable the correct modules in the kernel.  You need to enable I2C and the cx88 DVB modules under Device Drivers.  If you are new to building your own kernel, see [[Kernel26Compilation]]

snipped from my .config
 #
 # I2C support
 #
 CONFIG_I2C=m
 CONFIG_I2C_CHARDEV=m
 
 #
 # I2C Algorithms
 #
 CONFIG_I2C_ALGOBIT=m
 
 #
 # Video For Linux
 #
 
 #
 # Video Adapters
 #
 CONFIG_VIDEO_CX88=m
 CONFIG_VIDEO_CX88_ALSA=m
 CONFIG_VIDEO_CX88_DVB=m
 CONFIG_VIDEO_CX88_DVB_ALL_FRONTENDS=n
 CONFIG_VIDEO_CX88_VP3054=m
 #
 # Digital Video Broadcasting Devices
 #
 CONFIG_DVB=y
 CONFIG_DVB_CORE=m
 
 #
 # ATSC (North American/Korean Terresterial DTV) frontends
 #
 CONFIG_DVB_NXT200X=m
 
If you are a less advanced user, it won't hurt anything if you select everything that might remotely deal with DVB as a Module (hit `M`).  When you are done, save the configuration and compile the kernel.  Before you reboot, you need to download the firmware for the card.

== Firmware ==
Make sure you are in /usr/src/linux
 # pwd
 /usr/src/linux
There is a script provided that will download the appropriate firmware driver for you.  First, make it executable, then run it.
 # chmod +x Documentation/dvb/get_dvb_firmware
 # ./Documentation/dvb/get_dvb_firmware nxt2004
Then the firmware file needs to be copied to the directory where hotplug will find it.  On Slackware, this directory is /lib/firmware
 # cp dvb-fe-nxt2004.fw /lib/firmware
Now you can reboot in to your new kernel, and your card should be automatically recognized.  You can check to see if the modules loaded with lsmod
 $ lsmod | grep cx88
 cx88_dvb                8964  0
 cx8802                  8068  1 cx88_dvb
 cx88xx                 54180  2 cx88_dvb,cx8802
 ir_common               7812  1 cx88xx
 btcx_risc               3848  2 cx8802,cx88xx
 tveeprom               12304  1 cx88xx
 cx88_vp3054_i2c         3456  1 cx88_dvb
 i2c_algo_bit            7432  2 cx88xx,cx88_vp3054_i2c
 mt352                   5380  1 cx88_dvb
 or51132                 8324  1 cx88_dvb
 video_buf_dvb           4228  1 cx88_dvb
 video_buf              15364  4 cx88_dvb,cx8802,cx88xx,video_buf_dvb
 nxt200x                11524  1 cx88_dvb
 cx24123                 7684  1 cx88_dvb
 lgdt330x                6684  1 cx88_dvb
 cx22702                 5252  1 cx88_dvb
 i2c_core               15248  15 nvidia,w83627hf,eeprom,i2c_isa,i2c_nforce2,cx88_dvb,cx88xx,tveeprom,i2c_algo_bit,mt352,or51132,nxt200x,cx24123,lgdt330x,cx22702
 dvb_pll                 9220  4 cx88_dvb,or51132,nxt200x,cx22702

== DVB Apps ==
All that we are really interested in with DVB Apps is scan and azap.  I created a SlackBuild script that will create a package from the dvb apps cvs.  To use the SlackBuild script, you will first need to create a temporary directory to house the relevant components and then you will need to get the sources from the dvb apps CVS.  If you are new to SlackBuild scripts, check out the [[SlackBuild_Scripts]] tutorial.  You will log in to the cvs with an empty password.
 $ mkdir ~/dvb-apps-build
 $ cd ~/dvb-apps-build
 $ cvs -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv login
 $ cvs -z3 -d :pserver:anonymous@cvs.linuxtv.org:/cvs/linuxtv co dvb-apps

== Udev Rules ==
By default, my udev would not create the correct devices nodes, so I found these rules on a website which fixed the problem.  I can not remember what site I found them on at the moment, but I will be sure to give credit to that site when I find it again.  You will need to create or edit the file /etc/udev/rules.d/010_local.rules and place this information in it:
 #create correct dvb devices
 KERNEL=="dvb0.dvr*",        NAME="dvb/adapter0/dvr%n"
 KERNEL=="dvb0.demux*",      NAME="dvb/adapter0/demux%n"
 KERNEL=="dvb0.frontend*",   NAME="dvb/adapter0/frontend%n"
 KERNEL=="dvb0.audio*",      NAME="dvb/adapter0/audio%n"
 KERNEL=="dvb0.ca*",         NAME="dvb/adapter0/ca%n"
 KERNEL=="dvb0.osd*",        NAME="dvb/adapter0/osd%n"
 KERNEL=="dvb0.net*",        NAME="dvb/adapter0/net%n"
 KERNEL=="dvb0.video*",      NAME="dvb/adapter0/video%n"

== Scanning for Channels ==
Once dvb-apps is installed, you can see if everything is working correctly.  First, you need to create the ~/.azap directory, then you need to create your channels.conf file.  Since my ATI HDTVWonder uses an antenna to grab channels, I used the us-NTSC-center-frequencies-8VSB database file.
 $ mkdir ~/.azap
 $ touch ~/.azap/channels.conf
 $ scan /usr/local/share/dvb/scan/atsc/us-NTSC-center-frequencies-8VSB &gt; ~/.azap/channels.conf
This will take some time and it will give you a lot of "tuning failed" messages, but if it is successful, you will see something like this when it is done:
 dumping lists (12 services)
 WJZ-DT:617000000:8VSB:49:52:1
 WNUV High Def:629000000:8VSB:49:52:3
 WNUV - The Tube:629000000:8VSB:65:68:4
 Same as the Tube:629000000:8VSB:81:84:5
 FOX45 HDTV:665000000:8VSB:49:52:3
 FOX45 Digital Television:665000000:8VSB:65:68:4
 WMAR-Radar SD-3:701000000:8VSB:81:84:5
 WMAR-SD2:701000000:8VSB:65:68:4
 WMAR-HD:701000000:8VSB:49:52:3
 WMAR-TV:701000000:8VSB:0:0:65535
 WBALDT:743000000:8VSB:49:52:1
 WBALSD:743000000:8VSB:65:68:2
 Done.
You can edit that file to remove channels as you please.  If you want to use MPlayer for output, copy the channels.conf over to ~/.mplayer, and, likewise, ~/.xine for using Xine.  You can substitute symlinks if you are more comfortable with that, too.  Once the file is in ~/.azap, you can test the channels by running something similar to:
 $ azap -r WBALDT
 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
 tuning to 743000000 Hz
 video pid 0x0031, audio pid 0x0034
 status 1f | signal 9fb0 | snr 5c32 | ber 00000000 | unc 0000007f | FE_HAS_LOCK
 status 1f | signal fbf0 | snr df58 | ber 00000060 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc20 | snr de9c | ber 00000008 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fb50 | snr db7c | ber 00000018 | unc 00000000 | FE_HAS_LOCK
 status 1f | signal fc70 | snr dc66 | ber 00000028 | unc 00000000 | FE_HAS_LOCK
Hit CTRL+C after a few lines to exit out.  Those lines above show that everything is working alright.  You can also check that everything is o.k. with dmesg:
 $ dmesg
 ...
 nxt2004: Waiting for firmware upload (dvb-fe-nxt2004.fw)...
 nxt2004: Waiting for firmware upload(2)...
 nxt2004: Firmware upload complete
 cx88[0]/2: queue is empty - first active
 cx88[0]/2: cx8802_start_dma w: 0, h: 0, f: 2
 cx88[0]/2: setting the interrupt mask
 cx88[0]/2: [f53b9b80/0] cx8802_buf_queue - first active
 cx88[0]/2: cx8802_restart_queue
 cx88[0]/2: cx8802_restart_queue: queue is empty

== Setting up MPlayer ==
According to the MPlayer website, the configuration script should detect your DVB card and compile DVB support automatically. That did not work for me.  The configure script could not find my dvb include directory, so i had to specify it when I ran configure.  I edited Rob Workman's SlackBuild script [[http://slackbuilds.rlworkman.net/MPlayer/]] to allow for DVB support to be compiled.  Here is the configure options I used, the rest of the script was left untouched:
 ./configure \
   --prefix=/usr \
   --confdir=/etc/mplayer \
   --enable-gui \
   --enable-menu \
   --enable-dvb \
   --with-dvbincdir=/usr/src/linux/include \
   --enable-xmms \
   --with-codecsdir=$CODECSDIR \
   --with-win32libdir=$CODECSDIR 
 
Notice the "--enable-dvb" and "--with-dvbincdir" options.  Once I specified those, everything ran fine.  Once MPlayer is compiled correctly and installed, make sure you place a copy of channels.conf in ~/.mplayer.  When you are done that, you can run MPlayer by either specifying the device or by specifying the channel:
 $ mplayer /dev/dvb/adapter0/dvr0
or
 $ mplayer dvb://WMARHD
GMPlayer is a GTK frontend that gets installed with MPlayer and can also be used for DVB, but I have not figured out how to get a DVB option in the menus yet.  When I figure it out, I will update this accordingly.  Right now, you can launch gmplayer using the same lines above by simply substituting mplayer with gmplayer.

== Setting up Xine ==
According to everything I have read about Xine, it is supposed to compile automatically with DVB support.  However, I still can not get it to view my DVB stream.  As soon as I figure out how to make it work, I will update this page accordingly.

== Resources ==

http://www.mythtv.org/wiki/index.php/ATI_HDTV_Wonder

http://www.mythtv.org/wiki/index.php/Adding_QAM_Channels_For_HDTV_Tuner_Cards

http://www.mythtv.org/wiki/index.php/Dvb_Apps

http://www.linuxtv.org/</text>
    <sha1>ec6559520878aab1714f2b78351def4e6c009ce3</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>Slack-desc</title>
  <ns>0</ns>
  <id>17</id>
  <revision>
    <id>899</id>
    <parentid>570</parentid>
    <timestamp>2014-01-23T17:33:29Z</timestamp>
    <contributor>
      <username>Arfon</username>
      <id>70</id>
    </contributor>
    <minor/>
    <comment>/* Tools */  - linuxpackages.net is no more.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2046" xml:space="preserve">=Overview=
A proper slack-desc file should be written as follows:

 # HOW TO EDIT THIS FILE:
 # The "handy ruler" below makes it easier to edit a package description.  Line
 # up the first '|' above the ':' following the base package name, and the '|' on
 # the right side marks the last column you can put a character in.  You must make
 # exactly 11 lines for the formatting to be correct.  It's also customary to
 # leave one space after the ':'.
 
        |-----handy-ruler------------------------------------------------------|
 appname: appname (Short description of the application)
 appname:      &lt;this line is generally left blank&gt;
 appname: Description of application  -  this description should be fairly
 appname: in-depth; in other words, make it clear what the package does (and 
 appname: maybe include relevant links and/or instructions if there's room),
 appname: but don't get too verbose.  
 appname: This file can have a maximum of eleven (11) lines of text preceded by
 appname: the "appname: " designation.  
 appname:
 appname: It's a good idea to include a link to the application's homepage too.
 appname:

The "appname" string must *exactly* match the application name portion of the 
Slackware package (for example, a package titled "gaim-1.5-i486-1.tgz" must have 
a slack-desc file with the &lt;appname&gt; string of "gaim: " rather than "Gaim: " or 
"GAIM: " or something else.

The first line ''must'' show the application name followed by a short
description (enclosed in parentheses).

The "handy ruler" is meant to stop you at 79 characters, because the standard
console is 80x25 and if you go beyond this the words will wrap.

The space after the : is needed only when there is text after the :
In the above example lines 9 &amp; 11 should not have a space after the :

=Tools=
1. There is a command-line tool that automates the creation of slack-desc files and helps you generate legal slack-desc files with minimal effort:
http://slack-desc.sourceforge.net/

=See Also=
 man makepkg
 man pkgtool

[[Category:Tutorials]]</text>
    <sha1>0f3097d30f877cb9195c9d921fe5a49bafc34225</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>SlackBuild Scripts</title>
  <ns>0</ns>
  <id>15</id>
  <revision>
    <id>900</id>
    <parentid>897</parentid>
    <timestamp>2014-03-15T16:31:25Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Sinyorita|Sinyorita]] ([[User talk:Sinyorita|talk]]) to last revision by [[User:Rworkman|Rworkman]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2881" xml:space="preserve">SlackBuild scripts are simple shell scripts which can automate the compiling and packaging of a program from source. 

While not necessary to compile and create packages on Slackware, SlackBuilds serve as tools for scripting the compiling and packaging processes, which are often repetitive. Just as importantly, SlackBuilds also act as documentation of compile-time options and configurations for that particular package. For that reason, official Slackware packages come with SlackBuilds bundled with the source code, and the inclusion of a SlackBuild is desirable in third-party packages.

== Using SlackBuild Scripts ==
In this example I'm going to use the [http://www.pidgin.im Pidgin] slackbuild. First you find on the mirror in the source directory and download the whole directory of Pidgin:

: &lt;code&gt;mkdir pidgin&lt;/code&gt;
: &lt;code&gt;cd pidgin&lt;/code&gt;
: &lt;code&gt;wget --passive-ftp &lt;nowiki&gt;ftp://slackware.at/slackware-12.1/source/xap/pidgin/*&lt;/nowiki&gt;&lt;/code&gt;

This downloads the files needed for Slackware scripts.  The same idea applies for SlackBuild scripts from other
sources - you generally need to download all of the files in the directory that contains the build script.  For example, in the pidgin source directory, you would need the following files:

: &lt;code&gt;pidgin-2.4.1.tar.bz2  pidgin-encryption-3.0.tar.gz  pidgin.SlackBuild*  slack-desc &lt;/code&gt;

There will sometimes be other files, such as doinst.sh, diff.gz patch files, and rc.* scripts in this directory.

Now, say you want to get the newest version of pidgin? Well, you download the tar.bz2 file (in Pidgin, the script uses tar.bz2). Now you open up pidgin.Slackbuild:

: &lt;code&gt;VERSION=2.4.1&lt;/code&gt;

This is the line we are looking at. Now we can change this to

: &lt;code&gt;VERSION=2.4.2&lt;/code&gt;

Now you can edit the compile flags and other cool things not covered here. Now that we have downloaded and edited the SlackBuild script, let's make it executable:

: &lt;code&gt;chmod +x pidgin.SlackBuild&lt;/code&gt;

Now this is executable, and we want to run as root for permissions and other reasons so we want to become root:

: &lt;code&gt;su -&lt;/code&gt;

Now we start the script, and this will compile Pidgin and make a Slackware package.  Depending on how the 
script is written, the resulting package will be in /tmp, some directory of /tmp, or perhaps some
other location - have a look at the SlackBuild script for some hints if you can't find the package that
was built.  

Once you find the package, you simply use 'installpkg' to install it normally (and you probably want to
move it somewhere else on your system for safekeeping).

: &lt;code&gt;./pidgin.SlackBuild&lt;/code&gt;

=SlackBuild Archives=
;* http://www.slackbuilds.org
;* http://repository.slacky.eu
;* http://www.slackware.com/~alien/slackbuilds/

=Other Resources=
For a bit more detailed tutorial, see this entry: [[Writing A SlackBuild Script]]


[[Category:Tutorials]]</text>
    <sha1>5efc3844c6e55de198f33a7ed5009d1bd1cf0049</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>Broadcom Wireless</title>
  <ns>0</ns>
  <id>246</id>
  <revision>
    <id>902</id>
    <parentid>589</parentid>
    <timestamp>2014-04-01T21:42:31Z</timestamp>
    <contributor>
      <username>Beder</username>
      <id>313</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5078" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

=== Sbopkg method ===
If a working internet connection is available on the laptop (say a wired connection), use [http://sbopkg.org sbopkg] to install the drivers :
&lt;pre&gt;sbopkg -i broadcom-sta&lt;/pre&gt;

=== Manual method ===
Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

=== Kernel upgrade ===

If at any point you upgrade your kernel, you will have to do this process again, because the module is compiled against the running kernel only.

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/lib/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
blacklist bcma
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

If you still don't see the wireless extensions, check if any of the blacklisted modules are really not loaded:
&lt;pre&gt;
lsmod | grep ssb
lsmod | grep b43
lsmod | grep bcma
&lt;/pre&gt;

None of this commands should return anything. If any of the modules are still loaded, remove them manually:
&lt;pre&gt;
rmmod ssb
rmmod b43
rmmod bcma
&lt;/pre&gt;

You can also make sure that the "wl" module is properly loaded
&lt;pre&gt;
lsmod | grep wl
&lt;/pre&gt;

If there is no output, you may load the "wl" module manually
&lt;pre&gt;
modprobe wl
&lt;/pre&gt;


You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If a working internet connection is available on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;.

For example, on a 32-bit system running Slackware 13.37, as root:

&lt;pre&gt;
 wget http://slackware.dreamhost.com/slackware/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.

=== User note ===
In order to access the wicd client utilities, your user must also be in the netdev group. Add your user to the netdev group, logout and login to make it effective, then you can run the wicd client utilities as your user.
For the CLI based tool, there is wicd-cli and wicd-curses. For the GUI client, ther is wicd-client and wicd-gtk.</text>
    <sha1>7e4b9cfdcfc85840767fda07c59ce2ad56ddfc27</sha1>
  </revision>
  <revision>
    <id>903</id>
    <parentid>902</parentid>
    <timestamp>2014-04-03T03:36:33Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Do not edit files in /lib/modprobe.d/ - they are overwritten on upgrades</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5078" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

=== Sbopkg method ===
If a working internet connection is available on the laptop (say a wired connection), use [http://sbopkg.org sbopkg] to install the drivers :
&lt;pre&gt;sbopkg -i broadcom-sta&lt;/pre&gt;

=== Manual method ===
Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

=== Kernel upgrade ===

If at any point you upgrade your kernel, you will have to do this process again, because the module is compiled against the running kernel only.

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so open up the &lt;code&gt;/etc/modprobe.d/blacklist.conf&lt;/code&gt; using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
blacklist bcma
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

If you still don't see the wireless extensions, check if any of the blacklisted modules are really not loaded:
&lt;pre&gt;
lsmod | grep ssb
lsmod | grep b43
lsmod | grep bcma
&lt;/pre&gt;

None of this commands should return anything. If any of the modules are still loaded, remove them manually:
&lt;pre&gt;
rmmod ssb
rmmod b43
rmmod bcma
&lt;/pre&gt;

You can also make sure that the "wl" module is properly loaded
&lt;pre&gt;
lsmod | grep wl
&lt;/pre&gt;

If there is no output, you may load the "wl" module manually
&lt;pre&gt;
modprobe wl
&lt;/pre&gt;


You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If a working internet connection is available on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;.

For example, on a 32-bit system running Slackware 13.37, as root:

&lt;pre&gt;
 wget http://slackware.dreamhost.com/slackware/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.

=== User note ===
In order to access the wicd client utilities, your user must also be in the netdev group. Add your user to the netdev group, logout and login to make it effective, then you can run the wicd client utilities as your user.
For the CLI based tool, there is wicd-cli and wicd-curses. For the GUI client, ther is wicd-client and wicd-gtk.</text>
    <sha1>acead184858e2e6a3073e5477ead2970313cd166</sha1>
  </revision>
  <revision>
    <id>904</id>
    <parentid>903</parentid>
    <timestamp>2014-04-03T03:38:04Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>/* Blacklisting the b43 and ssb modules */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5151" xml:space="preserve">[[Category:Tutorials]]
== Introduction ==

This tutorial is written for setting up wireless on Slackware on laptops with Broadcom wireless cards. It deals with installing Boradcom's official proprietary '''wl''' driver for Linux that includes support for Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware.

== Prerequisites ==

This tutorial assumes a full Slackware installation. There should also be a way to transfer files to the target laptop - it can either be a working internet connection using the laptop's ethernet card, '''or''' a different machine with internet access and a USB thumb drive to transfer the files.
The regular user account on the laptop must also be a part of the ''netdev'' group.

== Getting Started ==

The first thing is to check if the user is part of the ''netdev'' group :

&lt;pre&gt;groups&lt;/pre&gt;

If the output does not contain &lt;code&gt;netdev&lt;/code&gt;, then as &lt;code&gt;root&lt;/code&gt;, enter the following command :

&lt;pre&gt;usermod -a -G netdev username&lt;/pre&gt;

where &lt;code&gt;username&lt;/code&gt; is the name of your user account.

== Installing the driver ==

=== Sbopkg method ===
If a working internet connection is available on the laptop (say a wired connection), use [http://sbopkg.org sbopkg] to install the drivers :
&lt;pre&gt;sbopkg -i broadcom-sta&lt;/pre&gt;

=== Manual method ===
Navigate to the slackbuilds.org's [http://slackbuilds.org/result/?search=broadcom-sta&amp;sv= broadcom-sta page] and build the package according to the [http://slackbuilds.org/howto/ instructions] given. Make sure to download the source code relevant to the architecture of your installation (32-bit or 64-bit).

=== Kernel upgrade ===

If at any point you upgrade your kernel, you will have to do this process again, because the module is compiled against the running kernel only.

== Blacklisting the b43 and ssb modules ==

The Broadcom's &lt;code&gt;wl&lt;/code&gt; driver conflicts with the kernel's &lt;code&gt;b43&lt;/code&gt; driver, so create the &lt;code&gt;/etc/modprobe.d/b43-blacklist.conf&lt;/code&gt; file (name doesn't matter, but it's nice to have something intuitive) using the text editor of your choice as &lt;code&gt;root&lt;/code&gt; and add the following lines to it :

&lt;pre&gt;
blacklist ssb
blacklist b43
blacklist bcma
&lt;/pre&gt;

== Final steps ==

At this point, reboot your machine. The drivers should be installed and work now. To test this, enter the &lt;code&gt;iwconfig&lt;/code&gt; command. you should see an output like this :

&lt;pre&gt;
$ iwconfig
lo        no wireless extensions.

eth1      IEEE 802.11  Nickname:"lapto"
          Access Point: Not-Associated   
          Link Quality:5  Signal level:217  Noise level:199
          Rx invalid nwid:0  invalid crypt:31  invalid misc:0

eth0      no wireless extensions.
&lt;/pre&gt;

This output suggests that the drivers installed right and your wireless card is recognized as &lt;code&gt;eth1&lt;/code&gt; by the kernel. Hooray!

If you still don't see the wireless extensions, check if any of the blacklisted modules are really not loaded:
&lt;pre&gt;
lsmod | grep ssb
lsmod | grep b43
lsmod | grep bcma
&lt;/pre&gt;

None of this commands should return anything. If any of the modules are still loaded, remove them manually:
&lt;pre&gt;
rmmod ssb
rmmod b43
rmmod bcma
&lt;/pre&gt;

You can also make sure that the "wl" module is properly loaded
&lt;pre&gt;
lsmod | grep wl
&lt;/pre&gt;

If there is no output, you may load the "wl" module manually
&lt;pre&gt;
modprobe wl
&lt;/pre&gt;


You can now either use the &lt;code&gt;iwconfig&lt;/code&gt; tool to configure your wireless networks, '''or''' if you prefer to use a GUI, follow the next section for installing Wicd.

== Installing Wicd ==

To make management of wireless connections easier, we will install [http://wicd.sourceforge.net/ Wicd] network manager that provides a simple configuration GUI and system tray icon.

=== Using slackpkg ===

If a working internet connection is available on the laptop (say a wired connection), simply use &lt;code&gt;slackpkg&lt;/code&gt; to install wicd :
&lt;pre&gt;slackpkg install wicd&lt;/pre&gt;

=== Using package tarball ===

Download the &lt;code&gt;Wicd&lt;/code&gt; package for your Slackware version from the ''extra/'' section of your preferred Slackware [http://slackware.osuosl.org/ mirror] and install using &lt;code&gt;installpkg&lt;/code&gt;.

For example, on a 32-bit system running Slackware 13.37, as root:

&lt;pre&gt;
 wget http://slackware.dreamhost.com/slackware/slackware-13.37/extra/wicd/wicd-1.7.0-i486-2.txz
 installpkg ./wicd-1.7.0-i486-2.txz
&lt;/pre&gt;

== Wicd usage ==
Start the Wicd daemon :

&lt;pre&gt;
 /etc/rc.d/rc.wicd start
&lt;/pre&gt;

Once its started, run &lt;code&gt;wicd-client&lt;/code&gt; and configure the network to your liking.

=== Caveat ===
Wicd by default treats &lt;code&gt;wlan0&lt;/code&gt; as the default wireless interface. Since the interface is &lt;code&gt;eth1&lt;/code&gt; in our case, you might want to correct this in Wicd's Preferences.

=== User note ===
In order to access the wicd client utilities, your user must also be in the netdev group. Add your user to the netdev group, logout and login to make it effective, then you can run the wicd client utilities as your user.
For the CLI based tool, there is wicd-cli and wicd-curses. For the GUI client, ther is wicd-client and wicd-gtk.</text>
    <sha1>9602ae0af77f289abf6c213a93861eb8f2dc1103</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>Talk:Broadcom Wireless</title>
  <ns>1</ns>
  <id>315</id>
  <revision>
    <id>905</id>
    <timestamp>2014-04-03T03:44:05Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Explanation of changes wrt /etc/modprobe.d/</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1159" xml:space="preserve">I just made a couple of relatively minor edits to the page (20140402):
First, admins shouldn't edit files in /lib/modprobe.d/ - those get overwritten on package upgrades; only /etc/modprobe.d/ or /run/modprobe.d/ should be used for local sysadmin edits, as they are not overwritten on upgrades.  However, /run is on a tmpfs, so it is not persistent across reboots; as such, it would applicable for e.g. rules that are auto-generated on system startup based on some nonstable attributes (whether that's a good idea is another discussion entirely, but I think not).  Given all of that, /etc/modprobe.d/ is the best location -- its intent is for sysadmins to copy files from /lib/modprobe.d/ and edit the copies if needed (same-named files in both /etc/modprobe.d/ and /lib/modprobe.d/ are handled such that the file in /etc/modprobe.d/ takes precedence).   This leads up to my second point:
Second, since there's no need in this particular case to override *all* of what's in /lib/modprobe.d/blacklist.conf (you only want to *add* content to it), it's a bit cleaner to just create a new file in /etc/modprobe.d/ with a sensible name and put what you want in it.</text>
    <sha1>e7aba4da0c121a7e0c36e38f48cb1e6ce20ca544</sha1>
  </revision>
  <revision>
    <id>906</id>
    <parentid>905</parentid>
    <timestamp>2014-04-03T03:44:38Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1171" xml:space="preserve">I just made a couple of relatively minor edits to the page (20140402):
First, admins shouldn't edit files in /lib/modprobe.d/ - those get overwritten on package upgrades; only /etc/modprobe.d/ or /run/modprobe.d/ should be used for local sysadmin edits, as they are not overwritten on upgrades.  However, /run is on a tmpfs, so it is not persistent across reboots; as such, it would applicable for e.g. rules that are auto-generated on system startup based on some nonstable attributes (whether that's a good idea is another discussion entirely, but I think not).  Given all of that, /etc/modprobe.d/ is the best location -- its intent is for sysadmins to copy files from /lib/modprobe.d/ and edit the copies if needed (same-named files in both /etc/modprobe.d/ and /lib/modprobe.d/ are handled such that the file in /etc/modprobe.d/ takes precedence).   This leads up to my second point:
Second, since there's no need in this particular case to override *all* of what's in /lib/modprobe.d/blacklist.conf (you only want to *add* content to it), it's a bit cleaner to just create a new file in /etc/modprobe.d/ with a sensible name and put what you want in it.  --rworkman</text>
    <sha1>ed7c40a4602d046b3ab4e1c62274c16f23eda157</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>Utf-8 linux console</title>
  <ns>0</ns>
  <id>177</id>
  <revision>
    <id>907</id>
    <parentid>415</parentid>
    <timestamp>2014-05-09T17:36:30Z</timestamp>
    <contributor>
      <username>Dive</username>
      <id>19</id>
    </contributor>
    <minor/>
    <comment>/* A Quick Look at Using UTF-8 in the Linux Console (without X) */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4696" xml:space="preserve">[[Category:Tutorials]]
''by Dive''

== A Quick Look at Using UTF-8 in the Linux Console (without X) ==

	A few people have asked about this in ##slackware lately so I though I'd put down a few notes on how I got utf-8 up and running. Feel free to add any further info. 

	In these days of high powered X desktop environments with all their flashy composite bells and whistles it may seem strange to worry about how the plain Linux console behaves, but we need to remember that there are some very nice applications that live in the console and can be just as (or even more) productive than the X Windows counterparts. I'm thinking of screen, irssi, mutt, elinks, vim/vi, mplayer (using svga), links, zgv and slrn to name but a few. And of course we have to mention Slackware tools like pgktool, slackpkg and sbopkg. Once you get hooked on using the console it is hard to go back.
	Anyway here we go ...

== The Console ==


	The first thing to do is configure the console. There is a kernel parameter we can add to 
/etc/lilo.conf to do this:

append="vt.default_utf8=1"

Here's an example from mine:

  # Linux bootable partition config begins
  image = /boot/vmlinuz-2.6.27.7-custom
  root = /dev/hda1
  label = Linux-custom
  append="resume=/dev/hda2 vt.default_utf8=1"
  read-only
  # Linux bootable partition config ends

Once you have saved lilo.conf and run '''lilo''' a quick reboot is needed.

== LANG environment variable ==

I find that typing multibyte characters like "ä" and erasing them with backspace, I can erase much more than what I wrote. It helps to set the LANG variable, preferably by editing /etc/profile.d/lang.sh (or lang.csh) to set it to en_US.UTF-8 or similar.

== Fonts ==


	After that we need to find a font that actually contains the characters you want to see. My 'font of the moment' is lat9w-16. This contains the British £ (pound) and € (euro) symbols that I need, plus a lot of useful accented characters. But what is just as important are the correct drawing characters so that curses programs like pkgtool and sbopkg are printed on the screen correctly. If you experiment with the '''setconsolefont''' command you will find that some fonts draw curses box borders as squares or question marks, so check out some fonts and see which ones work and which don't.
	The '''setconsolefont''' command will put your chosen font into /etc/rc.d/rc.font so it will load at bootup.


== Keyboard ==


	Ok, great you can now read characters correctly, but you need the correct keymap to be able to type them. That's a little harder. If you can find a utf-8 keymap for your locale/hardware then that's fine. Personally I didn't find any of the installed keymaps suitable so I looked around for an alternative. I found a uk-utf8 keymap on the intertubes, but this was unfortunately missing all the Ctrl+[a-z] keys so I edited it and added my own. I also added some AltGr+[a-z] (well not all of those) for accented characters. You may find this keymap useful as a starting point to create your own if you cannot find a more suitable one. Have a look through the comments and the codes and you should pick up the method.
	To add your own combinations you will need to know the correct codes for the characters you need. You can find a table of utf-8 characters here:

[http://home.tiscali.nl/t876506/utf8tbl.html]http://home.tiscali.nl/t876506/utf8tbl.html

Look up the code in that table and convert it to hex. E.G.
è is 232 in decimal, E8 in hex; é is code 233 in decimal, E9 in hex, so the entry in your keymap should be:

  # key      = normal   shifted   AltGr+e   AltGr+shift+e
  keycode 18 = e        E         U+00E8    U+00E9
  # prints:    e        E         è         é  

You can find the keycodes with the '''showkey''' program. Once edited you can load the map with the '''loadkeys''' program. Loadkeys will update /etc/rc.d/rc.keymap but you will need to copy the keymap to /usr/share/kbd/keymaps/i386/qwerty/ so it is found on bootup. Here is a link to my updated uk-utf8 map:

[http://www.unrealize.co.uk/source/uk-utf.map.gz]http://www.unrealize.co.uk/source/uk-utf.map.gz

You can load this ungzipped but it's better to gzip it back after editing to keep things consistent.

== Conclusion ==


	By now you should have a fully usable keyboard/console correctly printing unicode characters. You will probably need to tell some programs like mutt and irrsi that you are using a utf-8 system.


Note: There exists two shell scripts - '''unicode_start''' and '''unicode_stop'''. Typing '''unicode_start [font]''' will load the required font and set up keyboard correctly for unicode input.


Bye for now,

[[User:Dive|Dive]] 02:33, 20 March 2009 (UTC)</text>
    <sha1>76a7e301c82a1512ad9d2e3ecc318ab7a8358fa4</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>Antivirus</title>
  <ns>0</ns>
  <id>52</id>
  <revision>
    <id>908</id>
    <parentid>73</parentid>
    <timestamp>2014-07-04T15:49:46Z</timestamp>
    <contributor>
      <username>DanS</username>
      <id>353</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6828" xml:space="preserve">= Antivirus =


Why would you want antivirus software on a Linux box, when there are so few Linux viruses out there?  Maybe you don't want to spread them to Windows boxes, or maybe you're worried about getting windows viruses via Windows emulation software, or maybe you want a little extra insurance.  The next question is which one?  Depends on what you're looking for.  A good thread on this is [http://www.linuxquestions.org/questions/slackware-14/antivirus-636562/?highlight=antivirus].  I'll talk about  installing 2 antivirus programs, Clam and Antivir.

'''Clam''': I haven't used it, but it has a command line scanner and a manual updater.  Go to [http://www.slackbuilds.org] and search for clamav.  Follow the instructions.

'''Antivir''':  The good: updates virus definitions automatically, and scans files in realtime on open/close (can also scan on execute).  You can run scans manually from the command line, and there's a GUI if you want to use it.  The bad:  complicated setup, I don't think the free version scans samba shares, has spyware protection, and it won't automatically scan archive files until you extract them.  **Update** [http://www.avira.com/en/support-for-home-knowledgebase-detail/kbid/1491 Ending Support]

The rest of this tutorial helps you setup Antivir for Slackware 12.1 and Slackware 12.0.  This is a compilation of information from dazuko.org, the Antivir user manual, and my own personal experience.


==You need:==

#latest dazuko kernel module from [http://www.dazuko.org/indexold.shtml]
#antivir from [http://www.avira.com]
#some time to kill


==Slackware 12.1==

===Dazuko===

*Extract dazuko somewhere: &lt;code&gt;tar xzvf dazuko-2.3.4.tar.gz&lt;/code&gt;.  There are 2 ways to install the kernel module, either via LSM or syscall hooks.  The recommended way is via LSM, but I wasn't able to configure the Slackware 2.6.24.5 kernel to compile capabilities as a module (make menuconfig-&gt;Security Options-&gt;Default Linux Capabilities).  I was able to do this with the old kernel in Slackware 12.0, but not the new one.  View the FAQ at dazuko.org for more info.  Also view &lt;dazuko_dir&gt;/README.linux26 for info on using syscall hooks.

*Recompile the kernel (Tested).  You only need to do this if you're using an SMP (multi-processor capable) kernel.  I won't go into detail on how to recompile the kernel, as that's covered here [http://slackwiki.org/Kernel_Compilation].  Anyway, before you make the kernel, &lt;code&gt;cd /usr/src/linux&lt;/code&gt;, and patch the kernel like this:
**&lt;code&gt;patch fs/dcache.c &lt;dazuko_dir&gt;/patch_dpath.diff&lt;/code&gt;
**Finish recompiling the kernel, make sure everything boots up OK.
**&lt;code&gt;cd &lt;dazuko_dir&gt;&lt;/code&gt;
**&lt;code&gt;./configure --enable-syscalls --mapfile=/boot/System.map --disable-local-dpath&lt;/code&gt;
*if you don't need to recompile the kernel (non-SMP), do this:
**&lt;code&gt;./configure --enable-syscalls --mapfile=/boot/System.map&lt;/code&gt;
*Don't recompile the kernel, and pass in different flags to &lt;code&gt;./configure&lt;/code&gt; (Untested).  I'm not totally sure if you lose any functionality by doing this, but up to you.
**&lt;code&gt;cd &lt;dazuko_dir&gt;&lt;/code&gt;
**&lt;code&gt;./configure --enable-syscalls --mapfile=/boot/System.map --disable-chroot-support&lt;/code&gt;
*&lt;code&gt;make&lt;/code&gt;
*&lt;code&gt;cd example_c&lt;/code&gt;
*&lt;code&gt;make&lt;/code&gt;
*&lt;code&gt;example /tmp&lt;/code&gt;
*in another terminal, create a test file in your /tmp directory.  if you see output from example, dazuko is working correctly.
*&lt;code&gt;cd ..&lt;/code&gt;
*&lt;code&gt;make test&lt;/code&gt;
*&lt;code&gt;make install&lt;/code&gt;


===Antivir===

*Extract antivir somewhere.  There is documentation under &lt;code&gt;&lt;antivir_dir&gt;/doc/avserver_en.pdf&lt;/code&gt;, along with some readmes.
*Install with &lt;code&gt;./install&lt;/code&gt;.    Make sure that you specify to let antivir load the dazuko module (easier).  The path to it is &lt;code&gt;/lib/modules/`uname -r`/extra/dazuko.ko&lt;/code&gt;.  You probably want the default options, including the 2 hr updates.
*add users to the antivir group.  &lt;code&gt;vim /etc/group&lt;/code&gt;, and add usernames to the antivir group.
*my personal preference is to move infected files to /home/quarantine.  here's how you set it up:
**&lt;code&gt;mkdir /home/quarantine&lt;/code&gt;
**&lt;code&gt;chown nobody:antivir /home/quarantine&lt;/code&gt;
**&lt;code&gt;chmod 775 /home/quarantine&lt;/code&gt;
*under &lt;code&gt;/etc/avguard.conf&lt;/code&gt;, add/edit these lines:
**&lt;code&gt;MoveConcerningFilesTo /home/quarantine&lt;/code&gt;
**&lt;code&gt;IncludePath /opt/downloads&lt;/code&gt; (where I put all my downloads, /home already scanned by default)
*restart avguard with &lt;code&gt;/usr/sbin/avguard restart&lt;/code&gt;
*test that it works by going to [http://www.eicar.org].  There's a link for downloading sample viruses.  If everything works, the file should be moved immediately to &lt;code&gt;/home/quarantine&lt;/code&gt;.  For archive files (.zip, .tar, etc.), you will have to extract them before antivir will catch them.  Lame free restriction.
*files to remember:
**&lt;code&gt;/etc/avguard.conf&lt;/code&gt;
**&lt;code&gt;/etc/avupdater.conf&lt;/code&gt;
**&lt;code&gt;/var/log/avguard.log&lt;/code&gt;
**&lt;code&gt;/var/log/avupdater.log&lt;/code&gt;
**&lt;code&gt;/usr/bin/antivir&lt;/code&gt;
**&lt;code&gt;/usr/bin/antivir-gui&lt;/code&gt;
**&lt;code&gt;/usr/sbin/avguard&lt;/code&gt;
**&lt;code&gt;/usr/sbin/avupdater&lt;/code&gt;
*commands to remember
**to do a manual update
***&lt;code&gt;antivir --update&lt;/code&gt;
**to scan a directory manually, and all subdirectories, extracting archive files
***&lt;code&gt;antivir --allfiles -s -z --moveto=/home/quarantine &lt;directory_to_scan&gt;&lt;/code&gt;

==Slackware 12.0==

===Dazuko===

*Extract dazuko somewhere: tar xzvf dazuko-2.3.4.tar.gz.  We can install this the recommended way, via LSM.  You shouldn't need to recompile the kernel, as capabilities should be a module.  To check, do this:
**&lt;code&gt;lsmod | grep capab&lt;/code&gt;
**If you see it there, you're in luck.  Otherwise you need to recompile the kernel with this option:
***make menuconfig-&gt;Security Options-&gt;&lt;M&gt;Default Linux Capabilities.
*&lt;code&gt;cd &lt;dazuko_dir&gt;&lt;/code&gt;
*&lt;code&gt;./configure&lt;/code&gt;
*&lt;code&gt;make&lt;/code&gt; (probably need to be root)
*&lt;code&gt;rmmod capability&lt;/code&gt; (unload this for a second so we can try out dazuko).
*&lt;code&gt;make test&lt;/code&gt;
*&lt;code&gt;cd example_c&lt;/code&gt;
*&lt;code&gt;make&lt;/code&gt;
*&lt;code&gt;example /tmp&lt;/code&gt;
*in another terminal, create a test file in your /tmp directory.  if you see output from example, dazuko is working correctly.
*&lt;code&gt;cd ..&lt;/code&gt;
*&lt;code&gt;make install&lt;/code&gt;
*&lt;code&gt;modprobe capability&lt;/code&gt; (reload into memory)
*edit &lt;code&gt;/etc/rc.d/rc.modules&lt;/code&gt;, and add this line before the capability module is loaded:
**&lt;code&gt;/sbin/modprobe dazuko&lt;/code&gt;
*There is an issue when the capability module is loaded first.  The steps above load the dazuko module first, which should fix the problem.


===Antivir===

*Same as above, except tell antivir that the kernel will load the module.  This is so that you can load dazuko before capabilities in &lt;code&gt;/etc/rc.d/rc.modules&lt;/code&gt;.

[[Category:Tutorials]]</text>
    <sha1>fe6ea239a6a9b09ee415d57a1ef5a3c983b9e45c</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>Apc8750</title>
  <ns>0</ns>
  <id>316</id>
  <revision>
    <id>909</id>
    <timestamp>2014-08-03T14:17:24Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <comment>Created page with "   JUST PREPARING THE PAGE   Installing Slackware on apc-8750 http://apc.io/products/8750a/ http://apc.io/library/ https://github.com/linux-wmt/linux-vtwm http://arm.slackware..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4142" xml:space="preserve">


JUST PREPARING THE PAGE


Installing Slackware on apc-8750
http://apc.io/products/8750a/
http://apc.io/library/
https://github.com/linux-wmt/linux-vtwm
http://arm.slackware.com/getslack/
http://ftp.arm.slackware.com/slackwarearm/

Creating a bootable micro sd card
   problem
   solution

Installing slackware
   

Creating a bootable micro sd card
  For this you need a custom built kernel and a initramfs image from slackware for arm distribution - uinitrd-kirkwood.img

Preparing the micro sd card
  You need at least three partitions, one vfat, one or more Linux partitions, and a Linux swap partition. Here is how the partitions I used look like under fdisk ran on host.


Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap


1st partition: make it bootable, and create a file system using mkfs.vfat
2nd partition: create a reiserfs ( or other ) file system using mkreiserfs

Now you need to make a custom kernel for booting into. I used linux-vtwm-testing
available at https://github.com/linux-wmt/linux-vtwm
Please refer to the link: for the config file which was used.
also require a small initramfs image prepared from the boot media aviable at apc.io library. download it from here : initramfs_data.cpio.gz or
use the following init scrip with the initrd.gz from apc.io library.
init:

        #!/bin/busybox sh
        /bin/busybox mount -t proc /proc
        /bin/busybox mount -t sys /sys
        /bin/busybox echo /sbin/mdev &gt; /proc/sys/kernel/hotplug
        /bin/busybox mdev -s
        /bin/busybox --install
        mkfs.ext2 /dev/ram0
        mkdir /root
        mount /dev/ram0 /root
        cd /root
        mkdir /flash
        mount /dev/mmcblk0p1 /flash
        cpio -id &lt; /flash/initrd-kirkwood.cpio
        exec chroot /root /bin/busybox init
        exec /bin/busybox init

Copy the initramfs_data.cpio.gz for to $KERNEL_SRC/usr area.
In case you are building it on your own:
gunzip initrd.gz
mkdir initramfs_dat
mountpoint initramfs_data || mount -o loop initrd fs
create initramfs_data/init as shown above
chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &gt; ../initramfs_data.cpio.gz )


Please note that the kernel uses a CONFIG_CMDLINE=
for vga:
CONFIG_CMDLINE=" mem=440M console=tty0 mbtotal=52M"
for serial:
CONFIG_CMDLINE=" mem=440M console=ttyWMT0,115200n8 mbtotal=52M"
kernel is compiled on the host, using arm-2014.05 from arm.

Eg:
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin


Preparing the cpio archive:

        dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz
        gunzip initrd-kirkwood.cpio.gz

Once both uzImage.bin and initrd-kirkwood.cpio copy them to the bootable vfat partition. 
create a slackware14.1 directory in the reiserfs partition of the micro sd card.
copy slackware for arm distribution to the slackware14.1 directory. Now you 
are ready to boot the new disk, and install slackware from the pre mounted directory
under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ).</text>
    <sha1>4294ace4b61033232da12cf94d30177b9ecf0151</sha1>
  </revision>
  <revision>
    <id>910</id>
    <parentid>909</parentid>
    <timestamp>2014-08-03T14:45:20Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4255" xml:space="preserve">
== Trial Edition ==


== Installing Slackware on apc-8750 ==

== Creating a bootable micro sd card ==
  
For this you need a custom built kernel and a initramfs image from slackware for arm distribution - uinitrd-kirkwood.img

=== Preparing the micro sd card ===


You need at least three partitions, one vfat, one or more Linux partitions, and a Linux swap partition. Here is how the partitions I used look like under fdisk ran on host.

&lt;pre&gt;
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap

&lt;/pre&gt;

Creating filesystem:

* 1st partition: make it bootable, and create a file system using mkfs.vfat
* 2nd partition: create a reiserfs ( or other ) file system using mkreiserfs

Now you need to make a custom kernel for booting into. I used linux-vtwm-testing
available at https://github.com/linux-wmt/linux-vtwm
Please refer to the link: for the config file which was used.
also require a small initramfs image prepared from the boot media aviable at apc.io library. download it from here : initramfs_data.cpio.gz or
use the following init scrip with the initrd.gz from apc.io library.

init:
&lt;pre&gt;
        #!/bin/busybox sh
        /bin/busybox mount -t proc /proc
        /bin/busybox mount -t sys /sys
        /bin/busybox echo /sbin/mdev &gt; /proc/sys/kernel/hotplug
        /bin/busybox mdev -s
        /bin/busybox --install
        mkfs.ext2 /dev/ram0
        mkdir /root
        mount /dev/ram0 /root
        cd /root
        mkdir /flash
        mount /dev/mmcblk0p1 /flash
        cpio -id &lt; /flash/initrd-kirkwood.cpio
        exec chroot /root /bin/busybox init
        exec /bin/busybox init
&lt;/pre&gt;

Copy the initramfs_data.cpio.gz for to $KERNEL_SRC/usr area.
In case you are building it on your own:
&lt;pre&gt;
gunzip initrd.gz
mkdir initramfs_dat
mountpoint initramfs_data || mount -o loop initrd fs
create initramfs_data/init as shown above
chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &gt; ../initramfs_data.cpio.gz )
&lt;/pre&gt;

Please note that the kernel uses a CONFIG_CMDLINE=
for vga:
* CONFIG_CMDLINE=" mem=440M console=tty0 mbtotal=52M"
for serial:
* CONFIG_CMDLINE=" mem=440M console=ttyWMT0,115200n8 mbtotal=52M"
kernel is compiled on the host, using arm-2014.05 from arm.

Eg:
&lt;pre&gt;
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin

&lt;/pre&gt;
Preparing the cpio archive:
&lt;pre&gt;
        dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz
        gunzip initrd-kirkwood.cpio.gz
&lt;/pre&gt;
Once both uzImage.bin and initrd-kirkwood.cpio copy them to the bootable vfat partition. 

Create a slackware14.1 directory in the reiserfs partition of the micro sd card.
Copy slackware for arm distribution to the slackware14.1 directory. Now you 
are ready to boot the new disk, and install slackware from the pre mounted directory
under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ).

=== Configuration ===

For X Windows, use a window manager like fluxbox.

== links ==

http://apc.io/products/8750a/

http://apc.io/library/

https://github.com/linux-wmt/linux-vtwm

http://arm.slackware.com/getslack/

http://ftp.arm.slackware.com/slackwarearm/</text>
    <sha1>154b9bf6dabc6101cea231ee52e115b83e34a09f</sha1>
  </revision>
  <revision>
    <id>911</id>
    <parentid>910</parentid>
    <timestamp>2014-08-03T17:05:42Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <comment>/* Creating a bootable micro sd card */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4691" xml:space="preserve">
== Trial Edition ==


== Installing Slackware on apc-8750 ==

== Creating a bootable micro sd card ==
  
For this you need a custom built kernel and a initramfs image from slackware for arm distribution - uinitrd-kirkwood.img
 
             * uzImage.bin
                   [[Detailed description of how uzImage.bin was prepared.]]

             * initrd-kirkwood.cpio
                   [[Detailed description of how initrd-kirkwood.cpio was prepared.]]

Download and keep these files ready

=== Preparing the micro sd card ===

You need at least three partitions, one vfat, one or more Linux partitions, and a Linux swap partition for this method of installation. Here is how the partitions I used look like under fdisk ran on host.

&lt;pre&gt;
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap

&lt;/pre&gt;

Creating filesystem:

* 1st partition: make it bootable, and create a file system using mkfs.vfat
* 2nd partition: create a reiserfs ( or other ) file system using mkreiserfs

==== Detailed description of how uzImage.bin was prepared. ====

I used linux-vtwm-testing available at https://github.com/linux-wmt/linux-vtwm
Please refer to the link [[config.slackinstall.vga]] for the config file which was used. This method also require a small initramfs image prepared from the boot media aviable at apc.io library. download it from here : [[initramfs_data.cpio.gz]] or
use the following init scrip with the initrd.gz from apc.io library.

init:
&lt;pre&gt;
        #!/bin/busybox sh
        /bin/busybox mount -t proc /proc
        /bin/busybox mount -t sys /sys
        /bin/busybox echo /sbin/mdev &gt; /proc/sys/kernel/hotplug
        /bin/busybox mdev -s
        /bin/busybox --install
        mkfs.ext2 /dev/ram0
        mkdir /root
        mount /dev/ram0 /root
        cd /root
        mkdir /flash
        mount /dev/mmcblk0p1 /flash
        cpio -id &lt; /flash/initrd-kirkwood.cpio
        exec chroot /root /bin/busybox init
        exec /bin/busybox init
&lt;/pre&gt;

Copy the initramfs_data.cpio.gz for to $KERNEL_SRC/usr area.

===== Details of how initramfs_data.cpio.gz was prepared. =====

&lt;pre&gt;
gunzip initrd.gz
mkdir initramfs_data
mount -o loop initrd initramfs_data

create initramfs_data/init as shown above

chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &gt; ../initramfs_data.cpio.gz )

&lt;/pre&gt;

Please note that the kernel uses a CONFIG_CMDLINE=
for vga:
* CONFIG_CMDLINE=" mem=440M console=tty0 mbtotal=52M"
for serial:
* CONFIG_CMDLINE=" mem=440M console=ttyWMT0,115200n8 mbtotal=52M"
kernel is compiled on the host, using arm-2014.05 from arm.

kernel build procedure:
&lt;pre&gt;
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin

&lt;/pre&gt;
Preparing the cpio archive:
&lt;pre&gt;
        download uinitrd-kirkwood.img
        dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz
        gunzip initrd-kirkwood.cpio.gz
&lt;/pre&gt;

=== Copying slackware install files onto second partition ===

Create a slackware14.1 directory in the reiserfs partition of the micro sd card.
Copy slackware for arm distribution to the slackware14.1 directory. 

=== Booting and installing slackware ===

Now you are ready to boot the new disk, and install slackware from the pre mounted directory under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ).

=== Configuration ===

For X Windows, use a window manager like fluxbox.

== links ==

http://apc.io/products/8750a/

http://apc.io/library/

https://github.com/linux-wmt/linux-vtwm

http://arm.slackware.com/getslack/

http://ftp.arm.slackware.com/slackwarearm/</text>
    <sha1>89c7c2a440d493c4e714d5161bf989faf6b223d0</sha1>
  </revision>
  <revision>
    <id>912</id>
    <parentid>911</parentid>
    <timestamp>2014-08-03T17:58:39Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8089" xml:space="preserve">
== Installing Slackware on apc-8750 ==

Mainline linux kernel lacks support for Wondermedia 8750 currently. 
However linux-vtwm kernel available at github has support for Wondermedia 8750 SOC.
Since the kernel failed to load initrd cpio archive the normal way, a special method
was used for loading the setup image. 

* Create three partitions, first bootable vfat, second reiserfs and third Linux swap.
* Download and copy uzImage.bin and initrd-kirkwood.cpio to first vfat partition
* Download and copy Slackware installation files over to second partition
* Boot from the micro sd card prepared, install, and configure Slackware
* Download and replace the boot kernel with new uzImage.bin for booting from 
second partition.

== Creating a bootable micro sd card ==
  
For this you need a custom built kernel and a initramfs image from Slackware for 
arm distribution - uinitrd-kirkwood.img
 
             * uzImage.bin
                   [[Detailed description of how uzImage.bin was prepared.]]

             * initrd-kirkwood.cpio
                   [[Detailed description of how initrd-kirkwood.cpio was prepared.]]

Download and keep these files ready

=== Preparing the micro sd card ===

You need at least three partitions, one vfat, one or more Linux partitions, and a 
Linux swap partition for this method of installation. Here is how the partitions I
used look like under fdisk ran on host.

&lt;pre&gt;
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap

&lt;/pre&gt;

Creating filesystem:

* 1st partition: make it bootable, and create a file system using mkfs.vfat
* 2nd partition: create a reiserfs ( or other ) file system using mkreiserfs

==== Detailed description of how Slackware install kernel was prepared. ====

I used linux-vtwm-testing available at https://github.com/linux-wmt/linux-vtwm
Zipfile you download from the site may cause problem when extracting - few files
may be missing!. One option is to use p7zip or other unzip program instead of the
default zip utility in Slackware. You may also get a tar.gz file using
&lt;pre&gt;
wget --no-check-certificate \
    https://github.com/linux-wmt/linux-vtwm/archive/testing.tar.gz
&lt;/pre&gt;

Please refer to the link [[config.slackinstall.vga]] for the config file which was used. This method also require a small initramfs image prepared from the boot media available at apc.io library. download it from here : [[initramfs_data.cpio.gz]] or
use the following init scrip with the initrd.gz from apc.io library.

init:
&lt;pre&gt;
        #!/bin/busybox sh
        /bin/busybox mount -t proc /proc
        /bin/busybox mount -t sys /sys
        /bin/busybox echo /sbin/mdev &gt; /proc/sys/kernel/hotplug
        /bin/busybox mdev -s
        /bin/busybox --install
        mkfs.ext2 /dev/ram0
        mkdir /root
        mount /dev/ram0 /root
        cd /root
        mkdir /flash
        mount /dev/mmcblk0p1 /flash
        cpio -id &lt; /flash/initrd-kirkwood.cpio
        exec chroot /root /bin/busybox init
        exec /bin/busybox init
&lt;/pre&gt;

Copy the initramfs_data.cpio.gz for to $KERNEL_SRC/usr area.

===== Details of how initramfs_data.cpio.gz was prepared. =====

&lt;pre&gt;
gunzip initrd.gz
mkdir initramfs_data
mount -o loop initrd initramfs_data

create initramfs_data/init as shown above

chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &gt; ../initramfs_data.cpio.gz )

&lt;/pre&gt;

Please note that the kernel uses a CONFIG_CMDLINE=
for vga:
&lt;pre&gt;
CONFIG_CMDLINE=" mem=440M console=tty0 mbtotal=52M"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;
for serial:
&lt;pre&gt;
CONFIG_CMDLINE=" mem=440M console=ttyWMT0,115200n8 mbtotal=52M"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;
kernel is compiled on the host, using arm-2014.05 from arm.

kernel build procedure:
&lt;pre&gt;
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin

&lt;/pre&gt;
Preparing the cpio archive:

&lt;pre&gt;
        download http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img
        dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz
        gunzip initrd-kirkwood.cpio.gz
&lt;/pre&gt;

== Copying Slackware install files onto second partition ==

Create a slackware14.1 directory in the reiserfs partition of the micro sd card.
Copy Slackware for arm distribution to the slackware14.1 directory, from  http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/

      sdc1:
                /uzImage.bin
                /initrd-kirkwood.cpio
      sdc2:
                /slackware14.1/

== Booting with the installer and installing Slackware ==

Now you are ready to boot the from the new disk just prepared, and install Slackware from the pre mounted directory under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ). Put the newly prepared micro sd card in the slot and reboot apc-8750. Once you get the Slackware login prompt, proceed as usual.

=== Configuration ===

For X Windows, use a window manager like fluxbox.

== Post installation preparation ==

After the installation is done, you need to replace the kernel uzImage.bin with a new
one, this time with no initramfs_data.cpio.gz, and CONFIG_CMDLINE= changed for bootin from partition 2. 

&lt;pre&gt;
CONFIG_CMDLINE=" mem=460M root=/dev/mmcblk0p2 rootwait nonitrd ro console=tty0"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;

For this, download uzImage.bin from here, and copy over
to the first partition ( bootable vfat one ). Once that is done reboot the machine once again, to get Slackware going!

=== Procedure used for preparing the Slackware boot kernel ===

Please refer to the link [[config.slackboot.vga]] for the config file which was used.
&lt;pre&gt;
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackboot.vga $OBJ/.config
rm $KERNEL_SRC/usr/initramfs_data.cpio.g

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin

&lt;/pre&gt;

Once Slackware is installed, and the  new uzImage.bin is copied over

    sdc1:
              /uzImage.bin
              /initrd-kirkwood.cpio  =&gt; not required anymore

    sdc2:

              /bin
              /boot
              /cdrom
              /dev/
              /etc/
              /home/
              /proc/
              /slackware14.1  =&gt; not required anymore
              /usr/
              /var/

You may remove files which are not required anymore, and free up some space. Once that is done, reboot apc-8750. 
== links ==

http://apc.io/products/8750a/

http://apc.io/library/

https://github.com/linux-wmt/linux-vtwm

http://arm.slackware.com/getslack/

http://ftp.arm.slackware.com/slackwarearm/</text>
    <sha1>f3ed39fe0e1e7b16a2c98b1f804aa82f4ab73934</sha1>
  </revision>
  <revision>
    <id>913</id>
    <parentid>912</parentid>
    <timestamp>2014-08-03T18:21:24Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <comment>/* links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8121" xml:space="preserve">
== Installing Slackware on apc-8750 ==

Mainline linux kernel lacks support for Wondermedia 8750 currently. 
However linux-vtwm kernel available at github has support for Wondermedia 8750 SOC.
Since the kernel failed to load initrd cpio archive the normal way, a special method
was used for loading the setup image. 

* Create three partitions, first bootable vfat, second reiserfs and third Linux swap.
* Download and copy uzImage.bin and initrd-kirkwood.cpio to first vfat partition
* Download and copy Slackware installation files over to second partition
* Boot from the micro sd card prepared, install, and configure Slackware
* Download and replace the boot kernel with new uzImage.bin for booting from 
second partition.

== Creating a bootable micro sd card ==
  
For this you need a custom built kernel and a initramfs image from Slackware for 
arm distribution - uinitrd-kirkwood.img
 
             * uzImage.bin
                   [[Detailed description of how uzImage.bin was prepared.]]

             * initrd-kirkwood.cpio
                   [[Detailed description of how initrd-kirkwood.cpio was prepared.]]

Download and keep these files ready

=== Preparing the micro sd card ===

You need at least three partitions, one vfat, one or more Linux partitions, and a 
Linux swap partition for this method of installation. Here is how the partitions I
used look like under fdisk ran on host.

&lt;pre&gt;
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap

&lt;/pre&gt;

Creating filesystem:

* 1st partition: make it bootable, and create a file system using mkfs.vfat
* 2nd partition: create a reiserfs ( or other ) file system using mkreiserfs

==== Detailed description of how Slackware install kernel was prepared. ====

I used linux-vtwm-testing available at https://github.com/linux-wmt/linux-vtwm
Zipfile you download from the site may cause problem when extracting - few files
may be missing!. One option is to use p7zip or other unzip program instead of the
default zip utility in Slackware. You may also get a tar.gz file using
&lt;pre&gt;
wget --no-check-certificate \
    https://github.com/linux-wmt/linux-vtwm/archive/testing.tar.gz
&lt;/pre&gt;

Please refer to the link [[config.slackinstall.vga]] for the config file which was used. This method also require a small initramfs image prepared from the boot media available at apc.io library. download it from here : [[initramfs_data.cpio.gz]] or
use the following init scrip with the initrd.gz from apc.io library.

init:
&lt;pre&gt;
        #!/bin/busybox sh
        /bin/busybox mount -t proc /proc
        /bin/busybox mount -t sys /sys
        /bin/busybox echo /sbin/mdev &gt; /proc/sys/kernel/hotplug
        /bin/busybox mdev -s
        /bin/busybox --install
        mkfs.ext2 /dev/ram0
        mkdir /root
        mount /dev/ram0 /root
        cd /root
        mkdir /flash
        mount /dev/mmcblk0p1 /flash
        cpio -id &lt; /flash/initrd-kirkwood.cpio
        exec chroot /root /bin/busybox init
        exec /bin/busybox init
&lt;/pre&gt;

Copy the initramfs_data.cpio.gz for to $KERNEL_SRC/usr area.

===== Details of how initramfs_data.cpio.gz was prepared. =====

&lt;pre&gt;
gunzip initrd.gz
mkdir initramfs_data
mount -o loop initrd initramfs_data

create initramfs_data/init as shown above

chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &gt; ../initramfs_data.cpio.gz )

&lt;/pre&gt;

Please note that the kernel uses a CONFIG_CMDLINE=
for vga:
&lt;pre&gt;
CONFIG_CMDLINE=" mem=440M console=tty0 mbtotal=52M"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;
for serial:
&lt;pre&gt;
CONFIG_CMDLINE=" mem=440M console=ttyWMT0,115200n8 mbtotal=52M"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;
kernel is compiled on the host, using arm-2014.05 from arm.

kernel build procedure:
&lt;pre&gt;
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin

&lt;/pre&gt;
Preparing the cpio archive:

&lt;pre&gt;
        download http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img
        dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz
        gunzip initrd-kirkwood.cpio.gz
&lt;/pre&gt;

== Copying Slackware install files onto second partition ==

Create a slackware14.1 directory in the reiserfs partition of the micro sd card.
Copy Slackware for arm distribution to the slackware14.1 directory, from  http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/

      sdc1:
                /uzImage.bin
                /initrd-kirkwood.cpio
      sdc2:
                /slackware14.1/

== Booting with the installer and installing Slackware ==

Now you are ready to boot the from the new disk just prepared, and install Slackware from the pre mounted directory under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ). Put the newly prepared micro sd card in the slot and reboot apc-8750. Once you get the Slackware login prompt, proceed as usual.

=== Configuration ===

For X Windows, use a window manager like fluxbox.

== Post installation preparation ==

After the installation is done, you need to replace the kernel uzImage.bin with a new
one, this time with no initramfs_data.cpio.gz, and CONFIG_CMDLINE= changed for bootin from partition 2. 

&lt;pre&gt;
CONFIG_CMDLINE=" mem=460M root=/dev/mmcblk0p2 rootwait nonitrd ro console=tty0"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;

For this, download uzImage.bin from here, and copy over
to the first partition ( bootable vfat one ). Once that is done reboot the machine once again, to get Slackware going!

=== Procedure used for preparing the Slackware boot kernel ===

Please refer to the link [[config.slackboot.vga]] for the config file which was used.
&lt;pre&gt;
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackboot.vga $OBJ/.config
rm $KERNEL_SRC/usr/initramfs_data.cpio.g

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin

&lt;/pre&gt;

Once Slackware is installed, and the  new uzImage.bin is copied over

    sdc1:
              /uzImage.bin
              /initrd-kirkwood.cpio  =&gt; not required anymore

    sdc2:

              /bin
              /boot
              /cdrom
              /dev/
              /etc/
              /home/
              /proc/
              /slackware14.1  =&gt; not required anymore
              /usr/
              /var/

You may remove files which are not required anymore, and free up some space. Once that is done, reboot apc-8750. 
== links ==

http://apc.io/products/8750a/

http://apc.io/library/

https://github.com/linux-wmt/linux-vtwm

http://arm.slackware.com/getslack/

http://ftp.arm.slackware.com/slackwarearm/

https://github.com/gv1/apc8750</text>
    <sha1>937cc3530a0c1c662ce74ba220b36aabeaf305d3</sha1>
  </revision>
  <revision>
    <id>914</id>
    <parentid>913</parentid>
    <timestamp>2014-08-04T03:11:36Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <comment>/* links */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8900" xml:space="preserve">
== Installing Slackware on apc-8750 ==

Mainline linux kernel lacks support for Wondermedia 8750 currently. 
However linux-vtwm kernel available at github has support for Wondermedia 8750 SOC.
Since the kernel failed to load initrd cpio archive the normal way, a special method
was used for loading the setup image. 

* Create three partitions, first bootable vfat, second reiserfs and third Linux swap.
* Download and copy uzImage.bin and initrd-kirkwood.cpio to first vfat partition
* Download and copy Slackware installation files over to second partition
* Boot from the micro sd card prepared, install, and configure Slackware
* Download and replace the boot kernel with new uzImage.bin for booting from 
second partition.

== Creating a bootable micro sd card ==
  
For this you need a custom built kernel and a initramfs image from Slackware for 
arm distribution - uinitrd-kirkwood.img
 
             * uzImage.bin
                   [[Detailed description of how uzImage.bin was prepared.]]

             * initrd-kirkwood.cpio
                   [[Detailed description of how initrd-kirkwood.cpio was prepared.]]

Download and keep these files ready

=== Preparing the micro sd card ===

You need at least three partitions, one vfat, one or more Linux partitions, and a 
Linux swap partition for this method of installation. Here is how the partitions I
used look like under fdisk ran on host.

&lt;pre&gt;
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap

&lt;/pre&gt;

Creating filesystem:

* 1st partition: make it bootable, and create a file system using mkfs.vfat
* 2nd partition: create a reiserfs ( or other ) file system using mkreiserfs

==== Detailed description of how Slackware install kernel was prepared. ====

I used linux-vtwm-testing available at https://github.com/linux-wmt/linux-vtwm
Zipfile you download from the site may cause problem when extracting - few files
may be missing!. One option is to use p7zip or other unzip program instead of the
default zip utility in Slackware. You may also get a tar.gz file using
&lt;pre&gt;
wget --no-check-certificate \
    https://github.com/linux-wmt/linux-vtwm/archive/testing.tar.gz
&lt;/pre&gt;

Please refer to the link [[config.slackinstall.vga]] for the config file which was used. This method also require a small initramfs image prepared from the boot media available at apc.io library. download it from here : [[initramfs_data.cpio.gz]] or
use the following init scrip with the initrd.gz from apc.io library.

init:
&lt;pre&gt;
        #!/bin/busybox sh
        /bin/busybox mount -t proc /proc
        /bin/busybox mount -t sys /sys
        /bin/busybox echo /sbin/mdev &gt; /proc/sys/kernel/hotplug
        /bin/busybox mdev -s
        /bin/busybox --install
        mkfs.ext2 /dev/ram0
        mkdir /root
        mount /dev/ram0 /root
        cd /root
        mkdir /flash
        mount /dev/mmcblk0p1 /flash
        cpio -id &lt; /flash/initrd-kirkwood.cpio
        exec chroot /root /bin/busybox init
        exec /bin/busybox init
&lt;/pre&gt;

Copy the initramfs_data.cpio.gz for to $KERNEL_SRC/usr area.

===== Details of how initramfs_data.cpio.gz was prepared. =====

&lt;pre&gt;
gunzip initrd.gz
mkdir initramfs_data
mount -o loop initrd initramfs_data

create initramfs_data/init as shown above

chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &gt; ../initramfs_data.cpio.gz )

&lt;/pre&gt;

Please note that the kernel uses a CONFIG_CMDLINE=
for vga:
&lt;pre&gt;
CONFIG_CMDLINE=" mem=440M console=tty0 mbtotal=52M"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;
for serial:
&lt;pre&gt;
CONFIG_CMDLINE=" mem=440M console=ttyWMT0,115200n8 mbtotal=52M"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;
kernel is compiled on the host, using arm-2014.05 from arm.

kernel build procedure:
&lt;pre&gt;
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin

&lt;/pre&gt;
Preparing the cpio archive:

&lt;pre&gt;
        download http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img
        dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz
        gunzip initrd-kirkwood.cpio.gz
&lt;/pre&gt;

== Copying Slackware install files onto second partition ==

Create a slackware14.1 directory in the reiserfs partition of the micro sd card.
Copy Slackware for arm distribution to the slackware14.1 directory, from  http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/

      sdc1:
                /uzImage.bin
                /initrd-kirkwood.cpio
      sdc2:
                /slackware14.1/

== Booting with the installer and installing Slackware ==

Now you are ready to boot the from the new disk just prepared, and install Slackware from the pre mounted directory under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ). Put the newly prepared micro sd card in the slot and reboot apc-8750. Once you get the Slackware login prompt, proceed as usual.

=== Configuration ===

For X Windows, use a window manager like fluxbox.

== Post installation preparation ==

After the installation is done, you need to replace the kernel uzImage.bin with a new
one, this time with no initramfs_data.cpio.gz, and CONFIG_CMDLINE= changed for bootin from partition 2. 

&lt;pre&gt;
CONFIG_CMDLINE=" mem=460M root=/dev/mmcblk0p2 rootwait nonitrd ro console=tty0"
CONFIG_CMDLINE_FORCE=y
&lt;/pre&gt;

For this, download uzImage.bin from here, and copy over
to the first partition ( bootable vfat one ). Once that is done reboot the machine once again, to get Slackware going!

=== Procedure used for preparing the Slackware boot kernel ===

Please refer to the link [[config.slackboot.vga]] for the config file which was used.
&lt;pre&gt;
export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackboot.vga $OBJ/.config
rm $KERNEL_SRC/usr/initramfs_data.cpio.g

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
     -e 0x8000 -n "My Linux" -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin

&lt;/pre&gt;

Once Slackware is installed, and the  new uzImage.bin is copied over

    sdc1:
              /uzImage.bin
              /initrd-kirkwood.cpio  =&gt; not required anymore

    sdc2:

              /bin
              /boot
              /cdrom
              /dev/
              /etc/
              /home/
              /proc/
              /slackware14.1  =&gt; not required anymore
              /usr/
              /var/

You may remove files which are not required anymore, and free up some space. Once that is done, reboot apc-8750. 
== links ==

http://apc.io/products/8750a/

http://apc.io/library/

https://github.com/linux-wmt/linux-vtwm

http://arm.slackware.com/getslack/

http://ftp.arm.slackware.com/slackwarearm/

http://sourceforge.net/projects/slackwareonapc8750/files/

http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download

http://sourceforge.net/projects/slackwareonapc8750/files/install/vga/uzImage.bin/download

http://sourceforge.net/projects/slackwareonapc8750/files/boot/vga/uzImage.bin/download

http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackinst.vga/download

http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackboot.vga/download

http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackinst.ttyWMT0/download

http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackboot.ttyWMT0/download

http://sourceforge.net/projects/slackwareonapc8750/files/initramfs_data.cpio.gz/download</text>
    <sha1>19882d6ff78bd1ae8c1d05903b2ab99debced7f5</sha1>
  </revision>
  <revision>
    <id>915</id>
    <parentid>914</parentid>
    <timestamp>2014-08-07T07:37:54Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13017" xml:space="preserve">== Installing Slackware on APC-8750 ==

[[Image:http://apc.io/media/apc/img/apc-products-8750.jpg|APC 8750]]&lt;br /&gt;[http://apc.io/media/apc/img/apc-angle.jpg Another photograph of APC 8750]

[https://sourceforge.net/p/slackwareonapc8750 Project Area]

Mainline Linux kernel lacks support for [http://www.wondermedia.com.tw/en/products/platform/soc/wm8750/ Wondermedia WM 8750] currently. However [https://github.com/linux-wmt/linux-vtwm linux-vtwm-testing] kernel available at github has support for Wondermedia 8750 SOC. Since the kernel failed to load initrd cpio archive the normal way, a special method was used for loading the Slackware setup image. ( Installer Kernel booting from embedded initramfs image creates a filesystem on ramdisk, extracts Slackware setup initrd image and chroots to the filesystem on ramdisk ). Briefly, the steps followed in installing Slackware on APC 8750 are :

# '''Installing Slackware.'''
## Prepare boot media: Create three partitions, first bootable vfat, second reiserfs and third Linux swap.
## Copy installer boot files: Download and copy uzImage.bin and initrd-kirkwood.cpio to first vfat partition.
## Download and copy Slackware installation files over to second partition.
## Boot from the micro sd card prepared, install, and configure Slackware.
# '''Making new installtion bootable.'''
## Download and replace the installer kernel with new uzImage.bin for booting from second partition.
## Reboot.

=== Creating a bootable micro sd card for installation ===

For this you need a custom built kernel and a initramfs image from Slackware for arm distribution - [http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img uinitrd-kirkwood.img].

* [http://sourceforge.net/projects/slackwareonapc8750/files/install/vga/uzImage.bin/download uzImage.bin] for console on VGA monitor.&lt;br /&gt;If this kernel is chosen boot messages will appear on VGA monitor. or
* [http://sourceforge.net/projects/slackwareonapc8750/files/install/ttyWMT0/uzImage.bin/download uzImage.bin] for console on serial port.&lt;br /&gt;If this kernel is chosen boot messages will appear on the serial port.
* [http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio.gz] initramfs cpio archive.&lt;br /&gt;Download and gunzip this image file.
* Download [http://arm.slackware.com/getslack/ Slackware 14.1 for arm].&lt;br /&gt;If you prefer, you may download this to micro sd card directly, under slackware14.1 directory.

Download and keep these ready.

==== Preparing the micro sd card. ====

You need at least three partitions, one vfat, one or more Linux partitions, and a Linux swap partition for this method of installation. Here is how the partitions I used look like under fdisk ran on host.

&lt;pre&gt;
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap

&lt;/pre&gt;

==== Creating filesystems. ====

* 1st partition - make it bootable, and create a file system using mkfs.vfat
* 2nd partition - create a reiserfs file system using mkreiserfs ( or other tools for other types )

==== Copying Slackware install files onto second partition. ====

Create a slackware14.1 directory in the reiserfs partition of the micro sd card. Copy Slackware for arm distribution to the slackware14.1 directory, from http://arm.slackware.com/getslack/. Once the preparation is over,

&lt;pre&gt;sdc1: 
    /uzImage.bin  
    /initrd-kirkwood.cpio

sdc2:
    /slackware14.1/&lt;/pre&gt;
==== Booting with the installer and installing Slackware. ====

Now you are ready to boot from the new disk just prepared, and install Slackware from the pre mounted directory under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ). Put the newly prepared micro sd card in the slot and reboot APC-8750. Once you get the Slackware login prompt, proceed for installation as usual.

==== Configuration ====

For X Windows, use a lightweight window manager like Fluxbox.

=== Post installation preparation. ===

After the installation is done, you need to replace the kernel uzImage.bin with a new one, this time with no initramfs_data.cpio.gz, and CONFIG_CMDLINE= changed for booting from partition 2:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=460M root=/dev/mmcblk0p2 rootwait nonitrd ro console=tty0&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
For this, download one of

* [http://sourceforge.net/projects/slackwareonapc8750/files/boot/vga/uzImage.bin/download uzImage.bin] for console on VGA. Or
* [http://sourceforge.net/projects/slackwareonapc8750/files/boot/ttyWMT0/uzImage.bin/download uzImage.bin] for console on serial port.

and copy over to the first partition ( bootable vfat one ).

Once Slackware is installed, and the new uzImage.bin is copied over,

&lt;pre&gt;sdc1:
    /uzImage.bin
    /initrd-kirkwood.cpio  =&amp;gt; not required anymore

sdc2:
    /bin
    /boot
    /cdrom
    /dev/
    /etc/
    /home/
    /proc/
    /slackware14.1  =&amp;gt; not required anymore
    /usr/
    /var/&lt;/pre&gt;
You may remove files which are not required anymore, and free up some space. Once that is done, reboot APC-8750 to get Slackware up and running.

=== Information on building kernel and other images. ===

Please also refer to [http://sourceforge.net/projects/slackwareonapc8750/files/build.sh/download build.sh] script used to help the build procedure.

==== Detailed description of how Slackware install kernel was prepared. ====

===== Getting the Kernel source code. =====

I used [https://github.com/linux-wmt/linux-vtwm linux-vtwm-testing]. Zipfile you download from the site may cause problem when extracting on Linux. In my case couple of files were missing. One option is to use p7zip or other unzip program instead of the default zip utility in Slackware. You may also get a tar.gz file using:

&lt;pre&gt;wget --no-check-certificate \
    https://github.com/linux-wmt/linux-vtwm/archive/testing.tar.gz&lt;/pre&gt;
Please refer to the link [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackinst.vga/download config.slackinst.vga] or [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackinst.ttyWMT0/download config.slackinst.ttyWMT0] for the config file which was used.

===== Details of how initramfs_data.cpio.gz was prepared. =====

This method also require a small initramfs image prepared from the boot media available at [http://apc.io/library/ apc.io library]. Download it from here [http://sourceforge.net/projects/slackwareonapc8750/files/initramfs_data.cpio.gz/download initramfs_data.cpio.gz]&lt;br /&gt;or&lt;br /&gt;Use the following init scrip with a stripped down version of initrd.gz in [http://apc.io/media/apc/library/8750/apc-firmware-v1.0.2.zip apc-firmware-v1.0.2] from [http://apc.io/library/ apc.io library].

init:

&lt;pre&gt;#!/bin/busybox sh
/bin/busybox mount -t proc /proc
/bin/busybox mount -t sys /sys
/bin/busybox echo /sbin/mdev &amp;gt; /proc/sys/kernel/hotplug
/bin/busybox mdev -s
/bin/busybox --install
mkfs.ext2 /dev/ram0
mkdir /root
mount /dev/ram0 /root
cd /root
mkdir /flash
mount /dev/mmcblk0p1 /flash     
cpio -id &amp;lt; /flash/initrd-kirkwood.cpio
umount /flash
exec chroot /root /bin/busybox init
exec /bin/busybox init&lt;/pre&gt;
Commands to build initramfs_data.cpio.gz:

&lt;pre&gt;gunzip initrd.gz
mkdir initramfs_data
mount -o loop initrd initramfs_data
# create initramfs_data/init as shown above
sh build.sh init
chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &amp;gt; ../initramfs_data.cpio.gz )&lt;/pre&gt;
Copy [http://sourceforge.net/projects/slackwareonapc8750/files/initramfs_data.cpio.gz/download initramfs_data.cpio.gz] cpio archive to $KERNEL_SRC/usr area.

Please note that the kernel uses a CONFIG_CMDLINE= for VGA:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=440M console=tty0 mbtotal=52M&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
for serial:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=440M console=ttyWMT0,115200n8 mbtotal=52M&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
kernel is compiled on the host, using a cross compiler [http://www.elinux.org/ARMCompilers Sourcery CodeBench Lite 2014.05-28] for [http://www.arm.com/ arm]. For mkimage tool refer to [http://github.com/apc-io/apc-8750 Kernel and Bootloader] link at apc-io page at github.

===== kernel build procedure: =====

&lt;pre&gt;export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &amp;gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
       -e 0x8000 -n &amp;quot;My Linux&amp;quot; -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin&lt;/pre&gt;
===== Preparing the cpio archive: =====

&lt;pre&gt;wget -c http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img  
dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz  
gunzip initrd-kirkwood.cpio.gz  &lt;/pre&gt;
==== Procedure used for preparing the Slackware boot kernel. ====

Please refer to the link [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackboot.vga/download config.slackboot.vga] or [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackboot.ttyWMT0/download config.slackboot.ttyWMT0] for the config file which was used. Download and copy this file as .config in $OBJ area before starting the build

===== Kernel build procedure: =====

&lt;pre&gt;export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackboot.vga $OBJ/.config
rm $KERNEL_SRC/usr/initramfs_data.cpio.g

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &amp;gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
  -e 0x8000 -n &amp;quot;My Linux&amp;quot; -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin&lt;/pre&gt;
=== Additional info ===

From original boot messages on ttyS0:

&lt;pre&gt;Kernel command line: mem=460M root=/dev/mtdblock11 noinitrd rootfstype=yaffs2 rw console=ttyS0,115200n8 mbtotal=52M init=/init
Linux version 2.6.32.9-default (root@Ryan-VM-Ubuntu) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) ) #1 Wed Dec 5 19:29:52 CST 2012
CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387f
...
Memory: 460MB = 460MB total
Memory: 460288KB available (5188K code, 1069K data, 136K init, 0K highmem)
...
Creating 6 MTD partitions on &amp;quot;mtdsf device&amp;quot;:
0x000000000000-0x000000d00000 : &amp;quot;filesystem-SF&amp;quot;
0x000000d00000-0x000000f80000 : &amp;quot;kernel-SF&amp;quot;
0x000000f80000-0x000000fd0000 : &amp;quot;u-boot-SF&amp;quot;
0x000000fd0000-0x000000fe0000 : &amp;quot;u-boot env. cfg. 1-SF&amp;quot;
0x000000fe0000-0x000000ff0000 : &amp;quot;u-boot env. cfg. 2-SF&amp;quot;
0x000000ff0000-0x000001000000 : &amp;quot;w-load-SF&amp;quot;
wmt sf controller initial ok

...

NAND device: Manufacturer ID: 0xec, Chip ID: 0xd59476 (Samsung K9GAG08U0F)
Bad block at 16
Bad block at 17
Bad block at 89
Bad block at 613
Bad block at 880
Bad block at 1583
WMT_nand: uboot no dynamic partitions defined, use default static
Creating 11 MTD partitions on &amp;quot;WMT.nand&amp;quot;:
0x000000000000-0x000000100000 : &amp;quot;w-load-NAND&amp;quot;
0x000000100000-0x000000a00000 : &amp;quot;u-boot env. cfg. 1-NAND&amp;quot;
0x000000a00000-0x000001300000 : &amp;quot;u-boot-NAND&amp;quot;
0x000001300000-0x000001b00000 : &amp;quot;kernel-NAND&amp;quot;
0x000001b00000-0x000002100000 : &amp;quot;initrd-NAND&amp;quot;
0x000002100000-0x000012100000 : &amp;quot;filesystem-NAND&amp;quot;
0x000012100000-0x000012300000 : &amp;quot;u-boot-logo&amp;quot;
0x000012300000-0x000012700000 : &amp;quot;kernel-logo&amp;quot;
0x000012700000-0x000052700000 : &amp;quot;android-data&amp;quot;
0x000052700000-0x00005a700000 : &amp;quot;android-cache&amp;quot;
0x00005a700000-0x000080000000 : &amp;quot;LocalDisk&amp;quot;
nand initialised ok
...
VIA Networking Velocity Family Gigabit Ethernet Adapter Driver Ver. 1.14
...
eth0: VIA Networking Velocity Family Gigabit Ethernet Adapter
...
WMT_SOC: dai_name=i2s, codec_name=vt1603
WMT_SOC: single, wmt_i2s_rate=44100
...
VT1603 Audio Codec 0.10
wmt.audio.i2s = vt1603:f2:f2:f1:f1:100
...&lt;/pre&gt;</text>
    <sha1>2ad267fc298d79c035dbb51dd0bd1a241b368629</sha1>
  </revision>
  <revision>
    <id>916</id>
    <parentid>915</parentid>
    <timestamp>2014-08-07T08:22:11Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <comment>/* Additional info */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13300" xml:space="preserve">== Installing Slackware on APC-8750 ==

[[Image:http://apc.io/media/apc/img/apc-products-8750.jpg|APC 8750]]&lt;br /&gt;[http://apc.io/media/apc/img/apc-angle.jpg Another photograph of APC 8750]

[https://sourceforge.net/p/slackwareonapc8750 Project Area]

Mainline Linux kernel lacks support for [http://www.wondermedia.com.tw/en/products/platform/soc/wm8750/ Wondermedia WM 8750] currently. However [https://github.com/linux-wmt/linux-vtwm linux-vtwm-testing] kernel available at github has support for Wondermedia 8750 SOC. Since the kernel failed to load initrd cpio archive the normal way, a special method was used for loading the Slackware setup image. ( Installer Kernel booting from embedded initramfs image creates a filesystem on ramdisk, extracts Slackware setup initrd image and chroots to the filesystem on ramdisk ). Briefly, the steps followed in installing Slackware on APC 8750 are :

# '''Installing Slackware.'''
## Prepare boot media: Create three partitions, first bootable vfat, second reiserfs and third Linux swap.
## Copy installer boot files: Download and copy uzImage.bin and initrd-kirkwood.cpio to first vfat partition.
## Download and copy Slackware installation files over to second partition.
## Boot from the micro sd card prepared, install, and configure Slackware.
# '''Making new installtion bootable.'''
## Download and replace the installer kernel with new uzImage.bin for booting from second partition.
## Reboot.

=== Creating a bootable micro sd card for installation ===

For this you need a custom built kernel and a initramfs image from Slackware for arm distribution - [http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img uinitrd-kirkwood.img].

* [http://sourceforge.net/projects/slackwareonapc8750/files/install/vga/uzImage.bin/download uzImage.bin] for console on VGA monitor.&lt;br /&gt;If this kernel is chosen boot messages will appear on VGA monitor. or
* [http://sourceforge.net/projects/slackwareonapc8750/files/install/ttyWMT0/uzImage.bin/download uzImage.bin] for console on serial port.&lt;br /&gt;If this kernel is chosen boot messages will appear on the serial port.
* [http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio.gz] initramfs cpio archive.&lt;br /&gt;Download and gunzip this image file.
* Download [http://arm.slackware.com/getslack/ Slackware 14.1 for arm].&lt;br /&gt;If you prefer, you may download this to micro sd card directly, under slackware14.1 directory.

Download and keep these ready.

==== Preparing the micro sd card. ====

You need at least three partitions, one vfat, one or more Linux partitions, and a Linux swap partition for this method of installation. Here is how the partitions I used look like under fdisk ran on host.

&lt;pre&gt;
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap

&lt;/pre&gt;

==== Creating filesystems. ====

* 1st partition - make it bootable, and create a file system using mkfs.vfat
* 2nd partition - create a reiserfs file system using mkreiserfs ( or other tools for other types )

==== Copying Slackware install files onto second partition. ====

Create a slackware14.1 directory in the reiserfs partition of the micro sd card. Copy Slackware for arm distribution to the slackware14.1 directory, from http://arm.slackware.com/getslack/. Once the preparation is over,

&lt;pre&gt;sdc1: 
    /uzImage.bin  
    /initrd-kirkwood.cpio

sdc2:
    /slackware14.1/&lt;/pre&gt;
==== Booting with the installer and installing Slackware. ====

Now you are ready to boot from the new disk just prepared, and install Slackware from the pre mounted directory under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ). Put the newly prepared micro sd card in the slot and reboot APC-8750. Once you get the Slackware login prompt, proceed for installation as usual.

==== Configuration ====

For X Windows, use a lightweight window manager like Fluxbox.

=== Post installation preparation. ===

After the installation is done, you need to replace the kernel uzImage.bin with a new one, this time with no initramfs_data.cpio.gz, and CONFIG_CMDLINE= changed for booting from partition 2:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=460M root=/dev/mmcblk0p2 rootwait nonitrd ro console=tty0&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
For this, download one of

* [http://sourceforge.net/projects/slackwareonapc8750/files/boot/vga/uzImage.bin/download uzImage.bin] for console on VGA. Or
* [http://sourceforge.net/projects/slackwareonapc8750/files/boot/ttyWMT0/uzImage.bin/download uzImage.bin] for console on serial port.

and copy over to the first partition ( bootable vfat one ).

Once Slackware is installed, and the new uzImage.bin is copied over,

&lt;pre&gt;sdc1:
    /uzImage.bin
    /initrd-kirkwood.cpio  =&amp;gt; not required anymore

sdc2:
    /bin
    /boot
    /cdrom
    /dev/
    /etc/
    /home/
    /proc/
    /slackware14.1  =&amp;gt; not required anymore
    /usr/
    /var/&lt;/pre&gt;
You may remove files which are not required anymore, and free up some space. Once that is done, reboot APC-8750 to get Slackware up and running.

=== Information on building kernel and other images. ===

Please also refer to [http://sourceforge.net/projects/slackwareonapc8750/files/build.sh/download build.sh] script used to help the build procedure.

==== Detailed description of how Slackware install kernel was prepared. ====

===== Getting the Kernel source code. =====

I used [https://github.com/linux-wmt/linux-vtwm linux-vtwm-testing]. Zipfile you download from the site may cause problem when extracting on Linux. In my case couple of files were missing. One option is to use p7zip or other unzip program instead of the default zip utility in Slackware. You may also get a tar.gz file using:

&lt;pre&gt;wget --no-check-certificate \
    https://github.com/linux-wmt/linux-vtwm/archive/testing.tar.gz&lt;/pre&gt;
Please refer to the link [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackinst.vga/download config.slackinst.vga] or [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackinst.ttyWMT0/download config.slackinst.ttyWMT0] for the config file which was used.

===== Details of how initramfs_data.cpio.gz was prepared. =====

This method also require a small initramfs image prepared from the boot media available at [http://apc.io/library/ apc.io library]. Download it from here [http://sourceforge.net/projects/slackwareonapc8750/files/initramfs_data.cpio.gz/download initramfs_data.cpio.gz]&lt;br /&gt;or&lt;br /&gt;Use the following init scrip with a stripped down version of initrd.gz in [http://apc.io/media/apc/library/8750/apc-firmware-v1.0.2.zip apc-firmware-v1.0.2] from [http://apc.io/library/ apc.io library].

init:

&lt;pre&gt;#!/bin/busybox sh
/bin/busybox mount -t proc /proc
/bin/busybox mount -t sys /sys
/bin/busybox echo /sbin/mdev &amp;gt; /proc/sys/kernel/hotplug
/bin/busybox mdev -s
/bin/busybox --install
mkfs.ext2 /dev/ram0
mkdir /root
mount /dev/ram0 /root
cd /root
mkdir /flash
mount /dev/mmcblk0p1 /flash     
cpio -id &amp;lt; /flash/initrd-kirkwood.cpio
umount /flash
exec chroot /root /bin/busybox init
exec /bin/busybox init&lt;/pre&gt;
Commands to build initramfs_data.cpio.gz:

&lt;pre&gt;gunzip initrd.gz
mkdir initramfs_data
mount -o loop initrd initramfs_data
# create initramfs_data/init as shown above
sh build.sh init
chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &amp;gt; ../initramfs_data.cpio.gz )&lt;/pre&gt;
Copy [http://sourceforge.net/projects/slackwareonapc8750/files/initramfs_data.cpio.gz/download initramfs_data.cpio.gz] cpio archive to $KERNEL_SRC/usr area.

Please note that the kernel uses a CONFIG_CMDLINE= for VGA:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=440M console=tty0 mbtotal=52M&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
for serial:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=440M console=ttyWMT0,115200n8 mbtotal=52M&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
kernel is compiled on the host, using a cross compiler [http://www.elinux.org/ARMCompilers Sourcery CodeBench Lite 2014.05-28] for [http://www.arm.com/ arm]. For mkimage tool refer to [http://github.com/apc-io/apc-8750 Kernel and Bootloader] link at apc-io page at github.

===== kernel build procedure: =====

&lt;pre&gt;export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &amp;gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
       -e 0x8000 -n &amp;quot;My Linux&amp;quot; -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin&lt;/pre&gt;
===== Preparing the cpio archive: =====

&lt;pre&gt;wget -c http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img  
dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz  
gunzip initrd-kirkwood.cpio.gz  &lt;/pre&gt;
==== Procedure used for preparing the Slackware boot kernel. ====

Please refer to the link [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackboot.vga/download config.slackboot.vga] or [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackboot.ttyWMT0/download config.slackboot.ttyWMT0] for the config file which was used. Download and copy this file as .config in $OBJ area before starting the build

===== Kernel build procedure: =====

&lt;pre&gt;export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackboot.vga $OBJ/.config
rm $KERNEL_SRC/usr/initramfs_data.cpio.g

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &amp;gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
  -e 0x8000 -n &amp;quot;My Linux&amp;quot; -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin&lt;/pre&gt;
=== Additional info ===
From Slackware-14.1 boot messages:

&lt;pre&gt;Linux version 3.13.0-rc8 (ahoh@tampa) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-28) ) #23 Mon Aug 4 07 :40:48 IST 2014 
Kernel command line:  mem=460M root=/dev/mmcblk0p2 rootwait nonitrd ro console=tty0&lt;/pre&gt;

From original boot messages on ttyS0:

&lt;pre&gt;Linux version 2.6.32.9-default (root@Ryan-VM-Ubuntu) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) ) #1 Wed Dec 5 19:29:52 CST 2012
Kernel command line: mem=460M root=/dev/mtdblock11 noinitrd rootfstype=yaffs2 rw console=ttyS0,115200n8 mbtotal=52M init=/init
CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387f
...
Memory: 460MB = 460MB total
Memory: 460288KB available (5188K code, 1069K data, 136K init, 0K highmem)
...
Creating 6 MTD partitions on &amp;quot;mtdsf device&amp;quot;:
0x000000000000-0x000000d00000 : &amp;quot;filesystem-SF&amp;quot;
0x000000d00000-0x000000f80000 : &amp;quot;kernel-SF&amp;quot;
0x000000f80000-0x000000fd0000 : &amp;quot;u-boot-SF&amp;quot;
0x000000fd0000-0x000000fe0000 : &amp;quot;u-boot env. cfg. 1-SF&amp;quot;
0x000000fe0000-0x000000ff0000 : &amp;quot;u-boot env. cfg. 2-SF&amp;quot;
0x000000ff0000-0x000001000000 : &amp;quot;w-load-SF&amp;quot;
wmt sf controller initial ok

...

NAND device: Manufacturer ID: 0xec, Chip ID: 0xd59476 (Samsung K9GAG08U0F)
Bad block at 16
Bad block at 17
Bad block at 89
Bad block at 613
Bad block at 880
Bad block at 1583
WMT_nand: uboot no dynamic partitions defined, use default static
Creating 11 MTD partitions on &amp;quot;WMT.nand&amp;quot;:
0x000000000000-0x000000100000 : &amp;quot;w-load-NAND&amp;quot;
0x000000100000-0x000000a00000 : &amp;quot;u-boot env. cfg. 1-NAND&amp;quot;
0x000000a00000-0x000001300000 : &amp;quot;u-boot-NAND&amp;quot;
0x000001300000-0x000001b00000 : &amp;quot;kernel-NAND&amp;quot;
0x000001b00000-0x000002100000 : &amp;quot;initrd-NAND&amp;quot;
0x000002100000-0x000012100000 : &amp;quot;filesystem-NAND&amp;quot;
0x000012100000-0x000012300000 : &amp;quot;u-boot-logo&amp;quot;
0x000012300000-0x000012700000 : &amp;quot;kernel-logo&amp;quot;
0x000012700000-0x000052700000 : &amp;quot;android-data&amp;quot;
0x000052700000-0x00005a700000 : &amp;quot;android-cache&amp;quot;
0x00005a700000-0x000080000000 : &amp;quot;LocalDisk&amp;quot;
nand initialised ok
...
VIA Networking Velocity Family Gigabit Ethernet Adapter Driver Ver. 1.14
...
eth0: VIA Networking Velocity Family Gigabit Ethernet Adapter
...
WMT_SOC: dai_name=i2s, codec_name=vt1603
WMT_SOC: single, wmt_i2s_rate=44100
...
VT1603 Audio Codec 0.10
wmt.audio.i2s = vt1603:f2:f2:f1:f1:100
...&lt;/pre&gt;</text>
    <sha1>f03e47d8e10203227e1b8155c90bb8a9918c41af</sha1>
  </revision>
  <revision>
    <id>917</id>
    <parentid>916</parentid>
    <timestamp>2014-08-09T06:33:30Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <comment>/* Installing Slackware on APC-8750 */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13529" xml:space="preserve">== Installing Slackware on APC-8750 ==

[[Image:http://apc.io/media/apc/img/apc-products-8750.jpg|APC 8750]]&lt;br /&gt;[http://apc.io/media/apc/img/apc-angle.jpg Another photograph of APC 8750]

[https://sourceforge.net/p/slackwareonapc8750 Project Area]

[http://sourceforge.net/p/slackwareonapc8750/wiki/Home/ wiki @ sourceforge] Check this for latest updates
  
[http://sourceforge.net/p/slackwareonapc8750/code/ helper scripts] / [https://github.com/gv1/apc8750 helper scripts]  

Mainline Linux kernel lacks support for [http://www.wondermedia.com.tw/en/products/platform/soc/wm8750/ Wondermedia WM 8750] currently. However [https://github.com/linux-wmt/linux-vtwm linux-vtwm-testing] kernel available at github has support for Wondermedia 8750 SOC. Since the kernel failed to load initrd cpio archive the normal way, a special method was used for loading the Slackware setup image. ( Installer Kernel booting from embedded initramfs image creates a filesystem on ramdisk, extracts Slackware setup initrd image and chroots to the filesystem on ramdisk ). Briefly, the steps followed in installing Slackware on APC 8750 are :

# '''Installing Slackware.'''
## Prepare boot media: Create three partitions, first bootable vfat, second reiserfs and third Linux swap.
## Copy installer boot files: Download and copy uzImage.bin and initrd-kirkwood.cpio to first vfat partition.
## Download and copy Slackware installation files over to second partition.
## Boot from the micro sd card prepared, install, and configure Slackware.
# '''Making new installtion bootable.'''
## Download and replace the installer kernel with new uzImage.bin for booting from second partition.
## Reboot.

=== Creating a bootable micro sd card for installation ===

For this you need a custom built kernel and a initramfs image from Slackware for arm distribution - [http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img uinitrd-kirkwood.img].

* [http://sourceforge.net/projects/slackwareonapc8750/files/install/vga/uzImage.bin/download uzImage.bin] for console on VGA monitor.&lt;br /&gt;If this kernel is chosen boot messages will appear on VGA monitor. or
* [http://sourceforge.net/projects/slackwareonapc8750/files/install/ttyWMT0/uzImage.bin/download uzImage.bin] for console on serial port.&lt;br /&gt;If this kernel is chosen boot messages will appear on the serial port.
* [http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio.gz] initramfs cpio archive.&lt;br /&gt;Download and gunzip this image file.
* Download [http://arm.slackware.com/getslack/ Slackware 14.1 for arm].&lt;br /&gt;If you prefer, you may download this to micro sd card directly, under slackware14.1 directory.

Download and keep these ready.

==== Preparing the micro sd card. ====

You need at least three partitions, one vfat, one or more Linux partitions, and a Linux swap partition for this method of installation. Here is how the partitions I used look like under fdisk ran on host.

&lt;pre&gt;
Disk /dev/sdc: 15.9 GB, 15931539456 bytes
64 heads, 32 sectors/track, 15193 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *        2048      206847      102400    c  W95 FAT32 (LBA)
/dev/sdc2          206848    28878847    14336000   83  Linux
/dev/sdc3        28878848    31116287     1118720   82  Linux swap

&lt;/pre&gt;

==== Creating filesystems. ====

* 1st partition - make it bootable, and create a file system using mkfs.vfat
* 2nd partition - create a reiserfs file system using mkreiserfs ( or other tools for other types )

==== Copying Slackware install files onto second partition. ====

Create a slackware14.1 directory in the reiserfs partition of the micro sd card. Copy Slackware for arm distribution to the slackware14.1 directory, from http://arm.slackware.com/getslack/. Once the preparation is over,

&lt;pre&gt;sdc1: 
    /uzImage.bin  
    /initrd-kirkwood.cpio

sdc2:
    /slackware14.1/&lt;/pre&gt;
==== Booting with the installer and installing Slackware. ====

Now you are ready to boot from the new disk just prepared, and install Slackware from the pre mounted directory under /mnt/slackware14.1/slackware ( which is automounted as the selection for target is done ). Put the newly prepared micro sd card in the slot and reboot APC-8750. Once you get the Slackware login prompt, proceed for installation as usual.

==== Configuration ====

For X Windows, use a lightweight window manager like Fluxbox.

=== Post installation preparation. ===

After the installation is done, you need to replace the kernel uzImage.bin with a new one, this time with no initramfs_data.cpio.gz, and CONFIG_CMDLINE= changed for booting from partition 2:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=460M root=/dev/mmcblk0p2 rootwait nonitrd ro console=tty0&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
For this, download one of

* [http://sourceforge.net/projects/slackwareonapc8750/files/boot/vga/uzImage.bin/download uzImage.bin] for console on VGA. Or
* [http://sourceforge.net/projects/slackwareonapc8750/files/boot/ttyWMT0/uzImage.bin/download uzImage.bin] for console on serial port.

and copy over to the first partition ( bootable vfat one ).

Once Slackware is installed, and the new uzImage.bin is copied over,

&lt;pre&gt;sdc1:
    /uzImage.bin
    /initrd-kirkwood.cpio  =&amp;gt; not required anymore

sdc2:
    /bin
    /boot
    /cdrom
    /dev/
    /etc/
    /home/
    /proc/
    /slackware14.1  =&amp;gt; not required anymore
    /usr/
    /var/&lt;/pre&gt;
You may remove files which are not required anymore, and free up some space. Once that is done, reboot APC-8750 to get Slackware up and running.

=== Information on building kernel and other images. ===

Please also refer to [http://sourceforge.net/projects/slackwareonapc8750/files/build.sh/download build.sh] script used to help the build procedure.

==== Detailed description of how Slackware install kernel was prepared. ====

===== Getting the Kernel source code. =====

I used [https://github.com/linux-wmt/linux-vtwm linux-vtwm-testing]. Zipfile you download from the site may cause problem when extracting on Linux. In my case couple of files were missing. One option is to use p7zip or other unzip program instead of the default zip utility in Slackware. You may also get a tar.gz file using:

&lt;pre&gt;wget --no-check-certificate \
    https://github.com/linux-wmt/linux-vtwm/archive/testing.tar.gz&lt;/pre&gt;
Please refer to the link [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackinst.vga/download config.slackinst.vga] or [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackinst.ttyWMT0/download config.slackinst.ttyWMT0] for the config file which was used.

===== Details of how initramfs_data.cpio.gz was prepared. =====

This method also require a small initramfs image prepared from the boot media available at [http://apc.io/library/ apc.io library]. Download it from here [http://sourceforge.net/projects/slackwareonapc8750/files/initramfs_data.cpio.gz/download initramfs_data.cpio.gz]&lt;br /&gt;or&lt;br /&gt;Use the following init scrip with a stripped down version of initrd.gz in [http://apc.io/media/apc/library/8750/apc-firmware-v1.0.2.zip apc-firmware-v1.0.2] from [http://apc.io/library/ apc.io library].

init:

&lt;pre&gt;#!/bin/busybox sh
/bin/busybox mount -t proc /proc
/bin/busybox mount -t sys /sys
/bin/busybox echo /sbin/mdev &amp;gt; /proc/sys/kernel/hotplug
/bin/busybox mdev -s
/bin/busybox --install
mkfs.ext2 /dev/ram0
mkdir /root
mount /dev/ram0 /root
cd /root
mkdir /flash
mount /dev/mmcblk0p1 /flash     
cpio -id &amp;lt; /flash/initrd-kirkwood.cpio
umount /flash
exec chroot /root /bin/busybox init
exec /bin/busybox init&lt;/pre&gt;
Commands to build initramfs_data.cpio.gz:

&lt;pre&gt;gunzip initrd.gz
mkdir initramfs_data
mount -o loop initrd initramfs_data
# create initramfs_data/init as shown above
sh build.sh init
chmod a+x initramfs_data/init
sync
(cd initramfs_data ; find . | cpio -o -H newc | gzip  &amp;gt; ../initramfs_data.cpio.gz )&lt;/pre&gt;
Copy [http://sourceforge.net/projects/slackwareonapc8750/files/initramfs_data.cpio.gz/download initramfs_data.cpio.gz] cpio archive to $KERNEL_SRC/usr area.

Please note that the kernel uses a CONFIG_CMDLINE= for VGA:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=440M console=tty0 mbtotal=52M&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
for serial:

&lt;pre&gt;CONFIG_CMDLINE=&amp;quot; mem=440M console=ttyWMT0,115200n8 mbtotal=52M&amp;quot;
CONFIG_CMDLINE_FORCE=y&lt;/pre&gt;
kernel is compiled on the host, using a cross compiler [http://www.elinux.org/ARMCompilers Sourcery CodeBench Lite 2014.05-28] for [http://www.arm.com/ arm]. For mkimage tool refer to [http://github.com/apc-io/apc-8750 Kernel and Bootloader] link at apc-io page at github.

===== kernel build procedure: =====

&lt;pre&gt;export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackinst.vga $OBJ/.config
cp initramfs_data.cpio.gz $KERNEL_SRC/usr

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &amp;gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
       -e 0x8000 -n &amp;quot;My Linux&amp;quot; -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin&lt;/pre&gt;
===== Preparing the cpio archive: =====

&lt;pre&gt;wget -c http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.1/isolinux/uinitrd-kirkwood.img  
dd if=./uinitrd-kirkwood.img bs=64 skip=1 of=initrd-kirkwood.cpio.gz  
gunzip initrd-kirkwood.cpio.gz  &lt;/pre&gt;
==== Procedure used for preparing the Slackware boot kernel. ====

Please refer to the link [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackboot.vga/download config.slackboot.vga] or [http://sourceforge.net/projects/slackwareonapc8750/files/configs/config.slackboot.ttyWMT0/download config.slackboot.ttyWMT0] for the config file which was used. Download and copy this file as .config in $OBJ area before starting the build

===== Kernel build procedure: =====

&lt;pre&gt;export OBJ=/src/apc.io/obj.testing
export KERNEL_SRC=/src/apc.io/linux-vtwm-testing
export PATH=~/apc.io/apc-8750-master/u-boot/tools:$PATH
export PATH=/opt/local/arm/arm-2014.05/bin:$PATH
cp config.slackboot.vga $OBJ/.config
rm $KERNEL_SRC/usr/initramfs_data.cpio.g

make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- zImage -j 3
mv $OBJ/arch/arm/boot/zImage $1/$2/ ;
make -C $KERNEL_SRC O=$OBJ ARCH=arm CROSS_COMPILE=arm-none-eabi- dtbs
cat $1/$2/zImage $OBJ/arch/arm/boot/dts/wm8750-apc8750.dtb &amp;gt; $1/$2/zImage_w_dtb
mkimage -A arm -O linux -T kernel -C none -a 0x8000 \
  -e 0x8000 -n &amp;quot;My Linux&amp;quot; -d $1/$2/zImage_w_dtb $1/$2/uzImage.bin&lt;/pre&gt;
=== Additional info ===
From Slackware-14.1 boot messages:

&lt;pre&gt;Linux version 3.13.0-rc8 (ahoh@tampa) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-28) ) #23 Mon Aug 4 07 :40:48 IST 2014 
Kernel command line:  mem=460M root=/dev/mmcblk0p2 rootwait nonitrd ro console=tty0&lt;/pre&gt;

From original boot messages on ttyS0:

&lt;pre&gt;Linux version 2.6.32.9-default (root@Ryan-VM-Ubuntu) (gcc version 4.5.2 (Sourcery G++ Lite 2011.03-41) ) #1 Wed Dec 5 19:29:52 CST 2012
Kernel command line: mem=460M root=/dev/mtdblock11 noinitrd rootfstype=yaffs2 rw console=ttyS0,115200n8 mbtotal=52M init=/init
CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387f
...
Memory: 460MB = 460MB total
Memory: 460288KB available (5188K code, 1069K data, 136K init, 0K highmem)
...
Creating 6 MTD partitions on &amp;quot;mtdsf device&amp;quot;:
0x000000000000-0x000000d00000 : &amp;quot;filesystem-SF&amp;quot;
0x000000d00000-0x000000f80000 : &amp;quot;kernel-SF&amp;quot;
0x000000f80000-0x000000fd0000 : &amp;quot;u-boot-SF&amp;quot;
0x000000fd0000-0x000000fe0000 : &amp;quot;u-boot env. cfg. 1-SF&amp;quot;
0x000000fe0000-0x000000ff0000 : &amp;quot;u-boot env. cfg. 2-SF&amp;quot;
0x000000ff0000-0x000001000000 : &amp;quot;w-load-SF&amp;quot;
wmt sf controller initial ok

...

NAND device: Manufacturer ID: 0xec, Chip ID: 0xd59476 (Samsung K9GAG08U0F)
Bad block at 16
Bad block at 17
Bad block at 89
Bad block at 613
Bad block at 880
Bad block at 1583
WMT_nand: uboot no dynamic partitions defined, use default static
Creating 11 MTD partitions on &amp;quot;WMT.nand&amp;quot;:
0x000000000000-0x000000100000 : &amp;quot;w-load-NAND&amp;quot;
0x000000100000-0x000000a00000 : &amp;quot;u-boot env. cfg. 1-NAND&amp;quot;
0x000000a00000-0x000001300000 : &amp;quot;u-boot-NAND&amp;quot;
0x000001300000-0x000001b00000 : &amp;quot;kernel-NAND&amp;quot;
0x000001b00000-0x000002100000 : &amp;quot;initrd-NAND&amp;quot;
0x000002100000-0x000012100000 : &amp;quot;filesystem-NAND&amp;quot;
0x000012100000-0x000012300000 : &amp;quot;u-boot-logo&amp;quot;
0x000012300000-0x000012700000 : &amp;quot;kernel-logo&amp;quot;
0x000012700000-0x000052700000 : &amp;quot;android-data&amp;quot;
0x000052700000-0x00005a700000 : &amp;quot;android-cache&amp;quot;
0x00005a700000-0x000080000000 : &amp;quot;LocalDisk&amp;quot;
nand initialised ok
...
VIA Networking Velocity Family Gigabit Ethernet Adapter Driver Ver. 1.14
...
eth0: VIA Networking Velocity Family Gigabit Ethernet Adapter
...
WMT_SOC: dai_name=i2s, codec_name=vt1603
WMT_SOC: single, wmt_i2s_rate=44100
...
VT1603 Audio Codec 0.10
wmt.audio.i2s = vt1603:f2:f2:f1:f1:100
...&lt;/pre&gt;</text>
    <sha1>c0ee9556f332a82fc7e5fe5fd7a102e233fbd790</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>Linux-vserver</title>
  <ns>0</ns>
  <id>317</id>
  <revision>
    <id>918</id>
    <timestamp>2014-08-20T22:44:17Z</timestamp>
    <contributor>
      <username>Jlehtira</username>
      <id>358</id>
    </contributor>
    <comment>Linux-VServer info for Slackware. For now, the gotchas I ran into !</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1604" xml:space="preserve">[http://en.wikipedia.org/wiki/Linux-vserver Linux-VServer] is a virtual private server implementation that was created by adding operating system-level virtualization capabilities to the Linux kernel. 

=== Setting up a Linux-VServer host on Slackware ===

Linux-Vserver requires a patched kernel and specific utilities. Installation is outlined [http://linux-vserver.org/Installation_on_Linux_2.6 here]. The required steps for installing on Slackware are:

* Download a vanilla kernel source and a matching vserver patch [http://linux-vserver.org/Downloads#Kernel_Patches here]
* Unpack the kernel sources and apply the VServer patch. Copy .config file from Slackware's own kernel sources, just in case. Then use "make menuconfig" and check the [http://linux-vserver.org/Installation_on_Linux_2.6#Configuring_the_Kernel Linux VServer] settings, making sure to enable it.
* make &amp;&amp; make modules_install &amp;&amp; make install for easy kernel installation.
* Download and compile dietlibc. It is required, and Linux_Vserver will fail silently without it. It is available in [http://slackbuilds.org/repository/14.1/libraries/dietlibc/?search=dietlibc Slackbuilds.org] and easiest to install from there. The slackbuild puts it in /opt/diet .
* Download, compile and install [https://savannah.nongnu.org/projects/util-vserver/ util-vserver]. You should do "DIET=/opt/diet/bin/diet ./configure", otherwise the dietlibc isn't found.

=== Setting up a Slackware guest OS ===

Check up [http://notes.sagredo.eu/node/7 Roberto Puzzanghera's blog] for installation scripts.

'''To be continued'''


[[Category:Tutorials]]</text>
    <sha1>a43ae3a9885840d2de7e15a092086e6c897f54cc</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>User:AndDT</title>
  <ns>2</ns>
  <id>305</id>
  <revision>
    <id>919</id>
    <parentid>838</parentid>
    <timestamp>2014-08-24T13:48:18Z</timestamp>
    <contributor>
      <username>AndDT</username>
      <id>319</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="170" xml:space="preserve">Slackware user :) First met Slackware 20120328.

* Real Name: Andrew
* IRC Nickname: AndDT
* E-Mail: anddt@ukr.net
* My SlackBuilds: https://github.com/AndDT/SlackBuilds/</text>
    <sha1>ce02b12ef8c1607d860cbddb4419a9d2ba26b2a6</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>SlackwareOnMt6582Tablet</title>
  <ns>0</ns>
  <id>318</id>
  <revision>
    <id>920</id>
    <timestamp>2014-08-25T07:56:17Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <comment>Created page with " == specifications for the Tablet PC which was used here : ==  &lt;pre&gt; 	Processor : Arm Cortex A7, 1.3 GHz dual core. 		  : ARMv7 Processor rev 3 (v7l), 	Hardware  : MT8312 	SOC..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6144" xml:space="preserve">
== specifications for the Tablet PC which was used here : ==

&lt;pre&gt;
	Processor : Arm Cortex A7, 1.3 GHz dual core.
		  : ARMv7 Processor rev 3 (v7l),
	Hardware  : MT8312
	SOC       : mt6582.
	Memory    : 512MB RAM
	Storage   : 4GB Built in storage.
	Micro SD  : Slot for upto 32GB
	Display   : 7" WVGA 800x480
	OS        : Android 4.2 Jelly Bean
&lt;/pre&gt;
== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

&lt;pre&gt;
	mkfs.ext4 /dev/sdc1
	sync
	eject sdc
	eject -t sdc
	mkdir slack
	mount /dev/sdc1 slack
	cd slack
	mkdir sl
	cd sl
&lt;/pre&gt;

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 
&lt;pre&gt;
	(cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )
&lt;/pre&gt;

[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.
&lt;pre&gt;
	cpio -id &lt; initrd-kirkwood.cpio
	sync
	umount slack

Now that the sd card is ready for installation:

	eject sdc
&lt;/pre&gt;
	
and plug it into the device. Once that is done,

=== chroot to installer: ===

Now plug the card in tablet pc, boot, from host computer, 
&lt;pre&gt;
	adb shell
	su
	cd /data/local/tmp
	mkdir slackware
	mount /dev/block/mmcblk1p1 slackware
	cd slackware/sl
	export PATH=/data/local/tmp/bin:$PATH
	mountpoint proc || mount -t proc none proc/
	mountpoint sys || mount -t sysfs sys sys/
	mountpoint dev || mount -o bind  /dev dev/
	export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	pushd /dev
	ln -s /dev/block/mmc1blk* .
	popd
	chroot . /bin/bash
	mount -t ext4 /dev/mmcblk1p1 mnt
&lt;/pre&gt;

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware/slackware

&lt;pre&gt; 
	setup
	
		Proceed and select /dev/mmcblk1p1 as target, no format
		For source, select pre mounted directory option, /slackware/slackware
&lt;/pre&gt;	
=== Complete installation, and configure. Once the installation is done, ===
&lt;pre&gt;
	umount proc
	umount sys
	umount dev
	sync
	cd ../..
	umount slackware
&lt;/pre&gt;
== Getting into installed Slackware: ==
&lt;pre&gt;
	mount /dev/block/mmcblk1p1 slackware
	cd slackware
	mountpoint proc || mount -t proc none proc/
        mountpoint sys || mount -t sysfs sys sys/
        mountpoint dev || mount -o bind  /dev dev/
        export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	chroot . /bin/bash
&lt;/pre&gt;
From here you can do normal Slackware activities.
	
	
== Testing the framebuffer	==		

Stop android "Surfaceflinger":

make sure the display is on ( not blank ) and issue:
&lt;pre&gt;
	adb shell
	su
	stop
&lt;/pre&gt;
Now the display goes blank, still with backlight on.


Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet.

from Slackware shell:

&lt;pre&gt;
   gcc fbtest.c
   ./a.out
&lt;/pre&gt;
once done, go back to android su shell from adb, and:
&lt;pre&gt;
	start
&lt;/pre&gt;	
After few seconds android display will be back on. 

== Getting mali driver for Xorg ==

All these compilations are done under the chrooted slackware environment on the Tablet PC, using gcc
&lt;pre&gt;
	gcc version 4.8.2 (GCC) ( arm-slackware-linux-gnueabi-gcc )
&lt;/pre&gt;
[http://malideveloper.arm.com/downloads/drivers/DX910 Open Source Mali-200/300/400/450 GPU Kernel Dev]
[http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-linux-exadri2-and-x11-display-drivers/ Open Source Mali GPUs Linux EXA/DRI2 and X11 Display Drivers]

Get [http://malideveloper.arm.com/downloads/drivers/DX910/r4p1-01rel0/DX910-SW-99003-r4p1-01rel0.tgz DX910-SW-99003-r4p1-01rel0] or choose another version

Once downloaded:
&lt;pre&gt;
	tar xf DX910-SW-99003-r4p1-01rel0.tgz
	cd DX910-SW-99003-r4p1-01rel0/x11/xf86-video-mali-0.0.1
	./autogen.sh
	in src/Makefile:
	# mali_drv_la_LDFLAGS = -module -avoid-version -L$(MALI_DDK)/lib -lMali -lUMP -lpthread
	for now.
	mali_drv_la_LDFLAGS = -module -avoid-version -L$(MALI_DDK)/lib -lUMP -lpthread
&lt;/pre&gt;
	also get [http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-ump-user-space-drivers-source-code-2 ] [http://malideveloper.arm.com/downloads/drivers/DX910/r4p1-01rel0/DX910-SW-99006-r4p1-01rel0.tgz].

&lt;pre&gt;
	make/install
&lt;/pre&gt;

Once make/install is done for both,
&lt;pre&gt;
	cp src/.libs/mali_drv.* /usr/lib/xorg/modules/drivers/
	ldconfig
&lt;/pre&gt;

And do startx ( fails with following error ).

&lt;pre&gt;
[  9131.458] (II) LoadModule: "mali"
[  9131.461] (II) Loading /usr/lib/xorg/modules/drivers/mali_drv.so
[  9131.461] (II) Module mali: vendor="X.Org Foundation"
[  9131.462]    compiled for 1.14.3, module version = 0.4.2
[  9131.462]    ABI class: X.Org Video Driver, version 14.1
[  9131.462] (II) MALI: driver for Mali Framebuffer: mali
[  9131.462] (EE)
Fatal server error:
[  9131.462] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or direct
ory)
[  9131.463] (EE)
[  9131.463] (EE)
&lt;/pre&gt;
No further tests until I get to unlock bootloader or get a X server which requires no ttys!</text>
    <sha1>9cebc7bbf0b2faa9bd2671852a72eadda4f1e0ba</sha1>
  </revision>
  <revision>
    <id>921</id>
    <parentid>920</parentid>
    <timestamp>2014-08-25T11:29:50Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6898" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==

&lt;pre&gt;
	Processor : Arm Cortex A7, 1.3 GHz dual core.
		  : ARMv7 Processor rev 3 (v7l),
	Hardware  : MT8312
	SOC       : mt6582.
	Memory    : 512MB RAM
	Storage   : 4GB Built in storage.
	Micro SD  : Slot for upto 32GB
	Display   : 7" WVGA 800x480
	OS        : Android 4.2 Jelly Bean
        GPU       : Mali?
&lt;/pre&gt;

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

&lt;pre&gt;
	mkfs.ext4 /dev/sdc1
	sync
	eject sdc
	eject -t sdc
	mkdir slack
	mount /dev/sdc1 slack
	cd slack
	mkdir sl
	cd sl
&lt;/pre&gt;

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 
&lt;pre&gt;
        mkdir slackware14.1
        cd slackware14.1
	(cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )

&lt;/pre&gt;

[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.
&lt;pre&gt;
	cpio -id &lt; initrd-kirkwood.cpio
	sync
	umount slack

Now that the sd card is ready for installation:

	eject sdc
&lt;/pre&gt;
	
and plug it into the device. Once that is done,

=== chroot to installer: ===

Now plug the card in tablet pc, boot, from host computer, 
&lt;pre&gt;
	adb shell
	su
	cd /data/local/tmp
	mkdir slackware
	mount /dev/block/mmcblk1p1 slackware
	cd slackware/sl
	export PATH=/data/local/tmp/bin:$PATH
	mountpoint proc || mount -t proc none proc/
	mountpoint sys || mount -t sysfs sys sys/
	mountpoint dev || mount -o bind  /dev dev/
	export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	pushd /dev
	ln -s /dev/block/mmc1blk* .
	popd
	chroot . /bin/bash
	mount -t ext4 /dev/mmcblk1p1 mnt
&lt;/pre&gt;

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

&lt;pre&gt; 
	setup
	
		Proceed and select /dev/mmcblk1p1 as target, no format
		For source, select pre mounted directory option, /slackware14.1/slackware
&lt;/pre&gt;	

=== Complete installation, and configuration ===

Once the complete installation is done,

&lt;pre&gt;
	umount proc
	umount sys
	umount dev
	sync
	cd ../..
	umount slackware
&lt;/pre&gt;

== Getting into installed Slackware: ==

&lt;pre&gt;
	mount /dev/block/mmcblk1p1 slackware
	cd slackware
	mountpoint proc || mount -t proc none proc/
        mountpoint sys || mount -t sysfs sys sys/
        mountpoint dev || mount -o bind  /dev dev/
        export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	chroot . /bin/bash
&lt;/pre&gt;

From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		
== Testing the framebuffer ==		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.
Please not Slackware shell is also running as user root.

&lt;pre&gt;
	adb shell
	su
	stop
&lt;/pre&gt;

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

&lt;pre&gt;
   gcc fbtest.c
   ./a.out
&lt;/pre&gt;

once done, go back to android su shell from adb, and:

&lt;pre&gt;
	start
&lt;/pre&gt;	

After few seconds android display will be back on. 

== Failed test of running an Xorg session ==

=== Getting Mali driver for Xorg ===

All these compilations are done under the chrooted Slackware environment on the Tablet PC, using gcc

&lt;pre&gt;
	gcc version 4.8.2 (GCC) ( arm-slackware-linux-gnueabi-gcc )
&lt;/pre&gt;

[http://malideveloper.arm.com/downloads/drivers/DX910 Open Source Mali-200/300/400/450 GPU Kernel Dev]
[http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-linux-exadri2-and-x11-display-drivers/ Open Source Mali GPUs Linux EXA/DRI2 and X11 Display Drivers]

Get [http://malideveloper.arm.com/downloads/drivers/DX910/r4p1-01rel0/DX910-SW-99003-r4p1-01rel0.tgz DX910-SW-99003-r4p1-01rel0] or choose another version

Once downloaded, and adb pushed to tablet:

&lt;pre&gt;
	tar xf DX910-SW-99003-r4p1-01rel0.tgz
	cd DX910-SW-99003-r4p1-01rel0/x11/xf86-video-mali-0.0.1
	./autogen.sh
	in src/Makefile:
	# mali_drv_la_LDFLAGS = -module -avoid-version -L$(MALI_DDK)/lib -lMali -lUMP -lpthread
	for now.
	mali_drv_la_LDFLAGS = -module -avoid-version -L$(MALI_DDK)/lib -lUMP -lpthread
&lt;/pre&gt;

	also get [http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-ump-user-space-drivers-source-code-2 ump]

&lt;pre&gt;
	make and install
&lt;/pre&gt;

Once make/install is done for both,
&lt;pre&gt;
	cp src/.libs/mali_drv.* /usr/lib/xorg/modules/drivers/
	ldconfig
&lt;/pre&gt;

=== Run Xorg ===

And run startx, which fails with the following error.

&lt;pre&gt;
[  9131.458] (II) LoadModule: "mali"
[  9131.461] (II) Loading /usr/lib/xorg/modules/drivers/mali_drv.so
[  9131.461] (II) Module mali: vendor="X.Org Foundation"
[  9131.462]    compiled for 1.14.3, module version = 0.4.2
[  9131.462]    ABI class: X.Org Video Driver, version 14.1
[  9131.462] (II) MALI: driver for Mali Framebuffer: mali
[  9131.462] (EE)
Fatal server error:
[  9131.462] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or direct
ory)
[  9131.463] (EE)
[  9131.463] (EE)
&lt;/pre&gt;

No further tests until I get to unlock bootloader or get a X server which requires no ttys!</text>
    <sha1>63d8f96ec4388192e2c86c30f63c79c2ac405a15</sha1>
  </revision>
  <revision>
    <id>922</id>
    <parentid>921</parentid>
    <timestamp>2014-09-03T07:36:56Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11013" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==

&lt;pre&gt;
	Processor : Arm Cortex A7, 1.3 GHz dual core.
		  : ARMv7 Processor rev 3 (v7l),
	Hardware  : MT8312
	SOC       : mt6582.
	Memory    : 512MB RAM
	Storage   : 4GB Built in storage.
	Micro SD  : Slot for upto 32GB
	Display   : 7" WVGA 800x480
	OS        : Android 4.2 Jelly Bean
        GPU       : Mali?
&lt;/pre&gt;

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

&lt;pre&gt;
	mkfs.ext4 /dev/sdc1
	sync
	eject sdc
	eject -t sdc
	mkdir slack
	mount /dev/sdc1 slack
	cd slack
	mkdir sl
	cd sl
&lt;/pre&gt;

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 
&lt;pre&gt;
        mkdir slackware14.1
        cd slackware14.1
	(cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )

&lt;/pre&gt;

[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.
&lt;pre&gt;
	cpio -id &lt; initrd-kirkwood.cpio
	sync
	umount slack

Now that the sd card is ready for installation:

	eject sdc
&lt;/pre&gt;
	
and plug it into the device. Once that is done,

=== chroot to installer: ===

Now plug the card in tablet pc, boot, from host computer, 
&lt;pre&gt;
	adb shell
	su
	cd /data/local/tmp
	mkdir slackware
	mount /dev/block/mmcblk1p1 slackware
	cd slackware/sl
	export PATH=/data/local/tmp/bin:$PATH
	mountpoint proc || mount -t proc none proc/
	mountpoint sys || mount -t sysfs sys sys/
	mountpoint dev || mount -o bind  /dev dev/
	export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	pushd /dev
	ln -s /dev/block/mmc1blk* .
	popd
	chroot . /bin/bash
	mount -t ext4 /dev/mmcblk1p1 mnt
&lt;/pre&gt;

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

&lt;pre&gt; 
	setup
	
		Proceed and select /dev/mmcblk1p1 as target, no format
		For source, select pre mounted directory option, /slackware14.1/slackware
&lt;/pre&gt;	

=== Complete installation, and configuration ===

Once the complete installation is done,

&lt;pre&gt;
	umount proc
	umount sys
	umount dev
	sync
	cd ../..
	umount slackware
&lt;/pre&gt;

== Getting into installed Slackware: ==

&lt;pre&gt;
	mount /dev/block/mmcblk1p1 slackware
	cd slackware
	mountpoint proc || mount -t proc none proc/
        mountpoint sys || mount -t sysfs sys sys/
        mountpoint dev || mount -o bind  /dev dev/
        export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	chroot . /bin/bash
&lt;/pre&gt;

From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		
== Testing the framebuffer ==		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.
Please not Slackware shell is also running as user root.

&lt;pre&gt;
	adb shell
	su
	stop
&lt;/pre&gt;

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

&lt;pre&gt;
   gcc fbtest.c
   ./a.out
&lt;/pre&gt;

once done, go back to android su shell from adb, and:

&lt;pre&gt;
	start
&lt;/pre&gt;	

After few seconds android display will be back on. 

== Failed test of running an Xorg session ==

=== Getting Mali driver for Xorg ===

All these compilations are done under the chrooted Slackware environment on the Tablet PC, using gcc

&lt;pre&gt;
	gcc version 4.8.2 (GCC) ( arm-slackware-linux-gnueabi-gcc )
&lt;/pre&gt;

[http://malideveloper.arm.com/downloads/drivers/DX910 Open Source Mali-200/300/400/450 GPU Kernel Dev]
[http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-linux-exadri2-and-x11-display-drivers/ Open Source Mali GPUs Linux EXA/DRI2 and X11 Display Drivers]

Get [http://malideveloper.arm.com/downloads/drivers/DX910/r4p1-01rel0/DX910-SW-99003-r4p1-01rel0.tgz DX910-SW-99003-r4p1-01rel0] or choose another version

Once downloaded, and adb pushed to tablet:

&lt;pre&gt;
	tar xf DX910-SW-99003-r4p1-01rel0.tgz
	cd DX910-SW-99003-r4p1-01rel0/x11/xf86-video-mali-0.0.1
	./autogen.sh
	in src/Makefile:
	# mali_drv_la_LDFLAGS = -module -avoid-version -L$(MALI_DDK)/lib -lMali -lUMP -lpthread
	for now.
	mali_drv_la_LDFLAGS = -module -avoid-version -L$(MALI_DDK)/lib -lUMP -lpthread
&lt;/pre&gt;

	also get [http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-ump-user-space-drivers-source-code-2 ump]

&lt;pre&gt;
	make and install
&lt;/pre&gt;

Once make/install is done for both,
&lt;pre&gt;
	cp src/.libs/mali_drv.* /usr/lib/xorg/modules/drivers/
	ldconfig
&lt;/pre&gt;

=== Run Xorg ===

And run startx, which fails with the following error.

&lt;pre&gt;
[  9131.458] (II) LoadModule: "mali"
[  9131.461] (II) Loading /usr/lib/xorg/modules/drivers/mali_drv.so
[  9131.461] (II) Module mali: vendor="X.Org Foundation"
[  9131.462]    compiled for 1.14.3, module version = 0.4.2
[  9131.462]    ABI class: X.Org Video Driver, version 14.1
[  9131.462] (II) MALI: driver for Mali Framebuffer: mali
[  9131.462] (EE)
Fatal server error:
[  9131.462] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or direct
ory)
[  9131.463] (EE)
[  9131.463] (EE)
&lt;/pre&gt;


== Compiling and getting Xfbdev running! - Partially ==

Finally I found that the X VT requirement can be removed. 
In the first test, No keyboard and mouse, but startx opens a nice fluxbox window.
I can set DISPLAY=:0, and run xterm and other applications from adb shell onto the
X windows running on LCD. Here is what I did:

Procedure:

Get xorg-server-1.12.2 and required files from : http://xorg.freedesktop.org/archive
/X11R7.7/

Apply patch to hw/kdrive/linux/linux.c ( basically make most of the functions just e
mpty, so that no tty open etc are done - first step to test :-) ) refer to the patch 
at the end.

configure:
&lt;pre&gt;
export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
export PKG_CONFIG_PATH=/usr/lib/pkgconfig:$PKG_CONFIG_PATH
export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
export PATH=/opt/local/sw/bin:$PATH
# autoreconf --force -v --install || exit 1
./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --enabl
e-config-udev --disable-aiglx --disable-glx --disable-dri --disable-dri2 --disab
le-libdrm --disable-record --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xk
b-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-
xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --di
sable-xorg --enable-xnest --disable-dmx --disable-xquartz --disable-xwin --disab
le-xephyr --disable-config-udev

make -j 3
make install

Also install

xkeyboard-config-2.11
cd  /opt/local/sw/share/X11/xkb/rules/
ln -s base /opt/local/sw/share/X11/xkb/rules/base xorg
If this is not done, you will get:
        XKB: Failed to compile keymap


Once installed, run:
        startx -- ./Xfbdev -fb /dev/graphics/fb0
&lt;/pre&gt;

See the frame grab with scrot

x.png
x2.png


=== /hw/kdrive/linux/linux.c patch: ===

&lt;pre&gt;

--- linux.c     2014-09-03 08:29:11.000000000 +0530
+++ linux.c.org 2012-05-17 22:39:03.000000000 +0530
@@ -65,7 +65,6 @@
 static void
 LinuxCheckChown(char *file)
 {
-#ifdef GV
     struct stat st;
     __uid_t u;
     __gid_t g;
@@ -76,13 +75,11 @@
     g = getgid();
     if (st.st_uid != u || st.st_gid != g)
         chown(file, u, g);
-#endif
 }

 static int
 LinuxInit(void)
 {
-#ifdef GV
     int fd = -1;
     char vtname[11];
     struct vt_stat vts;
@@ -130,14 +127,13 @@
     if (ioctl(LinuxConsoleFd, VT_GETSTATE, &amp;vts) == 0) {
         activeVT = vts.v_active;
     }
-#endif
+
     return 1;
 }

 static void
 LinuxSetSwitchMode(int mode)
 {
-#ifdef GV
     struct sigaction act;
     struct vt_mode VT;

@@ -168,7 +164,6 @@
     if (ioctl(LinuxConsoleFd, VT_SETMODE, &amp;VT) &lt; 0) {
         FatalError("LinuxInit: VT_SETMODE failed\n");
     }
-#endif
 }

 static void
@@ -181,7 +176,6 @@
 static void
 LinuxApmWakeup(pointer blockData, int result, pointer pReadmask)
 {
-#ifdef GV
     fd_set *readmask = (fd_set *) pReadmask;

     if (result &gt; 0 &amp;&amp; LinuxApmFd &gt;= 0 &amp;&amp; FD_ISSET(LinuxApmFd, readmask)) {
@@ -219,7 +213,6 @@
             ioctl(LinuxApmFd, cmd, 0);
         }
     }
-#endif
 }

 #ifdef FNONBLOCK
@@ -231,7 +224,6 @@
 static void
 LinuxEnable(void)
 {
-#ifdef GV
     if (enabled)
         return;
     if (kdSwitchPending) {
@@ -265,14 +257,12 @@
     if (ioctl(LinuxConsoleFd, KDSETMODE, KD_GRAPHICS) &lt; 0) {
         FatalError("LinuxInit: KDSETMODE KD_GRAPHICS failed\n");
     }
-#endif
     enabled = TRUE;
 }
 static void
 LinuxDisable(void)
 {
-#ifdef GV
     ioctl(LinuxConsoleFd, KDSETMODE, KD_TEXT);  /* Back to text mode ... */
     if (kdSwitchPending) {
         kdSwitchPending = FALSE;
@@ -285,13 +275,11 @@
         close(LinuxApmFd);
         LinuxApmFd = -1;
     }
-#endif
 }

 static void
 LinuxFini(void)
 {
-#ifdef GV
     struct vt_mode VT;
     struct vt_stat vts;
     int fd;
@@ -339,7 +327,6 @@
         close(fd);
     }
     return;
-#endif
 }

 void
@@ -365,11 +352,9 @@
 static void
 LinuxBell(int volume, int pitch, int duration)
 {
-#ifdef GV
     if (volume &amp;&amp; pitch)
         ioctl(LinuxConsoleFd, KDMKTONE, ((1193190 / pitch) &amp; 0xffff) |
               (((unsigned long) duration * volume / 50) &lt;&lt; 16));
-#endif
 }

 KdOsFuncs LinuxFuncs = {
&lt;/pre&gt;</text>
    <sha1>5ef905964f09251920225f3a10c980b805e39542</sha1>
  </revision>
  <revision>
    <id>923</id>
    <parentid>922</parentid>
    <timestamp>2014-09-03T12:36:44Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="11450" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==

&lt;pre&gt;
	Processor : Arm Cortex A7, 1.3 GHz dual core.
		  : ARMv7 Processor rev 3 (v7l),
	Hardware  : MT8312
	SOC       : mt6582.
	Memory    : 512MB RAM
	Storage   : 4GB Built in storage.
	Micro SD  : Slot for upto 32GB
	Display   : 7" WVGA 800x480
	OS        : Android 4.2 Jelly Bean
        GPU       : Mali?
&lt;/pre&gt;

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

&lt;pre&gt;
	mkfs.ext4 /dev/sdc1
	sync
	eject sdc
	eject -t sdc
	mkdir slack
	mount /dev/sdc1 slack
	cd slack
	mkdir sl
	cd sl
&lt;/pre&gt;

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 
&lt;pre&gt;
        mkdir slackware14.1
        cd slackware14.1
	(cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )

&lt;/pre&gt;

[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.
&lt;pre&gt;
	cpio -id &lt; initrd-kirkwood.cpio
	sync
	umount slack

Now that the sd card is ready for installation:

	eject sdc
&lt;/pre&gt;
	
and plug it into the device. Once that is done,

=== chroot to installer: ===

Now plug the card in tablet pc, boot, from host computer, 
&lt;pre&gt;
	adb shell
	su
	cd /data/local/tmp
	mkdir slackware
	mount /dev/block/mmcblk1p1 slackware
	cd slackware/sl
	export PATH=/data/local/tmp/bin:$PATH
	mountpoint proc || mount -t proc none proc/
	mountpoint sys || mount -t sysfs sys sys/
	mountpoint dev || mount -o bind  /dev dev/
	export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	pushd /dev
	ln -s /dev/block/mmc1blk* .
	popd
	chroot . /bin/bash
	mount -t ext4 /dev/mmcblk1p1 mnt
&lt;/pre&gt;

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

&lt;pre&gt; 
	setup
	
		Proceed and select /dev/mmcblk1p1 as target, no format
		For source, select pre mounted directory option, /slackware14.1/slackware
&lt;/pre&gt;	

=== Complete installation, and configuration ===

Once the complete installation is done,

&lt;pre&gt;
	umount proc
	umount sys
	umount dev
	sync
	cd ../..
	umount slackware
&lt;/pre&gt;

== Getting into installed Slackware: ==

&lt;pre&gt;
	mount /dev/block/mmcblk1p1 slackware
	cd slackware
	mountpoint proc || mount -t proc none proc/
        mountpoint sys || mount -t sysfs sys sys/
        mountpoint dev || mount -o bind  /dev dev/
        export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	chroot . /bin/bash
&lt;/pre&gt;

From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		
== Testing the framebuffer ==		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.
Please not Slackware shell is also running as user root.

&lt;pre&gt;
	adb shell
	su
	stop
&lt;/pre&gt;

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

&lt;pre&gt;
   gcc fbtest.c
   ./a.out
&lt;/pre&gt;

once done, go back to android su shell from adb, and:

&lt;pre&gt;
	start
&lt;/pre&gt;	

After few seconds android display will be back on. 

== Failed test of running an Xorg session ==

=== Getting Mali driver for Xorg ===

All these compilations are done under the chrooted Slackware environment on the Tablet PC, using gcc

&lt;pre&gt;
	gcc version 4.8.2 (GCC) ( arm-slackware-linux-gnueabi-gcc )
&lt;/pre&gt;

[http://malideveloper.arm.com/downloads/drivers/DX910 Open Source Mali-200/300/400/450 GPU Kernel Dev]
[http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-linux-exadri2-and-x11-display-drivers/ Open Source Mali GPUs Linux EXA/DRI2 and X11 Display Drivers]

Get [http://malideveloper.arm.com/downloads/drivers/DX910/r4p1-01rel0/DX910-SW-99003-r4p1-01rel0.tgz DX910-SW-99003-r4p1-01rel0] or choose another version

Once downloaded, and adb pushed to tablet:

&lt;pre&gt;
	tar xf DX910-SW-99003-r4p1-01rel0.tgz
	cd DX910-SW-99003-r4p1-01rel0/x11/xf86-video-mali-0.0.1
	./autogen.sh
	in src/Makefile:
	# mali_drv_la_LDFLAGS = -module -avoid-version -L$(MALI_DDK)/lib -lMali -lUMP -lpthread
	for now.
	mali_drv_la_LDFLAGS = -module -avoid-version -L$(MALI_DDK)/lib -lUMP -lpthread
&lt;/pre&gt;

	also get [http://malideveloper.arm.com/develop-for-mali/drivers/open-source-mali-gpus-ump-user-space-drivers-source-code-2 ump]

&lt;pre&gt;
	make and install
&lt;/pre&gt;

Once make/install is done for both,
&lt;pre&gt;
	cp src/.libs/mali_drv.* /usr/lib/xorg/modules/drivers/
	ldconfig
&lt;/pre&gt;

=== Run Xorg ===

And run startx, which fails with the following error.

&lt;pre&gt;
[  9131.458] (II) LoadModule: "mali"
[  9131.461] (II) Loading /usr/lib/xorg/modules/drivers/mali_drv.so
[  9131.461] (II) Module mali: vendor="X.Org Foundation"
[  9131.462]    compiled for 1.14.3, module version = 0.4.2
[  9131.462]    ABI class: X.Org Video Driver, version 14.1
[  9131.462] (II) MALI: driver for Mali Framebuffer: mali
[  9131.462] (EE)
Fatal server error:
[  9131.462] (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or direct
ory)
[  9131.463] (EE)
[  9131.463] (EE)
&lt;/pre&gt;


== Compiling and getting Xfbdev running! - Partially ==

Finally I found that the X VT requirement can be removed. 
In the first test, No keyboard and mouse, but startx opens a nice fluxbox window.
I can set DISPLAY=:0, and run xterm and other applications from adb shell onto the
X windows running on LCD. Here is what I did:

Procedure:

Get xorg-server-1.12.2 and required files from : 
http://xorg.freedesktop.org/archive/X11R7.7/

Apply patch to hw/kdrive/linux/linux.c ( As first step, basically make most of the functions 
just empty, so that no tty open etc are done.) Refer to the patch at the end.

configure:

&lt;pre&gt;
export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
export PKG_CONFIG_PATH=/usr/lib/pkgconfig:$PKG_CONFIG_PATH
export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
export PATH=/opt/local/sw/bin:$PATH

# autoreconf --force -v --install || exit 1

./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --disab
le-aiglx --disable-glx --disable-dri --disable-dri2 --disable-libdrm --disable-r
ecord --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb
 --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with
-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xorg --enable-x
nest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --enable-co
nfig-udev --enable-tslib LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/incl
ude

make -j 3
make install
&lt;/pre&gt;

Also install xkeyboard-config-2.11.


Once it is installed:

&lt;pre&gt;
cd  /opt/local/sw/share/X11/xkb/rules/
ln -s base /opt/local/sw/share/X11/xkb/rules/base xorg
If this is not done, you will get error:
        XKB: Failed to compile keymap
&lt;/pre&gt;

Once installed, run X:

&lt;pre&gt;
Makesure the display is on.
Stop Surfaceflinger from adb shell ( as root ):
        stop

If "stop" step is not done, X will show up, but as soon as the screen is touched,
it will disappear.

From Slackware shell ( as root ), run:
        startx -- /opt/local/sw/bin/Xfbdev -fb /dev/graphics/fb0
 
Once done, restart Surfaceflinger from adb shell ( as root ):
        start
&lt;/pre&gt;

See the frame grab with scrot

x.png
x2.png


=== /hw/kdrive/linux/linux.c patch: ===

&lt;pre&gt;

--- linux.c.org	2012-05-17 22:39:03.000000000 +0530
+++ linux.c	2014-09-03 08:29:11.000000000 +0530
@@ -65,6 +65,7 @@
 static void
 LinuxCheckChown(char *file)
 {
+#ifdef GV
     struct stat st;
     __uid_t u;
     __gid_t g;
@@ -75,11 +76,13 @@
     g = getgid();
     if (st.st_uid != u || st.st_gid != g)
         chown(file, u, g);
+#endif
 }
 
 static int
 LinuxInit(void)
 {
+#ifdef GV
     int fd = -1;
     char vtname[11];
     struct vt_stat vts;
@@ -127,13 +130,14 @@
     if (ioctl(LinuxConsoleFd, VT_GETSTATE, &amp;vts) == 0) {
         activeVT = vts.v_active;
     }
-
+#endif
     return 1;
 }
 
 static void
 LinuxSetSwitchMode(int mode)
 {
+#ifdef GV
     struct sigaction act;
     struct vt_mode VT;
 
@@ -164,6 +168,7 @@
     if (ioctl(LinuxConsoleFd, VT_SETMODE, &amp;VT) &lt; 0) {
         FatalError("LinuxInit: VT_SETMODE failed\n");
     }
+#endif
 }
 
 static void
@@ -176,6 +181,7 @@
 static void
 LinuxApmWakeup(pointer blockData, int result, pointer pReadmask)
 {
+#ifdef GV
     fd_set *readmask = (fd_set *) pReadmask;
 
     if (result &gt; 0 &amp;&amp; LinuxApmFd &gt;= 0 &amp;&amp; FD_ISSET(LinuxApmFd, readmask)) {
@@ -213,6 +219,7 @@
             ioctl(LinuxApmFd, cmd, 0);
         }
     }
+#endif
 }
 
 #ifdef FNONBLOCK
@@ -224,6 +231,7 @@
 static void
 LinuxEnable(void)
 {
+#ifdef GV
     if (enabled)
         return;
     if (kdSwitchPending) {
@@ -257,12 +265,14 @@
     if (ioctl(LinuxConsoleFd, KDSETMODE, KD_GRAPHICS) &lt; 0) {
         FatalError("LinuxInit: KDSETMODE KD_GRAPHICS failed\n");
     }
+#endif
     enabled = TRUE;
 }
 
 static void
 LinuxDisable(void)
 {
+#ifdef GV
     ioctl(LinuxConsoleFd, KDSETMODE, KD_TEXT);  /* Back to text mode ... */
     if (kdSwitchPending) {
         kdSwitchPending = FALSE;
@@ -275,11 +285,13 @@
         close(LinuxApmFd);
         LinuxApmFd = -1;
     }
+#endif
 }
 
 static void
 LinuxFini(void)
 {
+#ifdef GV
     struct vt_mode VT;
     struct vt_stat vts;
     int fd;
@@ -327,6 +339,7 @@
         close(fd);
     }
     return;
+#endif
 }
 
 void
@@ -352,9 +365,11 @@
 static void
 LinuxBell(int volume, int pitch, int duration)
 {
+#ifdef GV
     if (volume &amp;&amp; pitch)
         ioctl(LinuxConsoleFd, KDMKTONE, ((1193190 / pitch) &amp; 0xffff) |
               (((unsigned long) duration * volume / 50) &lt;&lt; 16));
+#endif
 }
 
 KdOsFuncs LinuxFuncs = {

&lt;/pre&gt;</text>
    <sha1>e70d700159ba90ee5802eaa6deedb4851f92bd2a</sha1>
  </revision>
  <revision>
    <id>924</id>
    <parentid>923</parentid>
    <timestamp>2014-09-05T06:45:24Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38505" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==

&lt;pre&gt;
	Processor : Arm Cortex A7, 1.3 GHz dual core.
		: ARMv7 Processor rev 3 (v7l),
	Hardware  : MT8312
	SOC       : mt6582.
	Memory    : 512MB RAM
	Storage   : 4GB Built in storage.
	Micro SD  : Slot for upto 32GB
	Display   : 7" WVGA 800x480
	OS        : Android 4.2 Jelly Bean
	GPU       : Mali?
&lt;/pre&gt;

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

&lt;pre&gt;
	mkfs.ext4 /dev/sdc1
	sync
	eject sdc
	eject -t sdc
	mkdir slack
	mount /dev/sdc1 slack
	cd slack
	mkdir sl
	cd sl
&lt;/pre&gt;

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 
&lt;pre&gt;
        mkdir slackware14.1
        cd slackware14.1
	(cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )

&lt;/pre&gt;

[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.

&lt;pre&gt;
	cpio -id &lt; initrd-kirkwood.cpio
	sync
	umount slack

Now that the sd card is ready for installation:

	eject sdc
&lt;/pre&gt;
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====
&lt;pre&gt;
	adb shell
	su
&lt;/pre&gt;

==== chroot to installe ====
&lt;pre&gt;
	cd /data/local/tmp
	mkdir slackware
	mount /dev/block/mmcblk1p1 slackware
	cd slackware/sl
	export PATH=/data/local/tmp/bin:$PATH
	mountpoint proc || mount -t proc none proc/
	mountpoint sys || mount -t sysfs sys sys/
	mountpoint dev || mount -o bind  /dev dev/
	export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	pushd /dev
	ln -s /dev/block/mmc1blk* .
	popd
	chroot . /bin/bash
	mount -t ext4 /dev/mmcblk1p1 mnt
&lt;/pre&gt;

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

&lt;pre&gt; 
	setup
	
		Proceed and select /dev/mmcblk1p1 as target, no format
		For source, select pre mounted directory option, /slackware14.1/slackware
&lt;/pre&gt;	

=== Complete installation, and configuration ===

Once the complete installation is done,

&lt;pre&gt;
	umount proc
	umount sys
	umount dev
	sync
	cd ../..
	umount slackware
&lt;/pre&gt;

== Getting into installed Slackware: ==

==== Running slackware su shell ====
&lt;pre&gt;
	adb shell
	su
	mount /dev/block/mmcblk1p1 slackware
	cd slackware
	mountpoint proc || mount -t proc none proc/
        mountpoint sys || mount -t sysfs sys sys/
        mountpoint dev || mount -o bind  /dev dev/
        export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
	chroot . /bin/bash
	su -	
&lt;/pre&gt;

From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		
== Testing the framebuffer ==		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:
&lt;pre&gt;
	adb shell
	su
	stop
&lt;/pre&gt;

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

&lt;pre&gt;
   gcc fbtest.c
   ./a.out
&lt;/pre&gt;

once done, go back to android su shell from adb, and:

==== Getting back to android ====
&lt;pre&gt;
	start
&lt;/pre&gt;	

After few seconds android display will be back on. 

== Getting Xorg up - at least partially ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


==== synaptics ====

synaptics driver fails with error message relating to Protocol.

    xf86-input-synaptics-1.6.1.tar.bz2
    ./configure --prefix=/opt/local/sw CFLAGS=-I/opt/local/sw/include/xorg LDFLAGS=-L/opt/local/sw/lib
    make -j 3
    make install

When running Xorg, 

    [  4784.385] (EE) synaptics: mytouchscreen: Synaptics driver unable to detect protocol


=== Running X ===

make sure display is on, and

From adb shell as su:

    stop

From slackware chroot environment in adb shell [ see section ]:

    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0

Once Finished, from adb shell as su:

    start

=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
\# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>572e575a8c79724bd232b1dac41dfea818c042dc</sha1>
  </revision>
  <revision>
    <id>925</id>
    <parentid>924</parentid>
    <timestamp>2014-09-05T06:57:06Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38529" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/bash
    su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		
== Testing the framebuffer ==		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

== Getting Xorg up - at least partially ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


==== synaptics ====

synaptics driver fails with error message relating to Protocol.

    xf86-input-synaptics-1.6.1.tar.bz2
    ./configure --prefix=/opt/local/sw CFLAGS=-I/opt/local/sw/include/xorg LDFLAGS=-L/opt/local/sw/lib
    make -j 3
    make install

When running Xorg, 

    [  4784.385] (EE) synaptics: mytouchscreen: Synaptics driver unable to detect protocol


=== Running X ===

make sure display is on, and

From adb shell as su:

    stop

From slackware chroot environment in adb shell [ see section ]:

    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0

Once Finished, from adb shell as su:

    start

=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>a45c75669dfa2734f491e6425104b5f20af52917</sha1>
  </revision>
  <revision>
    <id>926</id>
    <parentid>925</parentid>
    <timestamp>2014-09-05T08:34:14Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38759" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/bash
    su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		
== Testing the framebuffer ==		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

== Getting Xorg up - at least partially ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


==== synaptics ====

synaptics driver fails with error message relating to Protocol.

    xf86-input-synaptics-1.6.1.tar.bz2
    ./configure --prefix=/opt/local/sw CFLAGS=-I/opt/local/sw/include/xorg LDFLAGS=-L/opt/local/sw/lib
    make -j 3
    make install

When running Xorg, 

    [  4784.385] (EE) synaptics: mytouchscreen: Synaptics driver unable to detect protocol


=== Running X ===

make sure display is on, and

From adb shell as su:

    stop

From slackware chroot environment in adb shell [ see section ]:

    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0

Once Finished, from adb shell as su:

    start

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd


=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>572eb9d35cda7bbe3db1b3135b87383aada1c6c3</sha1>
  </revision>
  <revision>
    <id>927</id>
    <parentid>926</parentid>
    <timestamp>2014-09-05T08:43:50Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38892" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/bash
    su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		
== Testing the framebuffer ==		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


==== synaptics ====

synaptics driver fails with error message relating to Protocol.

    xf86-input-synaptics-1.6.1.tar.bz2
    ./configure --prefix=/opt/local/sw CFLAGS=-I/opt/local/sw/include/xorg LDFLAGS=-L/opt/local/sw/lib
    make -j 3
    make install

When running Xorg, 

    [  4784.385] (EE) synaptics: mytouchscreen: Synaptics driver unable to detect protocol


=== Running X ===

make sure display is on, and

From adb shell as su:

    stop

From slackware chroot environment in adb shell [ see section ]:

    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0

Once Finished, from adb shell as su:

    start

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd


=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>5b966b862324ef05154d6139053caa82b6c1da9e</sha1>
  </revision>
  <revision>
    <id>928</id>
    <parentid>927</parentid>
    <timestamp>2014-09-05T08:58:36Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <comment>/* xorg.conf */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38894" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/bash
    su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		
== Testing the framebuffer ==		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


==== synaptics ====

synaptics driver fails with error message relating to Protocol.

    xf86-input-synaptics-1.6.1.tar.bz2
    ./configure --prefix=/opt/local/sw CFLAGS=-I/opt/local/sw/include/xorg LDFLAGS=-L/opt/local/sw/lib
    make -j 3
    make install

When running Xorg, 

    [  4784.385] (EE) synaptics: mytouchscreen: Synaptics driver unable to detect protocol


=== Running X ===

make sure display is on, and

From adb shell as su:

    stop

From slackware chroot environment in adb shell [ see section ]:

    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0

Once Finished, from adb shell as su:

    start

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd


=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>22299b221faabcd27fe0de7cf0981bd57189f3d2</sha1>
  </revision>
  <revision>
    <id>929</id>
    <parentid>928</parentid>
    <timestamp>2014-09-05T09:00:58Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38897" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/bash
    su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


==== synaptics ====

synaptics driver fails with error message relating to Protocol.

    xf86-input-synaptics-1.6.1.tar.bz2
    ./configure --prefix=/opt/local/sw CFLAGS=-I/opt/local/sw/include/xorg LDFLAGS=-L/opt/local/sw/lib
    make -j 3
    make install

When running Xorg, 

    [  4784.385] (EE) synaptics: mytouchscreen: Synaptics driver unable to detect protocol


=== Running X ===

make sure display is on, and

From adb shell as su:

    stop

From slackware chroot environment in adb shell [ see section ]:

    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0

Once Finished, from adb shell as su:

    start

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd


=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>118c457c9d9f3964a1ae18eb009c5d4768dbf1de</sha1>
  </revision>
  <revision>
    <id>930</id>
    <parentid>929</parentid>
    <timestamp>2014-09-05T09:26:26Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="38975" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s28.postimg.org/bco3gbdgt/ss2.png Screenshot]  of X windows running.

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/bash
    su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


==== synaptics ====

synaptics driver fails with error message relating to Protocol.

    xf86-input-synaptics-1.6.1.tar.bz2
    ./configure --prefix=/opt/local/sw CFLAGS=-I/opt/local/sw/include/xorg LDFLAGS=-L/opt/local/sw/lib
    make -j 3
    make install

When running Xorg, 

    [  4784.385] (EE) synaptics: mytouchscreen: Synaptics driver unable to detect protocol


=== Running X ===

make sure display is on, and

From adb shell as su:

    stop

From slackware chroot environment in adb shell [ see section ]:

    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0

Once Finished, from adb shell as su:

    start

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd


=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>ee956f81c902daa269ddb1f800428bd6a16338ca</sha1>
  </revision>
  <revision>
    <id>931</id>
    <parentid>930</parentid>
    <timestamp>2014-09-05T10:01:50Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39274" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s28.postimg.org/bco3gbdgt/ss2.png Screenshot]  of X windows running.

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/bash
    su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


==== synaptics ====

synaptics driver fails with error message relating to Protocol.

    xf86-input-synaptics-1.6.1.tar.bz2
    ./configure --prefix=/opt/local/sw CFLAGS=-I/opt/local/sw/include/xorg LDFLAGS=-L/opt/local/sw/lib
    make -j 3
    make install

When running Xorg, 

    [  4784.385] (EE) synaptics: mytouchscreen: Synaptics driver unable to detect protocol


=== Running X ===

make sure display is on, and

From adb shell as su:

    stop

From slackware chroot environment in adb shell [ see section ]:

    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0

Once Finished, from adb shell as su:

    start

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd

=== An application launcher ===
==== http://bbdock.nethence.com/ ====
Download and install [http://bbdock.nethence.com/download/bbdock-0.2.9.tar.gz bbdock-0.2.9.tar.gz] or [http://bbdock.nethence.com/download/ download] 

.bbdockrc sample : 

    /root/icons/xterm-color.png:xterm::1

Launch bbdock

=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>511647198205b0280c2a5f7c8057b6cf6970345d</sha1>
  </revision>
  <revision>
    <id>932</id>
    <parentid>931</parentid>
    <timestamp>2014-09-06T09:32:57Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39870" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. [http://s7.postimg.org/fww1ibfdn/image.png another one].
 

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case
were VTs (ttys). Compiling programs and running programs that require no X windows worked fine. I ran
couple of frame buffer tests too. 
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd

=== An application launcher ===
==== wbar ====
Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --hbar --pos bottom --isize 48 --idist 5 --nanim 4 --f
alfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: /system/bin/start
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: xkill
t: XKill
&lt;/pre&gt;

=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>ec44800c86ce59ca0b0f407b699ee8bf9372fc62</sha1>
  </revision>
  <revision>
    <id>933</id>
    <parentid>932</parentid>
    <timestamp>2014-09-06T09:36:47Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39926" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. [http://s7.postimg.org/fww1ibfdn/image.png another one].
 

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd

=== An application launcher ===
==== wbar ====
Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --hbar --pos bottom --isize 48 --idist 5 --nanim 4 --f
alfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: /system/bin/start
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: xkill
t: XKill
&lt;/pre&gt;

=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>ba72f9d162b85a48ea071c9c403fe12e7ede3ade</sha1>
  </revision>
  <revision>
    <id>934</id>
    <parentid>933</parentid>
    <timestamp>2014-09-06T09:41:11Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="39927" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. [http://s15.postimg.org/izdxddkqj/image.png another one].
 

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1 - sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installe ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== http://homepage3.nifty.com/tsato/xvkbd/ ====

Download [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], install
    xmkf
    make 
    make install

and run: 

    xvkbd

=== An application launcher ===
==== wbar ====
Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --hbar --pos bottom --isize 48 --idist 5 --nanim 4 --f
alfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: /system/bin/start
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: xkill
t: XKill
&lt;/pre&gt;

=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
GV: read 112
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.148724, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.148730, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.148734, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.148738, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.148742, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.148745, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.164975, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.164981, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.164985, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.164989, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.164994, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.164997, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.180722, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.180727, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.180731, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.180736, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.180740, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.180743, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.196495, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.196501, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.196505, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.196510, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.196514, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.196517, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.211803, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.211809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.211813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.211818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.211822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.211825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.225500, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.225504, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.225507, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.466531, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.466536, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.466540, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.466545, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.466549, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.466553, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.466556, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.482028, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.482033, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.482038, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.482042, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.482046, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.482049, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.497971, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.497977, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.497981, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.497986, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.497990, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.497993, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.514030, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.514036, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.514040, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.514044, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.514048, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.514051, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.530188, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.530194, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.530198, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.530202, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.530206, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.530210, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.545804, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.545809, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 341
Event: time 1409845467.545813, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 151
Event: time 1409845467.545818, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.545822, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.545825, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.559686, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.559690, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.559693, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845467.880062, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.880067, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.880072, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.880076, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.880080, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.880084, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.880088, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.895834, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.895839, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.895844, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.895848, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.895852, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.895855, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.911757, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.911762, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 678
Event: time 1409845467.911767, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 130
Event: time 1409845467.911771, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.911775, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.911778, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.927833, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.927838, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 680
Event: time 1409845467.927842, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.927847, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.927851, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.927854, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.944420, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.944426, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845467.944430, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.944434, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.944438, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.944442, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.959239, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.959244, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 683
Event: time 1409845467.959249, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.959253, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.959257, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.959260, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845467.974974, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.974980, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 685
Event: time 1409845467.974984, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 129
Event: time 1409845467.974988, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.974992, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.974996, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845467.989318, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845467.989321, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.989324, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.246567, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.246571, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.246576, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.246580, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.246584, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.246589, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.246592, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.262652, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.262657, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.262662, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.262666, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.262670, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.262673, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.278454, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.278460, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 659
Event: time 1409845468.278464, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.278468, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.278473, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.278476, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.293932, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.293938, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 653
Event: time 1409845468.293942, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 419
Event: time 1409845468.293946, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.293950, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.293953, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.309429, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.309434, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 639
Event: time 1409845468.309438, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 416
Event: time 1409845468.309443, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.309447, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.309450, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.323482, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.323486, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.323489, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.596393, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.596397, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.596402, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.596406, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.596410, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.596414, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.596417, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.612126, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.612132, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.612136, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.612140, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.612144, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.612147, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.628256, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.628262, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.628266, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.628271, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.628275, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.628278, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.644136, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.644142, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.644146, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.644151, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.644155, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.644158, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.659867, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.659873, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 226
Event: time 1409845468.659877, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 302
Event: time 1409845468.659882, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.659886, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.659889, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845468.673538, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845468.673541, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.673544, -------------- SYN_REPORT ------------
GV: read 112
Event: time 1409845468.946001, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845468.946005, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.946010, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.946014, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.946018, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.946022, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.946025, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.962071, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.962077, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.962081, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.962085, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.962089, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.962093, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.977741, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.977747, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.977751, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.977755, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.977759, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.977762, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845468.993678, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845468.993684, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845468.993688, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845468.993692, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845468.993696, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845468.993700, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.010083, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.010089, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 681
Event: time 1409845469.010093, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.010097, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.010101, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.010104, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.026187, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.026193, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 665
Event: time 1409845469.026197, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.026201, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.026205, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.026209, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.041432, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.041437, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 640
Event: time 1409845469.041442, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 357
Event: time 1409845469.041446, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.041450, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.041453, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.057294, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.057299, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 581
Event: time 1409845469.057304, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.057308, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.057312, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.057315, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.073883, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.073889, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 540
Event: time 1409845469.073893, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.073897, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.073901, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.073905, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.089886, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.089892, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 496
Event: time 1409845469.089896, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.089900, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.089904, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.089908, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.105335, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.105340, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 450
Event: time 1409845469.105344, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 364
Event: time 1409845469.105349, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.105353, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.105356, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.121183, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.121188, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 404
Event: time 1409845469.121192, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.121197, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.121201, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.121204, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.136794, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.136799, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 360
Event: time 1409845469.136803, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.136808, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.136812, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.136815, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.152605, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.152611, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 312
Event: time 1409845469.152615, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 360
Event: time 1409845469.152619, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.152623, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.152626, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.169594, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.169599, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 270
Event: time 1409845469.169604, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 366
Event: time 1409845469.169608, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.169612, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.169615, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.185263, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.185268, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 236
Event: time 1409845469.185273, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 373
Event: time 1409845469.185277, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.185281, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.185284, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.200843, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.200848, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.200853, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.200857, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.200861, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.200864, -------------- SYN_REPORT ------------
GV: read 96
Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
GV: read 48
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>a4479a4567df9b3fdf4830a2cfd3e545e2960c3d</sha1>
  </revision>
  <revision>
    <id>935</id>
    <parentid>934</parentid>
    <timestamp>2014-09-06T09:54:35Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15811" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].
 

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --hbar --pos bottom --isize 48 --idist 5 --nanim 4 --f
alfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: /system/bin/start
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: xkill
t: XKill
&lt;/pre&gt;

=== Files ===
==== xorg.conf ====

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------

...

Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>0494c5b49dffcaa819a425093bb508e214a44475</sha1>
  </revision>
  <revision>
    <id>936</id>
    <parentid>935</parentid>
    <timestamp>2014-09-07T05:12:09Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20035" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].
 

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.


=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --pos bottom --isize 48 --idist 5 --nanim 4 --falfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: LD_LIBRARY_PATH= /system/bin/sh /android.tmp/exitfromslackware.sh 
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: sleep 1 &amp;&amp; xkill
t: XKill

&lt;/pre&gt;

== Android app to launch X Windows directly from Android ==

=== Create StartX projec ===

Check [https://www.github.com/gv3/StartX StartX] project at github

Create a project:
    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy StartXActivity.java to  src/com/startx/android

If required,

   keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
     key.store=./gv.keystore
     key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
&lt;pre&gt;
// http://stackoverflow.com/questions/20932102/execute-shell-command-from-android
package com.startx.android;

import java.lang.*;
import java.io.* ;

import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;


public class StartXActivity extends Activity {
    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        
	Process p=null;
                try {
        	    TextView text = new TextView(this);
        	    text.setText("Starting X Windows...\n");
        	    setContentView(text);
		    Process su = Runtime.getRuntime().exec("su");
		    DataOutputStream os = new DataOutputStream(su.getOutputStream());              
		    os.writeBytes("sh /data/local/tmp/chroot2slackware.sh\n");
		    text.append("done\n");
		    os.flush();		    
		    os.writeBytes("exit\n");  
		    text.append("exit\n");
		    os.flush();		    
		    try 
 		    {
		      su.waitFor();
		    } catch(Exception e2) {
			e2.printStackTrace();
		    }
                } catch (IOException e) {
                    e.printStackTrace();
                } finally {
                    if(p!=null) p.destroy();
                }
    }
}
&lt;/pre&gt;

==== chroot2slackware.sh ====

Copy this file to /data/local/tmp/

&lt;pre&gt;

#!/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH
test -d /data/local/tmp/sdcard || mkdir /data/local/tmp/sdcard
mountpoint /data/local/tmp/sdcard || mount -t ext4 /dev/block/mmcblk1p1 /data/local/tmp/sdcard
test -d /data/local/tmp/slackware || mkdir /data/local/tmp/slackware
cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin \
  etc  tmp boot home root lib \
  media mnt opt  run sbin srv var android.tmp ;
do
	test -d $d || mkdir $d
	case $d in
		proc)
			mountpoint proc || mount -t proc none proc/
		;;
		sys)
			mountpoint sys  || mount -t sysfs sys sys/
		;;
		dev)
			mountpoint dev  || mount -o bind /dev dev/
		;;
		system)
			mountpoint system || mount -o bind /system system
		;;
		android.tmp)	
			mountpoint android.tmp || mount -o bind /data/local/tmp android.tmp
		;;
		*)
			mountpoint $d || mount -o bind /data/local/tmp/sdcard/$d $d
		;;
	esac
done


export PATH=/usr/bin:/bin:/usr/X11R6/bin:$PATH
# chroot . /bin/su -
# if non interactive
# test -z $PS1 || test -x /data/local/tmp/sdcard/init &amp;&amp; chroot . su - -c /init
# if interactive
# test -z $PS1 &amp;&amp; chroot . su -
chroot . /bin/bash -x &lt;&lt;'EOF'
	su -
	LD_LIBRARY_PATH= /system/bin/setprop ctl.stop surfaceflinger
	export PATH=/opt/local/sw/bin:/usr/bin:/bin:$PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:/usr/lib:$LD_LIBRARY_PATH
	killall -9 Xorg
	sleep 1
	# /usr/bin/startx -- /opt/local/sw/bin/Xorg :0 
	/usr/bin/xinit -- /opt/local/sw/bin/Xorg :0 
	wait
EOF
&lt;/pre&gt;

==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. It doesn't 
unmount partitions as expected, though

Copy this file to /data/local/tmp/

&lt;pre&gt;
#/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH

killall -9 fluxbox
killall -9 Xorg
killall -9 wbar

cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin etc \
	tmp boot home root init lib media mnt opt \
	run sbin srv var android.tmp;
do
	echo "umounting $d"
	mountpoint $d &amp;&amp; umount $d
done
mountpoint /data/local/tmp/sdcard &amp;&amp; umount /data/local/tmp/sdcard
# setprop ctl.start is not working.
# LD_LIBRARY_PATH= /system/bin/setprop ctl.start surfaceflinger
LD_LIBRARY_PATH= /system/bin/stop
LD_LIBRARY_PATH= /system/bin/start
&lt;/pre&gt;
 
== Files ==
=== xorg.conf ===

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

=== lnx_init.c patch ===

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------

...

Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>ffbae9f927ae74e22a01adaa9ef95b99655ecf4d</sha1>
  </revision>
  <revision>
    <id>937</id>
    <parentid>936</parentid>
    <timestamp>2014-09-07T05:18:19Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20094" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].
 

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

==== Compiling xorg-server-1.12.2 ====
	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

==== xorg.conf ====

Copy this file to /etc/X11

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --pos bottom --isize 48 --idist 5 --nanim 4 --falfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: LD_LIBRARY_PATH= /system/bin/sh /android.tmp/exitfromslackware.sh 
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: sleep 1 &amp;&amp; xkill
t: XKill

&lt;/pre&gt;

== Android app to launch X Windows directly from Android ==

=== Create StartX projec ===

Check [https://www.github.com/gv3/StartX StartX] project at github

Create a project:
    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy StartXActivity.java to  src/com/startx/android

If required,

   keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
     key.store=./gv.keystore
     key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
&lt;pre&gt;
// http://stackoverflow.com/questions/20932102/execute-shell-command-from-android
package com.startx.android;

import java.lang.*;
import java.io.* ;

import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;


public class StartXActivity extends Activity {
    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        
	Process p=null;
                try {
        	    TextView text = new TextView(this);
        	    text.setText("Starting X Windows...\n");
        	    setContentView(text);
		    Process su = Runtime.getRuntime().exec("su");
		    DataOutputStream os = new DataOutputStream(su.getOutputStream());              
		    os.writeBytes("sh /data/local/tmp/chroot2slackware.sh\n");
		    text.append("done\n");
		    os.flush();		    
		    os.writeBytes("exit\n");  
		    text.append("exit\n");
		    os.flush();		    
		    try 
 		    {
		      su.waitFor();
		    } catch(Exception e2) {
			e2.printStackTrace();
		    }
                } catch (IOException e) {
                    e.printStackTrace();
                } finally {
                    if(p!=null) p.destroy();
                }
    }
}
&lt;/pre&gt;

==== chroot2slackware.sh ====

Copy this file to /data/local/tmp/

&lt;pre&gt;

#!/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH
test -d /data/local/tmp/sdcard || mkdir /data/local/tmp/sdcard
mountpoint /data/local/tmp/sdcard || mount -t ext4 /dev/block/mmcblk1p1 /data/local/tmp/sdcard
test -d /data/local/tmp/slackware || mkdir /data/local/tmp/slackware
cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin \
  etc  tmp boot home root lib \
  media mnt opt  run sbin srv var android.tmp ;
do
	test -d $d || mkdir $d
	case $d in
		proc)
			mountpoint proc || mount -t proc none proc/
		;;
		sys)
			mountpoint sys  || mount -t sysfs sys sys/
		;;
		dev)
			mountpoint dev  || mount -o bind /dev dev/
		;;
		system)
			mountpoint system || mount -o bind /system system
		;;
		android.tmp)	
			mountpoint android.tmp || mount -o bind /data/local/tmp android.tmp
		;;
		*)
			mountpoint $d || mount -o bind /data/local/tmp/sdcard/$d $d
		;;
	esac
done


export PATH=/usr/bin:/bin:/usr/X11R6/bin:$PATH
# chroot . /bin/su -
# if non interactive
# test -z $PS1 || test -x /data/local/tmp/sdcard/init &amp;&amp; chroot . su - -c /init
# if interactive
# test -z $PS1 &amp;&amp; chroot . su -
chroot . /bin/bash -x &lt;&lt;'EOF'
	su -
	LD_LIBRARY_PATH= /system/bin/setprop ctl.stop surfaceflinger
	export PATH=/opt/local/sw/bin:/usr/bin:/bin:$PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:/usr/lib:$LD_LIBRARY_PATH
	killall -9 Xorg
	sleep 1
	# /usr/bin/startx -- /opt/local/sw/bin/Xorg :0 
	/usr/bin/xinit -- /opt/local/sw/bin/Xorg :0 
	wait
EOF
&lt;/pre&gt;

==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. It doesn't 
unmount partitions as expected, though

Copy this file to /data/local/tmp/

&lt;pre&gt;
#/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH

killall -9 fluxbox
killall -9 Xorg
killall -9 wbar

cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin etc \
	tmp boot home root init lib media mnt opt \
	run sbin srv var android.tmp;
do
	echo "umounting $d"
	mountpoint $d &amp;&amp; umount $d
done
mountpoint /data/local/tmp/sdcard &amp;&amp; umount /data/local/tmp/sdcard
# setprop ctl.start is not working.
# LD_LIBRARY_PATH= /system/bin/setprop ctl.start surfaceflinger
LD_LIBRARY_PATH= /system/bin/stop
LD_LIBRARY_PATH= /system/bin/start
&lt;/pre&gt;
 

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------

...

Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>3ec92b3d9ed39ef8f93abcc85a557b0659b8bb16</sha1>
  </revision>
  <revision>
    <id>938</id>
    <parentid>937</parentid>
    <timestamp>2014-09-07T05:21:37Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20092" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].
 

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

==== Compiling xorg-server-1.12.2 ====
	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

=== xorg.conf ===

Copy this file to /etc/X11

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --pos bottom --isize 48 --idist 5 --nanim 4 --falfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: LD_LIBRARY_PATH= /system/bin/sh /android.tmp/exitfromslackware.sh 
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: sleep 1 &amp;&amp; xkill
t: XKill

&lt;/pre&gt;

== Android app to launch X Windows directly from Android ==

=== Create StartX projec ===

Check [https://www.github.com/gv3/StartX StartX] project at github

Create a project:
    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy StartXActivity.java to  src/com/startx/android

If required,

   keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
     key.store=./gv.keystore
     key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
&lt;pre&gt;
// http://stackoverflow.com/questions/20932102/execute-shell-command-from-android
package com.startx.android;

import java.lang.*;
import java.io.* ;

import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;


public class StartXActivity extends Activity {
    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        
	Process p=null;
                try {
        	    TextView text = new TextView(this);
        	    text.setText("Starting X Windows...\n");
        	    setContentView(text);
		    Process su = Runtime.getRuntime().exec("su");
		    DataOutputStream os = new DataOutputStream(su.getOutputStream());              
		    os.writeBytes("sh /data/local/tmp/chroot2slackware.sh\n");
		    text.append("done\n");
		    os.flush();		    
		    os.writeBytes("exit\n");  
		    text.append("exit\n");
		    os.flush();		    
		    try 
 		    {
		      su.waitFor();
		    } catch(Exception e2) {
			e2.printStackTrace();
		    }
                } catch (IOException e) {
                    e.printStackTrace();
                } finally {
                    if(p!=null) p.destroy();
                }
    }
}
&lt;/pre&gt;

==== chroot2slackware.sh ====

Copy this file to /data/local/tmp/

&lt;pre&gt;

#!/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH
test -d /data/local/tmp/sdcard || mkdir /data/local/tmp/sdcard
mountpoint /data/local/tmp/sdcard || mount -t ext4 /dev/block/mmcblk1p1 /data/local/tmp/sdcard
test -d /data/local/tmp/slackware || mkdir /data/local/tmp/slackware
cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin \
  etc  tmp boot home root lib \
  media mnt opt  run sbin srv var android.tmp ;
do
	test -d $d || mkdir $d
	case $d in
		proc)
			mountpoint proc || mount -t proc none proc/
		;;
		sys)
			mountpoint sys  || mount -t sysfs sys sys/
		;;
		dev)
			mountpoint dev  || mount -o bind /dev dev/
		;;
		system)
			mountpoint system || mount -o bind /system system
		;;
		android.tmp)	
			mountpoint android.tmp || mount -o bind /data/local/tmp android.tmp
		;;
		*)
			mountpoint $d || mount -o bind /data/local/tmp/sdcard/$d $d
		;;
	esac
done


export PATH=/usr/bin:/bin:/usr/X11R6/bin:$PATH
# chroot . /bin/su -
# if non interactive
# test -z $PS1 || test -x /data/local/tmp/sdcard/init &amp;&amp; chroot . su - -c /init
# if interactive
# test -z $PS1 &amp;&amp; chroot . su -
chroot . /bin/bash -x &lt;&lt;'EOF'
	su -
	LD_LIBRARY_PATH= /system/bin/setprop ctl.stop surfaceflinger
	export PATH=/opt/local/sw/bin:/usr/bin:/bin:$PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:/usr/lib:$LD_LIBRARY_PATH
	killall -9 Xorg
	sleep 1
	# /usr/bin/startx -- /opt/local/sw/bin/Xorg :0 
	/usr/bin/xinit -- /opt/local/sw/bin/Xorg :0 
	wait
EOF
&lt;/pre&gt;

==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. It doesn't 
unmount partitions as expected, though

Copy this file to /data/local/tmp/

&lt;pre&gt;
#/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH

killall -9 fluxbox
killall -9 Xorg
killall -9 wbar

cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin etc \
	tmp boot home root init lib media mnt opt \
	run sbin srv var android.tmp;
do
	echo "umounting $d"
	mountpoint $d &amp;&amp; umount $d
done
mountpoint /data/local/tmp/sdcard &amp;&amp; umount /data/local/tmp/sdcard
# setprop ctl.start is not working.
# LD_LIBRARY_PATH= /system/bin/setprop ctl.start surfaceflinger
LD_LIBRARY_PATH= /system/bin/stop
LD_LIBRARY_PATH= /system/bin/start
&lt;/pre&gt;
 

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------

...

Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>72e67235229eb734548755ba82968f077b2b62f4</sha1>
  </revision>
  <revision>
    <id>939</id>
    <parentid>938</parentid>
    <timestamp>2014-09-07T05:34:21Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20110" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].
 

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

==== Compiling xorg-server-1.12.2 ====
	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

=== xorg.conf ===

Copy this file to /etc/X11

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --pos bottom --isize 48 --idist 5 --nanim 4 --falfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: LD_LIBRARY_PATH= /system/bin/sh /android.tmp/exitfromslackware.sh 
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: sleep 1 &amp;&amp; xkill
t: XKill

&lt;/pre&gt;

== Android app to launch X Windows directly from Android ==

=== Create StartX projec ===

Check [https://github.com/gv1/SlackwareOnMT6582 SlackwareOnMT6582] project at github

Create a project:
    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy StartXActivity.java to  src/com/startx/android

If required,

   keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
     key.store=./gv.keystore
     key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
&lt;pre&gt;
// http://stackoverflow.com/questions/20932102/execute-shell-command-from-android
package com.startx.android;

import java.lang.*;
import java.io.* ;

import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;


public class StartXActivity extends Activity {
    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        
	Process p=null;
                try {
        	    TextView text = new TextView(this);
        	    text.setText("Starting X Windows...\n");
        	    setContentView(text);
		    Process su = Runtime.getRuntime().exec("su");
		    DataOutputStream os = new DataOutputStream(su.getOutputStream());              
		    os.writeBytes("sh /data/local/tmp/chroot2slackware.sh\n");
		    text.append("done\n");
		    os.flush();		    
		    os.writeBytes("exit\n");  
		    text.append("exit\n");
		    os.flush();		    
		    try 
 		    {
		      su.waitFor();
		    } catch(Exception e2) {
			e2.printStackTrace();
		    }
                } catch (IOException e) {
                    e.printStackTrace();
                } finally {
                    if(p!=null) p.destroy();
                }
    }
}
&lt;/pre&gt;

==== chroot2slackware.sh ====

Copy this file to /data/local/tmp/

&lt;pre&gt;

#!/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH
test -d /data/local/tmp/sdcard || mkdir /data/local/tmp/sdcard
mountpoint /data/local/tmp/sdcard || mount -t ext4 /dev/block/mmcblk1p1 /data/local/tmp/sdcard
test -d /data/local/tmp/slackware || mkdir /data/local/tmp/slackware
cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin \
  etc  tmp boot home root lib \
  media mnt opt  run sbin srv var android.tmp ;
do
	test -d $d || mkdir $d
	case $d in
		proc)
			mountpoint proc || mount -t proc none proc/
		;;
		sys)
			mountpoint sys  || mount -t sysfs sys sys/
		;;
		dev)
			mountpoint dev  || mount -o bind /dev dev/
		;;
		system)
			mountpoint system || mount -o bind /system system
		;;
		android.tmp)	
			mountpoint android.tmp || mount -o bind /data/local/tmp android.tmp
		;;
		*)
			mountpoint $d || mount -o bind /data/local/tmp/sdcard/$d $d
		;;
	esac
done


export PATH=/usr/bin:/bin:/usr/X11R6/bin:$PATH
# chroot . /bin/su -
# if non interactive
# test -z $PS1 || test -x /data/local/tmp/sdcard/init &amp;&amp; chroot . su - -c /init
# if interactive
# test -z $PS1 &amp;&amp; chroot . su -
chroot . /bin/bash -x &lt;&lt;'EOF'
	su -
	LD_LIBRARY_PATH= /system/bin/setprop ctl.stop surfaceflinger
	export PATH=/opt/local/sw/bin:/usr/bin:/bin:$PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:/usr/lib:$LD_LIBRARY_PATH
	killall -9 Xorg
	sleep 1
	# /usr/bin/startx -- /opt/local/sw/bin/Xorg :0 
	/usr/bin/xinit -- /opt/local/sw/bin/Xorg :0 
	wait
EOF
&lt;/pre&gt;

==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. It doesn't 
unmount partitions as expected, though

Copy this file to /data/local/tmp/

&lt;pre&gt;
#/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH

killall -9 fluxbox
killall -9 Xorg
killall -9 wbar

cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin etc \
	tmp boot home root init lib media mnt opt \
	run sbin srv var android.tmp;
do
	echo "umounting $d"
	mountpoint $d &amp;&amp; umount $d
done
mountpoint /data/local/tmp/sdcard &amp;&amp; umount /data/local/tmp/sdcard
# setprop ctl.start is not working.
# LD_LIBRARY_PATH= /system/bin/setprop ctl.start surfaceflinger
LD_LIBRARY_PATH= /system/bin/stop
LD_LIBRARY_PATH= /system/bin/start
&lt;/pre&gt;
 

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------

...

Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>11eb486dd6658ba9338b537a3160cc5001612468</sha1>
  </revision>
  <revision>
    <id>940</id>
    <parentid>939</parentid>
    <timestamp>2014-09-07T07:12:49Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <comment>/* Specifications of the Tablet PC which was used here */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20236" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?

== External Links ==
[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].

[https://github.com/gv1/SlackwareOnMT6582/releases SlackwareOnMT6582] page at github, includes StartX apk.

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

==== lnx_init.c patch ====

&lt;pre&gt;
--- xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx_init.c	2014-09-04 22:53:13.450000054 +0530
+++ xorg-server-1.12.2.org/hw/xfree86/os-support/linux/lnx_init.c	2012-05-17 22:39:03.000000000 +0530
@@ -48,18 +48,15 @@
 static void
 drain_console(int fd, void *closure)
 {
-#ifdef GV
     errno = 0;
     if (tcflush(fd, TCIOFLUSH) == -1 &amp;&amp; errno == EIO) {
         xf86SetConsoleHandler(NULL, NULL);
     }
-#endif
 }
 
 static void
 switch_to(int vt, const char *from)
 {
-#ifdef GV
     int ret;
 
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_ACTIVATE, vt));
@@ -69,13 +66,11 @@
     SYSCALL(ret = ioctl(xf86Info.consoleFd, VT_WAITACTIVE, vt));
     if (ret &lt; 0)
         FatalError("%s: VT_WAITACTIVE failed: %s\n", from, strerror(errno));
-#endif
 }
 
 void
 xf86OpenConsole(void)
 {
-#ifdef GV
     int i, fd = -1, ret;
     struct vt_mode VT;
     struct vt_stat vts;
@@ -254,13 +249,11 @@
             switch_to(xf86Info.vtno, "xf86OpenConsole");
         }
     }
-#endif
 }
 
 void
 xf86CloseConsole(void)
 {
-#ifdef GV
     struct vt_mode VT;
     int ret;
 
@@ -307,7 +300,6 @@
         }
     }
     close(xf86Info.consoleFd);  /* make the vt-manager happy */
-#endif
 }
 
 int
&lt;/pre&gt;

==== Compiling xorg-server-1.12.2 ====
	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

=== xorg.conf ===

Copy this file to /etc/X11

&lt;pre&gt;
Section "ServerLayout"
Identifier	"myLaout"
Screen		"myScreen"
# InputDevice     "mymouse"
InputDevice	"mytouchscreen"
EndSection

Section "Screen"
Identifier	"myScreen"
Device		"myfbdev"
DefaultDepth 	24
EndSection

Section "Device"
Identifier	"myFbdev"
Driver		"fbdev"
Option		"fbdev" "/dev/graphics/fb0"
EndSection

Section "InputDevice"
 Identifier	"mytouchscreen"
 Driver		"evdev"
 # Driver 	"synaptics"
 Option		"Device" "/dev/input/event3"
 # Option	"Protocol" "Auto"
EndSection
&lt;/pre&gt;

=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

&lt;pre&gt;
i: /opt/local/sw/share/pixmaps/wbar/dock.png
c: wbar --bpress --above-desk --pos bottom --isize 48 --idist 5 --nanim 4 --falfa 65
t: /10

i: /opt/local/sw/share/pixmaps/wbar/wbar.png
c: wbar-config
t: Config

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/terminal.png
c: xterm
t: Xterm

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/keyboard.png
c: xvkbd -compact -no-repeat -geometry 800x200
t: Xvkbd

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/calculator.png
c: xcalc
t: XCalc

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/restart.png
c: LD_LIBRARY_PATH= /system/bin/sh /android.tmp/exitfromslackware.sh 
t: Backto Android

i: /opt/local/sw/share/icons/wm-icons/32x32-gant/window-close.png
c: sleep 1 &amp;&amp; xkill
t: XKill

&lt;/pre&gt;

== Android app to launch X Windows directly from Android ==

=== Create StartX projec ===

Check [https://github.com/gv1/SlackwareOnMT6582 SlackwareOnMT6582] project at github

Create a project:
    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy StartXActivity.java to  src/com/startx/android

If required,

   keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
     key.store=./gv.keystore
     key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
&lt;pre&gt;
// http://stackoverflow.com/questions/20932102/execute-shell-command-from-android
package com.startx.android;

import java.lang.*;
import java.io.* ;

import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;


public class StartXActivity extends Activity {
    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        
	Process p=null;
                try {
        	    TextView text = new TextView(this);
        	    text.setText("Starting X Windows...\n");
        	    setContentView(text);
		    Process su = Runtime.getRuntime().exec("su");
		    DataOutputStream os = new DataOutputStream(su.getOutputStream());              
		    os.writeBytes("sh /data/local/tmp/chroot2slackware.sh\n");
		    text.append("done\n");
		    os.flush();		    
		    os.writeBytes("exit\n");  
		    text.append("exit\n");
		    os.flush();		    
		    try 
 		    {
		      su.waitFor();
		    } catch(Exception e2) {
			e2.printStackTrace();
		    }
                } catch (IOException e) {
                    e.printStackTrace();
                } finally {
                    if(p!=null) p.destroy();
                }
    }
}
&lt;/pre&gt;

==== chroot2slackware.sh ====

Copy this file to /data/local/tmp/

&lt;pre&gt;

#!/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH
test -d /data/local/tmp/sdcard || mkdir /data/local/tmp/sdcard
mountpoint /data/local/tmp/sdcard || mount -t ext4 /dev/block/mmcblk1p1 /data/local/tmp/sdcard
test -d /data/local/tmp/slackware || mkdir /data/local/tmp/slackware
cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin \
  etc  tmp boot home root lib \
  media mnt opt  run sbin srv var android.tmp ;
do
	test -d $d || mkdir $d
	case $d in
		proc)
			mountpoint proc || mount -t proc none proc/
		;;
		sys)
			mountpoint sys  || mount -t sysfs sys sys/
		;;
		dev)
			mountpoint dev  || mount -o bind /dev dev/
		;;
		system)
			mountpoint system || mount -o bind /system system
		;;
		android.tmp)	
			mountpoint android.tmp || mount -o bind /data/local/tmp android.tmp
		;;
		*)
			mountpoint $d || mount -o bind /data/local/tmp/sdcard/$d $d
		;;
	esac
done


export PATH=/usr/bin:/bin:/usr/X11R6/bin:$PATH
# chroot . /bin/su -
# if non interactive
# test -z $PS1 || test -x /data/local/tmp/sdcard/init &amp;&amp; chroot . su - -c /init
# if interactive
# test -z $PS1 &amp;&amp; chroot . su -
chroot . /bin/bash -x &lt;&lt;'EOF'
	su -
	LD_LIBRARY_PATH= /system/bin/setprop ctl.stop surfaceflinger
	export PATH=/opt/local/sw/bin:/usr/bin:/bin:$PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:/usr/lib:$LD_LIBRARY_PATH
	killall -9 Xorg
	sleep 1
	# /usr/bin/startx -- /opt/local/sw/bin/Xorg :0 
	/usr/bin/xinit -- /opt/local/sw/bin/Xorg :0 
	wait
EOF
&lt;/pre&gt;

==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. It doesn't 
unmount partitions as expected, though

Copy this file to /data/local/tmp/

&lt;pre&gt;
#/system/bin/sh
export PATH=/data/local/tmp/bin:$PATH

killall -9 fluxbox
killall -9 Xorg
killall -9 wbar

cd /data/local/tmp/slackware

for d in sys proc dev system usr bin sbin etc \
	tmp boot home root init lib media mnt opt \
	run sbin srv var android.tmp;
do
	echo "umounting $d"
	mountpoint $d &amp;&amp; umount $d
done
mountpoint /data/local/tmp/sdcard &amp;&amp; umount /data/local/tmp/sdcard
# setprop ctl.start is not working.
# LD_LIBRARY_PATH= /system/bin/setprop ctl.start surfaceflinger
LD_LIBRARY_PATH= /system/bin/stop
LD_LIBRARY_PATH= /system/bin/start
&lt;/pre&gt;
 

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------

...

Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>8f97a3af8bc46ca6083d161181160759c58151d2</sha1>
  </revision>
  <revision>
    <id>941</id>
    <parentid>940</parentid>
    <timestamp>2014-09-07T11:11:28Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="15074" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?

== External Links ==
[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].

[https://github.com/gv1/SlackwareOnMT6582/releases SlackwareOnMT6582] page at github, includes StartX apk.

== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not
moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


	tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.

==== lnx_init.c patch ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/lnx_init.patch lnx_init.patch]

==== Compiling xorg-server-1.12.2 ====
	cd xorg-server-1.12.2
	export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
	export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
	export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
	export PATH=/opt/local/sw/bin:$PATH
	./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

	./configure --prefix=/opt/local/sw
	make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
	make install
	
=== Compiling additional drivers required ===

==== fbdev ====

xf86-video-fbdev-0.4.2
export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
./configure --prefix=/opt/local/sw

src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c
// #include "mibstore.h"

make -j 3
make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

=== xorg.conf ===

Copy this file to /etc/X11


[https://github.com/gv1/SlackwareOnMT6582/blob/master/xorg.conf xorg.conf]


=== Running X ===

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg -pointer mytouchscreen :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Once Finished,

run: 

    /system/bin/start

Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

Copy this file to /root/.wbar :

[https://github.com/gv1/SlackwareOnMT6582/blob/master/wbar .wbar]

== Android app to launch X Windows directly from Android ==

=== Create StartX projec ===

Check [https://github.com/gv1/SlackwareOnMT6582 SlackwareOnMT6582] project at github

Create a project:
    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java] to  src/com/startx/android

If required,

   keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
     key.store=./gv.keystore
     key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
Copy this file to StartX/src/com/startx/android

[https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java]

==== chroot2slackware.sh ====

Copy this file to /data/local/tmp/

[https://github.com/gv1/SlackwareOnMT6582/blob/master/chroot2slackware.sh chroot2slackware.sh]


==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. 

Copy this file to /data/local/tmp/

[https://github.com/gv1/SlackwareOnMT6582/blob/master/exitfromslackware.sh exitfromslackware.sh]


== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop"
command. Before running stop, make sure that the display is on ( not blank ). For these tests, I had
two terminals up on the host PC with one of them running just adb shell with su, and other running
chrooted slackware shell. SurfaceFlinger was stopped from su shell, and tests from Slackware shell.

Please not Slackware shell is also running as user root.

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

    adb shell
    su
    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


once done, go back to android su shell from adb, and:

==== Getting back to android ====
  
    start
	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

&lt;pre&gt;
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	mtk-kpd
/dev/input/event1:	ACCDET
/dev/input/event2:	hwmdata
/dev/input/event3:	mtk-tpd
Select the device event number [0-3]: Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "mtk-tpd"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 330 (BTN_TOUCH)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value      0
      Min        0
      Max      800
      Resolution     800
    Event code 1 (ABS_Y)
      Value      0
      Min        0
      Max      480
      Resolution     480
    Event code 24 (ABS_PRESSURE)
      Value      0
      Min        0
      Max      255
    Event code 48 (ABS_MT_TOUCH_MAJOR)
      Value      0
      Min        0
      Max      100
    Event code 49 (ABS_MT_TOUCH_MINOR)
      Value      0
      Min        0
      Max      100
    Event code 53 (ABS_MT_POSITION_X)
      Value      0
      Min        0
      Max      800
    Event code 54 (ABS_MT_POSITION_Y)
      Value      0
      Min        0
      Max      480
    Event code 57 (ABS_MT_TRACKING_ID)
      Value      0
      Min        0
      Max        0
Properties:
  Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)
Event: time 1409845467.116675, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1409845467.116682, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.116687, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.116691, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.116695, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.116699, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.116703, -------------- SYN_REPORT ------------
Event: time 1409845467.133145, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845467.133151, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 115
Event: time 1409845467.133155, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 96
Event: time 1409845467.133160, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845467.133164, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845467.133167, -------------- SYN_REPORT ------------

...

Event: time 1409845469.216857, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), value 1
Event: time 1409845469.216863, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 207
Event: time 1409845469.216867, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 376
Event: time 1409845469.216871, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 1
Event: time 1409845469.216875, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.216878, -------------- SYN_REPORT ------------
Event: time 1409845469.230419, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1409845469.230423, ++++++++++++++ SYN_MT_REPORT ++++++++++++
Event: time 1409845469.230426, -------------- SYN_REPORT ------------
&lt;/pre&gt;

=== Running xinput ===

	xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

	xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>47ea995046432fd655362f24978bad891e4cde8b</sha1>
  </revision>
  <revision>
    <id>942</id>
    <parentid>941</parentid>
    <timestamp>2014-09-07T11:59:41Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12147" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?

== External Links ==

[http://arm.slackware.com/getslack/ Slackware] for arm


[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].


[http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk]


[https://github.com/gv1/SlackwareOnMT6582/releases SlackwareOnMT6582] page at github, includes StartX apk.


== Rooting the Tablet PC ==

I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment.

So far, command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display. Since there is no VTs available was not able to test Xorg, though could get Mali module compiled and loaded. More details below.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su


==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 


==== lnx_init.c patch ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/lnx_init.patch lnx_init.patch]

==== Compiling xorg-server-1.12.2 ====

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


    tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.


    cd xorg-server-1.12.2
    export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
    export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
    export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
    export PATH=/opt/local/sw/bin:$PATH
    ./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
    make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

    ./configure --prefix=/opt/local/sw
    make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
    
    make install
	
=== Compiling additional drivers required ===

==== fbdev ====

    xf86-video-fbdev-0.4.2
    export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
    ./configure --prefix=/opt/local/sw

In src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c, comment:

    // #include "mibstore.h"

    make -j 3
    make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

=== xorg.conf ===

Copy this file to /etc/X11

[https://github.com/gv1/SlackwareOnMT6582/blob/master/xorg.conf xorg.conf]


=== Running X ===

In the final setup, these manual steps to switch between X and Android is
not required, StartX app and wbar button "Back to Android" does these tasks.

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Or
    Touch and run "StartX" app. 

Once Finished,

run: 

    /system/bin/start


Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

Copy this file to /root/.wbar :

[https://github.com/gv1/SlackwareOnMT6582/blob/master/wbar .wbar]

== Android app to launch X Windows directly from Android ==

=== Create StartX projec ===

Check [https://github.com/gv1/SlackwareOnMT6582 SlackwareOnMT6582] project at github

Create a project:

    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java] to  src/com/startx/android

If required,

    keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
    key.store=./gv.keystore
    key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
Copy this file to StartX/src/com/startx/android

[https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java]

==== chroot2slackware.sh ====

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/chroot2slackware.sh chroot2slackware.sh] to /data/local/tmp/


==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. 

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/exitfromslackware.sh exitfromslackware.sh] to /data/local/tmp/


== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop" command. Before running stop, make sure that the display is on ( not blank ).

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

From Slackware shell in adb:

    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


==== Getting back to android ====
  
Once done, go back to Slackware shell in adb, and:

    start	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/doc/evtest.log evtest.log]

=== Running xinput ===

    xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

    xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>6964b654f20b3af3a4cca4cae9f530b278820b15</sha1>
  </revision>
  <revision>
    <id>943</id>
    <parentid>942</parentid>
    <timestamp>2014-09-07T13:10:49Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12732" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?

== External Links ==

Get [http://arm.slackware.com/getslack/ Slackware] for arm

[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].

[http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk]

[https://github.com/gv1/SlackwareOnMT6582/releases SlackwareOnMT6582] page at github, includes [https://github.com/gv1/SlackwareOnMT6582/releases StartX] apk.


== Rooting the Tablet PC ==

A tablet with root access is required. I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment. Please not that you can try command line stuff with [http://proot.me/ proot] ( which requires no root access). Xorg however requires root permission since /dev/graphics/fb0 requires root permission.

So far, X windows using Xorg, and command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su

==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs were ok. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 


==== lnx_init.c patch ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/lnx_init.patch lnx_init.patch]

==== Compiling xorg-server-1.12.2 ====

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


    tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.


    cd xorg-server-1.12.2
    export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
    export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
    export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
    export PATH=/opt/local/sw/bin:$PATH
    ./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
    make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

    ./configure --prefix=/opt/local/sw
    make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
    
    make install
	
=== Compiling additional drivers required ===

==== fbdev ====

    xf86-video-fbdev-0.4.2
    export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
    ./configure --prefix=/opt/local/sw

In src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c, comment:

    // #include "mibstore.h"

    make -j 3
    make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

=== xorg.conf ===

Copy this file to /etc/X11

[https://github.com/gv1/SlackwareOnMT6582/blob/master/xorg.conf xorg.conf]


=== Running X ===

In the final setup, these manual steps to switch between X and Android is
not required, StartX app and wbar button "Back to Android" does these tasks.

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Or
    Touch and run "StartX" app. 

Once Finished,

run: 

    /system/bin/start


Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

Copy this file to /root/.wbar :

[https://github.com/gv1/SlackwareOnMT6582/blob/master/wbar .wbar]

== Android app to launch X Windows directly from Android ==

Install [https://github.com/gv1/SlackwareOnMT6582/releases/download/v0.1-alpha/StartXActivity-release.apk StartXActivity-release.apk] for starting X
windows from Android. You may use adb to install StartX after downloading it.
    
    adb install ./StartXActivity-release.apk

=== Create StartX projec ===

To build the the apk from scratch, check [https://github.com/gv1/SlackwareOnMT6582 SlackwareOnMT6582] project at github

Create a project:

    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java] to  src/com/startx/android

If required,

    keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
    key.store=./gv.keystore
    key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
Copy this file to StartX/src/com/startx/android before build.

[https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java]

==== chroot2slackware.sh ====

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/chroot2slackware.sh chroot2slackware.sh] to /data/local/tmp/ along with 

==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. 

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/exitfromslackware.sh exitfromslackware.sh] to /data/local/tmp/

Thse files are used by StartX app to launch X windows.

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop" command. Before running stop, make sure that the display is on ( not blank ).

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

From Slackware shell in adb:

    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


==== Getting back to android ====
  
Once done, go back to Slackware shell in adb, and:

    start	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/doc/evtest.log evtest.log]

=== Running xinput ===

    xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

    xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>b4986d5655ebc69b86cd82ef36770bfaf1382bf2</sha1>
  </revision>
  <revision>
    <id>944</id>
    <parentid>943</parentid>
    <timestamp>2014-09-07T13:14:06Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12774" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?

== External Links ==

Get [http://arm.slackware.com/getslack/ Slackware] for arm

[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].

[http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk]

[https://github.com/gv1/SlackwareOnMT6582/releases SlackwareOnMT6582] page at github, includes [https://github.com/gv1/SlackwareOnMT6582/releases StartX] apk.


== Rooting the Tablet PC ==

A tablet with root access is required. I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment. Please not that you can try command line stuff with [http://proot.me/ proot] ( which requires no root access). Xorg however requires root permission since /dev/graphics/fb0 requires root permission.

So far, X windows using Xorg, and command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su

==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs were ok. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 


==== lnx_init.c patch ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/lnx_init.patch lnx_init.patch]

==== Compiling xorg-server-1.12.2 ====

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


    tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.


    cd xorg-server-1.12.2
    export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
    export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
    export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
    export PATH=/opt/local/sw/bin:$PATH
    ./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
    make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

    ./configure --prefix=/opt/local/sw
    make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
    
    make install
	
=== Compiling additional drivers required ===

==== fbdev ====

    xf86-video-fbdev-0.4.2
    export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
    ./configure --prefix=/opt/local/sw

In src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c, comment:

    // #include "mibstore.h"

    make -j 3
    make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

=== xorg.conf ===

Copy this file to /etc/X11

[https://github.com/gv1/SlackwareOnMT6582/blob/master/xorg.conf xorg.conf]


=== Running X ===

In the final setup, these manual steps to switch between X and Android is
not required, StartX app and wbar button "Back to Android" does these tasks.

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Or
    Touch and run "StartX" app. 

Once Finished,

run: 

    /system/bin/start


Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

Copy this file to /root/.wbar :

[https://github.com/gv1/SlackwareOnMT6582/blob/master/wbar .wbar]

== Android app to launch X Windows directly from Android ==

=== Install apk ====

Install [https://github.com/gv1/SlackwareOnMT6582/releases/download/v0.1-alpha/StartXActivity-release.apk StartXActivity-release.apk] for starting X
windows from Android. You may use adb to install StartX after downloading it.
    
    adb install ./StartXActivity-release.apk

Or if you prefer,

=== Create StartX project ===

To build the the apk from scratch, check [https://github.com/gv1/SlackwareOnMT6582 SlackwareOnMT6582] project at github

Create a project:

    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java] to  src/com/startx/android

If required,

    keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
    key.store=./gv.keystore
    key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
Copy this file to StartX/src/com/startx/android before build.

[https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java]

==== chroot2slackware.sh ====

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/chroot2slackware.sh chroot2slackware.sh] to /data/local/tmp/ along with 

==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. 

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/exitfromslackware.sh exitfromslackware.sh] to /data/local/tmp/

Thse files are used by StartX app to launch X windows.

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop" command. Before running stop, make sure that the display is on ( not blank ).

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

From Slackware shell in adb:

    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


==== Getting back to android ====
  
Once done, go back to Slackware shell in adb, and:

    start	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/doc/evtest.log evtest.log]

=== Running xinput ===

    xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

    xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>7f76a557ab8f7f7ab2328114916fa1a19360cb41</sha1>
  </revision>
  <revision>
    <id>945</id>
    <parentid>944</parentid>
    <timestamp>2014-09-07T13:14:59Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12773" xml:space="preserve">
== Specifications of the Tablet PC which was used here ==


   Processor : Arm Cortex A7, 1.3 GHz dual core.
             : ARMv7 Processor rev 3 (v7l),
   Hardware  : MT8312
   SOC       : mt6582.
   Memory    : 512MB RAM
   Storage   : 4GB Built in storage.
   Micro SD  : Slot for upto 32GB
   Display   : 7" WVGA 800x480
   OS        : Android 4.2 Jelly Bean
   GPU       : Mali?

== External Links ==

Get [http://arm.slackware.com/getslack/ Slackware] for arm

[http://s7.postimg.org/fww1ibfdn/image.png Screenshot] of X windows with fluxbox and wbar. And [http://s15.postimg.org/izdxddkqj/image.png another one].

[http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk]

[https://github.com/gv1/SlackwareOnMT6582/releases SlackwareOnMT6582] page at github, includes [https://github.com/gv1/SlackwareOnMT6582/releases StartX] apk.


== Rooting the Tablet PC ==

A tablet with root access is required. I used [http://www.techverse.net/fastest-root-android-phone-computer/ Framaroot-1.9.3.apk] to root the device. 

== Installing Linux - Slackware 14.1, sort of. ==

With the problem of not having kernel source for the SOC, and no no bootloader unlock possible yet, next best option was to use a chroot environment. Please not that you can try command line stuff with [http://proot.me/ proot] ( which requires no root access). Xorg however requires root permission since /dev/graphics/fb0 requires root permission.

So far, X windows using Xorg, and command line mode works fine. Here is the description of how Slackware was installed on to external micro SD Card. Was able to do some basic tests on the frame buffer display.

=== Preparing SD Card on host computer ===

Use fdisk to create one or two partitions, one for ext4 and other ( optional ) swap partition. Once these are created, assuming the device on host is /dev/sdc,

    mkfs.ext4 /dev/sdc1
    sync
    eject sdc
    eject -t sdc
    mkdir slack
    mount /dev/sdc1 slack
    cd slack
    mkdir sl
    cd sl

If you don't have Slackware installation files, [http://arm.slackware.com/getslack/ Get Slackware Arm] first. 

    mkdir slackware14.1
    cd slackware14.1
    (cd /path..to../slackware14.1 ; tar cfz - *) | (tar xfz - )


[http://sourceforge.net/projects/slackwareonapc8750/files/initrd-kirkwood.cpio.gz/download initrd-kirkwood.cpio] contains the setup program, but since I couldn't boot with custom initrd, sdc1 /sl area is prepared to have the installation files.


    cpio -id &lt; initrd-kirkwood.cpio
    sync
    umount slack

Now that the sd card is ready for installation:

    eject sdc
	
and plug it into the device. Once that is done,

=== Getting installer ready ===

Now plug the card in tablet pc, boot, from host computer,

==== starting a adb shell with su ====

    adb shell
    su

==== chroot to installer ====

    cd /data/local/tmp
    mkdir slackware
    mount /dev/block/mmcblk1p1 slackware
    cd slackware/sl
    export PATH=/data/local/tmp/bin:$PATH
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    pushd /dev
    ln -s /dev/block/mmc1blk* .
    popd
    chroot . /bin/bash
    mount -t ext4 /dev/mmcblk1p1 mnt

=== Running setup ===

Install Slackware onto mmcblk1p1, from pre mounted directory, sdc1 : /slackware14.1/slackware

    setup
        Proceed and select /dev/mmcblk1p1 as target, no format
        For source, select pre mounted directory option, /slackware14.1/slackware
	

=== Complete installation, and configuration ===

Once the complete installation is done,

    umount proc
    umount sys
    umount dev
    sync
    cd ../..
    umount slackware

== Getting into installed Slackware: ==

==== Running slackware su shell ====

    adb shell
    su
    mount /dev/block/mmcblk1p1 slackware
    cd slackware
    mountpoint proc || mount -t proc none proc/
    mountpoint sys || mount -t sysfs sys sys/
    mountpoint dev || mount -o bind  /dev dev/
    test -d system || mkdir system
    mountpoint system || mount -o bind /system system
    export PATH=/usr/bin:/bin:/usr/lib/setup:$PATH
    chroot . /bin/su -	


From here you can do "normal" Slackware activities, sort of. Main things that were lacking in my case were VTs (ttys). Compiling programs and running programs were ok. I ran couple of frame buffer tests too. Fortunately, removing the VT requirement from Xorg was pretty simple. Here is how it was done.
		

== Getting Xorg up and running - kind of ==

=== Getting Xorg compiled ===

Ecept for Pointer ( touchscreen ) failure, Xorg seems to be working fine. evtest, xinput tests are showing touchscreen activity, but the cursor seems to be not moving. But if a window like xvkbd or xterm or so is launched, you can move the window using the touch screen!. And kvkbd input also works. 


==== lnx_init.c patch ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/lnx_init.patch lnx_init.patch]

==== Compiling xorg-server-1.12.2 ====

Download [http://www.x.org/releases/X11R7.7/src/everything/xorg-server-1.12.2.tar.bz2  xorg-server-1.12.2], 


    tar xf xorg-server-1.12.2.tar.bz2

Also make changes to xorg-server-1.12.2/hw/xfree86/os-support/linux/lnx\_init.c so that VT / console related code is disabled. See the patch section.


    cd xorg-server-1.12.2
    export PKG_CONFIG_PATH=/opt/local/sw/share/pkgconfig:$PKG_CONFIG_PATH
    export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
    export LD_LIBRARY_PATH=/opt/local/sw/lib:$LD_LIBRARY_PATH
    export PATH=/opt/local/sw/bin:$PATH
    ./configure --prefix=/opt/local/sw --enable-kdrive --enable-kdrive-evdev --with-xkb-path=/opt/local/sw/share/X11/xkb --with-xkb-output=/var/lib/xkb --with-xkb-bin-directory=/opt/local/sw/bin --with-default-xkb-rules=xorg --with-default-xkb-model=pc104 --with-default-xkb-layout=us  --disable-xnest --disable-dmx --disable-xquartz --disable-xwin --disable-xephyr --disable-config-udev --enable-tslib --disable-docs  --disable-devel-docs LDFLAGS=-L/opt/local/sw/lib CFLAGS=-I/opt/local/sw/include
    make -j 3

If all required packages are not on the system, compilation will fail. Download each of the requiered packags , untar, configure and install.

    ./configure --prefix=/opt/local/sw
    make -j 3 install

Once xorg-server-1.12.2 compilation is succesfull, 
    
    make install
	
=== Compiling additional drivers required ===

==== fbdev ====

    xf86-video-fbdev-0.4.2
    export PKG_CONFIG_PATH=/opt/local/sw/lib/pkgconfig:$PKG_CONFIG_PATH
    ./configure --prefix=/opt/local/sw

In src/fbdev.c xf86-video-fbdev-0.4.2/src/fbdev.c, comment:

    // #include "mibstore.h"

    make -j 3
    make install

==== evdev ====

    xf86-input-evdev-2.7.0
    ./configure --prefix=/opt/local/sw

    src/Makefile:
    evdev_drv_la_LIBADD = $(MTDEV_LIBS) $(UDEV_LIBS)
    ( if not done, causes evdev_drv.so: undefined symbol: udev_new when Xorg is ran)

    make -j 3 
    make install

Once installed make an xorg.conf [ see xorg.conf section ] in /etc/X11/
and run startx as described below.

=== xorg.conf ===

Copy this file to /etc/X11

[https://github.com/gv1/SlackwareOnMT6582/blob/master/xorg.conf xorg.conf]


=== Running X ===

In the final setup, these manual steps to switch between X and Android is
not required, StartX app and wbar button "Back to Android" does these tasks.

make sure display is on,
From slackware chroot environment in adb shell [ see section ]:

    /system/bin/stop
    startx -- /opt/local/sw/bin/Xorg :0
  
    Try disown / nohup to keep X running when disconnected from PC.

Or
    Touch and run "StartX" app. 

Once Finished,

run: 

    /system/bin/start


Or touch the "back to android" icon on wbar. to return to Android.

=== Virtual Keyboard ===

==== xvkbd ====

Download [http://homepage3.nifty.com/tsato/xvkbd/ xvkbd] from [http://homepage3.nifty.com/tsato/xvkbd/xvkbd-3.5.tar.gz xvkbd-3.5.tar.gz], and install:

    xmkf
    make 
    make install

Run: 

    xvkbd

=== An application launcher ===

==== wbar ====

Download [https://github.com/warlockcc/wbar wbar] from [https://code.google.com/p/wbar/downloads/detail?name=wbar-2.3.4.tgz&amp;can=2&amp;q= wbar-2.3.4.tgz] at [https://code.google.com/p/wbar/downloads/list wbar downloads at code.google.com]

==== .wbar ====

Copy this file to /root/.wbar :

[https://github.com/gv1/SlackwareOnMT6582/blob/master/wbar .wbar]

== Android app to launch X Windows directly from Android ==

=== Install apk ===

Install [https://github.com/gv1/SlackwareOnMT6582/releases/download/v0.1-alpha/StartXActivity-release.apk StartXActivity-release.apk] for starting X
windows from Android. You may use adb to install StartX after downloading it.
    
    adb install ./StartXActivity-release.apk

Or if you prefer,

=== Create StartX project ===

To build the the apk from scratch, check [https://github.com/gv1/SlackwareOnMT6582 SlackwareOnMT6582] project at github

Create a project:

    android  create project -n StartX -k com.startx.android -a StartXActivity -t 1 -p .

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java] to  src/com/startx/android

If required,

    keytool -genkey -v -keystore gv.keystore \
     -alias gv_ks -keyalg RSA -keysize 2048 -validity 10000

Add to project properties:
    key.store=./gv.keystore
    key.alias=gv_ks

Build and install:
     ant release install

==== StartXActivity.java ====
Copy this file to StartX/src/com/startx/android before build.

[https://github.com/gv1/SlackwareOnMT6582/blob/master/StartXActivity.java StartXActivity.java]

==== chroot2slackware.sh ====

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/chroot2slackware.sh chroot2slackware.sh] to /data/local/tmp/ along with 

==== exitfromslackware.sh ====

This file is called when "Back to Android" wbar button is touched. 

Copy [https://github.com/gv1/SlackwareOnMT6582/blob/master/exitfromslackware.sh exitfromslackware.sh] to /data/local/tmp/

Thse files are used by StartX app to launch X windows.

== Running some tests ==

=== Testing the framebuffer ===		

For these tests, I stopped android "SurfaceFlinger" and freed up /dev/graphics/fb0. by running "stop" command. Before running stop, make sure that the display is on ( not blank ).

==== Stopping android - sort of ====

Here is how to stop the SurfaceFlinger and get framebuffer free:

From Slackware shell in adb:

    stop

Now the display goes blank, with backlight on.

Get one of these tests.
[https://gist.githubusercontent.com/rafalrusin/1482697/raw/32c6c0d79b870ffb618aa7b7c664736ca5e150fe/fbtest.c  fbtest] or 
[http://stackoverflow.com/questions/4996777/paint-pixels-to-screen-via-linux-framebuffer Paint-pixels-to-screen-  via-linux-framebuffer] or 
[http://cep.xray.aps.anl.gov/software/qt4-x11-4.2.2/qtopiacore-testingframebuffer.html qtopiacore-testingframebuffer] All these tests worked on the Tablet. Transfer the tests to tablet using adb push
command.

from Slackware shell, running under adb shell:

    gcc fbtest.c
    ./a.out


==== Getting back to android ====
  
Once done, go back to Slackware shell in adb, and:

    start	

After few seconds android display will be back on. 

=== Running evtest ===

Download [http://cgit.freedesktop.org/~whot/evtest/tree/evtest.c evtest.c].

   gcc -o gcc -o evtest evtest.c
   ./evtest
   see evtest.log for sample outpu


==== evtest.log ====

[https://github.com/gv1/SlackwareOnMT6582/blob/master/doc/evtest.log evtest.log]

=== Running xinput ===

    xinput --list

&lt;pre&gt;
â¡ Virtual core pointer                         id=2    [master pointer  (3)]
â   â³ Virtual core XTEST pointer               id=4    [slave  pointer  (2)]
â   â³ mytouchscreen                            id=6    [slave  pointer  (2)]
â£ Virtual core keyboard                        id=3    [master keyboard (2)]
    â³ Virtual core XTEST keyboard              id=5    [slave  keyboard (3)]
&lt;/pre&gt;


==== xinput log ====

    xinput test 6

&lt;pre&gt;
motion a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=53 a[1]=58 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=53 a[1]=58 
motion a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=513 a[1]=91 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=513 a[1]=91 
motion a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=659 a[1]=436 a[2]=0 a[3]=1 a[4]=0 
button release 1 a[0]=659 a[1]=436 
motion a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
button press   1 a[0]=624 a[1]=152 a[2]=0 a[3]=1 a[4]=0 
motion a[0]=577 a[1]=174 
motion a[0]=501 a[1]=203 
motion a[0]=457 a[1]=219 
motion a[0]=411 a[1]=232 
motion a[0]=371 a[1]=240 
motion a[0]=341 a[1]=245 
button release 1 a[0]=341 a[1]=245 
&lt;/pre&gt;</text>
    <sha1>d307459f40a1870b70afbd7bc99e83db48fa9923</sha1>
  </revision>
</page>
<page arvcontinue="20140123030032|898">
  <title>UX32VD</title>
  <ns>0</ns>
  <id>313</id>
  <revision>
    <id>946</id>
    <parentid>890</parentid>
    <timestamp>2014-09-07T23:45:56Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7867" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
(build as module for optional external mic, see [[Audio]])
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;M&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Audio==
/etc/modprobe.d/intel-hda.conf
&lt;pre&gt;
options snd-hda-intel model=laptop-dmic
&lt;/pre&gt;

==Touchpad==
/etc/X11/xorg.conf.d/50-synaptics.conf 
&lt;pre&gt;
Section "InputClass"
      Identifier "Synaptics Touchpad"
      Driver "synaptics"
      MatchISTouchpad "on"
      MatchDriver "synaptics"
#      MatchDevice Path "/dev/input/event*"
#      Option "FastTaps" "1"
      Option "ClickPad"         "true"
      Option "HorizTwoFingerScroll" "on"
      Option "EmulateMidButtonTime" "0"
      Option "SoftButtonAreas"  "50% 0 82% 0 0 0 0 0"
      Option "CircularScrolling"          "on"
      Option "CircScrollTrigger"          "1"
      Option "FingerLow" "6"
      Option "FingerHigh" "13"
      Option "SHMConfig" "on"
EndSection
&lt;/pre&gt;

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>645320da80a1d95fc18a28669592fe7251c610de</sha1>
  </revision>
  <revision>
    <id>947</id>
    <parentid>946</parentid>
    <timestamp>2014-09-07T23:50:51Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7868" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
(build as module for optional external mic, see [[#Audio]])
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;M&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Audio==
/etc/modprobe.d/intel-hda.conf
&lt;pre&gt;
options snd-hda-intel model=laptop-dmic
&lt;/pre&gt;

==Touchpad==
/etc/X11/xorg.conf.d/50-synaptics.conf 
&lt;pre&gt;
Section "InputClass"
      Identifier "Synaptics Touchpad"
      Driver "synaptics"
      MatchISTouchpad "on"
      MatchDriver "synaptics"
#      MatchDevice Path "/dev/input/event*"
#      Option "FastTaps" "1"
      Option "ClickPad"         "true"
      Option "HorizTwoFingerScroll" "on"
      Option "EmulateMidButtonTime" "0"
      Option "SoftButtonAreas"  "50% 0 82% 0 0 0 0 0"
      Option "CircularScrolling"          "on"
      Option "CircScrollTrigger"          "1"
      Option "FingerLow" "6"
      Option "FingerHigh" "13"
      Option "SHMConfig" "on"
EndSection
&lt;/pre&gt;

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>23217587b21c90b4c395a20a7de8b375343fbb0e</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>949</id>
    <parentid>704</parentid>
    <timestamp>2014-10-26T23:34:54Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>MediaWiki upgraded</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4248" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>3815c2aee51fbdc7dee26b988b278e6a4705a736</sha1>
  </revision>
  <revision>
    <id>961</id>
    <parentid>949</parentid>
    <timestamp>2014-10-28T16:18:07Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Erik|Erik]] ([[User talk:Erik|talk]]) to last revision by [[User:Rworkman|Rworkman]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3438" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>6b3b81a3a9d0d4d69d7c37ee6df9263adf3cfe14</sha1>
  </revision>
  <revision>
    <id>962</id>
    <parentid>961</parentid>
    <timestamp>2014-10-28T16:18:50Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Rworkman|Rworkman]] ([[User talk:Rworkman|talk]]) to last revision by [[User:Erik|Erik]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4248" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>3815c2aee51fbdc7dee26b988b278e6a4705a736</sha1>
  </revision>
  <revision>
    <id>989</id>
    <parentid>962</parentid>
    <timestamp>2017-05-12T02:00:40Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>MediaWiki upgraded</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4355" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>83e0e5653d2efd9a882290a2d9161edb54e5f7b7</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Talk:Broadcom Wireless</title>
  <ns>1</ns>
  <id>315</id>
  <revision>
    <id>963</id>
    <parentid>906</parentid>
    <timestamp>2015-01-27T00:06:24Z</timestamp>
    <contributor>
      <username>Dijetlo</username>
      <id>355</id>
    </contributor>
    <comment>/* Issue with ssb as a dependency of the b44 module */ new section</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2050" xml:space="preserve">I just made a couple of relatively minor edits to the page (20140402):
First, admins shouldn't edit files in /lib/modprobe.d/ - those get overwritten on package upgrades; only /etc/modprobe.d/ or /run/modprobe.d/ should be used for local sysadmin edits, as they are not overwritten on upgrades.  However, /run is on a tmpfs, so it is not persistent across reboots; as such, it would applicable for e.g. rules that are auto-generated on system startup based on some nonstable attributes (whether that's a good idea is another discussion entirely, but I think not).  Given all of that, /etc/modprobe.d/ is the best location -- its intent is for sysadmins to copy files from /lib/modprobe.d/ and edit the copies if needed (same-named files in both /etc/modprobe.d/ and /lib/modprobe.d/ are handled such that the file in /etc/modprobe.d/ takes precedence).   This leads up to my second point:
Second, since there's no need in this particular case to override *all* of what's in /lib/modprobe.d/blacklist.conf (you only want to *add* content to it), it's a bit cleaner to just create a new file in /etc/modprobe.d/ with a sensible name and put what you want in it.  --rworkman

== Issue with ssb as a dependency of the b44 module ==

Copying /lib/modprobe.d/bcm43xx.conf to /etc/modprobe.d/bcm43xx.conf and then adding the blacklist entries there worked except for the ssb module. It seems ssb is a dependency of module b44 and is being successfully loaded which blocked the function of the wl module.
The fix was to run sbo packages b43-fwcutter and b43-firmware.

This page is a valuable resource for checking compliance.
http://linuxwireless.org/en/users/Drivers/b43/

Does anybody mind if I add a section referencing that? At the check where the reader runs the blacklisted modules in lsmod expecting a null return, put a fork in there and suggest if he gets a value after blacklisting and reboot, try the b43-fwcutter/b43-firmware approach.
Or he might check for b44 at the outset and opt for the sbo packages if it's loaded with ssb as a dependency.</text>
    <sha1>c12eff622dff14a532add278efc253c51abc8cd5</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Cgroups with KVM and Libvirt</title>
  <ns>0</ns>
  <id>319</id>
  <revision>
    <id>964</id>
    <timestamp>2015-05-11T14:59:09Z</timestamp>
    <contributor>
      <username>Crudo</username>
      <id>71</id>
    </contributor>
    <comment>Created page with "=Using cgroups in Slackware with KVM/Libvirt=  Hello friends, I’ve been using KVM a lot of months until now and every new host server that I create I need to change the way..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1116" xml:space="preserve">=Using cgroups in Slackware with KVM/Libvirt=

Hello friends, I’ve been using KVM a lot of months until now and every new host server that I create I need to change the way of how Slackware seems to create cgroups, libvirt doesn’t function very good if you don’t create specific directories in ‘/sys/fs/cgroup’ tree. So, to do that for me I made this script below

&lt;pre&gt;# cat /etc/rc.d/rc.cgroup

#!/bin/sh
#
# /etc/rc.d/rc.cgroup: cgroups init script
# Alexandre Mulatinho &lt;alex@mulatinho.net&gt;
# Unmount /sys/fs/cgroup
umount /sys/fs/cgroup

# Mount cgroup_root in /sys/fs/cgroup
mount -t tmpfs -o mode=755,rw cgroup_root /sys/fs/cgroup/

# Mount all the subsystems available in /sys/fs/cgroup as individual directory
for i in $(lssubsys -a);
do
        mkdir -pv /sys/fs/cgroup/$i
        mount -v -t cgroup -o $i $i /sys/fs/cgroup/$i
done

# chmod u+x /etc/rc.d/rc.cgroup&lt;/pre&gt;

And now everytime my slackware system boot, my cgroups tree are build in right way that KVM and libvirt can use him to manipulate things like memory, cpu, io, disk, etc. Hope it helps someone else :-)

[[Category:Tutorials]]</text>
    <sha1>caad596c06bf5d1399a5132dd8323a48975453ea</sha1>
  </revision>
  <revision>
    <id>965</id>
    <parentid>964</parentid>
    <timestamp>2015-05-18T00:24:05Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>/* Using cgroups in Slackware with KVM/Libvirt */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1995" xml:space="preserve">=Using cgroups in Slackware with KVM/Libvirt=

Hello friends, I’ve been using KVM a lot of months until now and every new host server that I create I need to change the way of how Slackware seems to create cgroups, libvirt doesn’t function very good if you don’t create specific directories in ‘/sys/fs/cgroup’ tree. So, to do that for me I made this script below

&lt;pre&gt;# cat /etc/rc.d/rc.cgroup

#!/bin/sh
#
# /etc/rc.d/rc.cgroup: cgroups init script
# Alexandre Mulatinho &lt;alex@mulatinho.net&gt;
# Unmount /sys/fs/cgroup
umount /sys/fs/cgroup

# Mount cgroup_root in /sys/fs/cgroup
mount -t tmpfs -o mode=755,rw cgroup_root /sys/fs/cgroup/

# Mount all the subsystems available in /sys/fs/cgroup as individual directory
for i in $(lssubsys -a);
do
        mkdir -pv /sys/fs/cgroup/$i
        mount -v -t cgroup -o $i $i /sys/fs/cgroup/$i
done

# chmod u+x /etc/rc.d/rc.cgroup&lt;/pre&gt;

And now everytime my slackware system boot, my cgroups tree are build in right way that KVM and libvirt can use him to manipulate things like memory, cpu, io, disk, etc. Hope it helps someone else :-)

* EDIT: (from rworkman)
This is not really the place to have such a question, but I don't find this to be necessary here (on a Slackware 14.1 system):
&lt;pre&gt;
root@fs:~# grep cgroup /proc/mounts 
cgroup_root /sys/fs/cgroup tmpfs rw,relatime,mode=755 0 0
cpuset /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0
cpu /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0
cpuacct /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0
blkio /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0
memory /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
devices /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0
freezer /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0
net_cls /sys/fs/cgroup/net_cls cgroup rw,relatime,net_cls 0 0
perf_event /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0
net_prio /sys/fs/cgroup/net_prio cgroup rw,relatime,net_prio 0 0
&lt;/pre&gt;
* END EDIT

[[Category:Tutorials]]</text>
    <sha1>6219ae8cd0bb5590861ceb06529c56566f58bc26</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>UX32VD</title>
  <ns>0</ns>
  <id>313</id>
  <revision>
    <id>966</id>
    <parentid>947</parentid>
    <timestamp>2015-09-23T19:23:39Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>Added fan control</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8063" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
(build as module for optional external mic, see [[#Audio]])
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;M&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Audio==
/etc/modprobe.d/intel-hda.conf
&lt;pre&gt;
options snd-hda-intel model=laptop-dmic
&lt;/pre&gt;

==Touchpad==
/etc/X11/xorg.conf.d/50-synaptics.conf 
&lt;pre&gt;
Section "InputClass"
      Identifier "Synaptics Touchpad"
      Driver "synaptics"
      MatchISTouchpad "on"
      MatchDriver "synaptics"
#      MatchDevice Path "/dev/input/event*"
#      Option "FastTaps" "1"
      Option "ClickPad"         "true"
      Option "HorizTwoFingerScroll" "on"
      Option "EmulateMidButtonTime" "0"
      Option "SoftButtonAreas"  "50% 0 82% 0 0 0 0 0"
      Option "CircularScrolling"          "on"
      Option "CircScrollTrigger"          "1"
      Option "FingerLow" "6"
      Option "FingerHigh" "13"
      Option "SHMConfig" "on"
EndSection
&lt;/pre&gt;

==Fan control==
https://github.com/daringer/asus-fan - not working with kernel 3.10.x

old modules:
https://gist.github.com/felipec/6169047
https://gist.github.com/daringer/721e2cea17b570512097

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme Calandrini]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>2b3fe352af6450e740f2a520821aa53ee7027097</sha1>
  </revision>
  <revision>
    <id>976</id>
    <parentid>966</parentid>
    <timestamp>2015-11-05T18:48:06Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8052" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
(build as module for optional external mic, see [[#Audio]])
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;M&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Audio==
/etc/modprobe.d/intel-hda.conf
&lt;pre&gt;
options snd-hda-intel model=laptop-dmic
&lt;/pre&gt;

==Touchpad==
/etc/X11/xorg.conf.d/50-synaptics.conf 
&lt;pre&gt;
Section "InputClass"
      Identifier "Synaptics Touchpad"
      Driver "synaptics"
      MatchISTouchpad "on"
      MatchDriver "synaptics"
#      MatchDevice Path "/dev/input/event*"
#      Option "FastTaps" "1"
      Option "ClickPad"         "true"
      Option "HorizTwoFingerScroll" "on"
      Option "EmulateMidButtonTime" "0"
      Option "SoftButtonAreas"  "50% 0 82% 0 0 0 0 0"
      Option "CircularScrolling"          "on"
      Option "CircScrollTrigger"          "1"
      Option "FingerLow" "6"
      Option "FingerHigh" "13"
      Option "SHMConfig" "on"
EndSection
&lt;/pre&gt;

==Fan control==
https://github.com/daringer/asus-fan - not working with kernel 3.10.x

old modules:
https://gist.github.com/felipec/6169047
https://gist.github.com/daringer/721e2cea17b570512097

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>fe225aa56263301be8e10c47127257574b22e0d3</sha1>
  </revision>
  <revision>
    <id>979</id>
    <parentid>976</parentid>
    <timestamp>2015-11-05T18:54:44Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>/* Contributors */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8052" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

'''SATA:''':&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
(build as module for optional external mic, see [[#Audio]])
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;M&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Audio==
/etc/modprobe.d/intel-hda.conf
&lt;pre&gt;
options snd-hda-intel model=laptop-dmic
&lt;/pre&gt;

==Touchpad==
/etc/X11/xorg.conf.d/50-synaptics.conf 
&lt;pre&gt;
Section "InputClass"
      Identifier "Synaptics Touchpad"
      Driver "synaptics"
      MatchISTouchpad "on"
      MatchDriver "synaptics"
#      MatchDevice Path "/dev/input/event*"
#      Option "FastTaps" "1"
      Option "ClickPad"         "true"
      Option "HorizTwoFingerScroll" "on"
      Option "EmulateMidButtonTime" "0"
      Option "SoftButtonAreas"  "50% 0 82% 0 0 0 0 0"
      Option "CircularScrolling"          "on"
      Option "CircScrollTrigger"          "1"
      Option "FingerLow" "6"
      Option "FingerHigh" "13"
      Option "SHMConfig" "on"
EndSection
&lt;/pre&gt;

==Fan control==
https://github.com/daringer/asus-fan - not working with kernel 3.10.x

old modules:
https://gist.github.com/felipec/6169047
https://gist.github.com/daringer/721e2cea17b570512097

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.com/User:mega-lnx Guilherme]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>55b1867207d0483b60ae60a64fd5337a058caf5a</sha1>
  </revision>
  <revision>
    <id>983</id>
    <parentid>979</parentid>
    <timestamp>2016-04-13T19:30:33Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>Added append entry for kernel booting</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8097" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS UX32VD==


==Hardware==
lspci&lt;pre&gt;
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] (rev ff)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235 (rev 24)
&lt;/pre&gt;

lsusb&lt;pre&gt;
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Bus 002 Device 003: ID 04f2:b330 Chicony Electronics Co., Ltd Asus 720p CMOS webcam
Bus 002 Device 005: ID 8087:07da Intel Corp. 
&lt;/pre&gt;

==Kernel Configuration==
Linux Kernel 3.10.x

Processor
&lt;pre&gt;
-&gt; Processor type and features
Processor family
(X) Core 2/newer Xeon
&lt;/pre&gt;

SATA:
&lt;pre&gt;
[*]   ATA ACPI Support
[*]   SATA Port Multiplier support
&lt;*&gt;   AHCI SATA support
[*]   ATA SFF support (for legacy IDE and PATA)
[*]     ATA BMDMA support
&lt;*&gt;       Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
&lt;*&gt;       Intel SCH PATA support
&lt;*&gt;     Intel PATA MPIIX support
&lt;M&gt;     ACPI firmware driver for PATA
&lt;/pre&gt;

Ethernet:
&lt;pre&gt;
-&gt; Device Drivers
-&gt; Network device support
-&gt; USB Network Adapters
&lt;M&gt;   ASIX AX88xxx Based USB 2.0 Ethernet Adapters
&lt;M&gt;   ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet
&lt;/pre&gt;

I2C:
&lt;pre&gt;
-&gt; Device Drivers -&gt; I2C support -&gt; I2C Hardware Bus support
&lt;M&gt; Intel 82801 (ICH/PCH)
&lt;M&gt; Intel SCH SMBus 1.0
&lt;M&gt; Intel iSMT SMBus Controller   
&lt;M&gt; SMBus Control Method Interface
 
Device Drivers &gt; GPIO Support
[*]   /sys/class/gpio/... (sysfs interface)
&lt;*&gt;   Generic memory-mapped GPIO controller support (MMIO platform device)
&lt;M&gt;   Intel ICH GPIO
&lt;/pre&gt;
 
Touchpad:
&lt;pre&gt;
Device Drivers -&gt; Input device support -&gt; Mice -&gt;
&lt;*&gt;   PS/2 mouse
[*]     ALPS PS/2 mouse protocol extension
[*]     Logitech PS/2++ mouse protocol extension
[*]     Synaptics PS/2 mouse protocol extension
[*]     Cypress PS/2 mouse protocol extension
[*]     Elantech PS/2 protocol extension
&lt;M&gt;   Synaptics I2C Touchpad support
&lt;M&gt;   Synaptics USB device support
&lt;/pre&gt;
 
Graphics support:
&lt;pre&gt;
Device Drivers -&gt;
&lt;*&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics
[*]   Enable modesetting on intel by default
&lt;/pre&gt;
 
Sound: Intel HD Audio
(build as module for optional external mic, see [[#Audio]])
&lt;pre&gt;
-&gt; Device Drivers -&gt; Sound card support -&gt; Advanced Linux Sound Architecture -&gt; PCI sound devices
&lt;*&gt; Sound card support  ---&gt;
[*]   Preclaim OSS device numbers
&lt;*&gt;   Advanced Linux Sound Architecture  ---&gt;
[*]   PCI sound devices  ---&gt;
&lt;M&gt;   Intel HD Audio  ---&gt;
(2048) Pre-allocated buffer size for HD-audio driver
-*-   Build hwdep interface for HD-audio driver
-*-     Allow dynamic codec reconfiguration
[ ]   Support digital beep via input layer
[*]   Support jack plugging notification via input layer
[*]   Support initialization patch loading for HD-audio
[*]   Build Realtek HD-audio codec support
[*]   Build Analog Device HD-audio codec support
[*]   Build IDT/Sigmatel HD-audio codec support
[*]   Build VIA HD-audio codec support
[*]   Build HDMI/DisplayPort HD-audio codec support
[*]   Build Cirrus Logic codec support
[*]   Build Conexant HD-audio codec support
[*]   Build Creative CA0110-IBG codec support
[*]   Build Creative CA0132 codec support
[*]     Support new DSP code for CA0132 codec
[*]   Build C-Media HD-audio codec support
[*]   Build Silicon Labs 3054 HD-modem codec support
-*-   Enable generic HD-audio codec parser
(600) Default time-out for HD-audio power-save mode
&lt;/pre&gt;
 
WIFI:
&lt;pre&gt;
Device Drivers -&gt; Network device support -&gt; Wireless LAN
[*] Network device support  ---&gt;
[*]   Wireless LAN  ---&gt;
&lt;*&gt;   Intel Wireless WiFi Next Gen AGN - Wireless-N/Advanced-N/Ultimate-N (iwlwifi)
&lt;*&gt;     Intel Wireless WiFi DVM Firmware support
&lt;*&gt;     Intel Wireless WiFi MVM Firmware support
[*]   iwlwifi experimental P2P support (NEW)
&lt;/pre&gt; 

USB:
&lt;pre&gt;
Device Drivers -&gt; USB support
&lt;*&gt;     xHCI HCD (USB 3.0) support
&lt;*&gt;     EHCI HCD (USB 2.0) support
&lt;*&gt;     OHCI HCD support
&lt;*&gt;     UHCI HCD (most Intel and VIA) support
&lt;/pre&gt;
 
Function keys:
&lt;pre&gt;
Device Drivers -&gt;
-*- X86 Platform Specific Device Drivers  ---&gt;
&lt;*&gt;   ASUS WMI Driver
&lt;*&gt;     Asus Notebook WMI Driver
&lt; &gt;     Eee PC WMI Driver
&lt;*&gt;   WMI
&lt;*&gt;   WMI support for MXM Laptop Graphics
Although function keys need a  i2c support with i2c-i801 module
&lt;/pre&gt;
 
IOMMU:&lt;pre&gt;
Device Drivers -&gt; IOMMU Hardware Support
[*]   Support for Intel IOMMU using DMA Remapping Devices
[*]     Enable Intel DMA Remapping Devices by default
[*]   Support for Interrupt Remapping
&lt;/pre&gt;

==Audio==
/etc/modprobe.d/intel-hda.conf
&lt;pre&gt;
options snd-hda-intel model=laptop-dmic
&lt;/pre&gt;

==Touchpad==
/etc/X11/xorg.conf.d/50-synaptics.conf 
&lt;pre&gt;
Section "InputClass"
      Identifier "Synaptics Touchpad"
      Driver "synaptics"
      MatchISTouchpad "on"
      MatchDriver "synaptics"
#      MatchDevice Path "/dev/input/event*"
#      Option "FastTaps" "1"
      Option "ClickPad"         "true"
      Option "HorizTwoFingerScroll" "on"
      Option "EmulateMidButtonTime" "0"
      Option "SoftButtonAreas"  "50% 0 82% 0 0 0 0 0"
      Option "CircularScrolling"          "on"
      Option "CircScrollTrigger"          "1"
      Option "FingerLow" "6"
      Option "FingerHigh" "13"
      Option "SHMConfig" "on"
EndSection
&lt;/pre&gt;


==ACPI OSI==
acpi_osi='!Windows 2012'


==Fan control==
https://github.com/daringer/asus-fan - not working with kernel 3.10.x

old modules:
https://gist.github.com/felipec/6169047
https://gist.github.com/daringer/721e2cea17b570512097

==Ambient Light Sensor==
See: [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller here]

In order to use the Ambient Light Sensor it is necessary to insert the module (insmod als.ko) and the acpi call module (insmod acpi_call.ko).
The acpi_call module is required to enable and disable the sensor.

Finally run the als-controller to create the service for management of brightness.

==Contributors==

*[http://slackwiki.com/User:mega-lnx Guilherme]

==External Links/ References==
* [https://github.com/mkottman/acpi_call/ acpi_call]
* [https://github.com/danieleds/Asus-Zenbook-Ambient-Light-Sensor-Controller/ als-controller]</text>
    <sha1>48a6bad76252dcebd16becdd62ff4dc3434b2351</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Mobilepowerhouse</title>
  <ns>0</ns>
  <id>320</id>
  <revision>
    <id>968</id>
    <timestamp>2015-10-28T13:23:32Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>Notes for creating a Slackware server for kvm virtualization</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="54" xml:space="preserve">==== Slackware kvm server ====

==== Thin clients ====</text>
    <sha1>49b4883cbfbb188bf6297e4f6fc8be1789f23e3b</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>EeePC 1215N</title>
  <ns>0</ns>
  <id>314</id>
  <revision>
    <id>969</id>
    <parentid>888</parentid>
    <timestamp>2015-11-05T18:25:18Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>add bios description</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1124" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

'''Ethernet:'''

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

'''Wifi:''' 

The wireless card has two controller solutions

Proprietary driver:

The Broadcom STA driver can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].

or

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
&lt;/pre&gt;

'''BIOS'''
 For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"
 Last bios version: 0503 (09/07/10)</text>
    <sha1>78110e67663c306ac00253149cd2d52febbaee77</sha1>
  </revision>
  <revision>
    <id>970</id>
    <parentid>969</parentid>
    <timestamp>2015-11-05T18:39:14Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>/* Slackware on an ASUS eeepc 1215N */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1780" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

'''Ethernet:'''

 Network nic: Atheros AR8152

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

Proprietary driver:
tar xcvf arl...-x.x.x.tar.gz
cd ark...-x.x.x/src
ln -s config.h autoconf.h
make
insmod arl1e/arl1c


'''Wifi:''' 

The BCM4313 wireless card has two controller solutions, the wl and the brcmsmac (brcm80211).

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
&lt;/pre&gt;

or

Proprietary driver:

The Broadcom STA driver, can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].
 tar zxvf hybrid-portsrc....tar.gz
 make
 make install

Optional:
Compiles against desired API
 make API=WEXT
 make API=CFG80211

Kernel 3.3.2 error
changes the follow line 
.ndo_set_multicast_list=
to
.ndo_set_rx_node=


Loading module
rmmod b43   | echo "blacklist b43" &gt;&gt; /etc/modprobe.d/blacklist
rmmod ssb   | echo "blacklist ssb" &gt;&gt; /etc/modprobe.d/blacklist
rmmod wl
rmmod bcma

modprobe lib80211
modprobe lib80211_crypt_tkip (optional)
modprobe wl


'''BIOS'''
 For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"
 Last bios version: 0503 (09/07/10)</text>
    <sha1>4fb56f0fbc5a69be2a8230e46528022949370852</sha1>
  </revision>
  <revision>
    <id>971</id>
    <parentid>970</parentid>
    <timestamp>2015-11-05T18:39:52Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>/* Slackware on an ASUS eeepc 1215N */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1778" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

'''Ethernet:'''
Network nic: Atheros AR8152

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

Proprietary driver:
tar xcvf arl...-x.x.x.tar.gz
cd ark...-x.x.x/src
ln -s config.h autoconf.h
make
insmod arl1e/arl1c


'''Wifi:''' 

The BCM4313 wireless card has two controller solutions, the wl and the brcmsmac (brcm80211).

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
&lt;/pre&gt;

or

Proprietary driver:

The Broadcom STA driver, can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].
 tar zxvf hybrid-portsrc....tar.gz
 make
 make install

Optional:
Compiles against desired API
 make API=WEXT
 make API=CFG80211

Kernel 3.3.2 error
changes the follow line 
.ndo_set_multicast_list=
to
.ndo_set_rx_node=


Loading module
rmmod b43   | echo "blacklist b43" &gt;&gt; /etc/modprobe.d/blacklist
rmmod ssb   | echo "blacklist ssb" &gt;&gt; /etc/modprobe.d/blacklist
rmmod wl
rmmod bcma

modprobe lib80211
modprobe lib80211_crypt_tkip (optional)
modprobe wl


'''BIOS'''
 For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"
 Last bios version: 0503 (09/07/10)</text>
    <sha1>51cd966874d104fca07e557b724c778675b780e5</sha1>
  </revision>
  <revision>
    <id>972</id>
    <parentid>971</parentid>
    <timestamp>2015-11-05T18:43:22Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>/* Slackware on an ASUS eeepc 1215N */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1882" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

'''Ethernet:'''
Network nic: Atheros AR8152

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

Building the proprietary driver:
 tar xcvf arl...-x.x.x.tar.gz
 cd ark...-x.x.x/src
 ln -s config.h autoconf.h
 make
 insmod arl1e/arl1c


'''Wifi:''' 

The BCM4313 wireless card has two controller solutions, the wl and the brcmsmac (brcm80211).

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
Broadcom specif AMBA
   &lt; M &gt; BCMA suport
    [ M ] Support for BCMA on PCI-Host bus
&lt;/pre&gt;


or

Proprietary driver:

The Broadcom STA driver, can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].
 tar zxvf hybrid-portsrc....tar.gz
 make
 make install

Optional:
Compiles against desired API
 make API=WEXT
 make API=CFG80211

Kernel 3.3.2 error
changes the follow line 
.ndo_set_multicast_list=
to
.ndo_set_rx_node=


Loading module
rmmod b43   | echo "blacklist b43" &gt;&gt; /etc/modprobe.d/blacklist
rmmod ssb   | echo "blacklist ssb" &gt;&gt; /etc/modprobe.d/blacklist
rmmod wl
rmmod bcma

modprobe lib80211
modprobe lib80211_crypt_tkip (optional)
modprobe wl


'''BIOS'''
 For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"
 Last bios version: 0503 (09/07/10)</text>
    <sha1>7e06b450d8d72a37842ad211fa5920d1eb43eb79</sha1>
  </revision>
  <revision>
    <id>973</id>
    <parentid>972</parentid>
    <timestamp>2015-11-05T18:44:12Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>/* Slackware on an ASUS eeepc 1215N */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1885" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

'''Ethernet:'''
Network nic: Atheros AR8152

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

Building the proprietary driver:
 tar xcvf arl...-x.x.x.tar.gz
 cd arl...-x.x.x/src
 ln -s config.h autoconf.h
 make
 insmod arl1e/arl1c


'''Wifi:''' 

The BCM4313 wireless card has two controller solutions, the wl and the brcmsmac (brcm80211).

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
Broadcom specif AMBA
   &lt; M &gt; BCMA suport
    [ M ] Support for BCMA on PCI-Host bus
&lt;/pre&gt;


or

Proprietary driver:

The Broadcom STA driver, can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].
 tar zxvf hybrid-portsrc....tar.gz
 make
 make install

Optional:
Compiles against desired API
 make API=WEXT
 make API=CFG80211

Kernel 3.3.2 error
changes the follow line 
.ndo_set_multicast_list=
to
.ndo_set_rx_node=


Loading module
rmmod b43   | echo "blacklist b43" &gt;&gt; /etc/modprobe.d/blacklist
rmmod ssb   | echo "blacklist ssb" &gt;&gt; /etc/modprobe.d/blacklist
rmmod wl
rmmod bcma

modprobe lib80211
modprobe lib80211_crypt_tkip (optional)
modprobe wl


'''BIOS'''
For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"

 Lastest bios version: 0503 (09/07/10)</text>
    <sha1>eab1d9b1542227df832d9e7ffed8e09ee5e60d12</sha1>
  </revision>
  <revision>
    <id>974</id>
    <parentid>973</parentid>
    <timestamp>2015-11-05T18:45:33Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>/* Slackware on an ASUS eeepc 1215N */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1913" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

'''Ethernet:'''
Network nic: Atheros AR8152

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

Building the proprietary driver:
 tar xcvf arl...-x.x.x.tar.gz
 cd arl...-x.x.x/src
 ln -s config.h autoconf.h
 make
 insmod arl1e/arl1c


'''Wifi:''' 

The BCM4313 wireless card has two controller solutions, the wl and the brcmsmac (brcm80211).

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
Broadcom specif AMBA
   &lt; M &gt; BCMA suport
    [ M ] Support for BCMA on PCI-Host bus
&lt;/pre&gt;


or

Proprietary driver:

The Broadcom STA driver, can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].
 tar zxvf hybrid-portsrc....tar.gz
 make
 make install

Optional:
Compiles against desired API
 make API=WEXT
 make API=CFG80211

Kernel 3.3.2 error
changes the follow line 
.ndo_set_multicast_list=
to
.ndo_set_rx_node=

Unload Linux modules:
 rmmod b43   | echo "blacklist b43" &gt;&gt; /etc/modprobe.d/blacklist
 rmmod ssb   | echo "blacklist ssb" &gt;&gt; /etc/modprobe.d/blacklist
 rmmod wl
 rmmod bcma

Loading module:
 modprobe lib80211
 modprobe lib80211_crypt_tkip (optional)
 modprobe wl


'''BIOS'''
For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"

 Lastest bios version: 0503 (09/07/10)</text>
    <sha1>64718303f2d14570beaf36337ce12dc51e769c37</sha1>
  </revision>
  <revision>
    <id>975</id>
    <parentid>974</parentid>
    <timestamp>2015-11-05T18:47:21Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <comment>/* Slackware on an ASUS eeepc 1215N */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1943" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

==== Device modules ====

'''Ethernet:'''
Network nic: Atheros AR8152

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

Building the proprietary driver:
 tar xcvf arl...-x.x.x.tar.gz
 cd arl...-x.x.x/src
 ln -s config.h autoconf.h
 make
 insmod arl1e/arl1c


'''Wifi:''' 

The BCM4313 wireless card has two controller solutions, the wl and the brcmsmac (brcm80211).

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
Broadcom specif AMBA
   &lt; M &gt; BCMA suport
    [ M ] Support for BCMA on PCI-Host bus
&lt;/pre&gt;


or

Proprietary driver:

The Broadcom STA driver, can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].
 tar zxvf hybrid-portsrc....tar.gz
 make
 make install

Optional:
Compiles against desired API
 make API=WEXT
 make API=CFG80211

Kernel 3.3.2 error
changes the follow line 
.ndo_set_multicast_list=
to
.ndo_set_rx_node=

Unload Linux modules:
 rmmod b43   | echo "blacklist b43" &gt;&gt; /etc/modprobe.d/blacklist
 rmmod ssb   | echo "blacklist ssb" &gt;&gt; /etc/modprobe.d/blacklist
 rmmod wl
 rmmod bcma

Loading module:
 modprobe lib80211
 modprobe lib80211_crypt_tkip (optional)
 modprobe wl


==== BIOS ====

For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"

 Latest bios version: 0503 (09/07/10)</text>
    <sha1>bc74d99e0ec54a46fb74500dd9baaab87002869d</sha1>
  </revision>
  <revision>
    <id>977</id>
    <parentid>975</parentid>
    <timestamp>2015-11-05T18:51:07Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2003" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

== Device modules ==

====Ethernet====
Network nic: Atheros AR8152

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

Building the proprietary driver:
 tar xcvf arl...-x.x.x.tar.gz
 cd arl...-x.x.x/src
 ln -s config.h autoconf.h
 make
 insmod arl1e/arl1c


====Wifi====

The BCM4313 wireless card has two controller solutions, the wl and the brcmsmac (brcm80211).

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
Broadcom specif AMBA
   &lt; M &gt; BCMA suport
    [ M ] Support for BCMA on PCI-Host bus
&lt;/pre&gt;


or

Proprietary driver:

The Broadcom STA driver, can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].
 tar zxvf hybrid-portsrc....tar.gz
 make
 make install

Optional:
Compiles against desired API
 make API=WEXT
 make API=CFG80211

Kernel 3.3.2 error
changes the follow line 
.ndo_set_multicast_list=
to
.ndo_set_rx_node=

Unload Linux modules:
 rmmod b43   | echo "blacklist b43" &gt;&gt; /etc/modprobe.d/blacklist
 rmmod ssb   | echo "blacklist ssb" &gt;&gt; /etc/modprobe.d/blacklist
 rmmod wl
 rmmod bcma

Loading module:
 modprobe lib80211
 modprobe lib80211_crypt_tkip (optional)
 modprobe wl


== BIOS ==

For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"

 Latest bios version: 0503 (09/07/10)

==Contributors==

*[http://slackwiki.org/User:mega-lnx Guilherme]</text>
    <sha1>a63cd153833d32c6ac61a1719ea3700459bbd911</sha1>
  </revision>
  <revision>
    <id>980</id>
    <parentid>977</parentid>
    <timestamp>2015-11-05T18:56:08Z</timestamp>
    <contributor>
      <username>Mega-lnx</username>
      <id>347</id>
    </contributor>
    <minor/>
    <comment>/* Contributors */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2003" xml:space="preserve">[[Category:Hardware]]
==Slackware on an ASUS eeepc 1215N ==

== Device modules ==

====Ethernet====
Network nic: Atheros AR8152

- Kernel version 2.6.x
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet (1000 Mbit) ---&gt;
        &lt; x &gt; Atheros L1C Gigabit Ethernet
&lt;/pre&gt;
- Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network Device Support ---&gt;
    [ x ] Ethernet driver support ---&gt;
      [ x ] Atheros Devices
        &lt; x &gt; Atheros L1C Gigabit Ethernet support
&lt;/pre&gt;

Building the proprietary driver:
 tar xcvf arl...-x.x.x.tar.gz
 cd arl...-x.x.x/src
 ln -s config.h autoconf.h
 make
 insmod arl1e/arl1c


====Wifi====

The BCM4313 wireless card has two controller solutions, the wl and the brcmsmac (brcm80211).

Kernel version 3.0.x +
&lt;pre&gt;
Device Drivers ---&gt;
  [ x ] Network device support ---&gt;
     [ x ] Wireless LAN ---&gt;
     [ M ] USB ZD1201 based Wireless device support
     [ M ] Broadcom IEEE802.11n PCIe SoftMAC WLAN driver
     [ M ] IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
Broadcom specif AMBA
   &lt; M &gt; BCMA suport
    [ M ] Support for BCMA on PCI-Host bus
&lt;/pre&gt;


or

Proprietary driver:

The Broadcom STA driver, can be downloaded [http://www.broadcom.com/support/802.11/linux_sta.php here].
 tar zxvf hybrid-portsrc....tar.gz
 make
 make install

Optional:
Compiles against desired API
 make API=WEXT
 make API=CFG80211

Kernel 3.3.2 error
changes the follow line 
.ndo_set_multicast_list=
to
.ndo_set_rx_node=

Unload Linux modules:
 rmmod b43   | echo "blacklist b43" &gt;&gt; /etc/modprobe.d/blacklist
 rmmod ssb   | echo "blacklist ssb" &gt;&gt; /etc/modprobe.d/blacklist
 rmmod wl
 rmmod bcma

Loading module:
 modprobe lib80211
 modprobe lib80211_crypt_tkip (optional)
 modprobe wl


== BIOS ==

For updating the bios using the EZ-Flash tool you should create a fat16 usb stick and then copy the rom named as "1215N.ROM"

 Latest bios version: 0503 (09/07/10)

==Contributors==

*[http://slackwiki.com/User:mega-lnx Guilherme]</text>
    <sha1>a7836600f8f5a7b8d044652dd2774ca192a5ef0a</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Btfirmware-nonfree</title>
  <ns>0</ns>
  <id>321</id>
  <revision>
    <id>981</id>
    <timestamp>2015-11-25T04:15:21Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Created page with "I recently was presented with a Thinkpad T430s containing a Broadcom BCM20702 bluetooth chip, and bluetooth wouldn't work at all on it.  &lt;code&gt;$ lsusb Bus 003 Device 009: ID 0..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5386" xml:space="preserve">I recently was presented with a Thinkpad T430s containing a Broadcom BCM20702 bluetooth chip, and bluetooth wouldn't work at all on it.

&lt;code&gt;$ lsusb
Bus 003 Device 009: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]
&lt;/code&gt;

On boot, I saw this in /var/log/syslog: &lt;br /&gt;
&lt;code&gt;Nov 24 13:37:35 liberty kernel: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2&lt;/code&gt; &lt;br /&gt;
Sure enough, /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd did not exist.

After a bit of research, I determined that nobody had already written clear instructions on just how to obtain the needed firmware. There were a few results with links to different firmware that someone had already obtained from some mysterious source, and vague references about "get it from your Windows system" and such, but well, I don't have a Windows system.

I went to the Lenovo support site, downloaded the bluetooth driver file (currently located at https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/g4wb12ww.exe but of course, this link will not always be valid), and poked around a bit in its contents. To do that, you'll first need to get innoextract (see http://constexpr.org/innoextract/ or search SlackBuilds.org for it).
&lt;br /&gt;
&lt;code&gt;
root@liberty:~/fw# ls &lt;br /&gt;
g4wb12ww.exe &lt;br /&gt;
root@liberty:~/fw# innoextract g4wb12ww.exe &lt;br /&gt;
...lots of output, all extracted to an "app/" directory... &lt;br /&gt;
&lt;/code&gt; &lt;br /&gt;

Now to see if we can find the important bits in here... I notice that the firmware expected to be loaded has "0a5c-21e6" in the name, and the usb ID of the bluetooth hardware is "0a5c:21e6" so let's poke around and see if we can find anything with that name: &lt;br /&gt; &lt;br /&gt;
&lt;code&gt;find app/ -name "*0a5c*" -o -name "*0A5C*"&lt;/code&gt; &lt;br /&gt; &lt;br /&gt;
Hmm, no output. Okay. &lt;br /&gt; &lt;br /&gt;
&lt;code&gt; &lt;br /&gt;
root@liberty:~/fw#grep -Eir 0a5c.*21e6 . &lt;br /&gt;
Binary file ./app/Win64/BTW.msi matches &lt;br /&gt;
./app/Win64/bcbtums-win7x64-brcm.inf:%BRCM20702Thinkpad.DeviceDesc%=RAMUSB21E6,  USB\VID_0A5C&amp;PID_21E6       ; 20702 non-UHE Lenovo Japan &lt;br /&gt;
Binary file ./app/Win32/BTW.msi matches &lt;br /&gt;
./app/Win32/bcbtums-win7x86-brcm.inf:%BRCM20702Thinkpad.DeviceDesc%=RAMUSB21E6,  USB\VID_0A5C&amp;PID_21E6       ; 20702 non-UHE Lenovo Japan &lt;br /&gt;
&lt;/code&gt; &lt;br /&gt; &lt;br /&gt;
Well, I don't want to poke around in binary files too much, but I know that .inf are plaintext files, so let's look in there. That "DeviceDesc" looks important, so we'll search for that in the .inf file once we get it opened. I use vi, but hopefully you know your editor well enough to do the equivalent, and you'll find something like this: &lt;br /&gt; &lt;br /&gt;

&lt;code&gt;
... &lt;br /&gt;
%BRCM20702Thinkpad.DeviceDesc%=RAMUSB21E6,  USB\VID_0A5C&amp;PID_21E6       ; 20702 non-UHE Lenovo Japan &lt;br /&gt;
... &lt;br /&gt;
;;;;;;;;;;;;;RAMUSB21E6;;;;;;;;;;;;;;;;; &lt;br /&gt;
&lt;br /&gt;
[RAMUSB21E6.CopyList]&lt;br /&gt;
bcbtums.sys&lt;br /&gt;
BCM20702A1_001.002.014.0449.0462.hex&lt;br /&gt;
&lt;br /&gt;
[RAMUSB21E6.NTX86]&lt;br /&gt;
Include=bth.inf&lt;br /&gt;
Needs=BthUsb.NT&lt;br /&gt;
FeatureScore=F0&lt;br /&gt;
CopyFiles=RAMUSB21E6.CopyList&lt;br /&gt;
&lt;br /&gt;
[RAMUSB21E6.NTX86.hw]&lt;br /&gt;
AddReg=RAMUSB21E6.NTX86.hw.reg&lt;br /&gt;
&lt;br /&gt;
[RAMUSB21E6.NTX86.hw.reg]&lt;br /&gt;
HKR,,LowerFilters, 0x00010000, "bcbtums"&lt;br /&gt;
HKR,,%RAMPatchFileName%,0x00000, "BCM20702A1_001.002.014.0449.0462.hex"&lt;br /&gt;
HKR,,%RemoteWakeEnabled%,0x00010001,1&lt;br /&gt;
HKR,,%DeviceRemoteWakeSupported%,0x00010001,1&lt;br /&gt;
&lt;br /&gt;
[RAMUSB21E6.NTX86.Services]&lt;br /&gt;
needs=BthUsb.NT.Services&lt;br /&gt;
AddService=bcbtums,,BCBTUMS_Service_Inst, BTWSECFL_EventLog_Inst&lt;br /&gt;
&lt;br /&gt;
... &lt;br /&gt;
&lt;/code&gt;
&lt;br /&gt;
I happen to know from my research that the firmware files are .hex file, so this line is awesome to see: &lt;br /&gt;
&lt;code&gt;HKR,,%RAMPatchFileName%,0x00000, "BCM20702A1_001.002.014.0449.0462.hex"&lt;/code&gt;
&lt;br /&gt;

Copy that file out of the directory structure into a place that's easier to work with:&lt;br /&gt;
&lt;code&gt;
root@liberty:~/fw# cp app/Win64/BCM20702A1_001.002.014.0449.0462.hex . &lt;br /&gt;
root@liberty:~/fw# ls &lt;br /&gt;
BCM20702A1_001.002.014.0449.0462.hex  app/  g4wb12ww.exe &lt;br /&gt;
&lt;/code&gt;
&lt;br /&gt;
Now we need to put this in a form that the linux kernel expects, so that's where hex2hcd comes in: &lt;br /&gt;
&lt;code&gt;
root@liberty:~/fw# git clone git://github.com/jessesung/hex2hcd.git &lt;br /&gt;
Cloning into 'hex2hcd'...&lt;br /&gt;
remote: Counting objects: 8, done.&lt;br /&gt;
remote: Compressing objects: 100% (7/7), done.&lt;br /&gt;
remote: Total 8 (delta 1), reused 8 (delta 1), pack-reused 0&lt;br /&gt;
Receiving objects: 100% (8/8), 8.71 KiB | 0 bytes/s, done.&lt;br /&gt;
Resolving deltas: 100% (1/1), done.&lt;br /&gt;
Checking connectivity... done.&lt;br /&gt;
root@liberty:~/fw# cd hex2hcd/&lt;br /&gt;
root@liberty:~/fw/hex2hcd# make&lt;br /&gt;
gcc -O2 -march=native    hex2hcd.c   -o hex2hcd&lt;br /&gt;
&lt;/code&gt;

Now we use hex2hcd:
&lt;code&gt;
root@liberty:~/fw/hex2hcd# ./hex2hcd ../BCM20702A1_001.002.014.0449.0462.hex ../BCM20702A1-0a5c-21e6.hcd &lt;br /&gt;
... lots of text and binary data ...&lt;br /&gt;
&lt;/code&gt;

Finally, let's back up a directory, make sure what think is there is actually there, and copy it into place:

&lt;code&gt;
root@liberty:~/fw/hex2hcd# cd ..&lt;br /&gt;
root@liberty:~/fw# ls&lt;br /&gt;
BCM20702A1-0a5c-21e6.hcd  BCM20702A1_001.002.014.0449.0462.hex  app/  g4wb12ww.exe  hex2hcd/&lt;br /&gt;
root@liberty:~/fw# cp BCM20702A1-0a5c-21e6.hcd /lib/firmware/brcm/&lt;br /&gt;
&lt;/code&gt;

The first person who finds this useful is expected to clean up the formatting and such. :-) Enjoy!  -RW</text>
    <sha1>68edaa3440483d8c8b87185bc7476beba3ef1b12</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Bluetooth</title>
  <ns>0</ns>
  <id>70</id>
  <revision>
    <id>982</id>
    <parentid>91</parentid>
    <timestamp>2015-11-25T04:20:11Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Add note re adding nonfree firmware</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13993" xml:space="preserve">[[Category:Tutorials]]

== Introduction ==
This tutorial is meant to simplify the process of configuring a GNU/Linux Distribution, specifically Slackware, to use Bluetooth wireless technology.  I will show you step by step how I setup my system and got Bluetooth functioning.  Since it is unlikely that you have the exact same hardware that I do, you may need to modify a few steps to fit your needs.

== Example System Information ==
This is a list of my specific hardware that applies to this topic.  Do not worry if your's is not exactly the same because you can still use this information to guide you through the process.

;Motherboard (USB Ports)
:[http://www.msicomputer.com/product/p_spec.asp?model=K8N_Neo4_Platinum/SLI MSI Neo4 Platinum/SLI]
;Bluetooth USB Dongle
:[http://www.amazon.com/gp/product/B0001Q5SZ0/103-7636612-6018206?v=glance&amp;n=172282 Kensington Bluetooth USB Adapter (33085)]
;Cell Phone
:[http://www.motorola.com/motoinfo/product/details.jsp?globalObjectId=72 Motorola V551]
;[http://www.slackware.org Slackware-Current (as of 5/31/06)]
;[http://www.kernel.org Kernel 2.6.16.16] (worked on 2.6.15.6 also)

== Kernel Configuration ==
The first step is enabling the drivers for USB and Bluetooth in your kernel.  I'm not sure exactly which kernel version began including Bluez Bluetooth drivers, but my 2.6.15.6 kernel had them.  [http://www.westmaster.com/zidek/p900/bluetooth/ From this page], it looks like 2.6.5 did not have Bluetooth drivers and needed to be patched.  If you are running an older kernel, follow the directions on that page to apply the Bluez patch.  If you are unfamiliar with the kernel configuration/compilation sequence, then check out the [[Kernel26Compilation]] tutorial before proceeding.

=== USB support ===
For the less-advanced user (like myself), it is safe to go through and answer `M` to everything that you can, and `Y` to everything that can not take `M`.  You should not enable any of the "debug" options, I'm not 100% sure why, but I'm pretty sure that these options will give you verbose output that is only needed for kernel hackers.  Below, you can see the options I have set in my .config file for my kernel.  The options listed are just those that I thought pertained to getting my USB ports working and able to recognize my USB dongle.
 #
 # USB support
 #
 CONFIG_USB_ARCH_HAS_HCD=y
 CONFIG_USB_ARCH_HAS_OHCI=y
 CONFIG_USB=y
 # CONFIG_USB_DEBUG is not set
 #
 # Miscellaneous USB options
 #
 CONFIG_USB_DEVICEFS=y
 CONFIG_USB_BANDWIDTH=y
 # CONFIG_USB_DYNAMIC_MINORS is not set
 # CONFIG_USB_SUSPEND is not set
 # CONFIG_USB_OTG is not set
 #
 # USB Host Controller Drivers
 #
 CONFIG_USB_EHCI_HCD=m
 CONFIG_USB_EHCI_SPLIT_ISO=y
 CONFIG_USB_EHCI_ROOT_HUB_TT=y
 CONFIG_USB_ISP116X_HCD=m
 CONFIG_USB_OHCI_HCD=y
 # CONFIG_USB_OHCI_BIG_ENDIAN is not set
 CONFIG_USB_OHCI_LITTLE_ENDIAN=y
 CONFIG_USB_UHCI_HCD=y
 CONFIG_USB_SL811_HCD=m

=== Bluetooth support ===
Again, it is safe to enable everything that says "Bluetooth" as a Module.  Below are the options from my .config file that I thought might be relevant.
 #
 # FIR device drivers
 #
 CONFIG_USB_IRDA=m
 CONFIG_SIGMATEL_FIR=m
 CONFIG_NSC_FIR=m
 CONFIG_WINBOND_FIR=m
 CONFIG_TOSHIBA_FIR=m
 CONFIG_SMC_IRCC_FIR=m
 CONFIG_ALI_FIR=m
 CONFIG_VLSI_FIR=m
 CONFIG_VIA_FIR=m
 CONFIG_BT=m
 CONFIG_BT_L2CAP=m
 CONFIG_BT_SCO=m
 CONFIG_BT_RFCOMM=m
 CONFIG_BT_RFCOMM_TTY=y
 CONFIG_BT_BNEP=m
 CONFIG_BT_BNEP_MC_FILTER=y
 CONFIG_BT_BNEP_PROTO_FILTER=y
 CONFIG_BT_HIDP=m
 #
 # Bluetooth device drivers
 #
 CONFIG_BT_HCIUSB=m
 CONFIG_BT_HCIUSB_SCO=y
 CONFIG_BT_HCIUART=m
 CONFIG_BT_HCIUART_H4=y
 CONFIG_BT_HCIUART_BCSP=y
 CONFIG_BT_HCIBCM203X=m
 CONFIG_BT_HCIBPA10X=m
 CONFIG_BT_HCIBFUSB=m
 CONFIG_BT_HCIVHCI=m
 CONFIG_IEEE80211=m
 # CONFIG_IEEE80211_DEBUG is not set
 CONFIG_IEEE80211_CRYPT_WEP=m
 CONFIG_IEEE80211_CRYPT_CCMP=m
 CONFIG_IEEE80211_CRYPT_TKIP=m

Now, just compile the kernel and reboot in to it.

== Userland ==
At a bare minimum, you need to install bluez-libs and bluez-utils from http://www.bluez.org.  I used the binary package provided by [http://www.develia.org/tarballs.php?p=networking develia.org], but that was before I knew about SlackBuild scripts.  If you can not find a SlackBuild script and you do not want to create your own, you should use [[Checkinstall]] at the very least.

At this time, you might as well install KDE-Bluetooth, also.  I think I grabbed my binary package from [http://www.linuxpackages.net LinuxPackages], but that was also before I knew better.  You can either grab the source code on it's own from [http://sourceforge.net/project/showfiles.php?group_id=89888 SoureForge] or as a part of [ftp://ftp.kde.org/pub/kde/snapshots/kdeextragear-multimedia.tar.bz2 KDE Extra Gear].  Again, use a Slackbuild script or [[Checkinstall]] to install these.

For more information on SlackBuild scripts, you can see the following tutorials: [[SlackBuild Scripts]], [[Writing A SlackBuild_ Script]], [[Slack-desc]], [[Different Approach To Buildscripts]], [[Checkinstall]]

If you happen to discover that your bluetooth chip is a Broadcom that requires nonredistributable firmware (which necessarily isn't in Slackware), then see [[Btfirmware-nonfree]]

== Configuration ==
Now, should have all of the tools you need to start connecting your computer to your bluetooth devices.  First, check the status of the bluetooth dongle with hciconfig.
 # hciconfig
 hci0:   Type: USB
        BD Address: 00:11:22:33:44:55 ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN 
        RX bytes:385 acl:0 sco:0 events:18 errors:0
        TX bytes:322 acl:0 sco:0 commands:18 errors:0
If yours says "UP RUNNING" then you are good to go.  If not, you need to bring the interface up.
 # hciconfig hci0 up
 # hciconfig hci0
 hci0:   Type: USB
        BD Address: 00:11:22:33:44:55 ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN 
        RX bytes:385 acl:0 sco:0 events:18 errors:0
        TX bytes:322 acl:0 sco:0 commands:18 errors:0
Since the dongle works, it's time to configure the programs that will make the actual connections.  Use your favorite text editor to edit the PIN in /etc/bluetooth/pin:
 # gvim /etc/bluetooth/pin
The PIN needs to be all digits.  I'm not sure if it needs to be exactly four (4) digits, but four (4) works well.  Here is an example:
 PIN:1234
Then you need to edit /etc/bluetooth/hcid.conf
 #
 # HCI daemon configuration file.
 #
 # HCId options
 options {
        autoinit yes;
        #security auto;
        security user;
        pairing multi;
        pin_helper /opt/kde/lib/kdebluetooth/kbluepin;
        #pin_helper /usr/bin/bluepin;
        #pin_helper /usr/bin/pin;
        #dbus_pin_helper;
 }
 device {
        name "BlueZ %h (%d)";
        class 0x3e0100;
        #pkt_type DH1,DM1,HV1;
        iscan enable; pscan enable;
        lm accept;
        lp rswitch,hold,sniff,park;
        # Authentication and Encryption (Security Mode 3)
        #auth enable;
        #encrypt enable;
 }

=== Choosing a PIN Helper ===
From all the other HOWTO's I read, I got the impression that the /usr/bin/bluepin script supplied with the Bluez-utils was junk.  I found a nice, simple replacement script on this page http://orin.meinlschmidt.org/~znouza/doc/r51/.  I will duplicate it here just for ease, but all rights and respect go to whoever made that page.  Use your favorite text editor and  create the new file /usr/bin/pin:
 #!/bin/bash
 # original script from http://orin.meinlschmidt.org/~znouza/doc/r51/
 cat /etc/bluetooth/pin
when you are done editing, save and close the file, then make it executable.  Choose your permissions wisely.
 # chmod 710 /usr/bin/pin
 # ls -la /usr/bin/pin
 -rwx--x--- 1 root root 35 2006-04-09 19:19 /usr/bin/pin
This /usr/bin/pin script will suffice for pretty much any way you want to connect to your phone.  If you want to use kdebluetooth to connect to your phone, then use kbluepin.  The example hcid.conf file above is already setup to use kbluepin.  To use /usr/bin/pin, simply comment out the kbluepin line and remove the comment character(#) from the /usr/bin/pin line.

=== Making the Connection ===
Next, you need to start up the hcid and sdpd daemons.  It is a good idea to add these to /etc/rc.d/rc.local so they start automatically with each reboot.  At the command line type:
 # /usr/sbin/hcid
 # /usr/sbin/sdpd
and add these lines to /etc/rc.d/rc.local
 /usr/sbin/hcid
 /usr/sbin/sdpd
Then, you can set your phone to "discover" mode, allowing other devices to see it is present, and scan for it.  On the Motorola V551 you go to Settings &gt; Connection &gt; Bluetooth Link &gt; Setup &gt; Find Me.
 # hcitool scan
 Scanning ...
        00:12:34:56:78:9A       Motorola Phone
Using the hardware address from the scan above, you can find out a lot of information about your phone.
 # sdptool records 00:12:34:56:78:9A
 Service Name: Dial-up networking Gateway
 Service Description: Dial-up networking Gateway
 Service Provider: Cingular
 Service RecHandle: 0x10001
 Service Class ID List:
   "Dialup Networking" (0x1103)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 1
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "Dialup Networking" (0x1103)
     Version: 0x0100
 
 Service Name: Voice Gateway
 Service Description: Headset Audio Gateway
 Service Provider: Cingular
 Service RecHandle: 0x10003
 Service Class ID List:
   "Headset Audio Gateway" (0x1112)
   "Generic Audio" (0x1203)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 3
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "Headset" (0x1108)
     Version: 0x0100
 
 Service Name: Hands-Free voice gateway
 Service Description: Hands-Free voice gateway
 Service Provider: Cingular
 Service RecHandle: 0x10007
 Service Class ID List:
   "Handfree Audio Gateway" (0x111f)
   "Generic Audio" (0x1203)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 7
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "Handsfree" (0x111e)
     Version: 0x0101
 
 Service Name: OBEX Object Push
 Service Description: OBEX Object Push
 Service Provider: Cingular
 Service RecHandle: 0x10008
 Service Class ID List:
   "OBEX Object Push" (0x1105)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 8
   "OBEX" (0x0008)
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "OBEX Object Push" (0x1105)
     Version: 0x0100
 
 Service Name: OBEX File Transfer
 Service Description: OBEX File Transfer
 Service Provider: Cingular
 Service RecHandle: 0x10009
 Service Class ID List:
   "OBEX File Transfer" (0x1106)
 Protocol Descriptor List:
   "L2CAP" (0x0100)
   "RFCOMM" (0x0003)
     Channel: 9
   "OBEX" (0x0008)
 Language Base Attr List:
   code_ISO639: 0x656e
   encoding:    0x6a
   base_offset: 0x100
   code_ISO639: 0x6672
   encoding:    0x6a
   base_offset: 0xd800
   code_ISO639: 0x6573
   encoding:    0x6a
   base_offset: 0xd803
   code_ISO639: 0x7074
   encoding:    0x6a
   base_offset: 0xd806
 Profile Descriptor List:
   "OBEX File Transfer" (0x1106)
     Version: 0x0100

=== Radio Frequency Communication (RFCOMM) ===
This is one way to use your phone as a modem.  I believe that most Cingular and T-Mobile (GSM/GPRS) in the USA use channel 1 for the Dial-Up Gateway.  One way to take advantage of this is to use rfcomm to connect to your phone.  In order to do that, you will need to edit /etc/bluetooth/rfcomm.conf:
 #
 # RFCOMM configuration file.
 #
 rfcomm0 {
        # Automatically bind the device at startup
        bind yes;
        # Bluetooth address of the device
        device 00:12:34:56:78:9A;
        # RFCOMM channel for the connection
        channel	1;
        # Description of the connection
        comment "Motorola V551";
 }
Then connect to the phone by typing:
 # rfcomm connect 0
I won't go in to any more details because I don't use my phone as a modem.  But, if you want to use your phone that way, there are plenty of resources out there to show you what to do.

=== KDE Bluetooth ===
I don't use KDE as my window manager/desktop, but kdebluetooth should automatically run when you start KDE.  If you don't use KDE, like me, you can start up the taskbar daemon by typing "kbluetoothd" in a terminal.  You can then use the KDE OBEX Push Client to transfer files to your phone.  I haven't figured out how to get files off of my phone (like pictures), but I have seen [http://openobex.triq.net/obexftp/obexftp obexftp] and [http://openobex.triq.net/obexfs obexfs] which look promising.  When I test those out, I will update this accordingly.

== References ==
http://www.linuxquestions.org/hcl/showproduct.php?product=2879&amp;cat=53

http://www.westmaster.com/zidek/p900/bluetooth/

http://www.bluez.org

http://www.develia.org/tarballs.php?p=networking

http://kde-bluetooth.sourceforge.net/

http://extragear.kde.org/

http://www.gentoo.org/doc/en/bluetooth-guide.xml</text>
    <sha1>b5ad2a96953ee8e1b75aecdabcb40bbf8006cf12</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Slackware On Odroid U3</title>
  <ns>0</ns>
  <id>322</id>
  <revision>
    <id>984</id>
    <timestamp>2016-11-16T14:17:13Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <comment>Slackware 14.2 installation on Odroid U3</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="22" xml:space="preserve">Slackware On Odroid U3</text>
    <sha1>28f1d0a4120b364ddbd60944a18e02f97497abcb</sha1>
  </revision>
  <revision>
    <id>985</id>
    <parentid>984</parentid>
    <timestamp>2016-11-16T14:54:14Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <comment>Slackware 14.2 On Odroid U3</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7029" xml:space="preserve">== Slackware 14.2 On Odroid U3 ==

=== 3+ partition method ===

In 3 partition method, installer root , like from the initrd image, is installed onto second par
tion, and booted to install the distribution to a third partition. You may refer
to multiboot document ( [https://github.com/gv1/Odroid.U3/blob/master/multiboot/README] ) to do a two partition method of installation. It is a bit more complicated than three partition method. This method can further be simplified to do installation into a single partition, provided a suitable u-boot firmware is fused. 

See the multiboot page at github [https://github.com/gv1/Odroid.U3/tree/master/multiboot] for a two partition method.

Ref:
# [https://github.com/gv1/Odroid.U3]


=== Requirements ===

==== 16/32 GB Micro SD card ====
You may also install on to a pen drive or external hard disk for usb and boot from there. But you still will require a micro sd card for booting.

==== A working Ubuntu image like ubuntu-16.04.1.lts ====
[http://dn.odroid.com/4412/Linux/ubuntu_16.04lts/ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz]
               
==== Slackware 14.2 for arm ====
[http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.2]

rsync --exclude '*/source/*' --exclude '*/testing/*' -Pavv --delete ftp.arm.slackware.com::slackwarearm/slackwarearm-14.2.

=== Installation ===

==== Install the u-boot header and FAT partiotion for zIamge, uInitrd and boot.ini ====

unxz ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz
xzcat --verbose ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | dd of=/dev/sdX count=300000

==== Create partitions on SD card ====
fdisk /dev/sdX

From partition created by dd from img in step 1, delete second and add three more
( or as many desired ).

First partion created from the image has size of ~128MB.
Make this partition bootable ( Boot flag on ), if not already so.
Size of second partion should hold the installer initrd ( uncompressed ) and also the distribution (slackware) for installation, something like 4GB. Third partition is where the distributions are installed. Size in the  order of 24GB or so. Fourth is the swap partion - 2GB or so.


        Device         Boot    Start      End  Sectors  Size Id Type
        /dev/sdX1 *        6144   268287   262144  128M  6 FAT16
        /dev/sdX2        268288  8656895  8388608    4G 83 Linux
        /dev/sdX3       8656896 58988543 50331648   24G 83 Linux
        /dev/sdX4      58988544 62945279  3956736  1.9G 82 Linux swap

==== Mount partition two, install 14.2 setup initrd image, copy kernel modules, firmware and installation sources. ====

From PC host / Odroid running other Linux 

&lt;source&gt;
mkdir odroid
cd ordoid
mkdir boot
mkdir root
mkfs.ext4 /dev/sdX2
tune2fs /dev/sdX2 -L installer
mount /dev/sdX2 boot
# copy / download distribution files, say slackwarearm-14.2 to boot/
wget http://www.arm.slackware.com/slackwarearm/slackwarearm-14.2/isolinux/initrd-armv7.img
                
or

mkdir boot/slackwarearm-14.2
cd boot/slackwarearm-14.2

For downloading:
Refer to http://arm.slackware.com and also consider donations.
cd slackwarearm-14.2
rsync --exclude '*/source/*' --exclude '*/testing/*' -Pavv --delete ftp.arm.slackware.com::slackwarearm/slackwarearm-14.2 .
cd ../..

cd boot
gzip -dc ../slackwarearm-14.2/isolinux/initrd-armv7.img | cpio -i --make-directories
sync
cd lib
rm -rf modules/*
rm -rf firmware/*
# mount and copy from Ubuntu.

&lt;/source&gt;

==== Install ubuntu on third partition, copy module and firmware files to installer partition. ====

&lt;source&gt;
mkdir ubuntu

if you have the image installed onto an sd card, use the second partition from there.

mount -r /dev/sdY2 ubuntu
                or
if you only have the image ( first unxz ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz )
parted -s ubuntu-16.04-mate-odroid-u2u3-20160920.img unit B print
find partition 2 start offset from the output.
p2offset=....
mount second partition from ubuntu-16.04-mate-odroid-u2u3-20160920.img -
mount -o loop,ro,offset=$p2offset ubuntu-16.04-mate-odroid-u2u3-20160920.img ubuntu

mkfs.ext4 /dev/sdX3
tune2fs /dev/sdX3 -L slackware14.2
mount /dev/sdX3 root
mkdir root/ubuntu-16.04.1.lts
mkdir root/installer
mkdir root/slackware-14.2
(cd ubuntu; tar cfz - *) | (cd root/ubuntu-16.04.1.lts; tar xfz - )
copy modules and firmware? to installer.
(cd root/ubuntu-16.04.1.lts/lib/ ; tar cfz - modules firmware ) | (cd boot/lib/; tar xfz - )
sync
sync
umount ubuntu
umount boot
umount root

&lt;/source&gt;

==== Reboot odroid, and if everything goes fine, will boot into slackware installer. ====

press enter to login as root
run setup:
                        setup
During installation,
Choose partition 3 as target, and dont' format it. It already has Ubuntu on it.
Choose source directory for installation  - /slackwarearm-14.2/slackware
Proceed with the normal slackware installation.

==== Modify boot.ini and reboot. ====
&lt;source&gt;
mount /dev/sdX1 boot
edit and modify boot/boot.ini to boot from parition 3
setenv bootargs "console=tty1 console=ttySAC1,115200n8 root=/dev/mmcblk0p3 rootwa
it ro mem=2047M ${videoconfig}"
sync
umount boot
&lt;/source&gt;

==== If you are planning for multiboot ====
&lt;source&gt;
cd root
mv * slackware-14.2
mv slackware-14.2/ubuntu-16.04.1.lts .
Now you have both Slackware and Ubuntu on same partition.
See README.odroid.u3.multiboot to see how to get a multiboot setup ( choo
se distribution at boot time ) so that you can choose the distribution at boot time. No fancy chooser 
this time, you need to enter the number corresponding to the distro at a prompt.

=== Other info ===

==== Mouse pointer issue.====
        Xorg ( with blackbox wm ) seems have no mouse curser until you open an xterm or s
o by clicking the right mouse button. Mouse pointer is okay if you have an .xinitrc that
starts an xterm or so.

==== No web browsers. ====

Browsers you can compile and run on odroid u3, slackware 14.2: sadly none of these browsers are available in the distribution. text based ones like lynx are there. Emacs supports web browsing mode too.

                Dillo version 3.0.5  ( fast , but premitive ) first step
                Mozilla Firefox 50.0 ( compile from source, took long time like more than
 6 hours)
[https://github.com/gv1/Odroid.U3/blob/master/firefox-50.0.tar.xz]

==== No libreoffice.===
        Office compilation - fail
                Libreoffice libreoffice-5.2.2.2 compiled, ( took very long time, 12 ho
urs or more ) starts, but fall into libreoffice docuement discovery mode and fail (repeat):

(soffice:1091): Gtk-WARNING **: Theme parsing error: &lt;data&gt;:1:59: 'min-width' is not a va
lid property name

(soffice:1091): Gtk-WARNING **: Theme parsing error: &lt;data&gt;:1:76: 'min-height' is not a v
alid property name

Shutdown seems not shutdown/poweroff complete, but keeps printing message, should not hav
e reached here.

But no other issues on reboot after shutdown. This gets fixed with 
[https://github.com/gv1/Odroid.U3/tree/master/linux-4.8.y]
[https://github.com/gv1/Odroid.U3/tree/master/u-boot-stable]</text>
    <sha1>c7756d0fb04b86fb264b65a12f9def3b563ac0ff</sha1>
  </revision>
  <revision>
    <id>986</id>
    <parentid>985</parentid>
    <timestamp>2016-11-16T17:16:01Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8164" xml:space="preserve">== Slackware 14.2 On Odroid U3 ==

=== 3+ partition method ===

In 3 partition method, installer root , like from the initrd image, is installed onto second par
tion, and booted to install the distribution to a third partition. You may refer
to multiboot document ( [https://github.com/gv1/Odroid.U3/blob/master/multiboot/README Multiboot README] ) to do a two partition method of installation. It is a bit more complicated than three partition method. This method can further be simplified to do installation into a single partition, provided a suitable u-boot firmware is fused. 

See the multiboot page at github [https://github.com/gv1/Odroid.U3/tree/master/multiboot Multiboot] for a two partition method.

Ref:
# [https://github.com/gv1/Odroid.U3 Odroid U3 related pages, from Gv]


=== Requirements ===

==== 16/32 GB Micro SD card ====
You may also install on to a pen drive or external hard disk for usb and boot from there. But you still will require a micro sd card for booting.

==== A working Ubuntu image like ubuntu-16.04.1.lts ====
[http://dn.odroid.com/4412/Linux/ubuntu_16.04lts/ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz]
               
==== Slackware 14.2 for arm ====
[http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.2 Slackwarearm-14.2]] 

    rsync --exclude '*/source/*' --exclude '*/testing/*' -Pavv --delete ftp.arm.slackware.com::slackwarearm/slackwarearm-14.2.

=== Installation ===

==== Install the u-boot header and FAT partiotion for zIamge, uInitrd and boot.ini ====

===== Method one, using Ubuntu 16.04 boot files =====

    xzcat --verbose ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | dd of=/dev/sdX count=300000


==== Create partitions on SD card ====


    fdisk /dev/sdX


From partition created by dd from img in step 1, delete second and add three more ( or as many desired ).

First partion created from the image has size of ~128MB. Make this partition bootable ( Boot flag on ), if not already so. Size of second partion should hold the installer initrd ( uncompressed ) and also the distribution (slackware) for installation, something like 4GB. Third partition is where the distributions are installed. Size in the  order of 24GB or so. Fourth is the swap partion - 2GB or so.


    Device         Boot    Start      End  Sectors  Size Id Type
    /dev/sdX1 *        6144   268287   262144  128M  6 FAT16
    /dev/sdX2        268288  8656895  8388608    4G 83 Linux
    /dev/sdX3       8656896 58988543 50331648   24G 83 Linux
    /dev/sdX4      58988544 62945279  3956736  1.9G 82 Linux swap


===== Method 2, using u-boot files =====

See [https://github.com/gv1/Odroid.U3/tree/master/u-boot-stable u-boot]
Parition the card like as in first method, manually. Next make the card u-boot capable by fusing the required firmware. Use sd_fusing_all.sh to fuse required U-Boot files on to sd card. See [https://github.com/gv1/Odroid.U3/tree/master/u-boot-stable u-boot-stable] directory for more info.

==== Mount partition two, install 14.2 setup initrd image, copy kernel modules, firmware and installation sources. ====

From PC host / Odroid running other Linux 

    mkdir odroid
    cd ordoid
    mkdir boot
    mkdir root
    mkfs.ext4 /dev/sdX2
    tune2fs /dev/sdX2 -L installer
    mount /dev/sdX2 boot


# copy / download distribution files, say slackwarearm-14.2 to boot/

    wget http://www.arm.slackware.com/slackwarearm/slackwarearm-14.2/isolinux/initrd-armv7.img
    mkdir boot/slackwarearm-14.2
    cd boot/slackwarearm-14.2

For downloading:
Refer to http://arm.slackware.com and also consider donations.

    rsync --exclude '*/source/*' --exclude '*/testing/*' -Pavv --delete ftp.arm.slackware.com::slackwarearm/slackwarearm-14.2 .
    cd ../..

Preparing the installer root partition:

    cd boot
    gzip -dc ../slackwarearm-14.2/isolinux/initrd-armv7.img | cpio -i --make-directories
    sync
    cd lib
    rm -rf modules/*
    rm -rf firmware/*
    # mount and copy from Ubuntu.


==== Install ubuntu on third partition, copy module and firmware files to installer partition. ====


    mkdir ubuntu


if you have the image installed onto an sd card, use the second partition from there.

    mount -r /dev/sdY2 ubuntu

Or
If you only have the image 

First 

    unxz ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz )
    parted -s ubuntu-16.04-mate-odroid-u2u3-20160920.img unit B print
    find partition 2 start offset from the output.
    p2offset=....
    mount second partition from ubuntu-16.04-mate-odroid-u2u3-20160920.img -
    mount -o loop,ro,offset=$p2offset ubuntu-16.04-mate-odroid-u2u3-20160920.img ubuntu

Or

    # find info about partitions
    xzcat ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | dd of=x.img count=1
    file x.img
    # rm x.img
    xzcat ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | dd of=ubuntu-16.04-mate-odroid-u2u3-20160920.img count=9216000 skip=268288
    mount -o loop ubuntu-16.04-mate-odroid-u2u3-20160920.img ubuntu


    mkfs.ext4 /dev/sdX3
    tune2fs /dev/sdX3 -L slackware14.2
    mount /dev/sdX3 root
    mkdir root/ubuntu-16.04.1.lts
    mkdir root/installer
    mkdir root/slackware-14.2
    (cd ubuntu; tar cfz - *) | (cd root/ubuntu-16.04.1.lts; tar xfz - )
    # copy modules and firmware? to installer.
    (cd root/ubuntu-16.04.1.lts/lib/ ; tar cfz - modules firmware ) | (cd boot/lib/; tar xfz - )
    sync
    sync
    umount ubuntu
    umount boot
    umount root
    

==== Reboot odroid, and if everything goes fine, will boot into slackware installer. ====

press enter to login as root
run setup:
         setup
During installation,
Choose partition 3 as target, and dont' format it. It already has Ubuntu on it.
Choose source directory for installation  - /slackwarearm-14.2/slackware
Proceed with the normal slackware installation.

==== Modify boot.ini and reboot. ====

    mount /dev/sdX1 boot
    edit and modify boot/boot.ini to boot from parition 3
    setenv bootargs "console=tty1 console=ttySAC1,115200n8 root=/dev/mmcblk0p3 rootwait ro mem=2047M ${videoconfig}"
    sync
    umount boot


==== If you are planning for multiboot ====
    cd root
    mv * slackware-14.2
    mv slackware-14.2/ubuntu-16.04.1.lts .

Now you have both Slackware and Ubuntu on same partition.
See [https://github.com/gv1/Odroid.U3/tree/master/multiboot multiboot] to see how to get a multiboot setup ( choose distribution at boot time ) so that you can choose the distribution at boot time. No fancy chooser this time, you need to enter the number corresponding to the distro at a prompt.

=== Other info ===

==== Mouse pointer issue.====
        Xorg ( with blackbox wm ) seems have no mouse curser until you open an xterm or s
o by clicking the right mouse button. Mouse pointer is okay if you have an .xinitrc that
starts an xterm or so.

==== No web browsers. ====

Browsers you can compile and run on odroid u3, slackware 14.2: sadly none of these browsers are available in the distribution. text based ones like lynx are there. Emacs supports web browsing mode too.
#[http://www.dillo.org Dillo] version 3.0.5  ( fast , but premitive ) first step
#[https://archive.mozilla.org/pub/PROJECT/releases/RELEASE/source/ Mozilla Firefox] 50.0 ( compile from source, took long time like more than 6 hours)
[https://github.com/gv1/Odroid.U3/blob/master/firefox-50.0.tar.xz firefox-50.0.tar.xz]

=== No libreoffice.===
        Office compilation - fail
                Libreoffice libreoffice-5.2.2.2 compiled, ( took very long time, 12 ho
urs or more ) starts, but fall into libreoffice docuement discovery mode and fail (repeat):

(soffice:1091): Gtk-WARNING **: Theme parsing error: &lt;data&gt;:1:59: 'min-width' is not a va
lid property name

(soffice:1091): Gtk-WARNING **: Theme parsing error: &lt;data&gt;:1:76: 'min-height' is not a v
alid property name

Shutdown seems not shutdown/poweroff complete, but keeps printing message, should not hav
e reached here.

But no other issues on reboot after shutdown. This gets fixed with 
[https://github.com/gv1/Odroid.U3/tree/master/linux-4.8.y linux-4.8.y]
[https://github.com/gv1/Odroid.U3/tree/master/u-boot-stable u-boot-stable]</text>
    <sha1>e927b93e31704740f85aee8088b4934aa64e3818</sha1>
  </revision>
  <revision>
    <id>987</id>
    <parentid>986</parentid>
    <timestamp>2016-11-17T08:50:58Z</timestamp>
    <contributor>
      <username>Gv</username>
      <id>356</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8936" xml:space="preserve">== Slackware 14.2 On Odroid U3 ==

=== 3+ partition method ===

In 3 partition method, installer root , like from the initrd image, is installed onto second par
tion, and booted to install the distribution to a third partition. You may refer
to multiboot document ( [https://github.com/gv1/Odroid.U3/blob/master/multiboot/README Multiboot README] ) to do a two partition method of installation. It is a bit more complicated than three partition method. This method can further be simplified to do installation into a single partition, provided a suitable u-boot firmware is fused. 

See the multiboot page at github [https://github.com/gv1/Odroid.U3/tree/master/multiboot Multiboot] for a two partition method.

Ref:
# [https://github.com/gv1/Odroid.U3 Odroid U3 related pages, from Gv]


=== Requirements ===

==== 16/32 GB Micro SD card ====
You may also install on to a pen drive or external hard disk for usb and boot from there. But you still will require a micro sd card for booting.

==== A working Ubuntu image like ubuntu-16.04.1.lts ====
[http://dn.odroid.com/4412/Linux/ubuntu_16.04lts/ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz]
               
==== Slackware 14.2 for arm ====
[http://ftp.arm.slackware.com/slackwarearm/slackwarearm-14.2 Slackwarearm-14.2]] 

    rsync --exclude '*/source/*' --exclude '*/testing/*' -Pavv --delete ftp.arm.slackware.com::slackwarearm/slackwarearm-14.2.

=== Installation ===

==== Install the u-boot header and FAT partiotion for zIamge, uInitrd and boot.ini ====

===== Method one, using Ubuntu 16.04 boot files =====

    xzcat --verbose ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | dd of=/dev/sdX count=300000

Here is some info on how to download just enough data from site:

    wget -qO-  http://dn.odroid.com/4412/Linux/ubuntu_16.04lts/ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | xzcat | dd of=x.img count=1
    file x.img
    # rm x.img
from 
    x.img: DOS/MBR boot sector; partition 1 : ID=0x6, start-CHS (0x0,97,34), end-CHS (0x10,178,34), startsector 6144, 262144 sectors; partition 2 : ID=0x83, start-CHS (0x60,0,1), end-CHS (0x24e,94,16), startsector 268288, 9216000 sectors

    # wget -qO-  http://dn.odroid.com/4412/Linux/ubuntu_16.04lts/ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | xzcat | dd of=ubuntu-16.04-mate-odroid-u2u3-20160920.img count=$((6144+262144))
    This is more useful when you want to download just partition one, not the entire distribution.

==== Create partitions on SD card ====


    fdisk /dev/sdX


From partition created by dd from img in step 1, delete second and add three more ( or as many desired ).

First partion created from the image has size of ~128MB. Make this partition bootable ( Boot flag on ), if not already so. Size of second partion should hold the installer initrd ( uncompressed ) and also the distribution (slackware) for installation, something like 4GB. Third partition is where the distributions are installed. Size in the  order of 24GB or so. Fourth is the swap partion - 2GB or so.


    Device         Boot    Start      End  Sectors  Size Id Type
    /dev/sdX1 *        6144   268287   262144  128M  6 FAT16
    /dev/sdX2        268288  8656895  8388608    4G 83 Linux
    /dev/sdX3       8656896 58988543 50331648   24G 83 Linux
    /dev/sdX4      58988544 62945279  3956736  1.9G 82 Linux swap


===== Method 2, using u-boot files =====

See [https://github.com/gv1/Odroid.U3/tree/master/u-boot-stable u-boot]
Parition the card like as in first method, manually. Next make the card u-boot capable by fusing the required firmware. Use sd_fusing_all.sh to fuse required U-Boot files on to sd card. See [https://github.com/gv1/Odroid.U3/tree/master/u-boot-stable u-boot-stable] directory for more info.

==== Mount partition two, install 14.2 setup initrd image, copy kernel modules, firmware and installation sources. ====

From PC host / Odroid running other Linux 

    mkdir odroid
    cd ordoid
    mkdir boot
    mkdir root
    mkfs.ext4 /dev/sdX2
    tune2fs /dev/sdX2 -L installer
    mount /dev/sdX2 boot


# copy / download distribution files, say slackwarearm-14.2 to boot/

    wget http://www.arm.slackware.com/slackwarearm/slackwarearm-14.2/isolinux/initrd-armv7.img
    mkdir boot/slackwarearm-14.2
    cd boot/slackwarearm-14.2

For downloading:
Refer to http://arm.slackware.com and also consider donations.

    rsync --exclude '*/source/*' --exclude '*/testing/*' -Pavv --delete ftp.arm.slackware.com::slackwarearm/slackwarearm-14.2 .
    cd ../..

Preparing the installer root partition:

    cd boot
    gzip -dc ../slackwarearm-14.2/isolinux/initrd-armv7.img | cpio -i --make-directories
    sync
    cd lib
    rm -rf modules/*
    rm -rf firmware/*
    # mount and copy from Ubuntu.


==== Install ubuntu on third partition, copy module and firmware files to installer partition. ====


    mkdir ubuntu


if you have the image installed onto an sd card, use the second partition from there.

    mount -r /dev/sdY2 ubuntu

Or
If you only have the image 

First 

    unxz ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz )
    parted -s ubuntu-16.04-mate-odroid-u2u3-20160920.img unit B print
    find partition 2 start offset from the output.
    p2offset=....
    mount second partition from ubuntu-16.04-mate-odroid-u2u3-20160920.img -
    mount -o loop,ro,offset=$p2offset ubuntu-16.04-mate-odroid-u2u3-20160920.img ubuntu

Or

    # find info about partitions
    xzcat ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | dd of=x.img count=1
    file x.img
    # rm x.img
    xzcat ubuntu-16.04-mate-odroid-u2u3-20160920.img.xz | dd of=ubuntu-16.04-mate-odroid-u2u3-20160920.img count=9216000 skip=268288
    mount -o loop ubuntu-16.04-mate-odroid-u2u3-20160920.img ubuntu


    mkfs.ext4 /dev/sdX3
    tune2fs /dev/sdX3 -L slackware14.2
    mount /dev/sdX3 root
    mkdir root/ubuntu-16.04.1.lts
    mkdir root/installer
    mkdir root/slackware-14.2
    (cd ubuntu; tar cfz - *) | (cd root/ubuntu-16.04.1.lts; tar xfz - )
    # copy modules and firmware? to installer.
    (cd root/ubuntu-16.04.1.lts/lib/ ; tar cfz - modules firmware ) | (cd boot/lib/; tar xfz - )
    sync
    sync
    umount ubuntu
    umount boot
    umount root
    

==== Reboot odroid, and if everything goes fine, will boot into slackware installer. ====

press enter to login as root
run setup:
         setup
During installation,
Choose partition 3 as target, and dont' format it. It already has Ubuntu on it.
Choose source directory for installation  - /slackwarearm-14.2/slackware
Proceed with the normal slackware installation.

==== Modify boot.ini and reboot. ====

    mount /dev/sdX1 boot
    edit and modify boot/boot.ini to boot from parition 3
    setenv bootargs "console=tty1 console=ttySAC1,115200n8 root=/dev/mmcblk0p3 rootwait ro mem=2047M ${videoconfig}"
    sync
    umount boot


==== If you are planning for multiboot ====
    cd root
    mv * slackware-14.2
    mv slackware-14.2/ubuntu-16.04.1.lts .

Now you have both Slackware and Ubuntu on same partition.
See [https://github.com/gv1/Odroid.U3/tree/master/multiboot multiboot] to see how to get a multiboot setup ( choose distribution at boot time ) so that you can choose the distribution at boot time. No fancy chooser this time, you need to enter the number corresponding to the distro at a prompt.

=== Other info ===

==== Mouse pointer issue.====
        Xorg ( with blackbox wm ) seems have no mouse curser until you open an xterm or s
o by clicking the right mouse button. Mouse pointer is okay if you have an .xinitrc that
starts an xterm or so.

==== No web browsers. ====

Browsers you can compile and run on odroid u3, slackware 14.2: sadly none of these browsers are available in the distribution. text based ones like lynx are there. Emacs supports web browsing mode too.
#[http://www.dillo.org Dillo] version 3.0.5  ( fast , but premitive ) first step
#[https://archive.mozilla.org/pub/PROJECT/releases/RELEASE/source/ Mozilla Firefox] 50.0 ( compile from source, took long time like more than 6 hours)
[https://github.com/gv1/Odroid.U3/blob/master/firefox-50.0.tar.xz firefox-50.0.tar.xz]

=== No libreoffice.===
        Office compilation - fail
                Libreoffice libreoffice-5.2.2.2 compiled, ( took very long time, 12 ho
urs or more ) starts, but fall into libreoffice docuement discovery mode and fail (repeat):

(soffice:1091): Gtk-WARNING **: Theme parsing error: &lt;data&gt;:1:59: 'min-width' is not a va
lid property name

(soffice:1091): Gtk-WARNING **: Theme parsing error: &lt;data&gt;:1:76: 'min-height' is not a v
alid property name

Shutdown seems not shutdown/poweroff complete, but keeps printing message, should not hav
e reached here.

But no other issues on reboot after shutdown. This gets fixed with 
[https://github.com/gv1/Odroid.U3/tree/master/linux-4.8.y linux-4.8.y]
[https://github.com/gv1/Odroid.U3/tree/master/u-boot-stable u-boot-stable]</text>
    <sha1>87b4a18b9f4d75a6e95e44f33edfd37b1781c9cd</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>SSL</title>
  <ns>0</ns>
  <id>144</id>
  <revision>
    <id>988</id>
    <parentid>361</parentid>
    <timestamp>2017-05-09T00:44:06Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Info from Xesco</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="12981" xml:space="preserve">[[Category:Tutorials]]
= openSSL 0.9.8e =
'''IMPORTANT: Since this version has a [http://www.mail-archive.com/openssl-users@openssl.org/msg48671.html bug in the blowfish encryption] it is recommended not to use blowfish since it is incompatible with all other openSSL versions!'''

&lt;br&gt;Everything you read here was tested on Slackware 12&lt;br&gt;

; wikipedia says about openSSL:
: ''OpenSSL is an open source implementation of the SSL and TLS protocols. The core library (written in the C programming language) implements the basic cryptographic functions and provides various utility functions. Wrappers allowing the use of the OpenSSL library in a variety of computer languages are available.''

There are many ways to use openSSL. This just covers certificates for use with httpd. You can also use easy-rsa that comes with the openVPN package and can be found in ''/usr/doc/openvpn-2.0.9/easy-rsa/''. For more information read the included ''README'' or look here: [http://openvpn.net/easyrsa.html A Guide to basic RSA Key Management].
Normally you will make a ''Certificate Signing Request (CSR)'' and send this one to a ''Certifying Authority (CA)'' to be signed. But since we don't wanna pay for this and only want to use it for our own special purpose, we don't need to do that and sign everything ourself.

= openSSL + httpd =
Switch to ''/etc/ssl''
&lt;pre&gt;
cd /etc/ssl
&lt;/pre&gt;

In this directory you should see the following listing.  One some non-Slackware linuxes, or if OpenSSL was installed from source, the appropriate directory might be ''/etc/openssl''.
&lt;pre&gt;
root@pecan:/etc/ssl# ls -l
total 24
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 certs/
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 misc/
-rw-r--r-- 1 root root 9374 2007-06-13 12:40 openssl.cnf
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 private/
root@pecan:/etc/ssl# 
&lt;/pre&gt;

We need to generate a private and public RSA key file.
The public key is used to encrypt messages to you and is distributed with your certificate.

== Creating a Self-Signed ''Certificate'' (CRT) ==

=== openssl.cnf + openSSL DB ===
(You should still do this step even if you are buying a commercial certificate.) First things first, so we gotta edit this file, mainly the ''[ CA_default ]'' section.
The 
&lt;pre&gt;
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
...
certificate	= $dir/cacert.pem 	# The CA certificate
...
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
...
&lt;/pre&gt;
to
&lt;pre&gt;
[ CA_default ]

dir		= /etc/ssl		# Where everything is kept
...
certificate	= $dir/certs/ca.crt   	# The CA certificate
...
crl		= $dir/crl/ca.crl	# The current CRL
private_key	= $dir/private/ca.key   # The private key
...
&lt;/pre&gt;
You can even change more options in this file but be aware what you are doing.&lt;br&gt;
openSSL has a database for storing information such as ''Certificate Revocation Lists'' (CRL). Since these files don't exist on startup and we don't use the ''CA.sh'' or ''CA.pl'' scripts we got to create them ourself:
&lt;pre&gt;
mkdir newcerts certs crl private
touch serial index.txt crlnumber crl/ca.crl
echo 01 | tee serial | tee crlnumber | Tee crl/ca.crl
&lt;/pre&gt;
Thanks to ''alienBOB''. Hail to tee king! :p

=== Becoming a ''Certification Authority'' (CA) ===
(Skip this step if you are buying a certificate from a commercial certificate authority such as GoDaddy.) Before you can create and sign your own certificates, you first have to establish yourself as a "Certificate Authority".
To do so, we first create our key file (with a public and a private key) and use it to create our "master certificate" to use when signing other certificates.

; Generate the CA RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/ca.key 4096&lt;/pre&gt;
; Create the CA CRT with the CA RSA Key
: &lt;pre&gt;openssl req -new -x509 -days 3650 -key private/ca.key -out certs/ca.crt&lt;/pre&gt;

=== Create Server CRT ===
A CRT contains your RSA public key, your name, the name of the CA, and is digitally signed by the CA. Browsers that know the CA can verify the signature on that CRT, thereby obtaining your RSA public key. That enables them to send messages which only you can decrypt.
The next step is to create a Server RSA key, generate a ''Certificate Signing Request'' (CSR) out of it and sign it with our CA CRT to get a working SSL CRT for our server.
A CSR is a digital file which contains your public key and your name. Normally you would send the CSR to a CA, who will convert it into a real certificate, by signing it.

; Generate the Server RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/server.key 1024&lt;/pre&gt;
; Create the Server CSR using the Server RSA Key
: '''When asked for the CommonName (CN) enter your domain!'''
: &lt;pre&gt;openssl req -new -key private/server.key -out private/server.csr&lt;/pre&gt;
; Sign the CSR with our CA CRT
: &lt;pre&gt;openssl ca -in private/server.csr -out certs/server.crt&lt;/pre&gt;

You can now delete ''server.csr'' if you want, because it is no longer needed.

(If you are using a commercially signed certificate from a place such as GoDaddy, do the first two commands above but not the last.  Then do ''cat private/server.csr'' to get the text of the certificate request, which you will paste into GoDaddy's web interface to get the certificate.  GoDaddy will then email the email address listed in the ''whois'' information for that domain (Make sure you haven't put in a fake address there to avoid spam!), and after the link in that email is clicked, GoDaddy will email another link to you from which you download a zip file.

The zip file will contain two .crt files, and you should put both of them in /etc/ssl/certs.  Other commerical certificate authorities follow a very similar procedure.)

== Setup httpd ==
=== Edit httpd.conf ===
The whole httpd config is located in ''/etc/httpd''. Fire up your preferred text editor and simply change this at Line 459:
&lt;pre&gt;
# Secure (SSL/TLS) connections
#Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to this
&lt;pre&gt;
# Secure (SSL/TLS) connections
Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to enable SSL support.

You may also have to uncomment the line that starts ''LoadModule ssl_module''.

=== Edit extra/httpd-ssl.conf ===
Now we're going into the guts of the httpd SSL config. Search for ''SSLCertificateFile'' and ''SSLCertificateKeyFile'' change the path to our newly created CRT:
&lt;pre&gt;
...
SSLCertificateFile /etc/ssl/certs/server.crt
...
SSLCertificateKeyFile /etc/ssl/private/server.key
...
SSLCertificateChainFile /etc/ssl/certs/server.crt
...
SSLCACertificatePath /etc/ssl/certs
SSLCACertificateFile /etc/ssl/certs/ca.crt
...
SSLCARevocationPath /etc/ssl/crl
SSLCARevocationFile /etc/ssl/crl/ca.crl
...
&lt;/pre&gt;

(If you have purchased a certificate from a commercial authority, the SSLCertificateFile will be one of the two files you receive from the CA (GoDaddy or VeriSign or whomever), and the SSLCACertificateFile will be the other.  The files will be named such that you can tell which is which -- the SSLCertificateFile will probably be something like ''www.yourdomainname.com.crt'' and the SSLCACertificateFile will be something like ''nameofca-bundle.crt''.)

== Pass-phrase on httpd startup ==
The reason this dialog pops up at startup and every re-start is that the RSA private key inside your ''server.key'' file is stored in encrypted format for security reasons. The pass-phrase is needed decrypt this file, so it can be read and parsed. Removing the pass-phrase removes a layer of security from your server - proceed with caution!
&lt;ol&gt;
&lt;li&gt;
Remove the encryption from the RSA private key (while keeping a backup copy of the original file):
&lt;pre&gt;
cd /etc/ssl
mv private/server.key private/server.key.org
cd private
openssl rsa -in server.key.org -out server.key
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
Make sure the server.key file is only readable by root since it is decrypted:
&lt;pre&gt;
cd /etc/ssl
chmod 0400 private/server.key
&lt;/pre&gt;
&lt;/li&gt;&lt;/ol&gt;
Now server.key contains an unencrypted copy of the key. If you point your server at this file, it will not prompt you for a pass-phrase. HOWEVER, if anyone gets this key they will be able to impersonate you on the net. PLEASE make sure that the permissions on this file are such that only root or the web server user can read it (preferably get your web server to start as root but run as another user, and have the key readable only by root).

As an alternative approach you can use the ''SSLPassPhraseDialog exec:/path/to/program'' facility. Bear in mind that this is neither more nor less secure, of course.

== Verifying and debugging ==
If you simply want to see every information on a CRT:
&lt;pre&gt;openssl x509 -noout -text -in XXX.crt&lt;/pre&gt;

=== Verifying ===
; Verify that a private key matches its Certificate
: Generate a MD5 out of the public key/CRT and compare
: &lt;pre&gt;openssl x509 -noout -modulus -in private/XXX.crt | openssl md5 &amp;&amp; openssl rsa -noout -modulus -in private/XXX.key | openssl md5&lt;/pre&gt;

=== Debugging ===
; s_server - Debugging clients
: &lt;pre&gt;openssl s_server -accept 443 -www&lt;/pre&gt;
; s_client - Debugging servers
: &lt;pre&gt;openssl s_client -connect localhost:443&lt;/pre&gt; or &lt;pre&gt;openssl s_client -connect localhost:443 -state -debug&lt;/pre&gt;

== Security ==
All the files expect the CRTs are only for your eyes, so we change the permissons:
&lt;pre&gt;chmod 0400 private/*.key&lt;/pre&gt;

=== Client Revokation ===
This is only needed if your server certificate is compromised (eg. someone hacked your server and stole your server.key).
&lt;pre&gt;
openssl ca -gencrl -keyfile private/ca.key -cert certs/ca.crt -out crl/ca.crl
&lt;/pre&gt;
That generated us the needed files which we use when we want to revoke a CRT.
&lt;br&gt;&lt;br&gt;
Now that we got a compromised CRT, we got to get rid of it:
&lt;pre&gt;openssl ca -revoke certs/server.crt -keyfile private/ca.key -cert certs/ca.crt&lt;/pre&gt;

== Other ==

=== Change the pass-phrase ===
&lt;pre&gt;
openssl rsa -des3 -in server.key -out server.key.new
mv server.key.new server.key
&lt;/pre&gt;
The first time you're asked for a PEM pass-phrase, you should enter the old pass-phrase. After that, you'll be asked again to enter a pass-phrase - this time, use the new pass-phrase. If you are asked to verify the pass-phrase, you'll need to enter the new pass-phrase a second time.

=== CRT for Clients ===
Ok.. i won't write anything on this, and simply just C/P:
&lt;pre&gt;
openssl genrsa -des3 -out private/client1_priv.key 2048
openssl genrsa -des3 -out private/client2_priv.key 2048
# and so on... depends on how much clients you wanna serv...
openssl req -new -key private/client1_priv.key -out private/client1.csr
openssl req -new -key private/client2_priv.key -out private/client2.csr
# and so on...
openssl ca -in private/client1.csr -out private/client1.crt
openssl ca -in private/client2.csr -out private/client2.crt
cp private/client1.crt private/client1_preconv.crt 
cat private/client1.key &gt;&gt; private/client1_preconv.crt
openssl pkcs12 -export -in private/client1_preconv.crt -out private/client1_postconv.p12 
&lt;/pre&gt;
Install in the clients browser... and change httpd.conf:
&lt;pre&gt;
SSLCACertificateFile PATH/TO/server.crt
SSLVerifyClient require
SSLVerifyDepth 1
&lt;/pre&gt;

=== Convert CRT from PEM to DER format ===
Normally all CRTs are stored in the PEM format.
&lt;pre&gt;openssl x509 -in ca.crt -out ca.crt.der -outform DER&lt;/pre&gt;

== Testing the CRT ==
If you have live web sites, you might wish to test your configuration before restarting apache, to avoid having that panicy few minutes of downtime while you scramble to see what you can do faster, fix the problem or copy back your backup configs.  Test like this:
&lt;pre&gt;httpd -t&lt;/pre&gt;
Look at the error messages it prints out, or the error_log as explained below, if it doesn't work.

Restart your httpd:
&lt;pre&gt;/etc/rc.d/rc.httpd restart&lt;/pre&gt;
Take a look at the httpd ''error_log'' and scroll to the end of the file:
&lt;pre&gt;jed /var/log/httpd/error_log&lt;/pre&gt;
If your getting an error like this:
&lt;pre&gt;[error] Init: Unable to read pass phrase [Hint: key introduced or changed before restart?]&lt;/pre&gt;
... then you should take a look at ''Pass-phrase on httpd startup'' ...

= openSSL + openVPN =
$foo ... maybe next month...

= External Links =
* [http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html SSL/TLS Strong Encryption: FAQ @ httpd.apache.org]
* [http://www.tc.umn.edu/~brams006/selfsign.html Creating a self-signed SSL certificate]
* [http://www.madboa.com/geek/openssl/ OpenSSL Command-Line HOWTO]
* [http://www.5dollarwhitebox.org/wiki/index.php/Howtos_Self_Signed_SSL_Certificates OpenSSL Quick Reference]
* [http://www.opensourcehowto.org/how-to/apache/setup-apache2-with-openssl.html Setup Apache2 with OpenSSL]
* [http://www.marschke.info/admin/ap_opssl_https.html Apache2, OpenSSL und HTTPS: Server- und Client-Authentifizierung mit Zertifikaten über verschlüsselte Internet-Verbindungen]
* [http://www.online-tutorials.net/security/openssl-tutorial/tutorials-t-69-207.html openSSL / openVPN.. comming soon]</text>
    <sha1>a6da7cf72f7d2cd2cd22156a533f8eb076c9dc6a</sha1>
  </revision>
  <revision>
    <id>990</id>
    <parentid>988</parentid>
    <timestamp>2017-05-28T13:23:55Z</timestamp>
    <contributor>
      <username>Krakanut</username>
      <id>364</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13150" xml:space="preserve">[[Category:Tutorials]]
= openSSL 0.9.8e =
'''IMPORTANT: Since this version has a [http://www.mail-archive.com/openssl-users@openssl.org/msg48671.html bug in the blowfish encryption] it is recommended not to use blowfish since it is incompatible with all other openSSL versions!'''

&lt;br&gt;Everything you read here was tested on Slackware 12&lt;br&gt;

; wikipedia says about openSSL:
: ''OpenSSL is an open source implementation of the SSL and TLS protocols. The core library (written in the C programming language) implements the basic cryptographic functions and provides various utility functions. Wrappers allowing the use of the OpenSSL library in a variety of computer languages are available.''

There are many ways to use openSSL. This just covers certificates for use with httpd. You can also use easy-rsa that comes with the openVPN package and can be found in ''/usr/doc/openvpn-2.0.9/easy-rsa/''. For more information read the included ''README'' or look here: [http://openvpn.net/easyrsa.html A Guide to basic RSA Key Management].
Normally you will make a ''Certificate Signing Request (CSR)'' and send this one to a ''Certifying Authority (CA)'' to be signed. But since we don't wanna pay for this and only want to use it for our own special purpose, we don't need to do that and sign everything ourself.

= openSSL + httpd =
Switch to ''/etc/ssl''
&lt;pre&gt;
cd /etc/ssl
&lt;/pre&gt;

In this directory you should see the following listing.  One some non-Slackware linuxes, or if OpenSSL was installed from source, the appropriate directory might be ''/etc/openssl''.
&lt;pre&gt;
root@pecan:/etc/ssl# ls -l
total 24
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 certs/
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 misc/
-rw-r--r-- 1 root root 9374 2007-06-13 12:40 openssl.cnf
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 private/
root@pecan:/etc/ssl# 
&lt;/pre&gt;

We need to generate a private and public RSA key file.
The public key is used to encrypt messages to you and is distributed with your certificate.

== Creating a Self-Signed ''Certificate'' (CRT) ==

=== openssl.cnf + openSSL DB ===
(You should still do this step even if you are buying a commercial certificate.) First things first, so we gotta edit this file, mainly the ''[ CA_default ]'' section.
The 
&lt;pre&gt;
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
...
certificate	= $dir/cacert.pem 	# The CA certificate
...
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
...
&lt;/pre&gt;
to
&lt;pre&gt;
[ CA_default ]

dir		= /etc/ssl		# Where everything is kept
...
certificate	= $dir/certs/ca.crt   	# The CA certificate
...
crl		= $dir/crl/ca.crl	# The current CRL
private_key	= $dir/private/ca.key   # The private key
...
&lt;/pre&gt;
You can even change more options in this file but be aware what you are doing.&lt;br&gt;
openSSL has a database for storing information such as ''Certificate Revocation Lists'' (CRL). Since these files don't exist on startup and we don't use the ''CA.sh'' or ''CA.pl'' scripts we got to create them ourself:
&lt;pre&gt;
mkdir newcerts certs crl private
touch serial index.txt crlnumber crl/ca.crl
echo 01 | tee serial | tee crlnumber | Tee crl/ca.crl
&lt;/pre&gt;
Thanks to ''alienBOB''. Hail to tee king! :p

You will want to create your CRL file in correct PEM format - you can use the command "openssl ca -config etc/ssl/openssl.cnf \
      -gencrl -out /etc/ssl/crl/ca.crl"

=== Becoming a ''Certification Authority'' (CA) ===
(Skip this step if you are buying a certificate from a commercial certificate authority such as GoDaddy.) Before you can create and sign your own certificates, you first have to establish yourself as a "Certificate Authority".
To do so, we first create our key file (with a public and a private key) and use it to create our "master certificate" to use when signing other certificates.

; Generate the CA RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/ca.key 4096&lt;/pre&gt;
; Create the CA CRT with the CA RSA Key
: &lt;pre&gt;openssl req -new -x509 -days 3650 -key private/ca.key -out certs/ca.crt&lt;/pre&gt;

=== Create Server CRT ===
A CRT contains your RSA public key, your name, the name of the CA, and is digitally signed by the CA. Browsers that know the CA can verify the signature on that CRT, thereby obtaining your RSA public key. That enables them to send messages which only you can decrypt.
The next step is to create a Server RSA key, generate a ''Certificate Signing Request'' (CSR) out of it and sign it with our CA CRT to get a working SSL CRT for our server.
A CSR is a digital file which contains your public key and your name. Normally you would send the CSR to a CA, who will convert it into a real certificate, by signing it.

; Generate the Server RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/server.key 1024&lt;/pre&gt;
; Create the Server CSR using the Server RSA Key
: '''When asked for the CommonName (CN) enter your domain!'''
: &lt;pre&gt;openssl req -new -key private/server.key -out private/server.csr&lt;/pre&gt;
; Sign the CSR with our CA CRT
: &lt;pre&gt;openssl ca -in private/server.csr -out certs/server.crt&lt;/pre&gt;

You can now delete ''server.csr'' if you want, because it is no longer needed.

(If you are using a commercially signed certificate from a place such as GoDaddy, do the first two commands above but not the last.  Then do ''cat private/server.csr'' to get the text of the certificate request, which you will paste into GoDaddy's web interface to get the certificate.  GoDaddy will then email the email address listed in the ''whois'' information for that domain (Make sure you haven't put in a fake address there to avoid spam!), and after the link in that email is clicked, GoDaddy will email another link to you from which you download a zip file.

The zip file will contain two .crt files, and you should put both of them in /etc/ssl/certs.  Other commerical certificate authorities follow a very similar procedure.)

== Setup httpd ==
=== Edit httpd.conf ===
The whole httpd config is located in ''/etc/httpd''. Fire up your preferred text editor and simply change this at Line 459:
&lt;pre&gt;
# Secure (SSL/TLS) connections
#Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to this
&lt;pre&gt;
# Secure (SSL/TLS) connections
Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to enable SSL support.

You may also have to uncomment the line that starts ''LoadModule ssl_module''.

=== Edit extra/httpd-ssl.conf ===
Now we're going into the guts of the httpd SSL config. Search for ''SSLCertificateFile'' and ''SSLCertificateKeyFile'' change the path to our newly created CRT:
&lt;pre&gt;
...
SSLCertificateFile /etc/ssl/certs/server.crt
...
SSLCertificateKeyFile /etc/ssl/private/server.key
...
SSLCertificateChainFile /etc/ssl/certs/server.crt
...
SSLCACertificatePath /etc/ssl/certs
SSLCACertificateFile /etc/ssl/certs/ca.crt
...
SSLCARevocationPath /etc/ssl/crl
SSLCARevocationFile /etc/ssl/crl/ca.crl
...
&lt;/pre&gt;

(If you have purchased a certificate from a commercial authority, the SSLCertificateFile will be one of the two files you receive from the CA (GoDaddy or VeriSign or whomever), and the SSLCACertificateFile will be the other.  The files will be named such that you can tell which is which -- the SSLCertificateFile will probably be something like ''www.yourdomainname.com.crt'' and the SSLCACertificateFile will be something like ''nameofca-bundle.crt''.)

== Pass-phrase on httpd startup ==
The reason this dialog pops up at startup and every re-start is that the RSA private key inside your ''server.key'' file is stored in encrypted format for security reasons. The pass-phrase is needed decrypt this file, so it can be read and parsed. Removing the pass-phrase removes a layer of security from your server - proceed with caution!
&lt;ol&gt;
&lt;li&gt;
Remove the encryption from the RSA private key (while keeping a backup copy of the original file):
&lt;pre&gt;
cd /etc/ssl
mv private/server.key private/server.key.org
cd private
openssl rsa -in server.key.org -out server.key
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
Make sure the server.key file is only readable by root since it is decrypted:
&lt;pre&gt;
cd /etc/ssl
chmod 0400 private/server.key
&lt;/pre&gt;
&lt;/li&gt;&lt;/ol&gt;
Now server.key contains an unencrypted copy of the key. If you point your server at this file, it will not prompt you for a pass-phrase. HOWEVER, if anyone gets this key they will be able to impersonate you on the net. PLEASE make sure that the permissions on this file are such that only root or the web server user can read it (preferably get your web server to start as root but run as another user, and have the key readable only by root).

As an alternative approach you can use the ''SSLPassPhraseDialog exec:/path/to/program'' facility. Bear in mind that this is neither more nor less secure, of course.

== Verifying and debugging ==
If you simply want to see every information on a CRT:
&lt;pre&gt;openssl x509 -noout -text -in XXX.crt&lt;/pre&gt;

=== Verifying ===
; Verify that a private key matches its Certificate
: Generate a MD5 out of the public key/CRT and compare
: &lt;pre&gt;openssl x509 -noout -modulus -in private/XXX.crt | openssl md5 &amp;&amp; openssl rsa -noout -modulus -in private/XXX.key | openssl md5&lt;/pre&gt;

=== Debugging ===
; s_server - Debugging clients
: &lt;pre&gt;openssl s_server -accept 443 -www&lt;/pre&gt;
; s_client - Debugging servers
: &lt;pre&gt;openssl s_client -connect localhost:443&lt;/pre&gt; or &lt;pre&gt;openssl s_client -connect localhost:443 -state -debug&lt;/pre&gt;

== Security ==
All the files expect the CRTs are only for your eyes, so we change the permissons:
&lt;pre&gt;chmod 0400 private/*.key&lt;/pre&gt;

=== Client Revokation ===
This is only needed if your server certificate is compromised (eg. someone hacked your server and stole your server.key).
&lt;pre&gt;
openssl ca -gencrl -keyfile private/ca.key -cert certs/ca.crt -out crl/ca.crl
&lt;/pre&gt;
That generated us the needed files which we use when we want to revoke a CRT.
&lt;br&gt;&lt;br&gt;
Now that we got a compromised CRT, we got to get rid of it:
&lt;pre&gt;openssl ca -revoke certs/server.crt -keyfile private/ca.key -cert certs/ca.crt&lt;/pre&gt;

== Other ==

=== Change the pass-phrase ===
&lt;pre&gt;
openssl rsa -des3 -in server.key -out server.key.new
mv server.key.new server.key
&lt;/pre&gt;
The first time you're asked for a PEM pass-phrase, you should enter the old pass-phrase. After that, you'll be asked again to enter a pass-phrase - this time, use the new pass-phrase. If you are asked to verify the pass-phrase, you'll need to enter the new pass-phrase a second time.

=== CRT for Clients ===
Ok.. i won't write anything on this, and simply just C/P:
&lt;pre&gt;
openssl genrsa -des3 -out private/client1_priv.key 2048
openssl genrsa -des3 -out private/client2_priv.key 2048
# and so on... depends on how much clients you wanna serv...
openssl req -new -key private/client1_priv.key -out private/client1.csr
openssl req -new -key private/client2_priv.key -out private/client2.csr
# and so on...
openssl ca -in private/client1.csr -out private/client1.crt
openssl ca -in private/client2.csr -out private/client2.crt
cp private/client1.crt private/client1_preconv.crt 
cat private/client1.key &gt;&gt; private/client1_preconv.crt
openssl pkcs12 -export -in private/client1_preconv.crt -out private/client1_postconv.p12 
&lt;/pre&gt;
Install in the clients browser... and change httpd.conf:
&lt;pre&gt;
SSLCACertificateFile PATH/TO/server.crt
SSLVerifyClient require
SSLVerifyDepth 1
&lt;/pre&gt;

=== Convert CRT from PEM to DER format ===
Normally all CRTs are stored in the PEM format.
&lt;pre&gt;openssl x509 -in ca.crt -out ca.crt.der -outform DER&lt;/pre&gt;

== Testing the CRT ==
If you have live web sites, you might wish to test your configuration before restarting apache, to avoid having that panicy few minutes of downtime while you scramble to see what you can do faster, fix the problem or copy back your backup configs.  Test like this:
&lt;pre&gt;httpd -t&lt;/pre&gt;
Look at the error messages it prints out, or the error_log as explained below, if it doesn't work.

Restart your httpd:
&lt;pre&gt;/etc/rc.d/rc.httpd restart&lt;/pre&gt;
Take a look at the httpd ''error_log'' and scroll to the end of the file:
&lt;pre&gt;jed /var/log/httpd/error_log&lt;/pre&gt;
If your getting an error like this:
&lt;pre&gt;[error] Init: Unable to read pass phrase [Hint: key introduced or changed before restart?]&lt;/pre&gt;
... then you should take a look at ''Pass-phrase on httpd startup'' ...

= openSSL + openVPN =
$foo ... maybe next month...

= External Links =
* [http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html SSL/TLS Strong Encryption: FAQ @ httpd.apache.org]
* [http://www.tc.umn.edu/~brams006/selfsign.html Creating a self-signed SSL certificate]
* [http://www.madboa.com/geek/openssl/ OpenSSL Command-Line HOWTO]
* [http://www.5dollarwhitebox.org/wiki/index.php/Howtos_Self_Signed_SSL_Certificates OpenSSL Quick Reference]
* [http://www.opensourcehowto.org/how-to/apache/setup-apache2-with-openssl.html Setup Apache2 with OpenSSL]
* [http://www.marschke.info/admin/ap_opssl_https.html Apache2, OpenSSL und HTTPS: Server- und Client-Authentifizierung mit Zertifikaten über verschlüsselte Internet-Verbindungen]
* [http://www.online-tutorials.net/security/openssl-tutorial/tutorials-t-69-207.html openSSL / openVPN.. comming soon]</text>
    <sha1>ac109dd72d8bde85795b861281e9414cac57711b</sha1>
  </revision>
  <revision>
    <id>991</id>
    <parentid>990</parentid>
    <timestamp>2017-05-28T13:25:44Z</timestamp>
    <contributor>
      <username>Krakanut</username>
      <id>364</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13128" xml:space="preserve">[[Category:Tutorials]]
= openSSL 0.9.8e =
'''IMPORTANT: Since this version has a [http://www.mail-archive.com/openssl-users@openssl.org/msg48671.html bug in the blowfish encryption] it is recommended not to use blowfish since it is incompatible with all other openSSL versions!'''

&lt;br&gt;Everything you read here was tested on Slackware 12&lt;br&gt;

; wikipedia says about openSSL:
: ''OpenSSL is an open source implementation of the SSL and TLS protocols. The core library (written in the C programming language) implements the basic cryptographic functions and provides various utility functions. Wrappers allowing the use of the OpenSSL library in a variety of computer languages are available.''

There are many ways to use openSSL. This just covers certificates for use with httpd. You can also use easy-rsa that comes with the openVPN package and can be found in ''/usr/doc/openvpn-2.0.9/easy-rsa/''. For more information read the included ''README'' or look here: [http://openvpn.net/easyrsa.html A Guide to basic RSA Key Management].
Normally you will make a ''Certificate Signing Request (CSR)'' and send this one to a ''Certifying Authority (CA)'' to be signed. But since we don't wanna pay for this and only want to use it for our own special purpose, we don't need to do that and sign everything ourself.

= openSSL + httpd =
Switch to ''/etc/ssl''
&lt;pre&gt;
cd /etc/ssl
&lt;/pre&gt;

In this directory you should see the following listing.  One some non-Slackware linuxes, or if OpenSSL was installed from source, the appropriate directory might be ''/etc/openssl''.
&lt;pre&gt;
root@pecan:/etc/ssl# ls -l
total 24
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 certs/
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 misc/
-rw-r--r-- 1 root root 9374 2007-06-13 12:40 openssl.cnf
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 private/
root@pecan:/etc/ssl# 
&lt;/pre&gt;

We need to generate a private and public RSA key file.
The public key is used to encrypt messages to you and is distributed with your certificate.

== Creating a Self-Signed ''Certificate'' (CRT) ==

=== openssl.cnf + openSSL DB ===
(You should still do this step even if you are buying a commercial certificate.) First things first, so we gotta edit this file, mainly the ''[ CA_default ]'' section.
The 
&lt;pre&gt;
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
...
certificate	= $dir/cacert.pem 	# The CA certificate
...
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
...
&lt;/pre&gt;
to
&lt;pre&gt;
[ CA_default ]

dir		= /etc/ssl		# Where everything is kept
...
certificate	= $dir/certs/ca.crt   	# The CA certificate
...
crl		= $dir/crl/ca.crl	# The current CRL
private_key	= $dir/private/ca.key   # The private key
...
&lt;/pre&gt;
You can even change more options in this file but be aware what you are doing.&lt;br&gt;
openSSL has a database for storing information such as ''Certificate Revocation Lists'' (CRL). Since these files don't exist on startup and we don't use the ''CA.sh'' or ''CA.pl'' scripts we got to create them ourself:
&lt;pre&gt;
mkdir newcerts certs crl private
touch serial index.txt crlnumber crl/ca.crl
echo 01 | tee serial | tee crlnumber | Tee crl/ca.crl
&lt;/pre&gt;
Thanks to ''alienBOB''. Hail to tee king! :p

You will want to create your CRL file in correct PEM format

&lt;pre&gt;
openssl ca -config etc/ssl/openssl.cnf -gencrl -out /etc/ssl/crl/ca.crl
&lt;/pre&gt;

=== Becoming a ''Certification Authority'' (CA) ===
(Skip this step if you are buying a certificate from a commercial certificate authority such as GoDaddy.) Before you can create and sign your own certificates, you first have to establish yourself as a "Certificate Authority".
To do so, we first create our key file (with a public and a private key) and use it to create our "master certificate" to use when signing other certificates.

; Generate the CA RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/ca.key 4096&lt;/pre&gt;
; Create the CA CRT with the CA RSA Key
: &lt;pre&gt;openssl req -new -x509 -days 3650 -key private/ca.key -out certs/ca.crt&lt;/pre&gt;

=== Create Server CRT ===
A CRT contains your RSA public key, your name, the name of the CA, and is digitally signed by the CA. Browsers that know the CA can verify the signature on that CRT, thereby obtaining your RSA public key. That enables them to send messages which only you can decrypt.
The next step is to create a Server RSA key, generate a ''Certificate Signing Request'' (CSR) out of it and sign it with our CA CRT to get a working SSL CRT for our server.
A CSR is a digital file which contains your public key and your name. Normally you would send the CSR to a CA, who will convert it into a real certificate, by signing it.

; Generate the Server RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/server.key 1024&lt;/pre&gt;
; Create the Server CSR using the Server RSA Key
: '''When asked for the CommonName (CN) enter your domain!'''
: &lt;pre&gt;openssl req -new -key private/server.key -out private/server.csr&lt;/pre&gt;
; Sign the CSR with our CA CRT
: &lt;pre&gt;openssl ca -in private/server.csr -out certs/server.crt&lt;/pre&gt;

You can now delete ''server.csr'' if you want, because it is no longer needed.

(If you are using a commercially signed certificate from a place such as GoDaddy, do the first two commands above but not the last.  Then do ''cat private/server.csr'' to get the text of the certificate request, which you will paste into GoDaddy's web interface to get the certificate.  GoDaddy will then email the email address listed in the ''whois'' information for that domain (Make sure you haven't put in a fake address there to avoid spam!), and after the link in that email is clicked, GoDaddy will email another link to you from which you download a zip file.

The zip file will contain two .crt files, and you should put both of them in /etc/ssl/certs.  Other commerical certificate authorities follow a very similar procedure.)

== Setup httpd ==
=== Edit httpd.conf ===
The whole httpd config is located in ''/etc/httpd''. Fire up your preferred text editor and simply change this at Line 459:
&lt;pre&gt;
# Secure (SSL/TLS) connections
#Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to this
&lt;pre&gt;
# Secure (SSL/TLS) connections
Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to enable SSL support.

You may also have to uncomment the line that starts ''LoadModule ssl_module''.

=== Edit extra/httpd-ssl.conf ===
Now we're going into the guts of the httpd SSL config. Search for ''SSLCertificateFile'' and ''SSLCertificateKeyFile'' change the path to our newly created CRT:
&lt;pre&gt;
...
SSLCertificateFile /etc/ssl/certs/server.crt
...
SSLCertificateKeyFile /etc/ssl/private/server.key
...
SSLCertificateChainFile /etc/ssl/certs/server.crt
...
SSLCACertificatePath /etc/ssl/certs
SSLCACertificateFile /etc/ssl/certs/ca.crt
...
SSLCARevocationPath /etc/ssl/crl
SSLCARevocationFile /etc/ssl/crl/ca.crl
...
&lt;/pre&gt;

(If you have purchased a certificate from a commercial authority, the SSLCertificateFile will be one of the two files you receive from the CA (GoDaddy or VeriSign or whomever), and the SSLCACertificateFile will be the other.  The files will be named such that you can tell which is which -- the SSLCertificateFile will probably be something like ''www.yourdomainname.com.crt'' and the SSLCACertificateFile will be something like ''nameofca-bundle.crt''.)

== Pass-phrase on httpd startup ==
The reason this dialog pops up at startup and every re-start is that the RSA private key inside your ''server.key'' file is stored in encrypted format for security reasons. The pass-phrase is needed decrypt this file, so it can be read and parsed. Removing the pass-phrase removes a layer of security from your server - proceed with caution!
&lt;ol&gt;
&lt;li&gt;
Remove the encryption from the RSA private key (while keeping a backup copy of the original file):
&lt;pre&gt;
cd /etc/ssl
mv private/server.key private/server.key.org
cd private
openssl rsa -in server.key.org -out server.key
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
Make sure the server.key file is only readable by root since it is decrypted:
&lt;pre&gt;
cd /etc/ssl
chmod 0400 private/server.key
&lt;/pre&gt;
&lt;/li&gt;&lt;/ol&gt;
Now server.key contains an unencrypted copy of the key. If you point your server at this file, it will not prompt you for a pass-phrase. HOWEVER, if anyone gets this key they will be able to impersonate you on the net. PLEASE make sure that the permissions on this file are such that only root or the web server user can read it (preferably get your web server to start as root but run as another user, and have the key readable only by root).

As an alternative approach you can use the ''SSLPassPhraseDialog exec:/path/to/program'' facility. Bear in mind that this is neither more nor less secure, of course.

== Verifying and debugging ==
If you simply want to see every information on a CRT:
&lt;pre&gt;openssl x509 -noout -text -in XXX.crt&lt;/pre&gt;

=== Verifying ===
; Verify that a private key matches its Certificate
: Generate a MD5 out of the public key/CRT and compare
: &lt;pre&gt;openssl x509 -noout -modulus -in private/XXX.crt | openssl md5 &amp;&amp; openssl rsa -noout -modulus -in private/XXX.key | openssl md5&lt;/pre&gt;

=== Debugging ===
; s_server - Debugging clients
: &lt;pre&gt;openssl s_server -accept 443 -www&lt;/pre&gt;
; s_client - Debugging servers
: &lt;pre&gt;openssl s_client -connect localhost:443&lt;/pre&gt; or &lt;pre&gt;openssl s_client -connect localhost:443 -state -debug&lt;/pre&gt;

== Security ==
All the files expect the CRTs are only for your eyes, so we change the permissons:
&lt;pre&gt;chmod 0400 private/*.key&lt;/pre&gt;

=== Client Revokation ===
This is only needed if your server certificate is compromised (eg. someone hacked your server and stole your server.key).
&lt;pre&gt;
openssl ca -gencrl -keyfile private/ca.key -cert certs/ca.crt -out crl/ca.crl
&lt;/pre&gt;
That generated us the needed files which we use when we want to revoke a CRT.
&lt;br&gt;&lt;br&gt;
Now that we got a compromised CRT, we got to get rid of it:
&lt;pre&gt;openssl ca -revoke certs/server.crt -keyfile private/ca.key -cert certs/ca.crt&lt;/pre&gt;

== Other ==

=== Change the pass-phrase ===
&lt;pre&gt;
openssl rsa -des3 -in server.key -out server.key.new
mv server.key.new server.key
&lt;/pre&gt;
The first time you're asked for a PEM pass-phrase, you should enter the old pass-phrase. After that, you'll be asked again to enter a pass-phrase - this time, use the new pass-phrase. If you are asked to verify the pass-phrase, you'll need to enter the new pass-phrase a second time.

=== CRT for Clients ===
Ok.. i won't write anything on this, and simply just C/P:
&lt;pre&gt;
openssl genrsa -des3 -out private/client1_priv.key 2048
openssl genrsa -des3 -out private/client2_priv.key 2048
# and so on... depends on how much clients you wanna serv...
openssl req -new -key private/client1_priv.key -out private/client1.csr
openssl req -new -key private/client2_priv.key -out private/client2.csr
# and so on...
openssl ca -in private/client1.csr -out private/client1.crt
openssl ca -in private/client2.csr -out private/client2.crt
cp private/client1.crt private/client1_preconv.crt 
cat private/client1.key &gt;&gt; private/client1_preconv.crt
openssl pkcs12 -export -in private/client1_preconv.crt -out private/client1_postconv.p12 
&lt;/pre&gt;
Install in the clients browser... and change httpd.conf:
&lt;pre&gt;
SSLCACertificateFile PATH/TO/server.crt
SSLVerifyClient require
SSLVerifyDepth 1
&lt;/pre&gt;

=== Convert CRT from PEM to DER format ===
Normally all CRTs are stored in the PEM format.
&lt;pre&gt;openssl x509 -in ca.crt -out ca.crt.der -outform DER&lt;/pre&gt;

== Testing the CRT ==
If you have live web sites, you might wish to test your configuration before restarting apache, to avoid having that panicy few minutes of downtime while you scramble to see what you can do faster, fix the problem or copy back your backup configs.  Test like this:
&lt;pre&gt;httpd -t&lt;/pre&gt;
Look at the error messages it prints out, or the error_log as explained below, if it doesn't work.

Restart your httpd:
&lt;pre&gt;/etc/rc.d/rc.httpd restart&lt;/pre&gt;
Take a look at the httpd ''error_log'' and scroll to the end of the file:
&lt;pre&gt;jed /var/log/httpd/error_log&lt;/pre&gt;
If your getting an error like this:
&lt;pre&gt;[error] Init: Unable to read pass phrase [Hint: key introduced or changed before restart?]&lt;/pre&gt;
... then you should take a look at ''Pass-phrase on httpd startup'' ...

= openSSL + openVPN =
$foo ... maybe next month...

= External Links =
* [http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html SSL/TLS Strong Encryption: FAQ @ httpd.apache.org]
* [http://www.tc.umn.edu/~brams006/selfsign.html Creating a self-signed SSL certificate]
* [http://www.madboa.com/geek/openssl/ OpenSSL Command-Line HOWTO]
* [http://www.5dollarwhitebox.org/wiki/index.php/Howtos_Self_Signed_SSL_Certificates OpenSSL Quick Reference]
* [http://www.opensourcehowto.org/how-to/apache/setup-apache2-with-openssl.html Setup Apache2 with OpenSSL]
* [http://www.marschke.info/admin/ap_opssl_https.html Apache2, OpenSSL und HTTPS: Server- und Client-Authentifizierung mit Zertifikaten über verschlüsselte Internet-Verbindungen]
* [http://www.online-tutorials.net/security/openssl-tutorial/tutorials-t-69-207.html openSSL / openVPN.. comming soon]</text>
    <sha1>add227e228cfee2df0ff61a715293a5c27d2ee6b</sha1>
  </revision>
  <revision>
    <id>992</id>
    <parentid>991</parentid>
    <timestamp>2017-05-28T13:26:23Z</timestamp>
    <contributor>
      <username>Krakanut</username>
      <id>364</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13128" xml:space="preserve">[[Category:Tutorials]]
= openSSL 0.9.8e =
'''IMPORTANT: Since this version has a [http://www.mail-archive.com/openssl-users@openssl.org/msg48671.html bug in the blowfish encryption] it is recommended not to use blowfish since it is incompatible with all other openSSL versions!'''

&lt;br&gt;Everything you read here was tested on Slackware 12&lt;br&gt;

; wikipedia says about openSSL:
: ''OpenSSL is an open source implementation of the SSL and TLS protocols. The core library (written in the C programming language) implements the basic cryptographic functions and provides various utility functions. Wrappers allowing the use of the OpenSSL library in a variety of computer languages are available.''

There are many ways to use openSSL. This just covers certificates for use with httpd. You can also use easy-rsa that comes with the openVPN package and can be found in ''/usr/doc/openvpn-2.0.9/easy-rsa/''. For more information read the included ''README'' or look here: [http://openvpn.net/easyrsa.html A Guide to basic RSA Key Management].
Normally you will make a ''Certificate Signing Request (CSR)'' and send this one to a ''Certifying Authority (CA)'' to be signed. But since we don't wanna pay for this and only want to use it for our own special purpose, we don't need to do that and sign everything ourself.

= openSSL + httpd =
Switch to ''/etc/ssl''
&lt;pre&gt;
cd /etc/ssl
&lt;/pre&gt;

In this directory you should see the following listing.  One some non-Slackware linuxes, or if OpenSSL was installed from source, the appropriate directory might be ''/etc/openssl''.
&lt;pre&gt;
root@pecan:/etc/ssl# ls -l
total 24
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 certs/
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 misc/
-rw-r--r-- 1 root root 9374 2007-06-13 12:40 openssl.cnf
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 private/
root@pecan:/etc/ssl# 
&lt;/pre&gt;

We need to generate a private and public RSA key file.
The public key is used to encrypt messages to you and is distributed with your certificate.

== Creating a Self-Signed ''Certificate'' (CRT) ==

=== openssl.cnf + openSSL DB ===
(You should still do this step even if you are buying a commercial certificate.) First things first, so we gotta edit this file, mainly the ''[ CA_default ]'' section.
The 
&lt;pre&gt;
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
...
certificate	= $dir/cacert.pem 	# The CA certificate
...
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
...
&lt;/pre&gt;
to
&lt;pre&gt;
[ CA_default ]

dir		= /etc/ssl		# Where everything is kept
...
certificate	= $dir/certs/ca.crt   	# The CA certificate
...
crl		= $dir/crl/ca.crl	# The current CRL
private_key	= $dir/private/ca.key   # The private key
...
&lt;/pre&gt;
You can even change more options in this file but be aware what you are doing.&lt;br&gt;
openSSL has a database for storing information such as ''Certificate Revocation Lists'' (CRL). Since these files don't exist on startup and we don't use the ''CA.sh'' or ''CA.pl'' scripts we got to create them ourself:
&lt;pre&gt;
mkdir newcerts certs crl private
touch serial index.txt crlnumber crl/ca.crl
echo 01 | tee serial | tee crlnumber | Tee crl/ca.crl
&lt;/pre&gt;
Thanks to ''alienBOB''. Hail to tee king! :p

You will need to create your CRL file in correct PEM format

&lt;pre&gt;
openssl ca -config etc/ssl/openssl.cnf -gencrl -out /etc/ssl/crl/ca.crl
&lt;/pre&gt;

=== Becoming a ''Certification Authority'' (CA) ===
(Skip this step if you are buying a certificate from a commercial certificate authority such as GoDaddy.) Before you can create and sign your own certificates, you first have to establish yourself as a "Certificate Authority".
To do so, we first create our key file (with a public and a private key) and use it to create our "master certificate" to use when signing other certificates.

; Generate the CA RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/ca.key 4096&lt;/pre&gt;
; Create the CA CRT with the CA RSA Key
: &lt;pre&gt;openssl req -new -x509 -days 3650 -key private/ca.key -out certs/ca.crt&lt;/pre&gt;

=== Create Server CRT ===
A CRT contains your RSA public key, your name, the name of the CA, and is digitally signed by the CA. Browsers that know the CA can verify the signature on that CRT, thereby obtaining your RSA public key. That enables them to send messages which only you can decrypt.
The next step is to create a Server RSA key, generate a ''Certificate Signing Request'' (CSR) out of it and sign it with our CA CRT to get a working SSL CRT for our server.
A CSR is a digital file which contains your public key and your name. Normally you would send the CSR to a CA, who will convert it into a real certificate, by signing it.

; Generate the Server RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/server.key 1024&lt;/pre&gt;
; Create the Server CSR using the Server RSA Key
: '''When asked for the CommonName (CN) enter your domain!'''
: &lt;pre&gt;openssl req -new -key private/server.key -out private/server.csr&lt;/pre&gt;
; Sign the CSR with our CA CRT
: &lt;pre&gt;openssl ca -in private/server.csr -out certs/server.crt&lt;/pre&gt;

You can now delete ''server.csr'' if you want, because it is no longer needed.

(If you are using a commercially signed certificate from a place such as GoDaddy, do the first two commands above but not the last.  Then do ''cat private/server.csr'' to get the text of the certificate request, which you will paste into GoDaddy's web interface to get the certificate.  GoDaddy will then email the email address listed in the ''whois'' information for that domain (Make sure you haven't put in a fake address there to avoid spam!), and after the link in that email is clicked, GoDaddy will email another link to you from which you download a zip file.

The zip file will contain two .crt files, and you should put both of them in /etc/ssl/certs.  Other commerical certificate authorities follow a very similar procedure.)

== Setup httpd ==
=== Edit httpd.conf ===
The whole httpd config is located in ''/etc/httpd''. Fire up your preferred text editor and simply change this at Line 459:
&lt;pre&gt;
# Secure (SSL/TLS) connections
#Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to this
&lt;pre&gt;
# Secure (SSL/TLS) connections
Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to enable SSL support.

You may also have to uncomment the line that starts ''LoadModule ssl_module''.

=== Edit extra/httpd-ssl.conf ===
Now we're going into the guts of the httpd SSL config. Search for ''SSLCertificateFile'' and ''SSLCertificateKeyFile'' change the path to our newly created CRT:
&lt;pre&gt;
...
SSLCertificateFile /etc/ssl/certs/server.crt
...
SSLCertificateKeyFile /etc/ssl/private/server.key
...
SSLCertificateChainFile /etc/ssl/certs/server.crt
...
SSLCACertificatePath /etc/ssl/certs
SSLCACertificateFile /etc/ssl/certs/ca.crt
...
SSLCARevocationPath /etc/ssl/crl
SSLCARevocationFile /etc/ssl/crl/ca.crl
...
&lt;/pre&gt;

(If you have purchased a certificate from a commercial authority, the SSLCertificateFile will be one of the two files you receive from the CA (GoDaddy or VeriSign or whomever), and the SSLCACertificateFile will be the other.  The files will be named such that you can tell which is which -- the SSLCertificateFile will probably be something like ''www.yourdomainname.com.crt'' and the SSLCACertificateFile will be something like ''nameofca-bundle.crt''.)

== Pass-phrase on httpd startup ==
The reason this dialog pops up at startup and every re-start is that the RSA private key inside your ''server.key'' file is stored in encrypted format for security reasons. The pass-phrase is needed decrypt this file, so it can be read and parsed. Removing the pass-phrase removes a layer of security from your server - proceed with caution!
&lt;ol&gt;
&lt;li&gt;
Remove the encryption from the RSA private key (while keeping a backup copy of the original file):
&lt;pre&gt;
cd /etc/ssl
mv private/server.key private/server.key.org
cd private
openssl rsa -in server.key.org -out server.key
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
Make sure the server.key file is only readable by root since it is decrypted:
&lt;pre&gt;
cd /etc/ssl
chmod 0400 private/server.key
&lt;/pre&gt;
&lt;/li&gt;&lt;/ol&gt;
Now server.key contains an unencrypted copy of the key. If you point your server at this file, it will not prompt you for a pass-phrase. HOWEVER, if anyone gets this key they will be able to impersonate you on the net. PLEASE make sure that the permissions on this file are such that only root or the web server user can read it (preferably get your web server to start as root but run as another user, and have the key readable only by root).

As an alternative approach you can use the ''SSLPassPhraseDialog exec:/path/to/program'' facility. Bear in mind that this is neither more nor less secure, of course.

== Verifying and debugging ==
If you simply want to see every information on a CRT:
&lt;pre&gt;openssl x509 -noout -text -in XXX.crt&lt;/pre&gt;

=== Verifying ===
; Verify that a private key matches its Certificate
: Generate a MD5 out of the public key/CRT and compare
: &lt;pre&gt;openssl x509 -noout -modulus -in private/XXX.crt | openssl md5 &amp;&amp; openssl rsa -noout -modulus -in private/XXX.key | openssl md5&lt;/pre&gt;

=== Debugging ===
; s_server - Debugging clients
: &lt;pre&gt;openssl s_server -accept 443 -www&lt;/pre&gt;
; s_client - Debugging servers
: &lt;pre&gt;openssl s_client -connect localhost:443&lt;/pre&gt; or &lt;pre&gt;openssl s_client -connect localhost:443 -state -debug&lt;/pre&gt;

== Security ==
All the files expect the CRTs are only for your eyes, so we change the permissons:
&lt;pre&gt;chmod 0400 private/*.key&lt;/pre&gt;

=== Client Revokation ===
This is only needed if your server certificate is compromised (eg. someone hacked your server and stole your server.key).
&lt;pre&gt;
openssl ca -gencrl -keyfile private/ca.key -cert certs/ca.crt -out crl/ca.crl
&lt;/pre&gt;
That generated us the needed files which we use when we want to revoke a CRT.
&lt;br&gt;&lt;br&gt;
Now that we got a compromised CRT, we got to get rid of it:
&lt;pre&gt;openssl ca -revoke certs/server.crt -keyfile private/ca.key -cert certs/ca.crt&lt;/pre&gt;

== Other ==

=== Change the pass-phrase ===
&lt;pre&gt;
openssl rsa -des3 -in server.key -out server.key.new
mv server.key.new server.key
&lt;/pre&gt;
The first time you're asked for a PEM pass-phrase, you should enter the old pass-phrase. After that, you'll be asked again to enter a pass-phrase - this time, use the new pass-phrase. If you are asked to verify the pass-phrase, you'll need to enter the new pass-phrase a second time.

=== CRT for Clients ===
Ok.. i won't write anything on this, and simply just C/P:
&lt;pre&gt;
openssl genrsa -des3 -out private/client1_priv.key 2048
openssl genrsa -des3 -out private/client2_priv.key 2048
# and so on... depends on how much clients you wanna serv...
openssl req -new -key private/client1_priv.key -out private/client1.csr
openssl req -new -key private/client2_priv.key -out private/client2.csr
# and so on...
openssl ca -in private/client1.csr -out private/client1.crt
openssl ca -in private/client2.csr -out private/client2.crt
cp private/client1.crt private/client1_preconv.crt 
cat private/client1.key &gt;&gt; private/client1_preconv.crt
openssl pkcs12 -export -in private/client1_preconv.crt -out private/client1_postconv.p12 
&lt;/pre&gt;
Install in the clients browser... and change httpd.conf:
&lt;pre&gt;
SSLCACertificateFile PATH/TO/server.crt
SSLVerifyClient require
SSLVerifyDepth 1
&lt;/pre&gt;

=== Convert CRT from PEM to DER format ===
Normally all CRTs are stored in the PEM format.
&lt;pre&gt;openssl x509 -in ca.crt -out ca.crt.der -outform DER&lt;/pre&gt;

== Testing the CRT ==
If you have live web sites, you might wish to test your configuration before restarting apache, to avoid having that panicy few minutes of downtime while you scramble to see what you can do faster, fix the problem or copy back your backup configs.  Test like this:
&lt;pre&gt;httpd -t&lt;/pre&gt;
Look at the error messages it prints out, or the error_log as explained below, if it doesn't work.

Restart your httpd:
&lt;pre&gt;/etc/rc.d/rc.httpd restart&lt;/pre&gt;
Take a look at the httpd ''error_log'' and scroll to the end of the file:
&lt;pre&gt;jed /var/log/httpd/error_log&lt;/pre&gt;
If your getting an error like this:
&lt;pre&gt;[error] Init: Unable to read pass phrase [Hint: key introduced or changed before restart?]&lt;/pre&gt;
... then you should take a look at ''Pass-phrase on httpd startup'' ...

= openSSL + openVPN =
$foo ... maybe next month...

= External Links =
* [http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html SSL/TLS Strong Encryption: FAQ @ httpd.apache.org]
* [http://www.tc.umn.edu/~brams006/selfsign.html Creating a self-signed SSL certificate]
* [http://www.madboa.com/geek/openssl/ OpenSSL Command-Line HOWTO]
* [http://www.5dollarwhitebox.org/wiki/index.php/Howtos_Self_Signed_SSL_Certificates OpenSSL Quick Reference]
* [http://www.opensourcehowto.org/how-to/apache/setup-apache2-with-openssl.html Setup Apache2 with OpenSSL]
* [http://www.marschke.info/admin/ap_opssl_https.html Apache2, OpenSSL und HTTPS: Server- und Client-Authentifizierung mit Zertifikaten über verschlüsselte Internet-Verbindungen]
* [http://www.online-tutorials.net/security/openssl-tutorial/tutorials-t-69-207.html openSSL / openVPN.. comming soon]</text>
    <sha1>d3ecc852402c2ee30ab67a5811517f0093a94acc</sha1>
  </revision>
  <revision>
    <id>993</id>
    <parentid>992</parentid>
    <timestamp>2017-05-28T13:29:00Z</timestamp>
    <contributor>
      <username>Krakanut</username>
      <id>364</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="13253" xml:space="preserve">[[Category:Tutorials]]
= openSSL 0.9.8e =
'''IMPORTANT: Since this version has a [http://www.mail-archive.com/openssl-users@openssl.org/msg48671.html bug in the blowfish encryption] it is recommended not to use blowfish since it is incompatible with all other openSSL versions!'''

&lt;br&gt;Everything you read here was tested on Slackware 12&lt;br&gt;

; wikipedia says about openSSL:
: ''OpenSSL is an open source implementation of the SSL and TLS protocols. The core library (written in the C programming language) implements the basic cryptographic functions and provides various utility functions. Wrappers allowing the use of the OpenSSL library in a variety of computer languages are available.''

There are many ways to use openSSL. This just covers certificates for use with httpd. You can also use easy-rsa that comes with the openVPN package and can be found in ''/usr/doc/openvpn-2.0.9/easy-rsa/''. For more information read the included ''README'' or look here: [http://openvpn.net/easyrsa.html A Guide to basic RSA Key Management].
Normally you will make a ''Certificate Signing Request (CSR)'' and send this one to a ''Certifying Authority (CA)'' to be signed. But since we don't wanna pay for this and only want to use it for our own special purpose, we don't need to do that and sign everything ourself.

= openSSL + httpd =
Switch to ''/etc/ssl''
&lt;pre&gt;
cd /etc/ssl
&lt;/pre&gt;

In this directory you should see the following listing.  One some non-Slackware linuxes, or if OpenSSL was installed from source, the appropriate directory might be ''/etc/openssl''.
&lt;pre&gt;
root@pecan:/etc/ssl# ls -l
total 24
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 certs/
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 misc/
-rw-r--r-- 1 root root 9374 2007-06-13 12:40 openssl.cnf
drwxr-xr-x 2 root root 4096 2007-06-13 12:40 private/
root@pecan:/etc/ssl# 
&lt;/pre&gt;

We need to generate a private and public RSA key file.
The public key is used to encrypt messages to you and is distributed with your certificate.

== Creating a Self-Signed ''Certificate'' (CRT) ==

=== openssl.cnf + openSSL DB ===
(You should still do this step even if you are buying a commercial certificate.) First things first, so we gotta edit this file, mainly the ''[ CA_default ]'' section.
The 
&lt;pre&gt;
[ CA_default ]

dir		= ./demoCA		# Where everything is kept
...
certificate	= $dir/cacert.pem 	# The CA certificate
...
crl		= $dir/crl.pem 		# The current CRL
private_key	= $dir/private/cakey.pem# The private key
...
&lt;/pre&gt;
to
&lt;pre&gt;
[ CA_default ]

dir		= /etc/ssl		# Where everything is kept
...
certificate	= $dir/certs/ca.crt   	# The CA certificate
...
crl		= $dir/crl/ca.crl	# The current CRL
private_key	= $dir/private/ca.key   # The private key
...
&lt;/pre&gt;
You can even change more options in this file but be aware what you are doing.&lt;br&gt;
openSSL has a database for storing information such as ''Certificate Revocation Lists'' (CRL). Since these files don't exist on startup and we don't use the ''CA.sh'' or ''CA.pl'' scripts we got to create them ourself:
&lt;pre&gt;
mkdir newcerts certs crl private
touch serial index.txt crlnumber crl/ca.crl
echo 01 | tee serial | tee crlnumber | Tee crl/ca.crl
&lt;/pre&gt;
Thanks to ''alienBOB''. Hail to tee king! :p

You will need to create your CRL file in correct PEM format

&lt;pre&gt;
openssl ca -config /etc/ssl/openssl.cnf -gencrl -out /etc/ssl/crl/ca.crl
&lt;/pre&gt;

You can test that the crl file is correct with the command:

&lt;pre&gt;
openssl crl -text -in /etc/ssl/crl/ca.crl -noout
&lt;/pre&gt;

=== Becoming a ''Certification Authority'' (CA) ===
(Skip this step if you are buying a certificate from a commercial certificate authority such as GoDaddy.) Before you can create and sign your own certificates, you first have to establish yourself as a "Certificate Authority".
To do so, we first create our key file (with a public and a private key) and use it to create our "master certificate" to use when signing other certificates.

; Generate the CA RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/ca.key 4096&lt;/pre&gt;
; Create the CA CRT with the CA RSA Key
: &lt;pre&gt;openssl req -new -x509 -days 3650 -key private/ca.key -out certs/ca.crt&lt;/pre&gt;

=== Create Server CRT ===
A CRT contains your RSA public key, your name, the name of the CA, and is digitally signed by the CA. Browsers that know the CA can verify the signature on that CRT, thereby obtaining your RSA public key. That enables them to send messages which only you can decrypt.
The next step is to create a Server RSA key, generate a ''Certificate Signing Request'' (CSR) out of it and sign it with our CA CRT to get a working SSL CRT for our server.
A CSR is a digital file which contains your public key and your name. Normally you would send the CSR to a CA, who will convert it into a real certificate, by signing it.

; Generate the Server RSA Key (Triple-DES encrypted and PEM formatted)
: &lt;pre&gt;openssl genrsa -des3 -out private/server.key 1024&lt;/pre&gt;
; Create the Server CSR using the Server RSA Key
: '''When asked for the CommonName (CN) enter your domain!'''
: &lt;pre&gt;openssl req -new -key private/server.key -out private/server.csr&lt;/pre&gt;
; Sign the CSR with our CA CRT
: &lt;pre&gt;openssl ca -in private/server.csr -out certs/server.crt&lt;/pre&gt;

You can now delete ''server.csr'' if you want, because it is no longer needed.

(If you are using a commercially signed certificate from a place such as GoDaddy, do the first two commands above but not the last.  Then do ''cat private/server.csr'' to get the text of the certificate request, which you will paste into GoDaddy's web interface to get the certificate.  GoDaddy will then email the email address listed in the ''whois'' information for that domain (Make sure you haven't put in a fake address there to avoid spam!), and after the link in that email is clicked, GoDaddy will email another link to you from which you download a zip file.

The zip file will contain two .crt files, and you should put both of them in /etc/ssl/certs.  Other commerical certificate authorities follow a very similar procedure.)

== Setup httpd ==
=== Edit httpd.conf ===
The whole httpd config is located in ''/etc/httpd''. Fire up your preferred text editor and simply change this at Line 459:
&lt;pre&gt;
# Secure (SSL/TLS) connections
#Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to this
&lt;pre&gt;
# Secure (SSL/TLS) connections
Include /etc/httpd/extra/httpd-ssl.conf
&lt;/pre&gt;
to enable SSL support.

You may also have to uncomment the line that starts ''LoadModule ssl_module''.

=== Edit extra/httpd-ssl.conf ===
Now we're going into the guts of the httpd SSL config. Search for ''SSLCertificateFile'' and ''SSLCertificateKeyFile'' change the path to our newly created CRT:
&lt;pre&gt;
...
SSLCertificateFile /etc/ssl/certs/server.crt
...
SSLCertificateKeyFile /etc/ssl/private/server.key
...
SSLCertificateChainFile /etc/ssl/certs/server.crt
...
SSLCACertificatePath /etc/ssl/certs
SSLCACertificateFile /etc/ssl/certs/ca.crt
...
SSLCARevocationPath /etc/ssl/crl
SSLCARevocationFile /etc/ssl/crl/ca.crl
...
&lt;/pre&gt;

(If you have purchased a certificate from a commercial authority, the SSLCertificateFile will be one of the two files you receive from the CA (GoDaddy or VeriSign or whomever), and the SSLCACertificateFile will be the other.  The files will be named such that you can tell which is which -- the SSLCertificateFile will probably be something like ''www.yourdomainname.com.crt'' and the SSLCACertificateFile will be something like ''nameofca-bundle.crt''.)

== Pass-phrase on httpd startup ==
The reason this dialog pops up at startup and every re-start is that the RSA private key inside your ''server.key'' file is stored in encrypted format for security reasons. The pass-phrase is needed decrypt this file, so it can be read and parsed. Removing the pass-phrase removes a layer of security from your server - proceed with caution!
&lt;ol&gt;
&lt;li&gt;
Remove the encryption from the RSA private key (while keeping a backup copy of the original file):
&lt;pre&gt;
cd /etc/ssl
mv private/server.key private/server.key.org
cd private
openssl rsa -in server.key.org -out server.key
&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;
Make sure the server.key file is only readable by root since it is decrypted:
&lt;pre&gt;
cd /etc/ssl
chmod 0400 private/server.key
&lt;/pre&gt;
&lt;/li&gt;&lt;/ol&gt;
Now server.key contains an unencrypted copy of the key. If you point your server at this file, it will not prompt you for a pass-phrase. HOWEVER, if anyone gets this key they will be able to impersonate you on the net. PLEASE make sure that the permissions on this file are such that only root or the web server user can read it (preferably get your web server to start as root but run as another user, and have the key readable only by root).

As an alternative approach you can use the ''SSLPassPhraseDialog exec:/path/to/program'' facility. Bear in mind that this is neither more nor less secure, of course.

== Verifying and debugging ==
If you simply want to see every information on a CRT:
&lt;pre&gt;openssl x509 -noout -text -in XXX.crt&lt;/pre&gt;

=== Verifying ===
; Verify that a private key matches its Certificate
: Generate a MD5 out of the public key/CRT and compare
: &lt;pre&gt;openssl x509 -noout -modulus -in private/XXX.crt | openssl md5 &amp;&amp; openssl rsa -noout -modulus -in private/XXX.key | openssl md5&lt;/pre&gt;

=== Debugging ===
; s_server - Debugging clients
: &lt;pre&gt;openssl s_server -accept 443 -www&lt;/pre&gt;
; s_client - Debugging servers
: &lt;pre&gt;openssl s_client -connect localhost:443&lt;/pre&gt; or &lt;pre&gt;openssl s_client -connect localhost:443 -state -debug&lt;/pre&gt;

== Security ==
All the files expect the CRTs are only for your eyes, so we change the permissons:
&lt;pre&gt;chmod 0400 private/*.key&lt;/pre&gt;

=== Client Revokation ===
This is only needed if your server certificate is compromised (eg. someone hacked your server and stole your server.key).
&lt;pre&gt;
openssl ca -gencrl -keyfile private/ca.key -cert certs/ca.crt -out crl/ca.crl
&lt;/pre&gt;
That generated us the needed files which we use when we want to revoke a CRT.
&lt;br&gt;&lt;br&gt;
Now that we got a compromised CRT, we got to get rid of it:
&lt;pre&gt;openssl ca -revoke certs/server.crt -keyfile private/ca.key -cert certs/ca.crt&lt;/pre&gt;

== Other ==

=== Change the pass-phrase ===
&lt;pre&gt;
openssl rsa -des3 -in server.key -out server.key.new
mv server.key.new server.key
&lt;/pre&gt;
The first time you're asked for a PEM pass-phrase, you should enter the old pass-phrase. After that, you'll be asked again to enter a pass-phrase - this time, use the new pass-phrase. If you are asked to verify the pass-phrase, you'll need to enter the new pass-phrase a second time.

=== CRT for Clients ===
Ok.. i won't write anything on this, and simply just C/P:
&lt;pre&gt;
openssl genrsa -des3 -out private/client1_priv.key 2048
openssl genrsa -des3 -out private/client2_priv.key 2048
# and so on... depends on how much clients you wanna serv...
openssl req -new -key private/client1_priv.key -out private/client1.csr
openssl req -new -key private/client2_priv.key -out private/client2.csr
# and so on...
openssl ca -in private/client1.csr -out private/client1.crt
openssl ca -in private/client2.csr -out private/client2.crt
cp private/client1.crt private/client1_preconv.crt 
cat private/client1.key &gt;&gt; private/client1_preconv.crt
openssl pkcs12 -export -in private/client1_preconv.crt -out private/client1_postconv.p12 
&lt;/pre&gt;
Install in the clients browser... and change httpd.conf:
&lt;pre&gt;
SSLCACertificateFile PATH/TO/server.crt
SSLVerifyClient require
SSLVerifyDepth 1
&lt;/pre&gt;

=== Convert CRT from PEM to DER format ===
Normally all CRTs are stored in the PEM format.
&lt;pre&gt;openssl x509 -in ca.crt -out ca.crt.der -outform DER&lt;/pre&gt;

== Testing the CRT ==
If you have live web sites, you might wish to test your configuration before restarting apache, to avoid having that panicy few minutes of downtime while you scramble to see what you can do faster, fix the problem or copy back your backup configs.  Test like this:
&lt;pre&gt;httpd -t&lt;/pre&gt;
Look at the error messages it prints out, or the error_log as explained below, if it doesn't work.

Restart your httpd:
&lt;pre&gt;/etc/rc.d/rc.httpd restart&lt;/pre&gt;
Take a look at the httpd ''error_log'' and scroll to the end of the file:
&lt;pre&gt;jed /var/log/httpd/error_log&lt;/pre&gt;
If your getting an error like this:
&lt;pre&gt;[error] Init: Unable to read pass phrase [Hint: key introduced or changed before restart?]&lt;/pre&gt;
... then you should take a look at ''Pass-phrase on httpd startup'' ...

= openSSL + openVPN =
$foo ... maybe next month...

= External Links =
* [http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html SSL/TLS Strong Encryption: FAQ @ httpd.apache.org]
* [http://www.tc.umn.edu/~brams006/selfsign.html Creating a self-signed SSL certificate]
* [http://www.madboa.com/geek/openssl/ OpenSSL Command-Line HOWTO]
* [http://www.5dollarwhitebox.org/wiki/index.php/Howtos_Self_Signed_SSL_Certificates OpenSSL Quick Reference]
* [http://www.opensourcehowto.org/how-to/apache/setup-apache2-with-openssl.html Setup Apache2 with OpenSSL]
* [http://www.marschke.info/admin/ap_opssl_https.html Apache2, OpenSSL und HTTPS: Server- und Client-Authentifizierung mit Zertifikaten über verschlüsselte Internet-Verbindungen]
* [http://www.online-tutorials.net/security/openssl-tutorial/tutorials-t-69-207.html openSSL / openVPN.. comming soon]</text>
    <sha1>a31bed3f0f2a5d9f8d10138391e2da382843c7f2</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>User:Gordus</title>
  <ns>2</ns>
  <id>323</id>
  <revision>
    <id>994</id>
    <timestamp>2017-07-05T15:45:27Z</timestamp>
    <contributor>
      <username>Gordus</username>
      <id>365</id>
    </contributor>
    <comment>Created page with "'''test'''"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="10" xml:space="preserve">'''test'''</text>
    <sha1>fcdcb5261868837c11a2a7216b64fe80a646046a</sha1>
  </revision>
  <revision>
    <id>995</id>
    <parentid>994</parentid>
    <timestamp>2017-07-05T15:45:48Z</timestamp>
    <contributor>
      <username>Gordus</username>
      <id>365</id>
    </contributor>
    <comment>Blanked the page</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="0" xml:space="preserve"></text>
    <sha1>da39a3ee5e6b4b0d3255bfef95601890afd80709</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Color Management</title>
  <ns>0</ns>
  <id>324</id>
  <revision>
    <id>996</id>
    <timestamp>2017-07-14T17:15:27Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>Created page with "== Color management and calibration software available ==  * colord * colord-gtk * xcalib * iccprofiles * oyranos * gnome-color-manager * DisplayCAL  Packages i can`t build on..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="319" xml:space="preserve">== Color management and calibration software available ==

* colord
* colord-gtk
* xcalib
* iccprofiles
* oyranos
* gnome-color-manager
* DisplayCAL

Packages i can`t build on Slackware

* lprof
* monica


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>984abc0919b1e7b08f5be0b5b99ec07810c3ff3c</sha1>
  </revision>
  <revision>
    <id>999</id>
    <parentid>996</parentid>
    <timestamp>2017-07-16T08:45:45Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="658" xml:space="preserve">== Color management and calibration software available ==

* colord
* colord-gtk
* xcalib
* iccprofiles
* oyranos
* gnome-color-manager
* DisplayCAL
* monica

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof
 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>9b061e63c071422984e3b21d791c5072b72634f8</sha1>
  </revision>
  <revision>
    <id>1000</id>
    <parentid>999</parentid>
    <timestamp>2017-07-16T08:50:23Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="781" xml:space="preserve">== Color management and calibration software available ==

* colord-gtk
* xcalib
* iccprofiles
* oyranos
* gnome-color-manager
* DisplayCAL
* monica


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof
 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>34c36158c4e253a49b6dc19d1aa726474682decb</sha1>
  </revision>
  <revision>
    <id>1001</id>
    <parentid>1000</parentid>
    <timestamp>2017-07-16T09:02:23Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>/* Color management and calibration software available */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="770" xml:space="preserve">== Color management and calibration software ==

* colord-gtk
* xcalib
* iccprofiles
* oyranos
* gnome-color-manager
* DisplayCAL
* monica

== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof
 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>400467eb7a6da7462da3b601238ace430acdfe6f</sha1>
  </revision>
  <revision>
    <id>1002</id>
    <parentid>1001</parentid>
    <timestamp>2017-07-16T11:52:42Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1130" xml:space="preserve">== Color management and calibration software ==

* colord-gtk
* xcalib
* iccprofiles
* oyranos
* gnome-color-manager
* DisplayCAL
* monica

== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>7e11c43f54f411477ff5f4ccc79b39dd85e22ade</sha1>
  </revision>
  <revision>
    <id>1003</id>
    <parentid>1002</parentid>
    <timestamp>2017-07-16T12:14:54Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1216" xml:space="preserve">== Color management and calibration software ==

* colord-gtk
* xcalib
* iccprofiles
* oyranos
* gnome-color-manager
* DisplayCAL
* monica

== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>57d56466041ac4ea38caf7a996013959464ca5c8</sha1>
  </revision>
  <revision>
    <id>1004</id>
    <parentid>1003</parentid>
    <timestamp>2017-07-16T12:15:27Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1233" xml:space="preserve">== Color management and calibration software ==

* colord-gtk
* xcalib
* iccprofiles
* oyranos
* gnome-color-manager
* DisplayCAL
* monica
* cups-calibrate

== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>b7bb5341ff028a0db0601b9573b658ee3330e534</sha1>
  </revision>
  <revision>
    <id>1005</id>
    <parentid>1004</parentid>
    <timestamp>2017-07-16T12:16:52Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1334" xml:space="preserve">== Color management and calibration software ==

* colord-gtk
* 
* oyranos
* gnome-color-manager
* DisplayCAL
* monica
* cups-calibrate

== Iccprofiles ==

Package with icc profiles kit.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>b29ae6945a415564c78a3e061dcf200624ba425d</sha1>
  </revision>
  <revision>
    <id>1007</id>
    <parentid>1005</parentid>
    <timestamp>2017-07-16T12:18:59Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1367" xml:space="preserve">== Color management and calibration software ==

* colord-gtk
* 
* oyranos
* gnome-color-manager
* DisplayCAL
* monica
* cups-calibrate

== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>d288baa9116cbd630caca0352ff9e3ccb2d065b3</sha1>
  </revision>
  <revision>
    <id>1008</id>
    <parentid>1007</parentid>
    <timestamp>2017-07-16T12:25:09Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1442" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate

== gnome-color-manager ==


== xiccd ==

Desktop color management daemon


== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

colord-gtk - gtk library for colord

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>7379e04d5a8b60a0caed20b64da66755b22ae1c4</sha1>
  </revision>
  <revision>
    <id>1009</id>
    <parentid>1008</parentid>
    <timestamp>2017-07-17T07:12:03Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>/* xiccd */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1459" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate

== gnome-color-manager ==


== xiccd ==

Desktop color management daemon
Depends on: colord

== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

colord-gtk - gtk library for colord

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>4c86af07a6b0d1b4097f68a68d7204117a713dd1</sha1>
  </revision>
  <revision>
    <id>1010</id>
    <parentid>1009</parentid>
    <timestamp>2017-07-17T07:12:20Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>/* xiccd */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1460" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate

== gnome-color-manager ==


== xiccd ==

Desktop color management daemon

Depends on: colord

== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

colord-gtk - gtk library for colord

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>819548273cd8a514f2f3673f660845a9890a9512</sha1>
  </revision>
  <revision>
    <id>1011</id>
    <parentid>1010</parentid>
    <timestamp>2017-07-17T07:13:27Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1462" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

colord-gtk - gtk library for colord


== gnome-color-manager ==


== xiccd ==

Desktop color management daemon

Depends on: colord

== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>20f468e689e26a74c28c8cee50c137d3431af9c9</sha1>
  </revision>
  <revision>
    <id>1012</id>
    <parentid>1011</parentid>
    <timestamp>2017-07-17T07:53:48Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1464" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

colord-gtk - gtk library for colord


== xiccd ==
Desktop color management daemon

Depends on: colord

== gnome-color-manager ==


== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>da8c5a595559d7f311f015a83f8d762c1043850c</sha1>
  </revision>
</page>
<page arvcontinue="20141026233454|949">
  <title>Epson printing</title>
  <ns>0</ns>
  <id>325</id>
  <revision>
    <id>997</id>
    <timestamp>2017-07-14T17:22:48Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>Created page with "== Installing Epson-printer-utility ==   1. Go [http://download.ebz.epson.net/dsc/du/02/DriverDownloadInfo.do?LG2=EN&amp;CN2=&amp;DSCMI=58594&amp;DSCCHK=ebfccde01491428edd9eacd52d9d4822cd..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1399" xml:space="preserve">== Installing Epson-printer-utility ==


1. Go [http://download.ebz.epson.net/dsc/du/02/DriverDownloadInfo.do?LG2=EN&amp;CN2=&amp;DSCMI=58594&amp;DSCCHK=ebfccde01491428edd9eacd52d9d4822cd6efb50 here], accept the license. If you're on Slackware 32-bit, download epson-printer-utility-1.0.2-1lsb3.2.i486.rpm
, otherwise (ie. Slackware 64-bit), download epson-printer-utility-1.0.2-1lsb3.2.x86_64.rpm.

2. Convert the rpm package you downloaded into a tgz Slackware package :
Code:
 # if you are on Slackware 32-bit
 $ rpm2tgz epson-printer-utility-1.0.2-1lsb3.2.i486.rpm

 # if you are on Slackware 64-bit
 $ rpm2tgz epson-printer-utility-1.0.2-1lsb3.2.x86_64.rpm

3. Install the generated slackware package :
Code:
 # if you are on Slackware 32-bit
 $ installpkg epson-printer-utility-1.0.2-1lsb3.2.i486.tgz

 # if you are on Slackware 64-bit
 $ installpkg epson-printer-utility-1.0.2-1lsb3.2.x86_64.tgz

4. Create the symlink below which is required by LSB :
Code:
 # if you are on Slackware 32-bit   
 $ ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

 # if you are on Slackware 64-bit   
 # ln -sf /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3

For epson-printer-utility to work, you first need to start /usr/lib/epson-backend/ecbd as root :
Code:
 $ su -
 $ /usr/lib/epson-backend/rc.d/ecbd start

Now, epson-printer-utility can be started :
Code:

 $ /opt/epson-printer-utility/bin/epson-printer-utility</text>
    <sha1>640b96cef2dab03761634e59a268f358a53db636</sha1>
  </revision>
  <revision>
    <id>998</id>
    <parentid>997</parentid>
    <timestamp>2017-07-14T17:24:49Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>epson-printer-utility installing</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1494" xml:space="preserve">== Installing Epson-printer-utility ==


1. Go [http://download.ebz.epson.net/dsc/du/02/DriverDownloadInfo.do?LG2=EN&amp;CN2=&amp;DSCMI=58594&amp;DSCCHK=ebfccde01491428edd9eacd52d9d4822cd6efb50 here], accept the license. If you're on Slackware 32-bit, download epson-printer-utility-1.0.2-1lsb3.2.i486.rpm
, otherwise (ie. Slackware 64-bit), download epson-printer-utility-1.0.2-1lsb3.2.x86_64.rpm.

2. Convert the rpm package you downloaded into a tgz Slackware package :
Code:
 # if you are on Slackware 32-bit
 $ rpm2tgz epson-printer-utility-1.0.2-1lsb3.2.i486.rpm

 # if you are on Slackware 64-bit
 $ rpm2tgz epson-printer-utility-1.0.2-1lsb3.2.x86_64.rpm

3. Install the generated slackware package :
Code:
 # if you are on Slackware 32-bit
 $ installpkg epson-printer-utility-1.0.2-1lsb3.2.i486.tgz

 # if you are on Slackware 64-bit
 $ installpkg epson-printer-utility-1.0.2-1lsb3.2.x86_64.tgz

4. Create the symlink below which is required by LSB :
Code:
 # if you are on Slackware 32-bit   
 $ ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3

 # if you are on Slackware 64-bit   
 # ln -sf /lib64/ld-linux-x86-64.so.2 /lib64/ld-lsb-x86-64.so.3

For epson-printer-utility to work, you first need to start /usr/lib/epson-backend/ecbd as root :
Code:
 $ su -
 $ /usr/lib/epson-backend/rc.d/ecbd start

Now, epson-printer-utility can be started :
Code:

 $ /opt/epson-printer-utility/bin/epson-printer-utility


Originally from [http://www.linuxquestions.org/questions/slackware-14/lsbc-4175609558/ here]</text>
    <sha1>a7b08d2c06eb1efe9a6789ede9df7487d55ac13f</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Color Management</title>
  <ns>0</ns>
  <id>324</id>
  <revision>
    <id>1013</id>
    <parentid>1012</parentid>
    <timestamp>2017-07-17T08:01:24Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>/* xiccd */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1527" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

colord-gtk - gtk library for colord


== xiccd ==
Desktop color management daemon

Depends on: colord

[https://forums.freebsd.org/threads/51153/ Guide for FreeBSD]

== gnome-color-manager ==


== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

Page in progress.</text>
    <sha1>81c1f1bcc67f6ec71c26da1a29f74f745d83766b</sha1>
  </revision>
  <revision>
    <id>1014</id>
    <parentid>1013</parentid>
    <timestamp>2017-07-17T08:05:36Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1600" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

colord-gtk - gtk library for colord


== xiccd ==
Desktop color management daemon

Depends on: colord

[https://forums.freebsd.org/threads/51153/ Guide for FreeBSD]

== gnome-color-manager ==


== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


== See also ==
[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]
[http://www.hughski.com/ Open source display colorimeter]

Page in progress.</text>
    <sha1>4586ddfd27445d73835167947ef2ceebcf16ca08</sha1>
  </revision>
  <revision>
    <id>1015</id>
    <parentid>1014</parentid>
    <timestamp>2017-07-17T08:05:50Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>/* See also */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1602" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

colord-gtk - gtk library for colord


== xiccd ==
Desktop color management daemon

Depends on: colord

[https://forums.freebsd.org/threads/51153/ Guide for FreeBSD]

== gnome-color-manager ==


== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for loading icc profile for monitor.


== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


== See also ==

[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

[http://www.hughski.com/ Open source display colorimeter]

Page in progress.</text>
    <sha1>428e76e6d3e0dfa685a329467fa3efe20db1a54f</sha1>
  </revision>
  <revision>
    <id>1018</id>
    <parentid>1015</parentid>
    <timestamp>2017-07-17T13:19:32Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1817" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

Provides '''colormgr''' console utility for color management.

colord-gtk - gtk library for colord

== xiccd ==
Desktop color management daemon.
It needed to import profiles into colord and apply them to monitor.
If you use KDE or Gnome, you do not need xiccd.

Depends on: colord

[https://forums.freebsd.org/threads/51153/ Guide for FreeBSD]

== gnome-color-manager ==

Useful GUI for colormgr utility.

== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for direct loading icc profile for monitor.

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


== See also ==

[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

[http://www.hughski.com/ Open source display colorimeter]

Page in progress.</text>
    <sha1>6f52559f1fbcbdd0141c5f05ffab5f74e6210bbd</sha1>
  </revision>
  <revision>
    <id>1019</id>
    <parentid>1018</parentid>
    <timestamp>2017-07-17T13:27:42Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1826" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

Provides '''colormgr''' console utility for color management.

== xiccd ==
Desktop color management daemon.
It needed to import profiles into colord and apply them to monitor.
If you use KDE or Gnome, you do not need xiccd.

Depends on: colord

[https://forums.freebsd.org/threads/51153/ Guide for FreeBSD]

== gnome-color-manager ==

Requires colord-gtk - gtk library for colord

Useful GUI for colormgr utility.

== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for direct loading icc profile for monitor.

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


== See also ==

[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

[http://www.hughski.com/ Open source display colorimeter]

Page in progress.</text>
    <sha1>5808f353a68a6d2a3f68cee8bd8269b44ab63b05</sha1>
  </revision>
  <revision>
    <id>1020</id>
    <parentid>1019</parentid>
    <timestamp>2017-07-17T13:39:38Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1868" xml:space="preserve">== Color management and calibration software ==

* oyranos
* DisplayCAL
* monica
* cups-calibrate


== Colord ==
[https://www.freedesktop.org/software/colord/ Homepage]
[https://slackbuilds.org/repository/14.2/system/colord/ SBo]

Provides '''colormgr''' console utility for color management.

== xiccd ==
Desktop color management daemon.
It needed to import profiles into colord and apply them to monitor.
If you use KDE or Gnome, you do not need xiccd. Gnome uses gnome-settings-daemon instead.

Depends on: colord

[https://forums.freebsd.org/threads/51153/ Guide for FreeBSD]

== gnome-color-manager ==

Requires colord-gtk - gtk library for colord

Useful GUI for colormgr utility.

== Iccprofiles ==

Package with common icc profiles collection from Adobe and ECI.

== Xcalib ==

xcalib is a tool for direct loading icc profile for monitor.

== lprof ==
[http://lprof.sourceforge.net/ Homepage]

Lprof does not included in slackbuilds repository.

Requires: [https://slackware.pkgs.org/14.2/slackonly-i486/qt3-3.3.8b-i486-6_slonly.txz.html qt3], [https://slackbuilds.org/repository/14.2/libraries/vigra/ Vigra] 

=== Installation ===

Create directory for installation. In my case:

 mkdir ~/software/lprof

In order to compile we need some tricks on source tree directory:

 find . -iname "*.c" -o -iname "*.cpp" -o -iname "*.h" | xargs sed -i 's/BOOL/bool/g'
 find . -iname "*.c" | xargs sed -i '/typedef long int bool/d'
 find . -iname "*.c" | xargs sed -i '1i typedef enum { FALSE, TRUE } bool;'

Then

 scons PREFIX=~/software/lprof/ qt_directory=/opt/kde3/lib/qt3-3.3.8b/ install

=== Usage ===

We can use lprof to create icc profile for monitor or camera/scanner.


== See also ==

[https://wiki.archlinux.org/index.php/ICC_profiles Page on Archwiki dedicated to this problem]

[http://www.hughski.com/ Open source display colorimeter]

Page in progress.</text>
    <sha1>bf7d0d6e0870b27e8c6fbf7125f8cc194d62241f</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Xterm</title>
  <ns>0</ns>
  <id>327</id>
  <revision>
    <id>1016</id>
    <timestamp>2017-07-17T09:01:13Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>Created page with "This page is about tweaking xterm.  For information about xterm in general see xterm(1)  Config in file ~/.Xdefaults  Copy selection to clipboard:   XTerm*selectToClipboard:true"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="177" xml:space="preserve">This page is about tweaking xterm.

For information about xterm in general see xterm(1)

Config in file ~/.Xdefaults

Copy selection to clipboard:

 XTerm*selectToClipboard:true</text>
    <sha1>2d321c010bf16a8229c4436adfa5c7b0326ea479</sha1>
  </revision>
  <revision>
    <id>1017</id>
    <parentid>1016</parentid>
    <timestamp>2017-07-17T09:02:28Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="224" xml:space="preserve">This page is about tweaking xterm.

For information about xterm in general see xterm(1)

Config in file ~/.Xdefaults

Copy selection to clipboard:

 XTerm*selectToClipboard:true


reload the configuration

 xrdb ~/.Xdefaults</text>
    <sha1>610996ef8375f5c221b34395dfbb7a75d9a944da</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Writing A SlackBuild Script</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>1021</id>
    <parentid>661</parentid>
    <timestamp>2017-07-19T08:40:57Z</timestamp>
    <contributor>
      <username>Aeifn</username>
      <id>367</id>
    </contributor>
    <comment>/* Introduction */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19352" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget http://www.latex2html.org/~latex2ht/current/latex2html-2002-2-1.tar.gz # 03.27.2012

Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>cdc180c408aabe3d4671ff124e6a712224688086</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Life of a Software Package</title>
  <ns>0</ns>
  <id>104</id>
  <revision>
    <id>3161</id>
    <parentid>1144</parentid>
    <timestamp>2018-03-11T17:29:18Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>Reverted edits by [[Special:Contributions/Jhonthomas|Jhonthomas]] ([[User talk:Jhonthomas|talk]]) to last revision by [[User:Grissiom|Grissiom]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="17274" xml:space="preserve">From the programmer's keyboard to your (Slackware) Linux system.

= Introduction =

This article explains how a program someone writes in one side of the world ends up being managed in your system. It's meant to be easy to understand for a novice user coming from Windows, and only requires some basic knowledge of Unix systems. Specifically, the reader should know:

* How basic Unix permissions work.
* How to interpret the basic output of the ''ls'' command.
* How a command line interface works.

It only contains general ideas that could help a novice user understand the existing differences when installing software under Windows and under Unix, but no specific information about how to do it. The distribution manual will give you the specific details you need, and may be a good read after you have read this article.

= From source code to machine language =

'''Note''': You do not need to run any of the commands in this section. It's enough to understand the text and part of the output.

When a programmer creates a program, it's very common to write the program in a so-called high level language. In other words, he doesn't create the program executable directly specifying the intructions for the computer to run. He writes the program in a language that allows him to represent the program structure and logic, and then that logic is translated to a language the bare machine can understand. Let's suppose someone wants to write a ''Hello, World'' program in the C programming language. This is a program that prints a message to the screen and finishes, in order to check your system can translate the language you have used to machine language and to test the basic stuff works, as well as to give the novice programmer an idea on how the high level language works. This would be a very simple ''Hello, World'' program written in C:

 #include &lt;stdio.h&gt;
 
 int main()
 {
 	printf("Hello, World!\n");
 	return 0;
 }

You do not need to understand that program. The above text is what is commonly known as the '''source code''' of the program. The source code of a program in C is usually spread over one or more source files, so this program could very well be stored in a plain text file called ''hello.c''. You could view this file using a plain text editor like the Windows notepad.

This file cannot be executed directly because it's not a real program. First off, it doesn't have execution permissions, and if we tried to give it execution permissions and run it, we would get an error message:

 $ ls -l hello.c
 -rw------- 1 rg3 users 74 2007-10-15 19:27 hello.c
 $ chmod +x hello.c
 $ ./hello.c
 ./hello.c: line 3: syntax error near unexpected token `('
 ./hello.c: line 3: `int main()'

We need to use a program called ''compiler'' to get a binary and executable file. A file in a specific format that the operating system (Linux in our case) can understand. When you run it, the operating system reads the file, copies the different program components to the computer's memory and starts the program execution. If our machine has everything ready to compile C programs and we want to use the GNU C Compiler (''gcc''), we could do something as simple as:

 $ gcc -o hello hello.c

And we would get a file named ''hello'' which is our program ready to be run. As you see, our program is simply called ''hello'' and not ''hello.exe'', which would be a common name if we were working under Windows. In Unix systems, the convention is that programs do not have any file extension in their name (like EXE). We could then run the program and see that it does what we wanted.

 $ ./hello
 Hello, World!
 $

= Complex programs use libraries =

Most programs do a more sophisticated task than printing a message on the screen and finishing. The source code of the program above has 7 lines. It is not uncommon for a simple program to have thousands of lines, and there are a good amount of complex programs out there that have millions of lines of source code. It is also a very common practice to use items called '''libraries''' (usually '''shared''' libraries) to build your program. Libraries are files that contain the machine code to perform several different tasks. For example, let's suppose you were going to create a program that needs to download some data from the Internet, via HTTP (the web) or via FTP or another network service. And also let's suppose you don't have much knowledge on how to create a program that talks to others using the network, or that the focus of your program is on solving some other problem and you don't want to lose time or create a lot of code just because you want it to be able to download a file. Fortunately for you, there is a library called ''libcurl'' that makes retrieving files over the network very easy. The library contains all the code you need, so the source code you are going to create will not contain anything specific to be able to use the network. You simply indicate that you want to use ''libcurl'' and call the library functions everytime you want to download a file. Do you need to learn to sail or fly a plane or a different language if you want to send a letter to a friend in a different continent? No, you put the letter in the mailbox and the postal service does it for you. Libraries work like this.

In the moment you decide to do this, your program starts '''depending''' on ''libcurl''. Some pieces of the library need to be present in your system if you want to compile that program to create an executable, and some other pieces need to be present in the moment you want to ''run'' the program. Else, the program will not compile or will not be able to run. Libraries are convenient because, if managed well, you can install them in your system once and they will be used by every program that needs them. This is why libraries are regarded as a ''good thing'' or a ''good idea'' in the programming world, in most cases.

In Windows, shared libraries are called DLLs, as the library files usually have the DLL extension. In Unix, it's common for them to have the ''.so'' suffix, or some other containing it. For example, I have ''libcurl'' in my system, and the shared library is located in the file ''/usr/lib/libcurl.so.4.0.0''.

= Libraries and programs all over the place need a package manager =

So your system is going to be populated by a lot of programs, many of them using many different libraries for different tasks, some of them having some libraries in common, others having nothing in common. As you can guess, this situation can evolve into a pretty chaotic system. Let's describe how Windows did this in the past, and how Unix systems have been trying to handle the situation for a good amount of years now.

In Windows, most people distribute programs already compiled. You get a group of files or a single file that holds your program already prepared to be run. You extract those contents and place them somewhere in your hard drive, usually all of them under a specific directory (folder). You could then create some shortcuts in the ''start'' menu and the program is ready to be run. A installer program usually does all of this for you, asking some questions. What happens when the program uses a library? If the library is not very common and cannot be assumed to exist in a standard Windows installation, the common practice is to include a copy of the library with the program. If it's a relatively uncommon library, the installer usually puts it in the same place as the program, and when it is run and requests the library, the system first looks in the folder holding the program and finds the library there, and starts to use it. If it's not an uncommon library but you need a specific version of it, the installer may try to install it in a common place so all the programs can use it. It was very typical, when you had a system in which you had installed a lot of software as time passed, that the installer would ask you "I am trying to install the following library, but it appears to be present in your system in a newer version. Do you want me to replace the copy of it with my copy or do I leave it as it is?". And, in the same line, when you removed the program it would say "I was going to remove this library from the common place, but other programs may want to use it. Can I remove it or should I keep it there?". This chaos was called "DLL Hell".

Unix tries to avoid this problem in several ways, and its solutions bring the need of a package manager as we will explain. First off, in Unix the files on your hard drive are not grouped by program, but by their function. All binaries are stored in two or three folders, and the same for libraries or help documents. If all the documentation and help for the different programs is installed in a common location, it's easier to create a help system from which you can browse the documentation of every program installed on the computer, for example. This is generally considered a good idea and it's the tradition, but of course the idea has its detractors. Anyway, a second difference is that in Unix programs are distributed alone. If a program needs a library to be run, it needs to specify that somewhere, but only under special circumstances it's recommended to include the library as part of the program. In most cases, the library is distributed apart. Those two differences avoid the DLL hell. By installing libraries, programs, documentation and other data to common system locations, you avoid duplicating data. If there's a security problem using a library and every program using it could become compromised and make the system vulnerable, you update the library once and all the programs that use it are automatically protected, as each program doesn't include its own copy in its directory. By separating the programs from the libraries they use and distributing them apart, you make sure programs do not overwrite the libraries used by others or remove common libraries when they are removed.

However, the solution itself brings some new problems. For example, if a program installs files all over common system directories and I later want to remove it, how do I know which files need to be removed? And if a program requires a library to run, can I or should I specify that fact somewhere? Package managers are the answer. Under Unix, software is many times distributed as '''packages'''. Packages are groups of files that contain programs, libraries, documentation or simply data. Under Windows, to install a program many times you download an installer file, run it and the program is installed. This installer file that holds inside all the files the program needs and extracts them to the proper location could be considered a form of package, so you get an idea. Packages in Unix are usually managed by a package manager. A package manager is a program that allows you to install packages, check the list of installed packages, remove packages and many more complex tasks depending on how powerful and featureful the package manager itself is.

When you install a program using a package, the package holds the program binary, the program data and the program documentation, typically, along with information on where those files should be installed in the system, all over the place. Fortunately, prior, during or after the installation, after copying the files to your system, the package manager records somewhere the name and version of the package and the files it installed. This is the trick that allows you to later remove the package using the package manager without having to remember which files had been installed where. In addition, the package may hold information about other packages it needs installed for it to run, and this information may be used by the package manager to automatically download and install them too. Hopefully, you now start to understand the practical vision behind packages and package managers.

= Too many package managers =

The problem with package managers is that many Unix systems and even many different Linux distributions use many different package managers. Each one uses different package formats that cannot understand each other. Slackware uses ''pkgtools'', Debian and Ubuntu use ''apt-get'', Red Hat uses ''yum'', Mandriva uses ''urpmi'', Arch uses ''pacman'', etc.

You are a programmer and created the ''Hello, World'' program we saw at the beginning. How do you distribute your program? You have several solutions. If you don't want people to get the source code of your program, you need to distribute the program already compiled and probably packaged. To do that, you could provide your own program to install and uninstall the package cleanly from any system, and distribute it somehow and break some rules to achieve maximum compatibility, so the program will run on many different systems and distributions. Many commercial games are shipped this way. Unreal Tournament 2004 for Linux is distributed this way, for example. You could also provide it as a package for each of a subset of supported systems. Many companies do this. They give you Debian, Red Hat, Suse and Mandriva packages for you to choose, for example, each in the proper format to be used with the package manager from that distribution. If you want to use the software under other system you are out of luck. You can try some tricks but it's not guaranteed to work.

If, on the other hand, your program is open source and you don't mind people reading the source code of your program, the common case is to avoid creating a package for anything. You simply distribute a tarball (similar to a ZIP or RAR file) containing the source code and instructions to compile it. If someone wants a Debian package to install it, someone will have to compile your program under Debian, and make a package with the result. This is a very very very common case. In fact, distributions like Ubuntu or Debian heavily rely on '''package repositories''', network locations from where you can download thousands of packages for your system, created by a myriad of official and unofficial packagers (people that create packages for the system). For example, if you want to install a program under Ubuntu, it's very infrequent for the program not to exist already packaged in a repository, and you can download and install it, together with its dependencies, in a couple of mouse clicks.

= Summing up =

* Many times the programmer creates programs using source code that must be compiled.
* They use libraries to make writing programs easy.
* Distributing the resulting program is easier using a package manager.
* Many programmers only give you the source code due to the diversity of package managers and systems.
* Someone else is responsible for creating a package for a specific system.

= Slackware specifics =

Slackware is, as you may know, a very simple system. Being simple doesn't mean it's simple to use. On the contrary, a system with a simple design and simple tools usually requires the user to do more things to achieve a goal. The advantage of a simple design is that it's easier to understand if you want to know how your system works, and sometimes it's also more stable and has less bugs. As part of its simple design, the package manager in Slackware is also very simple, and its packages are also very simple. Slackware packages are tarballs (again, something like ZIP files) that, if extracted in the right place, will populate the system with the package files, and it also holds some special files with information about the package itself. As they are simple tarballs, Slackware doesn't try to hide this fact, and Slackware packages have the ''tgz/txz'' extension (short for ''tar.gz/tar.xz''), contrary to other systems in which packages have a special extension to make it clear that they are packages, like ''rpm'' or ''deb''.

This is not a problem, but sometimes this confuses novice users. They go to the program webpage and download the program source code in a tarball (usually a file with ''tar.gz'' extension) and think "Hey, if Slackware packages are tarballs and this is a tarball, I'm going to install this file with the package manager". Wrong! Even when the package manager complains that the package name does not end in ''tgz'' but on ''tar.gz'', they many times rename the file and try again. Those are two mistakes in a row. The package manager will try to extact the tarball contents to that special location we mentioned earlier and nothing will happen, as the files inside the tarball are not structured as they need to be, but this is the small problem. The big one is that what you are trying to install is the source code of the program, and not the program itself! Remember, you need to compile it first in the majority of cases.

Under Slackware, you should first check if there is an official package for the program. If there is not, you could try to to download a ready to use package from a place or someone you trust. Else, you could compile the program yourself and create a package for it, and then install the package. The compilation and package creation can be automated sometimes for ease of use, for example using [[SlackBuild Scripts|SlackBuild scripts]].

[[Category:Information]]</text>
    <sha1>712647b02c547102f2dcd6c07bd337eb916207ca</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>3166</id>
    <parentid>989</parentid>
    <timestamp>2018-03-11T20:21:30Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Upgraded MediaWiki</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4464" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>32d6e0186fe969f9ac624fc07ccf76e93d2b1c3b</sha1>
  </revision>
  <revision>
    <id>3173</id>
    <parentid>3166</parentid>
    <timestamp>2018-06-16T17:59:02Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>/* News */  Version update</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4572" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>ae8cf9d7d606f1011a031d67270ad8fe2da7c7b0</sha1>
  </revision>
  <revision>
    <id>3176</id>
    <parentid>3173</parentid>
    <timestamp>2018-10-27T18:42:37Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4683" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)

MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>2d297986436011cbb841d9d36ecec3973317e894</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>ATI Graphics</title>
  <ns>0</ns>
  <id>36</id>
  <revision>
    <id>3167</id>
    <parentid>57</parentid>
    <timestamp>2018-05-10T19:55:47Z</timestamp>
    <contributor>
      <username>Phorneker</username>
      <id>604</id>
    </contributor>
    <comment>/* Notes */   Support information about video support for the ATI Radeon Mobility 2600 was added.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6600" xml:space="preserve">[[Category:Hardware]]
===Introduction===

ATI drivers come in two flavours:

1) X.Org open source 'radeon' driver - full support (accelerated 2D and 3D) for the Radeon 9200 and earlier. (Also supported for the 9200 - X850 for Slackware -current, or any Slackware newer than 11.0)

2) ATI's proprietary closed source 'fglrx' driver - support for the 9500 and above (all support for earlier cards has now been dropped). This is the only driver with any support, either 2D or 3D, for the X1xxx series of cards (R500 and newer).

====Kernel====

AGPGART: If you have an AGP card, you should ensure AGPGART and support for your specific GART are built in the kernel (built in or module is fine)

PCI Express: If you have a PCI Express card, you should ensure PCI Express support is built in the kernel.

==Seting up the 'radeon' driver==

===Preparing Your System===

====Kernel====

Direct Rendering Manager (DRM): Module or built in, plus the module under this for "ATI Radeon"

===Initial Setup===
Edit /etc/X11/xorg.conf

In Section "Module" add:

 Load "glx"
 Load "dri"

At the end of the file, add

 Section "DRI"
   Mode 0666
 EndSection

(Or use 'Xorg -configure' to generate a new xorg.conf to autodetect the ATi card)

===Tweaking===

To increase performance for Radeon users (in particular, R300 and R400), you may also want to add the following under the "Device" section for the radeon:

====AGP users====
 
 Option "AGPMode" "8" # Modify accordingly if you don't have an AGP 8x card 
 Option "AGPFastWrite" "true" # This one has big warnings all over it, so test it first! 

====Mobility card users====
 
 Option "DynamicClocks" "true" # The equivalent of ATi's PowerPlay 
 Option "BIOSHotkeys" "true" # You _might_ need this for some special function keys on your laptop 

====All users====
 
 Option "EnablePageFlip" "true" 
 Option "ColorTiling" "true" 

===Final Check===

Run 'glxinfo | grep render'. It will return something like the following (the last line will vary depending on R300/ R400, PCI/ PCIE or AGP, etc). The important thing is that this reports "direct rendering: yes".

 direct rendering: Yes
 OpenGL renderer string: Mesa DRI R300 20060815 AGP 8x x86/MMX+/3DNow!+/SSE TCL

===Notes===

'''R300 - R400:'''

Please note that these cards do not have accelerated hardware support in X.Org &lt; 6.9 (i.e. Slackware 11.0 or older)

'''R500 (X1xxx and above)'''

Sorry, there is no open source accelerated support in X for these cards. Either use fglrx or vesa.

'''R600'''

For the ATI Radeon Mobility 2600 (the built in video on the HP Compaq 8510p), the radeon driver must be used for accelerated support.  The amdgpu driver will not work with this video board.

==Setting up the 'fglrx' driver==

===Preparing Your System===

====Libraries====

The fglrx driver requires that you have the package cxxlibs installed on your system to build it.

'''(Slamd64)''': You will also need the 32 bit compatibility libraries from c/

====Kernel====

Direct Rendering Manager (DRM): Must *not* be built into the kernel - it should be a module (and not loaded) or not built.

Frame Buffer: Must *not* be built into the kernel - it should be a module or not built (it is not compatible with the current fglrx drivers).

===Installing the Driver===

You will need to download the 'ATI Driver Installer' package (the RPM packages do not have support for X.Org 6.9).

Once you have downloaded the installer, run it (I reccommend using sudo, as you need root permissions but also need access to the X server. You could use xhost+ and then su, but this is not safe).

 sudo sh ati-driver-installer-$VERSION-$ARCH.run

You need to select the 'Install driver' (the ATI installer cannot generate a Slackware package), and then it is reccommended you choose "automatic" on the next screen. The driver will now install itself.

Make sure that you mount tmpfs for 3D acceleration, or you can get unexpected results.

ie: 
 'FGLTexMgr: open of shared memory object failed (Function not implemented)
 __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
 fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!'
 
Add the following to /etc/fstab:
 tmpfs     /dev/shm           tmpfs        defaults            0 0
then 'mount /dev/shm' on a console

===Patching the Driver===

If you are running the latest kernel, more often than not you will need to patch the fglrx driver. At the very least, you will need to manually rebuild it if you change your kernel - follow instruction 1 if necessary, then 2 and 3.

There is no central repository of these, so it is not possible to point you to a specific place to check for them (although the [http://ati.cchtml.com Unofficial ATI Bugzilla] or [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D Linux Drivers forum] are good places to check).

Once you have downloaded the patches:

1. Apply them in /lib/modules/fglrx (or /lib/modules/fglrx/build_mod)

 cd /lib/modules/fglrx/build_mod
 cat somepatch.diff | patch -p1

2. Rebuild the fglrx module

 sh /lib/modules/fglrx/build_mod/make.sh

N.B. Modules built are kernel specific - you can only build a module for the kernel you are currently running.

3. Install the module

 sh /lib/modules/fglrx/make_install.sh

===Configuring the X server===

If you have not installed the fglrx driver before, run:

 aticonfig --initial --input=/etc/X11/xorg.conf
 aticonfig --ovt=Xv

This will add an fglrx 'Section "Device"' to /etc/X11/xorg.conf and enable video overlay (enables video playback)

Edit /etc/X11/xorg.conf (you need to do this with root permissions)

Find:

1) A 'Section "Device"' that contains fglrx
2) 'Section "Screen"'

Then:

1) Under the Section "Device" that contains fglrx&lt;br /&gt;
1A). Make a note of the value of "Indentifier"&lt;br /&gt;

2) Under Section "Screen", replace the value of "Device" with the value you just noted from fglrx

At the end of /etc/X11/xorg.conf, add this section (This allows all users to access the direct rendering mode - without it, you can't use acceleration as a user):

 Section "DRI"
        Mode         0666
 EndSection

Restart the X server

===Final Check===

To check that fglrx has been installed and setup correctly, run 'fglrxinfo' in a terminal under X. It should return something like:

 display: :0.0  screen: 0
 OpenGL vendor string: ATI Technologies Inc.
 OpenGL renderer string: MOBILITY RADEON X700 Generic
 OpenGL version string: 2.0.5642 (8.22.5)

(The 'renderer' string will vary depending on the chip your card actually has).

===Uninstalling the driver===

With root permissions, run:

 sh /usr/share/fglrx/fglrx-uninstall.sh</text>
    <sha1>2a49c0a5ac692e8702d6f28a5e3fa898e4704368</sha1>
  </revision>
  <revision>
    <id>3168</id>
    <parentid>3167</parentid>
    <timestamp>2018-05-10T19:56:09Z</timestamp>
    <contributor>
      <username>Phorneker</username>
      <id>604</id>
    </contributor>
    <comment>/* Notes */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6606" xml:space="preserve">[[Category:Hardware]]
===Introduction===

ATI drivers come in two flavours:

1) X.Org open source 'radeon' driver - full support (accelerated 2D and 3D) for the Radeon 9200 and earlier. (Also supported for the 9200 - X850 for Slackware -current, or any Slackware newer than 11.0)

2) ATI's proprietary closed source 'fglrx' driver - support for the 9500 and above (all support for earlier cards has now been dropped). This is the only driver with any support, either 2D or 3D, for the X1xxx series of cards (R500 and newer).

====Kernel====

AGPGART: If you have an AGP card, you should ensure AGPGART and support for your specific GART are built in the kernel (built in or module is fine)

PCI Express: If you have a PCI Express card, you should ensure PCI Express support is built in the kernel.

==Seting up the 'radeon' driver==

===Preparing Your System===

====Kernel====

Direct Rendering Manager (DRM): Module or built in, plus the module under this for "ATI Radeon"

===Initial Setup===
Edit /etc/X11/xorg.conf

In Section "Module" add:

 Load "glx"
 Load "dri"

At the end of the file, add

 Section "DRI"
   Mode 0666
 EndSection

(Or use 'Xorg -configure' to generate a new xorg.conf to autodetect the ATi card)

===Tweaking===

To increase performance for Radeon users (in particular, R300 and R400), you may also want to add the following under the "Device" section for the radeon:

====AGP users====
 
 Option "AGPMode" "8" # Modify accordingly if you don't have an AGP 8x card 
 Option "AGPFastWrite" "true" # This one has big warnings all over it, so test it first! 

====Mobility card users====
 
 Option "DynamicClocks" "true" # The equivalent of ATi's PowerPlay 
 Option "BIOSHotkeys" "true" # You _might_ need this for some special function keys on your laptop 

====All users====
 
 Option "EnablePageFlip" "true" 
 Option "ColorTiling" "true" 

===Final Check===

Run 'glxinfo | grep render'. It will return something like the following (the last line will vary depending on R300/ R400, PCI/ PCIE or AGP, etc). The important thing is that this reports "direct rendering: yes".

 direct rendering: Yes
 OpenGL renderer string: Mesa DRI R300 20060815 AGP 8x x86/MMX+/3DNow!+/SSE TCL

===Notes===

'''R300 - R400:'''

Please note that these cards do not have accelerated hardware support in X.Org &lt; 6.9 (i.e. Slackware 11.0 or older)

'''R500 (X1xxx and above)'''

Sorry, there is no open source accelerated support in X for these cards. Either use fglrx or vesa.

'''R600'''

For the ATI Radeon Mobility 2600 (the built in video on the HP Compaq 8510p), the '''radeon''' driver must be used for accelerated support.  The amdgpu driver will not work with this video board.

==Setting up the 'fglrx' driver==

===Preparing Your System===

====Libraries====

The fglrx driver requires that you have the package cxxlibs installed on your system to build it.

'''(Slamd64)''': You will also need the 32 bit compatibility libraries from c/

====Kernel====

Direct Rendering Manager (DRM): Must *not* be built into the kernel - it should be a module (and not loaded) or not built.

Frame Buffer: Must *not* be built into the kernel - it should be a module or not built (it is not compatible with the current fglrx drivers).

===Installing the Driver===

You will need to download the 'ATI Driver Installer' package (the RPM packages do not have support for X.Org 6.9).

Once you have downloaded the installer, run it (I reccommend using sudo, as you need root permissions but also need access to the X server. You could use xhost+ and then su, but this is not safe).

 sudo sh ati-driver-installer-$VERSION-$ARCH.run

You need to select the 'Install driver' (the ATI installer cannot generate a Slackware package), and then it is reccommended you choose "automatic" on the next screen. The driver will now install itself.

Make sure that you mount tmpfs for 3D acceleration, or you can get unexpected results.

ie: 
 'FGLTexMgr: open of shared memory object failed (Function not implemented)
 __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
 fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!'
 
Add the following to /etc/fstab:
 tmpfs     /dev/shm           tmpfs        defaults            0 0
then 'mount /dev/shm' on a console

===Patching the Driver===

If you are running the latest kernel, more often than not you will need to patch the fglrx driver. At the very least, you will need to manually rebuild it if you change your kernel - follow instruction 1 if necessary, then 2 and 3.

There is no central repository of these, so it is not possible to point you to a specific place to check for them (although the [http://ati.cchtml.com Unofficial ATI Bugzilla] or [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D Linux Drivers forum] are good places to check).

Once you have downloaded the patches:

1. Apply them in /lib/modules/fglrx (or /lib/modules/fglrx/build_mod)

 cd /lib/modules/fglrx/build_mod
 cat somepatch.diff | patch -p1

2. Rebuild the fglrx module

 sh /lib/modules/fglrx/build_mod/make.sh

N.B. Modules built are kernel specific - you can only build a module for the kernel you are currently running.

3. Install the module

 sh /lib/modules/fglrx/make_install.sh

===Configuring the X server===

If you have not installed the fglrx driver before, run:

 aticonfig --initial --input=/etc/X11/xorg.conf
 aticonfig --ovt=Xv

This will add an fglrx 'Section "Device"' to /etc/X11/xorg.conf and enable video overlay (enables video playback)

Edit /etc/X11/xorg.conf (you need to do this with root permissions)

Find:

1) A 'Section "Device"' that contains fglrx
2) 'Section "Screen"'

Then:

1) Under the Section "Device" that contains fglrx&lt;br /&gt;
1A). Make a note of the value of "Indentifier"&lt;br /&gt;

2) Under Section "Screen", replace the value of "Device" with the value you just noted from fglrx

At the end of /etc/X11/xorg.conf, add this section (This allows all users to access the direct rendering mode - without it, you can't use acceleration as a user):

 Section "DRI"
        Mode         0666
 EndSection

Restart the X server

===Final Check===

To check that fglrx has been installed and setup correctly, run 'fglrxinfo' in a terminal under X. It should return something like:

 display: :0.0  screen: 0
 OpenGL vendor string: ATI Technologies Inc.
 OpenGL renderer string: MOBILITY RADEON X700 Generic
 OpenGL version string: 2.0.5642 (8.22.5)

(The 'renderer' string will vary depending on the chip your card actually has).

===Uninstalling the driver===

With root permissions, run:

 sh /usr/share/fglrx/fglrx-uninstall.sh</text>
    <sha1>7973b83acafdda2af6ebc3134827688b0713fd36</sha1>
  </revision>
  <revision>
    <id>3169</id>
    <parentid>3168</parentid>
    <timestamp>2018-05-10T19:58:05Z</timestamp>
    <contributor>
      <username>Phorneker</username>
      <id>604</id>
    </contributor>
    <comment>/* Notes */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6753" xml:space="preserve">[[Category:Hardware]]
===Introduction===

ATI drivers come in two flavours:

1) X.Org open source 'radeon' driver - full support (accelerated 2D and 3D) for the Radeon 9200 and earlier. (Also supported for the 9200 - X850 for Slackware -current, or any Slackware newer than 11.0)

2) ATI's proprietary closed source 'fglrx' driver - support for the 9500 and above (all support for earlier cards has now been dropped). This is the only driver with any support, either 2D or 3D, for the X1xxx series of cards (R500 and newer).

====Kernel====

AGPGART: If you have an AGP card, you should ensure AGPGART and support for your specific GART are built in the kernel (built in or module is fine)

PCI Express: If you have a PCI Express card, you should ensure PCI Express support is built in the kernel.

==Seting up the 'radeon' driver==

===Preparing Your System===

====Kernel====

Direct Rendering Manager (DRM): Module or built in, plus the module under this for "ATI Radeon"

===Initial Setup===
Edit /etc/X11/xorg.conf

In Section "Module" add:

 Load "glx"
 Load "dri"

At the end of the file, add

 Section "DRI"
   Mode 0666
 EndSection

(Or use 'Xorg -configure' to generate a new xorg.conf to autodetect the ATi card)

===Tweaking===

To increase performance for Radeon users (in particular, R300 and R400), you may also want to add the following under the "Device" section for the radeon:

====AGP users====
 
 Option "AGPMode" "8" # Modify accordingly if you don't have an AGP 8x card 
 Option "AGPFastWrite" "true" # This one has big warnings all over it, so test it first! 

====Mobility card users====
 
 Option "DynamicClocks" "true" # The equivalent of ATi's PowerPlay 
 Option "BIOSHotkeys" "true" # You _might_ need this for some special function keys on your laptop 

====All users====
 
 Option "EnablePageFlip" "true" 
 Option "ColorTiling" "true" 

===Final Check===

Run 'glxinfo | grep render'. It will return something like the following (the last line will vary depending on R300/ R400, PCI/ PCIE or AGP, etc). The important thing is that this reports "direct rendering: yes".

 direct rendering: Yes
 OpenGL renderer string: Mesa DRI R300 20060815 AGP 8x x86/MMX+/3DNow!+/SSE TCL

===Notes===

'''R300 - R400:'''

Please note that these cards do not have accelerated hardware support in X.Org &lt; 6.9 (i.e. Slackware 11.0 or older)

'''R500 (X1xxx and above)'''

Sorry, there is no open source accelerated support in X for these cards. Either use fglrx or vesa.

'''R600'''

For the ATI Radeon Mobility 2600 (the built in video on the HP Compaq 8510p), the '''radeon''' driver must be used for accelerated support.  The amdgpu driver will not work with this video board.  Though the fglrx driver can be used with this video board, it is not necessary to install the proprietary driver to get this video board working.

==Setting up the 'fglrx' driver==

===Preparing Your System===

====Libraries====

The fglrx driver requires that you have the package cxxlibs installed on your system to build it.

'''(Slamd64)''': You will also need the 32 bit compatibility libraries from c/

====Kernel====

Direct Rendering Manager (DRM): Must *not* be built into the kernel - it should be a module (and not loaded) or not built.

Frame Buffer: Must *not* be built into the kernel - it should be a module or not built (it is not compatible with the current fglrx drivers).

===Installing the Driver===

You will need to download the 'ATI Driver Installer' package (the RPM packages do not have support for X.Org 6.9).

Once you have downloaded the installer, run it (I reccommend using sudo, as you need root permissions but also need access to the X server. You could use xhost+ and then su, but this is not safe).

 sudo sh ati-driver-installer-$VERSION-$ARCH.run

You need to select the 'Install driver' (the ATI installer cannot generate a Slackware package), and then it is reccommended you choose "automatic" on the next screen. The driver will now install itself.

Make sure that you mount tmpfs for 3D acceleration, or you can get unexpected results.

ie: 
 'FGLTexMgr: open of shared memory object failed (Function not implemented)
 __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
 fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!'
 
Add the following to /etc/fstab:
 tmpfs     /dev/shm           tmpfs        defaults            0 0
then 'mount /dev/shm' on a console

===Patching the Driver===

If you are running the latest kernel, more often than not you will need to patch the fglrx driver. At the very least, you will need to manually rebuild it if you change your kernel - follow instruction 1 if necessary, then 2 and 3.

There is no central repository of these, so it is not possible to point you to a specific place to check for them (although the [http://ati.cchtml.com Unofficial ATI Bugzilla] or [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D Linux Drivers forum] are good places to check).

Once you have downloaded the patches:

1. Apply them in /lib/modules/fglrx (or /lib/modules/fglrx/build_mod)

 cd /lib/modules/fglrx/build_mod
 cat somepatch.diff | patch -p1

2. Rebuild the fglrx module

 sh /lib/modules/fglrx/build_mod/make.sh

N.B. Modules built are kernel specific - you can only build a module for the kernel you are currently running.

3. Install the module

 sh /lib/modules/fglrx/make_install.sh

===Configuring the X server===

If you have not installed the fglrx driver before, run:

 aticonfig --initial --input=/etc/X11/xorg.conf
 aticonfig --ovt=Xv

This will add an fglrx 'Section "Device"' to /etc/X11/xorg.conf and enable video overlay (enables video playback)

Edit /etc/X11/xorg.conf (you need to do this with root permissions)

Find:

1) A 'Section "Device"' that contains fglrx
2) 'Section "Screen"'

Then:

1) Under the Section "Device" that contains fglrx&lt;br /&gt;
1A). Make a note of the value of "Indentifier"&lt;br /&gt;

2) Under Section "Screen", replace the value of "Device" with the value you just noted from fglrx

At the end of /etc/X11/xorg.conf, add this section (This allows all users to access the direct rendering mode - without it, you can't use acceleration as a user):

 Section "DRI"
        Mode         0666
 EndSection

Restart the X server

===Final Check===

To check that fglrx has been installed and setup correctly, run 'fglrxinfo' in a terminal under X. It should return something like:

 display: :0.0  screen: 0
 OpenGL vendor string: ATI Technologies Inc.
 OpenGL renderer string: MOBILITY RADEON X700 Generic
 OpenGL version string: 2.0.5642 (8.22.5)

(The 'renderer' string will vary depending on the chip your card actually has).

===Uninstalling the driver===

With root permissions, run:

 sh /usr/share/fglrx/fglrx-uninstall.sh</text>
    <sha1>f470bb8a17cea9f3aedec8b1cbf1b9ef19815f2f</sha1>
  </revision>
  <revision>
    <id>3170</id>
    <parentid>3169</parentid>
    <timestamp>2018-05-10T19:58:44Z</timestamp>
    <contributor>
      <username>Phorneker</username>
      <id>604</id>
    </contributor>
    <comment>/* Notes */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6752" xml:space="preserve">[[Category:Hardware]]
===Introduction===

ATI drivers come in two flavours:

1) X.Org open source 'radeon' driver - full support (accelerated 2D and 3D) for the Radeon 9200 and earlier. (Also supported for the 9200 - X850 for Slackware -current, or any Slackware newer than 11.0)

2) ATI's proprietary closed source 'fglrx' driver - support for the 9500 and above (all support for earlier cards has now been dropped). This is the only driver with any support, either 2D or 3D, for the X1xxx series of cards (R500 and newer).

====Kernel====

AGPGART: If you have an AGP card, you should ensure AGPGART and support for your specific GART are built in the kernel (built in or module is fine)

PCI Express: If you have a PCI Express card, you should ensure PCI Express support is built in the kernel.

==Seting up the 'radeon' driver==

===Preparing Your System===

====Kernel====

Direct Rendering Manager (DRM): Module or built in, plus the module under this for "ATI Radeon"

===Initial Setup===
Edit /etc/X11/xorg.conf

In Section "Module" add:

 Load "glx"
 Load "dri"

At the end of the file, add

 Section "DRI"
   Mode 0666
 EndSection

(Or use 'Xorg -configure' to generate a new xorg.conf to autodetect the ATi card)

===Tweaking===

To increase performance for Radeon users (in particular, R300 and R400), you may also want to add the following under the "Device" section for the radeon:

====AGP users====
 
 Option "AGPMode" "8" # Modify accordingly if you don't have an AGP 8x card 
 Option "AGPFastWrite" "true" # This one has big warnings all over it, so test it first! 

====Mobility card users====
 
 Option "DynamicClocks" "true" # The equivalent of ATi's PowerPlay 
 Option "BIOSHotkeys" "true" # You _might_ need this for some special function keys on your laptop 

====All users====
 
 Option "EnablePageFlip" "true" 
 Option "ColorTiling" "true" 

===Final Check===

Run 'glxinfo | grep render'. It will return something like the following (the last line will vary depending on R300/ R400, PCI/ PCIE or AGP, etc). The important thing is that this reports "direct rendering: yes".

 direct rendering: Yes
 OpenGL renderer string: Mesa DRI R300 20060815 AGP 8x x86/MMX+/3DNow!+/SSE TCL

===Notes===

'''R300 - R400:'''

Please note that these cards do not have accelerated hardware support in X.Org &lt; 6.9 (i.e. Slackware 11.0 or older)

'''R500 (X1xxx and above)'''

Sorry, there is no open source accelerated support in X for these cards. Either use fglrx or vesa.

'''R600'''

For the ATI Radeon Mobility 2600 (the built in video on the HP Compaq 8510p), the '''radeon''' driver can be used for accelerated support.  The amdgpu driver will not work with this video board.  Though the fglrx driver can be used with this video board, it is not necessary to install the proprietary driver to get this video board working.

==Setting up the 'fglrx' driver==

===Preparing Your System===

====Libraries====

The fglrx driver requires that you have the package cxxlibs installed on your system to build it.

'''(Slamd64)''': You will also need the 32 bit compatibility libraries from c/

====Kernel====

Direct Rendering Manager (DRM): Must *not* be built into the kernel - it should be a module (and not loaded) or not built.

Frame Buffer: Must *not* be built into the kernel - it should be a module or not built (it is not compatible with the current fglrx drivers).

===Installing the Driver===

You will need to download the 'ATI Driver Installer' package (the RPM packages do not have support for X.Org 6.9).

Once you have downloaded the installer, run it (I reccommend using sudo, as you need root permissions but also need access to the X server. You could use xhost+ and then su, but this is not safe).

 sudo sh ati-driver-installer-$VERSION-$ARCH.run

You need to select the 'Install driver' (the ATI installer cannot generate a Slackware package), and then it is reccommended you choose "automatic" on the next screen. The driver will now install itself.

Make sure that you mount tmpfs for 3D acceleration, or you can get unexpected results.

ie: 
 'FGLTexMgr: open of shared memory object failed (Function not implemented)
 __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
 fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!'
 
Add the following to /etc/fstab:
 tmpfs     /dev/shm           tmpfs        defaults            0 0
then 'mount /dev/shm' on a console

===Patching the Driver===

If you are running the latest kernel, more often than not you will need to patch the fglrx driver. At the very least, you will need to manually rebuild it if you change your kernel - follow instruction 1 if necessary, then 2 and 3.

There is no central repository of these, so it is not possible to point you to a specific place to check for them (although the [http://ati.cchtml.com Unofficial ATI Bugzilla] or [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D Linux Drivers forum] are good places to check).

Once you have downloaded the patches:

1. Apply them in /lib/modules/fglrx (or /lib/modules/fglrx/build_mod)

 cd /lib/modules/fglrx/build_mod
 cat somepatch.diff | patch -p1

2. Rebuild the fglrx module

 sh /lib/modules/fglrx/build_mod/make.sh

N.B. Modules built are kernel specific - you can only build a module for the kernel you are currently running.

3. Install the module

 sh /lib/modules/fglrx/make_install.sh

===Configuring the X server===

If you have not installed the fglrx driver before, run:

 aticonfig --initial --input=/etc/X11/xorg.conf
 aticonfig --ovt=Xv

This will add an fglrx 'Section "Device"' to /etc/X11/xorg.conf and enable video overlay (enables video playback)

Edit /etc/X11/xorg.conf (you need to do this with root permissions)

Find:

1) A 'Section "Device"' that contains fglrx
2) 'Section "Screen"'

Then:

1) Under the Section "Device" that contains fglrx&lt;br /&gt;
1A). Make a note of the value of "Indentifier"&lt;br /&gt;

2) Under Section "Screen", replace the value of "Device" with the value you just noted from fglrx

At the end of /etc/X11/xorg.conf, add this section (This allows all users to access the direct rendering mode - without it, you can't use acceleration as a user):

 Section "DRI"
        Mode         0666
 EndSection

Restart the X server

===Final Check===

To check that fglrx has been installed and setup correctly, run 'fglrxinfo' in a terminal under X. It should return something like:

 display: :0.0  screen: 0
 OpenGL vendor string: ATI Technologies Inc.
 OpenGL renderer string: MOBILITY RADEON X700 Generic
 OpenGL version string: 2.0.5642 (8.22.5)

(The 'renderer' string will vary depending on the chip your card actually has).

===Uninstalling the driver===

With root permissions, run:

 sh /usr/share/fglrx/fglrx-uninstall.sh</text>
    <sha1>f0118afe0a67a801f8005916b6e4e0249d8729fb</sha1>
  </revision>
  <revision>
    <id>3174</id>
    <parentid>3170</parentid>
    <timestamp>2018-10-13T02:46:43Z</timestamp>
    <contributor>
      <username>Phorneker</username>
      <id>604</id>
    </contributor>
    <comment>/* Notes */ Updated information for configuring the R600 chipset to work with X11.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="6939" xml:space="preserve">[[Category:Hardware]]
===Introduction===

ATI drivers come in two flavours:

1) X.Org open source 'radeon' driver - full support (accelerated 2D and 3D) for the Radeon 9200 and earlier. (Also supported for the 9200 - X850 for Slackware -current, or any Slackware newer than 11.0)

2) ATI's proprietary closed source 'fglrx' driver - support for the 9500 and above (all support for earlier cards has now been dropped). This is the only driver with any support, either 2D or 3D, for the X1xxx series of cards (R500 and newer).

====Kernel====

AGPGART: If you have an AGP card, you should ensure AGPGART and support for your specific GART are built in the kernel (built in or module is fine)

PCI Express: If you have a PCI Express card, you should ensure PCI Express support is built in the kernel.

==Seting up the 'radeon' driver==

===Preparing Your System===

====Kernel====

Direct Rendering Manager (DRM): Module or built in, plus the module under this for "ATI Radeon"

===Initial Setup===
Edit /etc/X11/xorg.conf

In Section "Module" add:

 Load "glx"
 Load "dri"

At the end of the file, add

 Section "DRI"
   Mode 0666
 EndSection

(Or use 'Xorg -configure' to generate a new xorg.conf to autodetect the ATi card)

===Tweaking===

To increase performance for Radeon users (in particular, R300 and R400), you may also want to add the following under the "Device" section for the radeon:

====AGP users====
 
 Option "AGPMode" "8" # Modify accordingly if you don't have an AGP 8x card 
 Option "AGPFastWrite" "true" # This one has big warnings all over it, so test it first! 

====Mobility card users====
 
 Option "DynamicClocks" "true" # The equivalent of ATi's PowerPlay 
 Option "BIOSHotkeys" "true" # You _might_ need this for some special function keys on your laptop 

====All users====
 
 Option "EnablePageFlip" "true" 
 Option "ColorTiling" "true" 

===Final Check===

Run 'glxinfo | grep render'. It will return something like the following (the last line will vary depending on R300/ R400, PCI/ PCIE or AGP, etc). The important thing is that this reports "direct rendering: yes".

 direct rendering: Yes
 OpenGL renderer string: Mesa DRI R300 20060815 AGP 8x x86/MMX+/3DNow!+/SSE TCL

===Notes===

'''R300 - R400:'''

Please note that these cards do not have accelerated hardware support in X.Org &lt; 6.9 (i.e. Slackware 11.0 or older)

'''R500 (X1xxx and above)'''

Sorry, there is no open source accelerated support in X for these cards. Either use fglrx or vesa.

'''R600'''

For the ATI Radeon Mobility 2600 (the built in video on the HP Compaq 8510p), the '''ati''' driver can be used for accelerated support.  The amdgpu driver will not work with this video board.  Though the fglrx driver can be used with this video board, it is not necessary to install the proprietary driver to get this video board working.

Upcoming releases of Slackware will have '''ati''' driver instead of '''radeon''', so /etc/X11/xorg.conf will have to be updated accordingly as you upgrade Slackware to the latest release.

==Setting up the 'fglrx' driver==

===Preparing Your System===

====Libraries====

The fglrx driver requires that you have the package cxxlibs installed on your system to build it.

'''(Slamd64)''': You will also need the 32 bit compatibility libraries from c/

====Kernel====

Direct Rendering Manager (DRM): Must *not* be built into the kernel - it should be a module (and not loaded) or not built.

Frame Buffer: Must *not* be built into the kernel - it should be a module or not built (it is not compatible with the current fglrx drivers).

===Installing the Driver===

You will need to download the 'ATI Driver Installer' package (the RPM packages do not have support for X.Org 6.9).

Once you have downloaded the installer, run it (I reccommend using sudo, as you need root permissions but also need access to the X server. You could use xhost+ and then su, but this is not safe).

 sudo sh ati-driver-installer-$VERSION-$ARCH.run

You need to select the 'Install driver' (the ATI installer cannot generate a Slackware package), and then it is reccommended you choose "automatic" on the next screen. The driver will now install itself.

Make sure that you mount tmpfs for 3D acceleration, or you can get unexpected results.

ie: 
 'FGLTexMgr: open of shared memory object failed (Function not implemented)
 __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
 fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!'
 
Add the following to /etc/fstab:
 tmpfs     /dev/shm           tmpfs        defaults            0 0
then 'mount /dev/shm' on a console

===Patching the Driver===

If you are running the latest kernel, more often than not you will need to patch the fglrx driver. At the very least, you will need to manually rebuild it if you change your kernel - follow instruction 1 if necessary, then 2 and 3.

There is no central repository of these, so it is not possible to point you to a specific place to check for them (although the [http://ati.cchtml.com Unofficial ATI Bugzilla] or [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D Linux Drivers forum] are good places to check).

Once you have downloaded the patches:

1. Apply them in /lib/modules/fglrx (or /lib/modules/fglrx/build_mod)

 cd /lib/modules/fglrx/build_mod
 cat somepatch.diff | patch -p1

2. Rebuild the fglrx module

 sh /lib/modules/fglrx/build_mod/make.sh

N.B. Modules built are kernel specific - you can only build a module for the kernel you are currently running.

3. Install the module

 sh /lib/modules/fglrx/make_install.sh

===Configuring the X server===

If you have not installed the fglrx driver before, run:

 aticonfig --initial --input=/etc/X11/xorg.conf
 aticonfig --ovt=Xv

This will add an fglrx 'Section "Device"' to /etc/X11/xorg.conf and enable video overlay (enables video playback)

Edit /etc/X11/xorg.conf (you need to do this with root permissions)

Find:

1) A 'Section "Device"' that contains fglrx
2) 'Section "Screen"'

Then:

1) Under the Section "Device" that contains fglrx&lt;br /&gt;
1A). Make a note of the value of "Indentifier"&lt;br /&gt;

2) Under Section "Screen", replace the value of "Device" with the value you just noted from fglrx

At the end of /etc/X11/xorg.conf, add this section (This allows all users to access the direct rendering mode - without it, you can't use acceleration as a user):

 Section "DRI"
        Mode         0666
 EndSection

Restart the X server

===Final Check===

To check that fglrx has been installed and setup correctly, run 'fglrxinfo' in a terminal under X. It should return something like:

 display: :0.0  screen: 0
 OpenGL vendor string: ATI Technologies Inc.
 OpenGL renderer string: MOBILITY RADEON X700 Generic
 OpenGL version string: 2.0.5642 (8.22.5)

(The 'renderer' string will vary depending on the chip your card actually has).

===Uninstalling the driver===

With root permissions, run:

 sh /usr/share/fglrx/fglrx-uninstall.sh</text>
    <sha1>fb9502aff8b83c8fdbefac43e6a963ff87f429ec</sha1>
  </revision>
  <revision>
    <id>3175</id>
    <parentid>3174</parentid>
    <timestamp>2018-10-13T02:49:34Z</timestamp>
    <contributor>
      <username>Phorneker</username>
      <id>604</id>
    </contributor>
    <comment>/* Notes */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="7149" xml:space="preserve">[[Category:Hardware]]
===Introduction===

ATI drivers come in two flavours:

1) X.Org open source 'radeon' driver - full support (accelerated 2D and 3D) for the Radeon 9200 and earlier. (Also supported for the 9200 - X850 for Slackware -current, or any Slackware newer than 11.0)

2) ATI's proprietary closed source 'fglrx' driver - support for the 9500 and above (all support for earlier cards has now been dropped). This is the only driver with any support, either 2D or 3D, for the X1xxx series of cards (R500 and newer).

====Kernel====

AGPGART: If you have an AGP card, you should ensure AGPGART and support for your specific GART are built in the kernel (built in or module is fine)

PCI Express: If you have a PCI Express card, you should ensure PCI Express support is built in the kernel.

==Seting up the 'radeon' driver==

===Preparing Your System===

====Kernel====

Direct Rendering Manager (DRM): Module or built in, plus the module under this for "ATI Radeon"

===Initial Setup===
Edit /etc/X11/xorg.conf

In Section "Module" add:

 Load "glx"
 Load "dri"

At the end of the file, add

 Section "DRI"
   Mode 0666
 EndSection

(Or use 'Xorg -configure' to generate a new xorg.conf to autodetect the ATi card)

===Tweaking===

To increase performance for Radeon users (in particular, R300 and R400), you may also want to add the following under the "Device" section for the radeon:

====AGP users====
 
 Option "AGPMode" "8" # Modify accordingly if you don't have an AGP 8x card 
 Option "AGPFastWrite" "true" # This one has big warnings all over it, so test it first! 

====Mobility card users====
 
 Option "DynamicClocks" "true" # The equivalent of ATi's PowerPlay 
 Option "BIOSHotkeys" "true" # You _might_ need this for some special function keys on your laptop 

====All users====
 
 Option "EnablePageFlip" "true" 
 Option "ColorTiling" "true" 

===Final Check===

Run 'glxinfo | grep render'. It will return something like the following (the last line will vary depending on R300/ R400, PCI/ PCIE or AGP, etc). The important thing is that this reports "direct rendering: yes".

 direct rendering: Yes
 OpenGL renderer string: Mesa DRI R300 20060815 AGP 8x x86/MMX+/3DNow!+/SSE TCL

===Notes===

'''R300 - R400:'''

Please note that these cards do not have accelerated hardware support in X.Org &lt; 6.9 (i.e. Slackware 11.0 or older)

'''R500 (X1xxx and above)'''

Sorry, there is no open source accelerated support in X for these cards. Either use fglrx or vesa.

'''R600'''

For the ATI Radeon Mobility 2600 (the built in video on the HP Compaq 8510p), the '''ati''' driver can be used for accelerated support.  The amdgpu driver will not work with this video board.  Though the fglrx driver can be used with this video board, it is not necessary to install the proprietary driver to get this video board working.

Upcoming releases of Slackware will have '''ati''' driver instead of '''radeon''', so /etc/X11/xorg.conf will have to be updated accordingly as you upgrade Slackware to the latest release.  Fortunately, Slackware 14.2 (stable) configures this chipset correctly for the ATi Radeon Mobility 2600.  The change is necessary
only if you are running '''current''', or whenever Slackware 15.x is released.

==Setting up the 'fglrx' driver==

===Preparing Your System===

====Libraries====

The fglrx driver requires that you have the package cxxlibs installed on your system to build it.

'''(Slamd64)''': You will also need the 32 bit compatibility libraries from c/

====Kernel====

Direct Rendering Manager (DRM): Must *not* be built into the kernel - it should be a module (and not loaded) or not built.

Frame Buffer: Must *not* be built into the kernel - it should be a module or not built (it is not compatible with the current fglrx drivers).

===Installing the Driver===

You will need to download the 'ATI Driver Installer' package (the RPM packages do not have support for X.Org 6.9).

Once you have downloaded the installer, run it (I reccommend using sudo, as you need root permissions but also need access to the X server. You could use xhost+ and then su, but this is not safe).

 sudo sh ati-driver-installer-$VERSION-$ARCH.run

You need to select the 'Install driver' (the ATI installer cannot generate a Slackware package), and then it is reccommended you choose "automatic" on the next screen. The driver will now install itself.

Make sure that you mount tmpfs for 3D acceleration, or you can get unexpected results.

ie: 
 'FGLTexMgr: open of shared memory object failed (Function not implemented)
 __FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
 fglX11AllocateManagedSurface: __FGLTexMgrCreateObject failed!!'
 
Add the following to /etc/fstab:
 tmpfs     /dev/shm           tmpfs        defaults            0 0
then 'mount /dev/shm' on a console

===Patching the Driver===

If you are running the latest kernel, more often than not you will need to patch the fglrx driver. At the very least, you will need to manually rebuild it if you change your kernel - follow instruction 1 if necessary, then 2 and 3.

There is no central repository of these, so it is not possible to point you to a specific place to check for them (although the [http://ati.cchtml.com Unofficial ATI Bugzilla] or [http://www.rage3d.com/board/forumdisplay.php?f=88 Rage3D Linux Drivers forum] are good places to check).

Once you have downloaded the patches:

1. Apply them in /lib/modules/fglrx (or /lib/modules/fglrx/build_mod)

 cd /lib/modules/fglrx/build_mod
 cat somepatch.diff | patch -p1

2. Rebuild the fglrx module

 sh /lib/modules/fglrx/build_mod/make.sh

N.B. Modules built are kernel specific - you can only build a module for the kernel you are currently running.

3. Install the module

 sh /lib/modules/fglrx/make_install.sh

===Configuring the X server===

If you have not installed the fglrx driver before, run:

 aticonfig --initial --input=/etc/X11/xorg.conf
 aticonfig --ovt=Xv

This will add an fglrx 'Section "Device"' to /etc/X11/xorg.conf and enable video overlay (enables video playback)

Edit /etc/X11/xorg.conf (you need to do this with root permissions)

Find:

1) A 'Section "Device"' that contains fglrx
2) 'Section "Screen"'

Then:

1) Under the Section "Device" that contains fglrx&lt;br /&gt;
1A). Make a note of the value of "Indentifier"&lt;br /&gt;

2) Under Section "Screen", replace the value of "Device" with the value you just noted from fglrx

At the end of /etc/X11/xorg.conf, add this section (This allows all users to access the direct rendering mode - without it, you can't use acceleration as a user):

 Section "DRI"
        Mode         0666
 EndSection

Restart the X server

===Final Check===

To check that fglrx has been installed and setup correctly, run 'fglrxinfo' in a terminal under X. It should return something like:

 display: :0.0  screen: 0
 OpenGL vendor string: ATI Technologies Inc.
 OpenGL renderer string: MOBILITY RADEON X700 Generic
 OpenGL version string: 2.0.5642 (8.22.5)

(The 'renderer' string will vary depending on the chip your card actually has).

===Uninstalling the driver===

With root permissions, run:

 sh /usr/share/fglrx/fglrx-uninstall.sh</text>
    <sha1>dd61b65a6b283823bec5d13d0aed7002b4b5a278</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Bash Autocompletion</title>
  <ns>0</ns>
  <id>41</id>
  <revision>
    <id>3171</id>
    <parentid>62</parentid>
    <timestamp>2018-06-04T06:02:38Z</timestamp>
    <contributor>
      <username>Cwilling</username>
      <id>606</id>
    </contributor>
    <comment>Recent bash-completion packages now have system files in /usr/share/bash-completion (not /etc as previously).</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2636" xml:space="preserve">[[Category:Tips]]

Did you know that Bash has a really powerful autocompletion system, which can and usually will make your life easier? If you have used ZSH, you probably know what I'm talking about.

For example, you can type

   svn co''&lt;TAB&gt;&lt;TAB&gt;''

and bash will attempt to auto complete as it does normally with paths and variables, but instead it will output:

  ismael@damned_02:~/src/chkout$ svn co''&lt;TAB&gt;&lt;TAB&gt;''
  co      commit  copy    
  ismael@damned_02:~/src/chkout$ svn co

Then you can type:

  ismael@damned_02:~/src/chkout$ svn com''&lt;TAB&gt;''

and BASH will auto complete to:

  ismael@damned_02:~/src/chkout$ svn commit

Or if you're running as root and want to get rid of that *$@&amp; module wich keeps crashing your machine:

   root@damned_02:~# rmmod n''&lt;TAB&gt;''
   root@damned_02:~# rmmod nvidia


If you think all that is neat, all that you have to do to enable this kind of auto completion in Slackware is to install the bash-completion package, which can be found under [http://slackware.osuosl.org/slackware-11.0/extra/bash-completion/bash-completion-20060301-noarch-1.tgz /extra]:

   root@damned_02:~# mount /mnt/cdrom
   root@damned_02:~# installpkg /mnt/cdrom/extra/bash-completion/bash-completion-20060301-noarch-1.tgz
   ...

(BTW, bash-completion also autocompletes ''installpkg, upgradepkg'' and ''removepkg'' with .tgz files and installed packages for ''removepkg''. It can also fill mount commands with data from fstab).

Then you can just logout and login again or

   source /usr/share/bash-completion/bash_completion

and ''voila''!


You can see which commands have autocompletion by issuing:

  complete -p | sed -e's/.* \([^ ]\+\)/\1/' | sort | less

You can also add your own commands at /etc/bash_completion.d/ You may want to see the available completions to understand how they work.

For your own personal user account you can edit your ~/.bash_completion file.

Here is a sample BASH completion function I made to give the script 'test' 3 completion
options:

&lt;pre&gt;
_test ()
{
         local cur
         cur=${COMP_WORDS[COMP_CWORD]}

         if [[ "$cur" == -* ]]; then
         COMPREPLY=( $( compgen -W '-option -test -foobar' -- $cur ))

         else
             _filedir
         fi
}

complete -F _test test
&lt;/pre&gt;

I put that into my ~/.bash_completion file and now

  $ test -&lt;tab&gt;
  -foobar  -option  -test

brings up those three options (-option,-test and -foobar). You have to reload your terminal first to see the changes or re-source /etc/bash_completion

  $ . /usr/share/bash-compoletion/bash_completion

or just re-source your ~/.bash_completion

  $ . ./.bash_completion</text>
    <sha1>378bc78148839e573ec1e31a583f247f8a9d5214</sha1>
  </revision>
  <revision>
    <id>3172</id>
    <parentid>3171</parentid>
    <timestamp>2018-06-04T06:04:49Z</timestamp>
    <contributor>
      <username>Cwilling</username>
      <id>606</id>
    </contributor>
    <minor/>
    <comment>typo</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2635" xml:space="preserve">[[Category:Tips]]

Did you know that Bash has a really powerful autocompletion system, which can and usually will make your life easier? If you have used ZSH, you probably know what I'm talking about.

For example, you can type

   svn co''&lt;TAB&gt;&lt;TAB&gt;''

and bash will attempt to auto complete as it does normally with paths and variables, but instead it will output:

  ismael@damned_02:~/src/chkout$ svn co''&lt;TAB&gt;&lt;TAB&gt;''
  co      commit  copy    
  ismael@damned_02:~/src/chkout$ svn co

Then you can type:

  ismael@damned_02:~/src/chkout$ svn com''&lt;TAB&gt;''

and BASH will auto complete to:

  ismael@damned_02:~/src/chkout$ svn commit

Or if you're running as root and want to get rid of that *$@&amp; module wich keeps crashing your machine:

   root@damned_02:~# rmmod n''&lt;TAB&gt;''
   root@damned_02:~# rmmod nvidia


If you think all that is neat, all that you have to do to enable this kind of auto completion in Slackware is to install the bash-completion package, which can be found under [http://slackware.osuosl.org/slackware-11.0/extra/bash-completion/bash-completion-20060301-noarch-1.tgz /extra]:

   root@damned_02:~# mount /mnt/cdrom
   root@damned_02:~# installpkg /mnt/cdrom/extra/bash-completion/bash-completion-20060301-noarch-1.tgz
   ...

(BTW, bash-completion also autocompletes ''installpkg, upgradepkg'' and ''removepkg'' with .tgz files and installed packages for ''removepkg''. It can also fill mount commands with data from fstab).

Then you can just logout and login again or

   source /usr/share/bash-completion/bash_completion

and ''voila''!


You can see which commands have autocompletion by issuing:

  complete -p | sed -e's/.* \([^ ]\+\)/\1/' | sort | less

You can also add your own commands at /etc/bash_completion.d/ You may want to see the available completions to understand how they work.

For your own personal user account you can edit your ~/.bash_completion file.

Here is a sample BASH completion function I made to give the script 'test' 3 completion
options:

&lt;pre&gt;
_test ()
{
         local cur
         cur=${COMP_WORDS[COMP_CWORD]}

         if [[ "$cur" == -* ]]; then
         COMPREPLY=( $( compgen -W '-option -test -foobar' -- $cur ))

         else
             _filedir
         fi
}

complete -F _test test
&lt;/pre&gt;

I put that into my ~/.bash_completion file and now

  $ test -&lt;tab&gt;
  -foobar  -option  -test

brings up those three options (-option,-test and -foobar). You have to reload your terminal first to see the changes or re-source /etc/bash_completion

  $ . /usr/share/bash-completion/bash_completion

or just re-source your ~/.bash_completion

  $ . ./.bash_completion</text>
    <sha1>dc970308415afe4913f56d10b9581d47fa5c3d84</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Install Slackware Using A USB Flash Drive</title>
  <ns>0</ns>
  <id>233</id>
  <revision>
    <id>3177</id>
    <parentid>843</parentid>
    <timestamp>2018-10-27T19:19:44Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3143" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

The following command will overwrite all the files currently present on the USB drive so prior backups are highly advisable:

 dd if=slackware-13.1-install-dvd.iso of=/dev/sdX

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is. When installing, choose "Install from a Slackware CD or DVD". Then select the "manual" option, then the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed as when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>4607e08f44001c2df9a9d18ed3b33dcd2a63bbaf</sha1>
  </revision>
  <revision>
    <id>3178</id>
    <parentid>3177</parentid>
    <timestamp>2018-10-27T19:36:39Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* Copy the ISO to the USB flash drive */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3360" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Syslinux &gt;= 3.72

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

to identify the designation of your usb stick/drive use 

 fdisk -l

dd will write the iso to whatever drive you tell it to so make double sure 
you have the right drive designation in the following command


The following command will overwrite all the files currently present on the USB drive with a bootable iso

 dd if=slackware-14.2-install-dvd.iso of=/path/to/usb (example of=/dev/sdX)

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is. When installing, choose "Install from a Slackware CD or DVD". Then select the "manual" option, then the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed as when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>a3f2babee8c25bac5b80d38e7dbe04536e7d8da9</sha1>
  </revision>
  <revision>
    <id>3179</id>
    <parentid>3178</parentid>
    <timestamp>2018-10-27T19:37:57Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* Prerequisites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3342" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO one, available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

to identify the designation of your usb stick/drive use 

 fdisk -l

dd will write the iso to whatever drive you tell it to so make double sure 
you have the right drive designation in the following command


The following command will overwrite all the files currently present on the USB drive with a bootable iso

 dd if=slackware-14.2-install-dvd.iso of=/path/to/usb (example of=/dev/sdX)

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is. When installing, choose "Install from a Slackware CD or DVD". Then select the "manual" option, then the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed as when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>6a15d1fdd01393fb956389c4d1673446a5d9abab</sha1>
  </revision>
  <revision>
    <id>3180</id>
    <parentid>3179</parentid>
    <timestamp>2018-10-27T19:39:05Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* Prerequisites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3337" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

to identify the designation of your usb stick/drive use 

 fdisk -l

dd will write the iso to whatever drive you tell it to so make double sure 
you have the right drive designation in the following command


The following command will overwrite all the files currently present on the USB drive with a bootable iso

 dd if=slackware-14.2-install-dvd.iso of=/path/to/usb (example of=/dev/sdX)

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is. When installing, choose "Install from a Slackware CD or DVD". Then select the "manual" option, then the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed as when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>07327f2597ca2391d67201f83eed4f151a6180e6</sha1>
  </revision>
  <revision>
    <id>3181</id>
    <parentid>3180</parentid>
    <timestamp>2018-10-27T19:39:48Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* Prerequisites */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3353" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image (4GB or larger)

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

to identify the designation of your usb stick/drive use 

 fdisk -l

dd will write the iso to whatever drive you tell it to so make double sure 
you have the right drive designation in the following command


The following command will overwrite all the files currently present on the USB drive with a bootable iso

 dd if=slackware-14.2-install-dvd.iso of=/path/to/usb (example of=/dev/sdX)

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is. When installing, choose "Install from a Slackware CD or DVD". Then select the "manual" option, then the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed as when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>5e154d3a6397361a8f2cd2683589abedd6352283</sha1>
  </revision>
  <revision>
    <id>3182</id>
    <parentid>3181</parentid>
    <timestamp>2018-10-27T19:44:17Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* Copy the ISO to the USB flash drive */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3335" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image (4GB or larger)

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

to identify the designation of your usb stick/drive use 

 fdisk -l

dd will write the iso to whatever drive you tell it to so make double sure 
you have the right drive designation in the following command


The following command will overwrite all the files currently present on the USB drive with a bootable iso

 dd if=/path/to/iso of=/path/to/usb (example of=/dev/sdX)

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

Before running '''setup''', look up (with '''fdisk -l''') which device your USB drive is. When installing, choose "Install from a Slackware CD or DVD". Then select the "manual" option, then the "custom" option.
Enter /dev/sdX1 (as shown by "fdisk -l") and installation will proceed as when installing from a DVD.

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>16ac079eb369046d15ed83f35722d57969b93a5a</sha1>
  </revision>
  <revision>
    <id>3183</id>
    <parentid>3182</parentid>
    <timestamp>2018-10-27T21:47:22Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* Installation */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="3268" xml:space="preserve">[[Category:Tutorials]]

Installing Slackware using a USB flash drive is very easy.

Slackware includes a usbboot.img in the usb-and-pxe-installers directory of the official installation media, which is a minimal image very handy for FTP or other kinds of network installations.

In the same directory one can also find usbimg2disk.sh, a script that will dump the usbboot.img image to a flash drive, useful in case the above image does not work for you out of the box.

Additionally, AlienBOB has written two articles in his blog on how to install Slackware using a USB flash drive from either

[http://alien.slackbook.org/blog/welcome-windows-user/ Microsoft Windows] or [http://alien.slackbook.org/blog/installing-slackware-using-usb-thumb-drive/ Linux].

This document describes yet another way of creating an image capable of booting from USB, containing all of the packages neeeded for an installation, using [http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE Isohybrid].

== Prerequisites ==

A USB flash drive that can fit the ISO image (4GB or larger)

Additionally you should either have:

a) official Slackware installation media, preferably the DVD ISO available on any Slackware mirror

or

b) a local copy of the Slackware tree.

That may be the tree of a stable release, or even the tree of the Slackware current development cycle.

If you choose to use a local copy of the tree you should be able to create your own ISO image using a script such as:

Pat's [http://slackware.osuosl.org/slackware/isolinux/README.TXT DVD script], AlienBOB's [http://www.slackware.com/~alien/tools/mirror-slackware-current.sh mirror-slackware-current script] or even a custom one of your own.

== Copy the ISO to the USB flash drive ==

All that is left to do now is copy the ISO to the USB flash drive.

This can be done using the [http://linux.die.net/man/1/dd dd] command as the root user.

to identify the designation of your usb stick/drive use 

 fdisk -l

dd will write the iso to whatever drive you tell it to so make double sure 
you have the right drive designation in the following command


The following command will overwrite all the files currently present on the USB drive with a bootable iso

 dd if=/path/to/iso of=/path/to/usb (example of=/dev/sdX)

PS1. dd expects the name of a device, not a partition, so you should use eg. /dev/sdb instead of /dev/sdb1.

PS2. the USB drive should NOT be mounted during dd invocation.

== Installation ==

Boot the machine using the USB drive.

When installing, choose "Install from a slackware USB stick". follow the steps. setup your keyboard
add swap space (if used) and select your target drive. when selecting source select 

 Install from a Slackware USB stick

and follow the prompts

== Install with Unetbootin ==

It is possible to install with unetbootin. Download the Slackware iso image of your choice and then install to a USB drive using unetbootin. Tutorials for unetbootin are everywhere. Then, when you get to the SOURCE option in setup use the drive you are installing slackware from (usually it is /dev/sdb1). When it asks where the packages are, enter /slackware for 32 bit or /slackware64 for 64 bit. This was tested using the Slackware 14.0 64-bit x86_64 iso.</text>
    <sha1>7df30ee8fbccec751de349097fa31a07eebfb004</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Third Party Package Managers</title>
  <ns>0</ns>
  <id>170</id>
  <revision>
    <id>3184</id>
    <parentid>659</parentid>
    <timestamp>2018-10-28T00:22:22Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* swaret */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9605" xml:space="preserve">= Purpose =

The mere mention of third party package managers (such as [http://software.jaos.org/#slapt-get slapt-get] and [http://swaret.sourceforge.net/ swaret]) often results in a quick admonishment from Slackware users, and unfortunately, the only reason given in most cases is something along the lines of "they'll break your system."  This leaves users in a state of confusion, as the respective web sites of these third party tools tout them as an improvement.  The purpose of this page is to explain why and how these tools will often result in system breakage.

= Overview of Slackware's Native Package Tools =

Slackware's native package management utilities (&lt;tt&gt;pkgtool(8)&lt;/tt&gt;, &lt;tt&gt;installpkg(8)&lt;/tt&gt;, &lt;tt&gt;removepkg(8)&lt;/tt&gt;, and &lt;tt&gt;upgradepkg(8)&lt;/tt&gt;) do not support any form of dependency checking.  A Slackware package is essentially a compressed tarball of the files associated with an application, a file containing a short description of the application (&lt;tt&gt;./install/slack-desc&lt;/tt&gt;), and a script that performs some essential post-installation tasks (&lt;tt&gt;./install/doinst.sh&lt;/tt&gt;).  Installing a Slackware package simply copies those files to the filesystem and then executes the post-install script, while removing the package removes the files and reverses the post-install script.  As result, there is no guarantee that libraries and other files needed by a particular package are already present on the system when that particular package is installed.

= Overview of Selected Third Party Tools =

As stated above, Slackware's native package management suite neither has nor supports dependency resolution.  Because the third-party add-ons all use Slackware's native package tools, they are bound by this same limitation, at least to some extent, but some of them try to mitigate this in various ways; the following is an overview.


== swaret ==

no longer a viable package management solution

== slapt-get ==

=== Overview ===

Slapt-get makes use of additional files (&lt;tt&gt;slack-required&lt;/tt&gt;, &lt;tt&gt;slack-suggests&lt;/tt&gt;, &lt;tt&gt;slack-conflicts&lt;/tt&gt;) inside a Slackware package.  Essentially, if a package is listed in &lt;tt&gt;slack-required&lt;/tt&gt;, then slapt-get will install or upgrade it first; if a package is listed in &lt;tt&gt;slack-conflicts&lt;/tt&gt;, then slapt-get will remove it first; if a package is listed in &lt;tt&gt;slack-suggests&lt;/tt&gt;, then slapt-get will offer to install it in addition to the packages noted in &lt;tt&gt;slack-required&lt;/tt&gt;.

=== Potential Problems ===

Since official Slackware packages do not have the &lt;tt&gt;slack-required&lt;/tt&gt; and other files needed for slapt-get to determine dependencies, it is not able to resolve dependencies for them.  Therefore, slapt-get's perceived usefulness is in keeping unofficial third-party packages (or at least those which do contain the necessary files) up to date.  See the discussion below for more information on unofficial third-party packages.
Also, slapt-get, like swaret, will not "downgrade" a package to a previous version if it occurs in the upstream Slackware tree.

== sbopkg ==

=== Overview ===

[http://www.sbopkg.org/ SBopkg] is a tool for automating the download, compile and package build for SBo projects hosted in the [http://www.slackbuilds.org SlackBuilds.org ] repository.  SBo packages are reviewed by team members for completeness as well as applicability to each Slackware release.  SBo package documentation includes information regarding dependencies.

= Third Party (Unofficial) Packages =

This subject can elicit opinions just as strong as the topic of third-party package managers, and there are knowledgeable people on both sides of the issue.  Third party packages can obviously present a security risk, as there's no way to know what's really in them, but for the average user, there are (amazingly enough) bigger concerns.  On one hand, the user wants a package of some application that's not included with Slackware, but he doesn't want it to create other problems.  Oftentimes, third party packages are not built on "clean" systems -- that is, the computer on which they're built has quite a few other non-official packages installed -- so the resulting package needs those other things to work properly.  If the packager doesn't make note of all the different packages that this one depends on, the user installs it only to find that it still doesn't work.  Even worse, those other dependencies are often not even necessary if the package is built on a clean system - if the other package had not been present, the new one obviously wouldn't have linked against it.  
Installing third party packages from two different packagers can cause problems.  Package A might depend on Package B, which depends on Package C and optionally Package D.  If the person who built Package B only linked it against Package C (not D), but the Package A expects Package B to have both Package C and Package D dependencies, then Package A may not work, even though you (think you) have everything it needs installed.
Another frequent problem with third party packages is encountered by replacing stock (official) packages with unofficial ones.  In addition to the library version issues mentioned in the swaret discussion, newer package versions often require newer versions of other packages, which might require newer versions of still other packages, and before you know it, you have replaced a sizable portion of the official Slackware packages.  If/when something breaks, you will find it very difficult to find someone willing to help you, as there's no way to know how much effect the unofficial packages are having.


= Slackware -current =

Slackware -current is *not* a stable release of Slackware.  It is intended for advanced users who are familiar with how Slackware works to test (and report success/failure, find and fix bugs, etcetera) the new packages leading to the next stable release of Slackware.  Packages are constantly being added, removed, split up, merged, and otherwise mangled, and third party package managers (swaret/slapt-get/et al) should not be expected to know how to deal with this.  If you use one of those tools while trying to run Slackware -current and you don't understand how they work and their limitations, you *will* break your system and you will *not* have much luck finding someone who is sympathetic.  You have been warned.

You may be wondering why these tools have trouble with -current.  I won't even attempt to detail all of the potential issues, but here are a couple:
1. When upgrading to -current with one of these tools, the package sets are upgraded in alphabetical order (and the packages therein also in alphabetical order).  This means that a/bash will be upgraded before a/glibc-solibs.  If bash has been recompiled against newer glibc, and you upgrade to that new version, it will promptly stop working due to the fact that the needed version of glibc has not been upgraded yet; at that point, you are stuck with a "chicken and egg" problem.
2. Third party package tools will not install *new* packages that have been added in Slackware -current.  This is not a bug - it's a feature; if you purposefully didn't install something, then you don't want your automatic package updater reinstalling it.  However, when a package depends on something else that has been added or split out of an existing package, and your add-on package manager upgrades the existing package but doesn't install the added one, then the (upgraded) existing package will not work any more.


= Solutions and Suggestions =

For upgrading to Slackware -current, there is only *one* supported method: &lt;tt&gt;UPGRADE.TXT&lt;/tt&gt;  --  you can find this file on any Slackware mirror.  Note that this is also the only supported method to upgrade from one stable release of Slackware to another.

For keeping up to date on post-release patches added to a stable release of Slackware, you will *usually* be okay to use one of the third party package managers.  You should still read the &lt;tt&gt;ChangeLog.txt&lt;/tt&gt; before doing any upgrades, though, as new packages are occasionally added in /patches when circumstances require it.

For software not included in official Slackware, consider building it yourself or using a SlackBuild script from one of the projects which provides them.

One of the regular Slackware contributors, PiterPUNK, wrote and maintains a third-party package manager that minimizes all of the risks mentioned above.  [http://slackpkg.org Slackpkg] does not support downloading or installing unofficial packages, and it has provisions to install any added packages and uninstall any removed packages as well as the normal install/upgrade/remove routines.

Another third party package manager that promotes good practices is [http://slackroll.sourceforge.net/ SlackRoll] (see [[SlackRoll Tutorial|tutorial]]). Its philosophy is similar to that of Slackpkg but it is not included as part of Slackware. Programmed in Python, it is faster, has more features and detects more events from Slackware -current. However, the initial setup and workflow are a bit more complex.

= See Also =

* &lt;tt&gt;pkgtool(8)&lt;/tt&gt; -- man 8 pkgtool
* &lt;tt&gt;installpkg(8)&lt;/tt&gt; -- man 8 installpkg
* &lt;tt&gt;removepkg(8)&lt;/tt&gt; -- man 8 removepkg
* &lt;tt&gt;upgradepkg(8)&lt;/tt&gt; -- man 8 upgradepkg
* &lt;tt&gt;makepkg(8)&lt;/tt&gt; -- man 8 makepkg
* &lt;tt&gt;explodepkg(8)&lt;/tt&gt; -- man 8 explodepkg


= TODO =

* Add links to other wiki pages that are related to this topic (add to "See Also" above)
* Add hyperlinks to slapt-get, swaret, and other projects mentioned on this page
* Others?

[[Category:Information]]
[[Category:Tutorials]]</text>
    <sha1>21a63798668f6bcc5cc5e9bfd730e4972ed211c1</sha1>
  </revision>
  <revision>
    <id>3185</id>
    <parentid>3184</parentid>
    <timestamp>2018-10-28T00:45:38Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9993" xml:space="preserve">= Purpose =

The mere mention of third party package managers (such as [http://software.jaos.org/#slapt-get slapt-get] and [http://swaret.sourceforge.net/ swaret]) often results in a quick admonishment from Slackware users, and unfortunately, the only reason given in most cases is something along the lines of "they'll break your system."  This leaves users in a state of confusion, as the respective web sites of these third party tools tout them as an improvement.  The purpose of this page is to explain why and how these tools will often result in system breakage.

= Overview of Slackware's Native Package Tools =

Slackware's native package management utilities (&lt;tt&gt;pkgtool(8)&lt;/tt&gt;, &lt;tt&gt;installpkg(8)&lt;/tt&gt;, &lt;tt&gt;removepkg(8)&lt;/tt&gt;, and &lt;tt&gt;upgradepkg(8)&lt;/tt&gt;) do not support any form of dependency checking.  A Slackware package is essentially a compressed tarball of the files associated with an application, a file containing a short description of the application (&lt;tt&gt;./install/slack-desc&lt;/tt&gt;), and a script that performs some essential post-installation tasks (&lt;tt&gt;./install/doinst.sh&lt;/tt&gt;).  Installing a Slackware package simply copies those files to the filesystem and then executes the post-install script, while removing the package removes the files and reverses the post-install script.  As result, there is no guarantee that libraries and other files needed by a particular package are already present on the system when that particular package is installed.

= Overview of Selected Third Party Tools =

As stated above, Slackware's native package management suite neither has nor supports dependency resolution.  Because the third-party add-ons all use Slackware's native package tools, they are bound by this same limitation, at least to some extent, but some of them try to mitigate this in various ways; the following is an overview.


== swaret ==

no longer a viable package management solution

== slapt-get ==

=== Overview ===

Slapt-get makes use of additional files (&lt;tt&gt;slack-required&lt;/tt&gt;, &lt;tt&gt;slack-suggests&lt;/tt&gt;, &lt;tt&gt;slack-conflicts&lt;/tt&gt;) inside a Slackware package.  Essentially, if a package is listed in &lt;tt&gt;slack-required&lt;/tt&gt;, then slapt-get will install or upgrade it first; if a package is listed in &lt;tt&gt;slack-conflicts&lt;/tt&gt;, then slapt-get will remove it first; if a package is listed in &lt;tt&gt;slack-suggests&lt;/tt&gt;, then slapt-get will offer to install it in addition to the packages noted in &lt;tt&gt;slack-required&lt;/tt&gt;.

=== Potential Problems ===

Since official Slackware packages do not have the &lt;tt&gt;slack-required&lt;/tt&gt; and other files needed for slapt-get to determine dependencies, it is not able to resolve dependencies for them.  Therefore, slapt-get's perceived usefulness is in keeping unofficial third-party packages (or at least those which do contain the necessary files) up to date.  See the discussion below for more information on unofficial third-party packages.
Also, slapt-get, like swaret, will not "downgrade" a package to a previous version if it occurs in the upstream Slackware tree.

== sbopkg ==

=== Overview ===

[http://www.sbopkg.org/ SBopkg] is a tool for automating the download, compile and package build for SBo projects hosted in the [http://www.slackbuilds.org SlackBuilds.org ] repository.  SBo packages are reviewed by team members for completeness as well as applicability to each Slackware release.  SBo package documentation includes information regarding dependencies.

== sbotools ==

=== Overview ===


[https://pink-mist.github.io/sbotools/ sbotools] provides a ports-like interface to SlackBuilds.org. It consists of several commands, and a configuration file. It is written entirely in Perl and bundles a copy of the Sort::Versions module with itself for its own usage; this will not interfere with copies installed via the CPAN or SlackBuilds.org.


= Third Party (Unofficial) Packages =

This subject can elicit opinions just as strong as the topic of third-party package managers, and there are knowledgeable people on both sides of the issue.  Third party packages can obviously present a security risk, as there's no way to know what's really in them, but for the average user, there are (amazingly enough) bigger concerns.  On one hand, the user wants a package of some application that's not included with Slackware, but he doesn't want it to create other problems.  Oftentimes, third party packages are not built on "clean" systems -- that is, the computer on which they're built has quite a few other non-official packages installed -- so the resulting package needs those other things to work properly.  If the packager doesn't make note of all the different packages that this one depends on, the user installs it only to find that it still doesn't work.  Even worse, those other dependencies are often not even necessary if the package is built on a clean system - if the other package had not been present, the new one obviously wouldn't have linked against it.  
Installing third party packages from two different packagers can cause problems.  Package A might depend on Package B, which depends on Package C and optionally Package D.  If the person who built Package B only linked it against Package C (not D), but the Package A expects Package B to have both Package C and Package D dependencies, then Package A may not work, even though you (think you) have everything it needs installed.
Another frequent problem with third party packages is encountered by replacing stock (official) packages with unofficial ones.  In addition to the library version issues mentioned in the swaret discussion, newer package versions often require newer versions of other packages, which might require newer versions of still other packages, and before you know it, you have replaced a sizable portion of the official Slackware packages.  If/when something breaks, you will find it very difficult to find someone willing to help you, as there's no way to know how much effect the unofficial packages are having.


= Slackware -current =

Slackware -current is *not* a stable release of Slackware.  It is intended for advanced users who are familiar with how Slackware works to test (and report success/failure, find and fix bugs, etcetera) the new packages leading to the next stable release of Slackware.  Packages are constantly being added, removed, split up, merged, and otherwise mangled, and third party package managers (swaret/slapt-get/et al) should not be expected to know how to deal with this.  If you use one of those tools while trying to run Slackware -current and you don't understand how they work and their limitations, you *will* break your system and you will *not* have much luck finding someone who is sympathetic.  You have been warned.

You may be wondering why these tools have trouble with -current.  I won't even attempt to detail all of the potential issues, but here are a couple:
1. When upgrading to -current with one of these tools, the package sets are upgraded in alphabetical order (and the packages therein also in alphabetical order).  This means that a/bash will be upgraded before a/glibc-solibs.  If bash has been recompiled against newer glibc, and you upgrade to that new version, it will promptly stop working due to the fact that the needed version of glibc has not been upgraded yet; at that point, you are stuck with a "chicken and egg" problem.
2. Third party package tools will not install *new* packages that have been added in Slackware -current.  This is not a bug - it's a feature; if you purposefully didn't install something, then you don't want your automatic package updater reinstalling it.  However, when a package depends on something else that has been added or split out of an existing package, and your add-on package manager upgrades the existing package but doesn't install the added one, then the (upgraded) existing package will not work any more.


= Solutions and Suggestions =

For upgrading to Slackware -current, there is only *one* supported method: &lt;tt&gt;UPGRADE.TXT&lt;/tt&gt;  --  you can find this file on any Slackware mirror.  Note that this is also the only supported method to upgrade from one stable release of Slackware to another.

For keeping up to date on post-release patches added to a stable release of Slackware, you will *usually* be okay to use one of the third party package managers.  You should still read the &lt;tt&gt;ChangeLog.txt&lt;/tt&gt; before doing any upgrades, though, as new packages are occasionally added in /patches when circumstances require it.

For software not included in official Slackware, consider building it yourself or using a SlackBuild script from one of the projects which provides them.

One of the regular Slackware contributors, PiterPUNK, wrote and maintains a third-party package manager that minimizes all of the risks mentioned above.  [http://slackpkg.org Slackpkg] does not support downloading or installing unofficial packages, and it has provisions to install any added packages and uninstall any removed packages as well as the normal install/upgrade/remove routines.

Another third party package manager that promotes good practices is [http://slackroll.sourceforge.net/ SlackRoll] (see [[SlackRoll Tutorial|tutorial]]). Its philosophy is similar to that of Slackpkg but it is not included as part of Slackware. Programmed in Python, it is faster, has more features and detects more events from Slackware -current. However, the initial setup and workflow are a bit more complex.

= See Also =

* &lt;tt&gt;pkgtool(8)&lt;/tt&gt; -- man 8 pkgtool
* &lt;tt&gt;installpkg(8)&lt;/tt&gt; -- man 8 installpkg
* &lt;tt&gt;removepkg(8)&lt;/tt&gt; -- man 8 removepkg
* &lt;tt&gt;upgradepkg(8)&lt;/tt&gt; -- man 8 upgradepkg
* &lt;tt&gt;makepkg(8)&lt;/tt&gt; -- man 8 makepkg
* &lt;tt&gt;explodepkg(8)&lt;/tt&gt; -- man 8 explodepkg


= TODO =

* Add links to other wiki pages that are related to this topic (add to "See Also" above)
* Add hyperlinks to slapt-get, swaret, and other projects mentioned on this page
* Others?

[[Category:Information]]
[[Category:Tutorials]]</text>
    <sha1>dc842fb2ec0f25c90d0d0f5e2fc4dbb5195ca29e</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>Reinstalling Lilo</title>
  <ns>0</ns>
  <id>140</id>
  <revision>
    <id>3186</id>
    <parentid>166</parentid>
    <timestamp>2018-10-28T13:27:25Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="861" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

mount /dev/sda1 /mnt

mount -o bind /dev /mnt/dev

mount -o bind /proc /mnt/proc

mount -o bind /sys /mnt/sys

'''Chrooting'''

Once the partition is mounted, we can chroot to it:

chroot /mnt /bin/bash

now simply run "liloconfig" and follow the prompts</text>
    <sha1>01f81919a36c947981a9ba4c33b48175b1ebdbfa</sha1>
  </revision>
  <revision>
    <id>3187</id>
    <parentid>3186</parentid>
    <timestamp>2018-10-28T13:28:40Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="858" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

mount /dev/sda1 /mnt

mount -o bind /dev /mnt/dev

mount -o bind /proc /mnt/proc

mount -o bind /sys /mnt/sys

'''Chrooting'''

Once everything is mounted, we can chroot to it:

chroot /mnt /bin/bash

now simply run "liloconfig" and follow the prompts</text>
    <sha1>c5d195ee09c490c667d9d6c98733c74fb4a91f79</sha1>
  </revision>
  <revision>
    <id>3188</id>
    <parentid>3187</parentid>
    <timestamp>2018-10-28T13:40:50Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="858" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

mount /dev/sdX1 /mnt

mount -o bind /dev /mnt/dev

mount -o bind /proc /mnt/proc

mount -o bind /sys /mnt/sys

'''Chrooting'''

Once everything is mounted, we can chroot to it:

chroot /mnt /bin/bash

now simply run "liloconfig" and follow the prompts</text>
    <sha1>c9b2a98ff28d257c19f7a01c0a929ec2a4b49b8f</sha1>
  </revision>
  <revision>
    <id>3189</id>
    <parentid>3188</parentid>
    <timestamp>2018-10-28T13:41:59Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="898" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

mount /dev/sdX1 /mnt   (where /dev/sdx1 is your / partition)

mount -o bind /dev /mnt/dev

mount -o bind /proc /mnt/proc

mount -o bind /sys /mnt/sys

'''Chrooting'''

Once everything is mounted, we can chroot to it:

chroot /mnt /bin/bash

now simply run "liloconfig" and follow the prompts</text>
    <sha1>9d6f052724ad8c5d0f918ab088a3cb3988720511</sha1>
  </revision>
  <revision>
    <id>3190</id>
    <parentid>3189</parentid>
    <timestamp>2018-10-28T13:45:00Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="920" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

''mount /dev/sdX1 /mnt''   (where /dev/sdx1 is your / partition)

''mount -o bind /dev /mnt/dev''

''mount -o bind /proc /mnt/proc''

''mount -o bind /sys /mnt/sys''

'''Chrooting'''

Once everything is mounted, we can chroot to it:

''chroot /mnt /bin/bash''

now simply run ''liloconfig'' and follow the prompts</text>
    <sha1>8f40a645265fcdf9fbea67a7f6a414e95b57a464</sha1>
  </revision>
  <revision>
    <id>3192</id>
    <parentid>3190</parentid>
    <timestamp>2018-10-28T22:22:28Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="945" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

''mount /dev/sdX1 /mnt''   (where /dev/sdx1 is your / partition)

''mount -o bind /dev /mnt/dev''

''mount -o bind /proc /mnt/proc''

''mount -o bind /sys /mnt/sys''

'''Chrooting'''

Once everything is mounted, we can chroot to it:

''chroot /mnt /bin/bash''

now simply run ''liloconfig'' and follow the prompts


[[Category:Tutorials]]</text>
    <sha1>6e8e66f3fd2940eb147f0a812d237a31a7b5017b</sha1>
  </revision>
  <revision>
    <id>3193</id>
    <parentid>3192</parentid>
    <timestamp>2018-10-28T22:57:36Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="950" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

 ''mount /dev/sdX1 /mnt''   (where /dev/sdx1 is your / partition)

 ''mount -o bind /dev /mnt/dev''

 ''mount -o bind /proc /mnt/proc''

 ''mount -o bind /sys /mnt/sys''

'''Chrooting'''

Once everything is mounted, we can chroot to it:

 ''chroot /mnt /bin/bash''

now simply run ''liloconfig'' and follow the prompts


[[Category:Tutorials]]</text>
    <sha1>09cc04e3ae26214f7b5673c541ffd1f727fef382</sha1>
  </revision>
  <revision>
    <id>3194</id>
    <parentid>3193</parentid>
    <timestamp>2018-10-28T22:58:16Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="947" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

 ''mount /dev/sdX1 /mnt''   (where /dev/sdx1 is your / partition)
 ''mount -o bind /dev /mnt/dev''
 ''mount -o bind /proc /mnt/proc''
 ''mount -o bind /sys /mnt/sys''

'''Chrooting'''

Once everything is mounted, we can chroot to it:

 ''chroot /mnt /bin/bash''

now simply run ''liloconfig'' and follow the prompts


[[Category:Tutorials]]</text>
    <sha1>5a62b84ae39c5d74413646a9102e59df0b4d739c</sha1>
  </revision>
  <revision>
    <id>3195</id>
    <parentid>3194</parentid>
    <timestamp>2018-10-28T23:21:24Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1392" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

'''Chrooting'''

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

 ''mount /dev/sdX1 /mnt''   (where /dev/sdx1 is your / partition)
 ''mount -o bind /dev /mnt/dev''
 ''mount -o bind /proc /mnt/proc''
 ''mount -o bind /sys /mnt/sys''
 
'''Chrooting'''

Once everything is mounted, we can chroot to it:

 ''chroot /mnt /bin/bash''

now simply run ''liloconfig'' and follow the prompts


'''Booting your system from the installation media'''

often times you can boot your system from the installation media as well
simply boot the installation media and on the very first page are the following instructions


 In a pinch, you can boot your system from here with a command like:
 boot: huge.s root=/dev/sda1 rdinit= ro 
 In the example above, /dev/sda1 is the / Linux partition.

once booted run ''liloconfig''


[[Category:Tutorials]]</text>
    <sha1>0df70bb3ac5e481702878229343b8a348d8ef59e</sha1>
  </revision>
  <revision>
    <id>3196</id>
    <parentid>3195</parentid>
    <timestamp>2018-10-28T23:22:14Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1396" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

'''Chroot method'''

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

 ''mount /dev/sdX1 /mnt''   (where /dev/sdx1 is your / partition)
 ''mount -o bind /dev /mnt/dev''
 ''mount -o bind /proc /mnt/proc''
 ''mount -o bind /sys /mnt/sys''
 
'''Chrooting'''

Once everything is mounted, we can chroot to it:

 ''chroot /mnt /bin/bash''

now simply run ''liloconfig'' and follow the prompts


'''Booting your system from the installation media'''

often times you can boot your system from the installation media as well
simply boot the installation media and on the very first page are the following instructions


 In a pinch, you can boot your system from here with a command like:
 boot: huge.s root=/dev/sda1 rdinit= ro 
 In the example above, /dev/sda1 is the / Linux partition.

once booted run ''liloconfig''


[[Category:Tutorials]]</text>
    <sha1>b429bc2ebaa55684d6af3296f43be75388f7d99c</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>CPU Frequency Scaling</title>
  <ns>0</ns>
  <id>10</id>
  <revision>
    <id>3191</id>
    <parentid>13</parentid>
    <timestamp>2018-10-28T22:10:03Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1145" xml:space="preserve">The CPU frequency scaling feature present in modern computers allows lowering and increasing the processor speed dynamically in runtime so as to save energy while having the possibility of increasing the performance and power consumption if needed. Activating CPU frequency scaling under Slackware is very easy, and requires loading a minimum of two kernel modules and running a simple command. On the one hand, you need to load a specific CPU driver that will activate the frequency scaling feature in your platform. Second, you need to choose a CPU frequency scaling governor, a module that will decide how and when to change the internal processor speed. There are governors to always run at full speed, governors to always run at low speed, governors to increase and decrease the speed based on the CPU load, etc.


= Find available governors  =

 cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors 


= Setting a governor =

 edit ''/etc/default/cpufreq''

= Applying the governor =

 ''/etc/rc.d/rc.cpufreq'' should already be executable
 make sure its running 
 ''/etc.rc.d/rc.cpufreq restart''


[[Category:Tutorials]]</text>
    <sha1>c62e658832e8d92aff111035ca4614d3cc9ce929</sha1>
  </revision>
  <revision>
    <id>3197</id>
    <parentid>3191</parentid>
    <timestamp>2018-10-29T13:11:32Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2521" xml:space="preserve">The CPU frequency scaling feature present in modern computers allows lowering and increasing the processor speed dynamically in runtime so as to save energy while having the possibility of increasing the performance and power consumption if needed. Activating CPU frequency scaling under Slackware is very easy, and requires loading a minimum of two kernel modules and running a simple command. On the one hand, you need to load a specific CPU driver that will activate the frequency scaling feature in your platform. Second, you need to choose a CPU frequency scaling governor, a module that will decide how and when to change the internal processor speed. There are governors to always run at full speed, governors to always run at low speed, governors to increase and decrease the speed based on the CPU load, etc.


= Find available governors  =

 cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors 


= Setting a governor =

 edit ''/etc/default/cpufreq''

= Applying the governor =

 ''/etc/rc.d/rc.cpufreq'' should already be executable
 make sure its running 
 ''/etc.rc.d/rc.cpufreq restart''


= Governor types = 

'''Performance'''

 The CPUfreq governor "performance" sets the CPU statically to the
 highest frequency within the borders of scaling_min_freq and
 scaling_max_freq.


'''Powersave'''

 The CPUfreq governor "powersave" sets the CPU statically to the
 lowest frequency within the borders of scaling_min_freq and
 scaling_max_freq.


'''Userspace'''


 The CPUfreq governor "userspace" allows the user, or any userspace
 program running with UID "root", to set the CPU to a specific frequency
 by making a sysfs file "scaling_setspeed" available in the CPU-device
 directory.


'''Ondemand'''


 The CPUfreq governor "ondemand" sets the CPU frequency depending on the
 current system load. Load estimation is triggered by the scheduler
 through the update_util_data-&gt;func hook; when triggered, cpufreq checks
 the CPU-usage statistics over the last period and the governor sets the
 CPU accordingly.  The CPU must have the capability to switch the
 frequency very quickly.


'''Conservative'''


 The CPUfreq governor "conservative", much like the "ondemand"
 governor, sets the CPU frequency depending on the current usage.  It
 differs in behaviour in that it gracefully increases and decreases the
 CPU speed rather than jumping to max speed the moment there is any load
 on the CPU. This behaviour is more suitable in a battery powered
 environment.


[[Category:Tutorials]]</text>
    <sha1>bb3f0742f72827ba693a7e5e13b6201fcace3030</sha1>
  </revision>
  <revision>
    <id>3198</id>
    <parentid>3197</parentid>
    <timestamp>2018-10-29T13:31:02Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2518" xml:space="preserve">The CPU frequency scaling feature present in modern computers allows lowering and increasing the processor speed dynamically in runtime so as to save energy while having the possibility of increasing the performance and power consumption if needed. Activating CPU frequency scaling under Slackware is very easy, and requires loading a minimum of two kernel modules and running a simple command. On the one hand, you need to load a specific CPU driver that will activate the frequency scaling feature in your platform. Second, you need to choose a CPU frequency scaling governor, a module that will decide how and when to change the internal processor speed. There are governors to always run at full speed, governors to always run at low speed, governors to increase and decrease the speed based on the CPU load, etc.


= Find available governors  =

 cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors 


= Setting a governor =

 edit ''/etc/default/cpufreq''

= Applying the governor =

 ''/etc/rc.d/rc.cpufreq'' should already be executable
 make sure its running 
 ''/etc.rc.d/rc.cpufreq restart''


= Governor types = 

'''Performance'''

 The CPUfreq governor "performance" sets the CPU statically to the
 highest frequency within the borders of scaling_min_freq and
 scaling_max_freq.


'''Powersave'''

 The CPUfreq governor "powersave" sets the CPU statically to the
 lowest frequency within the borders of scaling_min_freq and
 scaling_max_freq.


'''Userspace'''

 The CPUfreq governor "userspace" allows the user, or any userspace
 program running with UID "root", to set the CPU to a specific frequency
 by making a sysfs file "scaling_setspeed" available in the CPU-device
 directory.


'''Ondemand'''

 The CPUfreq governor "ondemand" sets the CPU frequency depending on the
 current system load. Load estimation is triggered by the scheduler
 through the update_util_data-&gt;func hook; when triggered, cpufreq checks
 the CPU-usage statistics over the last period and the governor sets the
 CPU accordingly.  The CPU must have the capability to switch the
 frequency very quickly.


'''Conservative'''

 The CPUfreq governor "conservative", much like the "ondemand"
 governor, sets the CPU frequency depending on the current usage.  It
 differs in behaviour in that it gracefully increases and decreases the
 CPU speed rather than jumping to max speed the moment there is any load
 on the CPU. This behaviour is more suitable in a battery powered
 environment.


[[Category:Tutorials]]</text>
    <sha1>6a8863a77b81d9ab3f09bd5d43effbc7b4d5f92b</sha1>
  </revision>
</page>
<page arvcontinue="20170717080124|1013">
  <title>LVM/Luks Encryption</title>
  <ns>0</ns>
  <id>328</id>
  <revision>
    <id>3199</id>
    <timestamp>2018-11-05T15:20:43Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>Created page with "This article assumes that this will be the only operating system installed. Also wherever you see '''''sdx2''''' it is referring to the single large partition (probably /dev/s..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8066" xml:space="preserve">This article assumes that this will be the only operating system installed. Also wherever you see '''''sdx2''''' it is referring to the single large partition (probably /dev/sda2) made in the first step. It also assumes you know your way around the slackware installer.
Swap space setup is documented here but note its only needed if you plan to hibernate e.g. a laptop.

'''Partitioning'''

Boot the installer. Login as '''''root''''' and run 

 cfdisk

What you’re doing here is setting up the partitions. Essentially, we’re dividing up the hard drive into a few logical partitions so that certain things can run in certain places, and not be affected by others. In order to create a bootable encrypted drive there needs to be a small partition that is not encrypted, it’s unencrypted and readable, so the computer can use it to figure out how to start the operating system.

The first partition to make is a boot partition. Delete every other existing partition (if there are any) and write (again, assuming this will be your only OS). Next, select new and create a primary partition that is relatively small, I usually do 1G (which is rather large but i often juggle multiple kernels). Select ''Beginning'', which puts the partition at the front of the disk. DO NOT forget to make the first partition bootable, otherwise the installation won’t know to use this partition to install the boot scripts and such.

Next, create another partition with the remaining space. Follow the same steps, except do not make it bootable and use the rest of the available space. Just hit enter when it asks how much space to use. After you’ve done this, make sure you go down and select '''''write''''' to ensure the changes are made. Then exit cfdisk.

It's a good idea for you to rewrite the entire large partition with random data. This is so computer forensics folks cannot determine where encryption starts and stops, making it harder to find out a way to circumvent the encryption and stuff. To do this, run

 dd if=/dev/urandom of=/dev/sdx2

'''NOTE***'''  this can take quite some time.

'''LVM / Luks Config'''

LVM or Logical Volume Manager is used here to configure volumes inside of the large partition set up earlier (sdx2). LVM makes it easy to separate things internally and keep it all encrypted as one partition. 

 cryptsetup -s 512 -y luksFormat /dev/sdx2

Type '''''YES''''', then decide on a password and type it. Be careful, later on if you put stuff on the drive and you forget your password, it’s gone forever. Such is the nature of encryption. 

Basically this is setting up luks encryption on /dev/sdx2.

 cryptsetup luksOpen /dev/sdx2 slackcrypt

pvcreate is a linux command used to initialize physical volumes for use by logical volume management (lvm) later.

 pvcreate /dev/mapper/slackcrypt 

This creates the volume group “cryptvg”.

 vgcreate cryptvg /dev/mapper/slackcrypt

Create three internal logical volumes, '''''root''''', '''''home''''', and '''''swap'''''. If you have a unique setup and prefer it a different way, just follow the same steps and size them how you want. the sizes used are example only

 lvcreate -L 20G -n root cryptvg

 lvcreate -L 2G -n swap cryptvg

 lvcreate -l 100%FREE -n home cryptvg


These will be your '''''/root''''', '''''/home''''', and '''''/swap''''' “partitions”. You can adjust the sizes to whatever you want them to be. I use a pretty large amount of space in root because I have run out of space installing tons of programs before, but I’ve also used tiny root partitions on machines where I didn’t plan on installing much. It really depends, but if you have the extra space I’d do like 20+ just to be on the safe side. The home directory gets everything that’s not allocated to swap or root.

Next thing we’ve got to do is make sure some nodes get set so everything knows where things are and what not

 vgscan --mknodes

 vgchange -ay

make sure the slackware installer can detect the swap partition

 mkswap /dev/cryptvg/swap

'''Slack Setup and Installation'''

Run the slackware installer

 setup 

the installer will walk you through it from here. it should auto-detect the swap partition we designated

Selecting '''''root''''' partition

Make sure you select /dev/cryptvg/root here, because that’ll be your LVM root partition. Pick whichever file-system you like. After that it should bring you back to the same screen. It’s important to designate your other partitions here.

Select /dev/cryptvg/home and format it.

Next designate boot, which is essential, otherwise your machine will not work properly. Select '''''/dev/sdx1/''''' (probably /dev/sda1), format it, and type ''/boot''.
Now simply install slackware as you normally would until you get to 

'''Install LILO'''

To install the bootloader Lilo select '''''expert''''', then begin. Ignore the optional LILO Append, you probably don’t need to do anything with that.
Select ''mbr'', hit confirm when it asks you to confirm /dev/sdx (probably /dev/sda), and keep going through the options until you’re back at the screen where you selected “begin”.

Now you have to select '''''Linux: Add a linux partition'''''... and select /dev/cryptvg/root. (/dev/cryptvg/root, NOT /boot).

Once that’s been selected, install lilo. . Continue with the installation until you reach a screen listing slackwares installation steps.

Eit the installer and select '''''No''''' to get dropped to a command prompt.

'''Creating an initrd'''

Now we have to fix lilo because of our encryption scheme.

chroot /mnt 

The simple explanation for this command is that you basically just entered the installed system, which is mounted at /mnt. Now you can work on things that are installed on the system. 

The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. to create an initrd run

 /usr/share/mkinitrd/mkinitrd_command_generator.sh

it will look similar to this

 mkinitrd -c -k 4.19.0 -f ext4 -r /dev/cryptvg/root -m usb-storage:xhci-
 hcd:usbhid:hid_generic:mbcache:jbd2:ext4 -C /dev/sda2 -h /dev/cryptvg/swap 
 -L -u -o /boot/initrd.gz

Run the resulting command (yours will surely be different  from the example). This will write an image to /boot/initrd.gz in your system which we will use for booting. The '''''-h /dev/cryptvg/swap''''' has been added to enable hibernation. it was not part of the resulting mikinitrd_command_generator.sh command

If you need to know what kernel you just installed try

 uname -a

'''Fixing LILO'''

Next, you have to edit lilo’s configuration file and point it to the correct places so it knows what to boot with. Don’t forget the initrd line here.
(use your preferred editor)

 vim /etc/lilo.conf

Edit the pertinent parts to look like this:

image = /boot/vmlinuz-generic-4.19.0
 initrd = /boot/initrd.gz
 root = /dev/cryptvg/root
 label = Slackware
 read-only  # Partitions should be mounted read-only for checking

Above that, there’s an “append” line. Edit it to look something like this:

 append = "vt.default_utf8=0 resume=/dev/cryptvg/swap"

Of course, substituting your kernel where necessary. You can check what you need to put for “image = ” by going to /boot and checking which generic kernel you want to use to boot. Save your changes and exit.

Run

 lilo -v

You may get an error or two from lilo, but you can usually ignore these.
type 
 exit
to leave the chroot and then
 reboot


If something went wrong, you probably configured something incorrectly along the way. To get back into your system and repair lilo or some other part of the system, follow these steps to chroot from installation media


 cryptsetup luksOpen /dev/sdx2 slackcrypt
 vgscan --mknodes
 vgchange -ay
 lvscan 
 mount /dev/cryptvg/root /mnt
 mount /dev/cryptvg/home /mnt/home
 mount /dev/sdx1 /mnt/boot
 mount -o bind /proc /mnt/proc
 mount -o bind /sys /mnt/sys
 mount -o bind /dev /mnt/dev
 chroot /mnt</text>
    <sha1>ed5b41804b77115f8b5777ea967ff27544c430eb</sha1>
  </revision>
  <revision>
    <id>3200</id>
    <parentid>3199</parentid>
    <timestamp>2018-11-05T15:22:23Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8091" xml:space="preserve">[[Category:Tutorials]]


This article assumes that this will be the only operating system installed. Also wherever you see '''''sdx2''''' it is referring to the single large partition (probably /dev/sda2) made in the first step. It also assumes you know your way around the slackware installer.
Swap space setup is documented here but note its only needed if you plan to hibernate e.g. a laptop.

'''Partitioning'''

Boot the installer. Login as '''''root''''' and run 

 cfdisk

What you’re doing here is setting up the partitions. Essentially, we’re dividing up the hard drive into a few logical partitions so that certain things can run in certain places, and not be affected by others. In order to create a bootable encrypted drive there needs to be a small partition that is not encrypted, it’s unencrypted and readable, so the computer can use it to figure out how to start the operating system.

The first partition to make is a boot partition. Delete every other existing partition (if there are any) and write (again, assuming this will be your only OS). Next, select new and create a primary partition that is relatively small, I usually do 1G (which is rather large but i often juggle multiple kernels). Select ''Beginning'', which puts the partition at the front of the disk. DO NOT forget to make the first partition bootable, otherwise the installation won’t know to use this partition to install the boot scripts and such.

Next, create another partition with the remaining space. Follow the same steps, except do not make it bootable and use the rest of the available space. Just hit enter when it asks how much space to use. After you’ve done this, make sure you go down and select '''''write''''' to ensure the changes are made. Then exit cfdisk.

It's a good idea for you to rewrite the entire large partition with random data. This is so computer forensics folks cannot determine where encryption starts and stops, making it harder to find out a way to circumvent the encryption and stuff. To do this, run

 dd if=/dev/urandom of=/dev/sdx2

'''NOTE***'''  this can take quite some time.

'''LVM / Luks Config'''

LVM or Logical Volume Manager is used here to configure volumes inside of the large partition set up earlier (sdx2). LVM makes it easy to separate things internally and keep it all encrypted as one partition. 

 cryptsetup -s 512 -y luksFormat /dev/sdx2

Type '''''YES''''', then decide on a password and type it. Be careful, later on if you put stuff on the drive and you forget your password, it’s gone forever. Such is the nature of encryption. 

Basically this is setting up luks encryption on /dev/sdx2.

 cryptsetup luksOpen /dev/sdx2 slackcrypt

pvcreate is a linux command used to initialize physical volumes for use by logical volume management (lvm) later.

 pvcreate /dev/mapper/slackcrypt 

This creates the volume group “cryptvg”.

 vgcreate cryptvg /dev/mapper/slackcrypt

Create three internal logical volumes, '''''root''''', '''''home''''', and '''''swap'''''. If you have a unique setup and prefer it a different way, just follow the same steps and size them how you want. the sizes used are example only

 lvcreate -L 20G -n root cryptvg

 lvcreate -L 2G -n swap cryptvg

 lvcreate -l 100%FREE -n home cryptvg


These will be your '''''/root''''', '''''/home''''', and '''''/swap''''' “partitions”. You can adjust the sizes to whatever you want them to be. I use a pretty large amount of space in root because I have run out of space installing tons of programs before, but I’ve also used tiny root partitions on machines where I didn’t plan on installing much. It really depends, but if you have the extra space I’d do like 20+ just to be on the safe side. The home directory gets everything that’s not allocated to swap or root.

Next thing we’ve got to do is make sure some nodes get set so everything knows where things are and what not

 vgscan --mknodes

 vgchange -ay

make sure the slackware installer can detect the swap partition

 mkswap /dev/cryptvg/swap

'''Slack Setup and Installation'''

Run the slackware installer

 setup 

the installer will walk you through it from here. it should auto-detect the swap partition we designated

Selecting '''''root''''' partition

Make sure you select /dev/cryptvg/root here, because that’ll be your LVM root partition. Pick whichever file-system you like. After that it should bring you back to the same screen. It’s important to designate your other partitions here.

Select /dev/cryptvg/home and format it.

Next designate boot, which is essential, otherwise your machine will not work properly. Select '''''/dev/sdx1/''''' (probably /dev/sda1), format it, and type ''/boot''.
Now simply install slackware as you normally would until you get to 

'''Install LILO'''

To install the bootloader Lilo select '''''expert''''', then begin. Ignore the optional LILO Append, you probably don’t need to do anything with that.
Select ''mbr'', hit confirm when it asks you to confirm /dev/sdx (probably /dev/sda), and keep going through the options until you’re back at the screen where you selected “begin”.

Now you have to select '''''Linux: Add a linux partition'''''... and select /dev/cryptvg/root. (/dev/cryptvg/root, NOT /boot).

Once that’s been selected, install lilo. . Continue with the installation until you reach a screen listing slackwares installation steps.

Eit the installer and select '''''No''''' to get dropped to a command prompt.

'''Creating an initrd'''

Now we have to fix lilo because of our encryption scheme.

chroot /mnt 

The simple explanation for this command is that you basically just entered the installed system, which is mounted at /mnt. Now you can work on things that are installed on the system. 

The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. to create an initrd run

 /usr/share/mkinitrd/mkinitrd_command_generator.sh

it will look similar to this

 mkinitrd -c -k 4.19.0 -f ext4 -r /dev/cryptvg/root -m usb-storage:xhci-
 hcd:usbhid:hid_generic:mbcache:jbd2:ext4 -C /dev/sda2 -h /dev/cryptvg/swap 
 -L -u -o /boot/initrd.gz

Run the resulting command (yours will surely be different  from the example). This will write an image to /boot/initrd.gz in your system which we will use for booting. The '''''-h /dev/cryptvg/swap''''' has been added to enable hibernation. it was not part of the resulting mikinitrd_command_generator.sh command

If you need to know what kernel you just installed try

 uname -a

'''Fixing LILO'''

Next, you have to edit lilo’s configuration file and point it to the correct places so it knows what to boot with. Don’t forget the initrd line here.
(use your preferred editor)

 vim /etc/lilo.conf

Edit the pertinent parts to look like this:

image = /boot/vmlinuz-generic-4.19.0
 initrd = /boot/initrd.gz
 root = /dev/cryptvg/root
 label = Slackware
 read-only  # Partitions should be mounted read-only for checking

Above that, there’s an “append” line. Edit it to look something like this:

 append = "vt.default_utf8=0 resume=/dev/cryptvg/swap"

Of course, substituting your kernel where necessary. You can check what you need to put for “image = ” by going to /boot and checking which generic kernel you want to use to boot. Save your changes and exit.

Run

 lilo -v

You may get an error or two from lilo, but you can usually ignore these.
type 
 exit
to leave the chroot and then
 reboot


If something went wrong, you probably configured something incorrectly along the way. To get back into your system and repair lilo or some other part of the system, follow these steps to chroot from installation media


 cryptsetup luksOpen /dev/sdx2 slackcrypt
 vgscan --mknodes
 vgchange -ay
 lvscan 
 mount /dev/cryptvg/root /mnt
 mount /dev/cryptvg/home /mnt/home
 mount /dev/sdx1 /mnt/boot
 mount -o bind /proc /mnt/proc
 mount -o bind /sys /mnt/sys
 mount -o bind /dev /mnt/dev
 chroot /mnt</text>
    <sha1>dedec3acaf5a8fd4c3ddb35a34d14535f670dcda</sha1>
  </revision>
  <revision>
    <id>3201</id>
    <parentid>3200</parentid>
    <timestamp>2018-11-05T19:23:10Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8765" xml:space="preserve">[[Category:Tutorials]]

'''LVM'''
LVM is a tool for logical volume management which includes allocating disks, striping, mirroring and resizing logical volumes. With LVM, a hard drive or set of hard drives is allocated to one or more physical volumes. LVM physical volumes can be placed on other block devices which might span two or more disks.

'''LUKS'''

LUKS is the standard for Linux hard disk encryption. By providing a standard on-disk-format, it does not
only facilitate compatibility among distributions, but also provides secure management of multiple user passwords.
LUKS stores all necessary setup information in the partition header, enabling to transport or migrate data seamlessly.

This article assumes that this will be the only operating system installed. Also wherever you see '''''sdx2''''' it is referring to the single large partition (probably /dev/sda2) made in the first step. It also assumes you know your way around the slackware installer.
Swap space setup is documented here but note its only needed if you plan to hibernate e.g. a laptop.

'''Partitioning'''

Boot the installer. Login as '''''root''''' and run 

 cfdisk

What you’re doing here is setting up the partitions. Essentially, we’re dividing up the hard drive into a few logical partitions so that certain things can run in certain places, and not be affected by others. In order to create a bootable encrypted drive there needs to be a small partition that is not encrypted, it’s unencrypted and readable, so the computer can use it to figure out how to start the operating system.

The first partition to make is a boot partition. Delete every other existing partition (if there are any) and write (again, assuming this will be your only OS). Next, select new and create a primary partition that is relatively small, I usually do 1G (which is rather large but i often juggle multiple kernels). Select ''Beginning'', which puts the partition at the front of the disk. DO NOT forget to make the first partition bootable, otherwise the installation won’t know to use this partition to install the boot scripts and such.

Next, create another partition with the remaining space. Follow the same steps, except do not make it bootable and use the rest of the available space. Just hit enter when it asks how much space to use. After you’ve done this, make sure you go down and select '''''write''''' to ensure the changes are made. Then exit cfdisk.

It's a good idea for you to rewrite the entire large partition with random data. This is so computer forensics folks cannot determine where encryption starts and stops, making it harder to find out a way to circumvent the encryption and stuff. To do this, run

 dd if=/dev/urandom of=/dev/sdx2

'''NOTE***'''  this can take quite some time.

'''LVM / Luks Config'''

LVM or Logical Volume Manager is used here to configure volumes inside of the large partition set up earlier (sdx2). LVM makes it easy to separate things internally and keep it all encrypted as one partition. 

 cryptsetup -s 512 -y luksFormat /dev/sdx2

Type '''''YES''''', then decide on a password and type it. Be careful, later on if you put stuff on the drive and you forget your password, it’s gone forever. Such is the nature of encryption. 

Basically this is setting up luks encryption on /dev/sdx2.

 cryptsetup luksOpen /dev/sdx2 slackcrypt

pvcreate is a linux command used to initialize physical volumes for use by logical volume management (lvm) later.

 pvcreate /dev/mapper/slackcrypt 

This creates the volume group “cryptvg”.

 vgcreate cryptvg /dev/mapper/slackcrypt

Create three internal logical volumes, '''''root''''', '''''home''''', and '''''swap'''''. If you have a unique setup and prefer it a different way, just follow the same steps and size them how you want. the sizes used are example only

 lvcreate -L 20G -n root cryptvg

 lvcreate -L 2G -n swap cryptvg

 lvcreate -l 100%FREE -n home cryptvg


These will be your '''''/root''''', '''''/home''''', and '''''/swap''''' “partitions”. You can adjust the sizes to whatever you want them to be. I use a pretty large amount of space in root because I have run out of space installing tons of programs before, but I’ve also used tiny root partitions on machines where I didn’t plan on installing much. It really depends, but if you have the extra space I’d do like 20+ just to be on the safe side. The home directory gets everything that’s not allocated to swap or root.

Next thing we’ve got to do is make sure some nodes get set so everything knows where things are and what not

 vgscan --mknodes

 vgchange -ay

make sure the slackware installer can detect the swap partition

 mkswap /dev/cryptvg/swap

'''Slack Setup and Installation'''

Run the slackware installer

 setup 

the installer will walk you through it from here. it should auto-detect the swap partition we designated

Selecting '''''root''''' partition

Make sure you select /dev/cryptvg/root here, because that’ll be your LVM root partition. Pick whichever file-system you like. After that it should bring you back to the same screen. It’s important to designate your other partitions here.

Select /dev/cryptvg/home and format it.

Next designate boot, which is essential, otherwise your machine will not work properly. Select '''''/dev/sdx1/''''' (probably /dev/sda1), format it, and type ''/boot''.
Now simply install slackware as you normally would until you get to 

'''Install LILO'''

To install the bootloader Lilo select '''''expert''''', then begin. Ignore the optional LILO Append, you probably don’t need to do anything with that.
Select ''mbr'', hit confirm when it asks you to confirm /dev/sdx (probably /dev/sda), and keep going through the options until you’re back at the screen where you selected “begin”.

Now you have to select '''''Linux: Add a linux partition'''''... and select /dev/cryptvg/root. (/dev/cryptvg/root, NOT /boot).

Once that’s been selected, install lilo. . Continue with the installation until you reach a screen listing slackwares installation steps.

Eit the installer and select '''''No''''' to get dropped to a command prompt.

'''Creating an initrd'''

Now we have to fix lilo because of our encryption scheme.

chroot /mnt 

The simple explanation for this command is that you basically just entered the installed system, which is mounted at /mnt. Now you can work on things that are installed on the system. 

The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. to create an initrd run

 /usr/share/mkinitrd/mkinitrd_command_generator.sh

it will look similar to this

 mkinitrd -c -k 4.19.0 -f ext4 -r /dev/cryptvg/root -m usb-storage:xhci-
 hcd:usbhid:hid_generic:mbcache:jbd2:ext4 -C /dev/sda2 -h /dev/cryptvg/swap 
 -L -u -o /boot/initrd.gz

Run the resulting command (yours will surely be different  from the example). This will write an image to /boot/initrd.gz in your system which we will use for booting. The '''''-h /dev/cryptvg/swap''''' has been added to enable hibernation. it was not part of the resulting mikinitrd_command_generator.sh command

If you need to know what kernel you just installed try

 uname -a

'''Fixing LILO'''

Next, you have to edit lilo’s configuration file and point it to the correct places so it knows what to boot with. Don’t forget the initrd line here.
(use your preferred editor)

 vim /etc/lilo.conf

Edit the pertinent parts to look like this:

image = /boot/vmlinuz-generic-4.19.0
 initrd = /boot/initrd.gz
 root = /dev/cryptvg/root
 label = Slackware
 read-only  # Partitions should be mounted read-only for checking

Above that, there’s an “append” line. Edit it to look something like this:

 append = "vt.default_utf8=0 resume=/dev/cryptvg/swap"

Of course, substituting your kernel where necessary. You can check what you need to put for “image = ” by going to /boot and checking which generic kernel you want to use to boot. Save your changes and exit.

Run

 lilo -v

You may get an error or two from lilo, but you can usually ignore these.
type 
 exit
to leave the chroot and then
 reboot


If something went wrong, you probably configured something incorrectly along the way. To get back into your system and repair lilo or some other part of the system, follow these steps to chroot from installation media


 cryptsetup luksOpen /dev/sdx2 slackcrypt
 vgscan --mknodes
 vgchange -ay
 lvscan 
 mount /dev/cryptvg/root /mnt
 mount /dev/cryptvg/home /mnt/home
 mount /dev/sdx1 /mnt/boot
 mount -o bind /proc /mnt/proc
 mount -o bind /sys /mnt/sys
 mount -o bind /dev /mnt/dev
 chroot /mnt</text>
    <sha1>cad012f744c9c498f3451206038565caeb533bb7</sha1>
  </revision>
  <revision>
    <id>3202</id>
    <parentid>3201</parentid>
    <timestamp>2018-11-05T19:23:30Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8766" xml:space="preserve">[[Category:Tutorials]]

'''LVM'''

LVM is a tool for logical volume management which includes allocating disks, striping, mirroring and resizing logical volumes. With LVM, a hard drive or set of hard drives is allocated to one or more physical volumes. LVM physical volumes can be placed on other block devices which might span two or more disks.

'''LUKS'''

LUKS is the standard for Linux hard disk encryption. By providing a standard on-disk-format, it does not
only facilitate compatibility among distributions, but also provides secure management of multiple user passwords.
LUKS stores all necessary setup information in the partition header, enabling to transport or migrate data seamlessly.

This article assumes that this will be the only operating system installed. Also wherever you see '''''sdx2''''' it is referring to the single large partition (probably /dev/sda2) made in the first step. It also assumes you know your way around the slackware installer.
Swap space setup is documented here but note its only needed if you plan to hibernate e.g. a laptop.

'''Partitioning'''

Boot the installer. Login as '''''root''''' and run 

 cfdisk

What you’re doing here is setting up the partitions. Essentially, we’re dividing up the hard drive into a few logical partitions so that certain things can run in certain places, and not be affected by others. In order to create a bootable encrypted drive there needs to be a small partition that is not encrypted, it’s unencrypted and readable, so the computer can use it to figure out how to start the operating system.

The first partition to make is a boot partition. Delete every other existing partition (if there are any) and write (again, assuming this will be your only OS). Next, select new and create a primary partition that is relatively small, I usually do 1G (which is rather large but i often juggle multiple kernels). Select ''Beginning'', which puts the partition at the front of the disk. DO NOT forget to make the first partition bootable, otherwise the installation won’t know to use this partition to install the boot scripts and such.

Next, create another partition with the remaining space. Follow the same steps, except do not make it bootable and use the rest of the available space. Just hit enter when it asks how much space to use. After you’ve done this, make sure you go down and select '''''write''''' to ensure the changes are made. Then exit cfdisk.

It's a good idea for you to rewrite the entire large partition with random data. This is so computer forensics folks cannot determine where encryption starts and stops, making it harder to find out a way to circumvent the encryption and stuff. To do this, run

 dd if=/dev/urandom of=/dev/sdx2

'''NOTE***'''  this can take quite some time.

'''LVM / Luks Config'''

LVM or Logical Volume Manager is used here to configure volumes inside of the large partition set up earlier (sdx2). LVM makes it easy to separate things internally and keep it all encrypted as one partition. 

 cryptsetup -s 512 -y luksFormat /dev/sdx2

Type '''''YES''''', then decide on a password and type it. Be careful, later on if you put stuff on the drive and you forget your password, it’s gone forever. Such is the nature of encryption. 

Basically this is setting up luks encryption on /dev/sdx2.

 cryptsetup luksOpen /dev/sdx2 slackcrypt

pvcreate is a linux command used to initialize physical volumes for use by logical volume management (lvm) later.

 pvcreate /dev/mapper/slackcrypt 

This creates the volume group “cryptvg”.

 vgcreate cryptvg /dev/mapper/slackcrypt

Create three internal logical volumes, '''''root''''', '''''home''''', and '''''swap'''''. If you have a unique setup and prefer it a different way, just follow the same steps and size them how you want. the sizes used are example only

 lvcreate -L 20G -n root cryptvg

 lvcreate -L 2G -n swap cryptvg

 lvcreate -l 100%FREE -n home cryptvg


These will be your '''''/root''''', '''''/home''''', and '''''/swap''''' “partitions”. You can adjust the sizes to whatever you want them to be. I use a pretty large amount of space in root because I have run out of space installing tons of programs before, but I’ve also used tiny root partitions on machines where I didn’t plan on installing much. It really depends, but if you have the extra space I’d do like 20+ just to be on the safe side. The home directory gets everything that’s not allocated to swap or root.

Next thing we’ve got to do is make sure some nodes get set so everything knows where things are and what not

 vgscan --mknodes

 vgchange -ay

make sure the slackware installer can detect the swap partition

 mkswap /dev/cryptvg/swap

'''Slack Setup and Installation'''

Run the slackware installer

 setup 

the installer will walk you through it from here. it should auto-detect the swap partition we designated

Selecting '''''root''''' partition

Make sure you select /dev/cryptvg/root here, because that’ll be your LVM root partition. Pick whichever file-system you like. After that it should bring you back to the same screen. It’s important to designate your other partitions here.

Select /dev/cryptvg/home and format it.

Next designate boot, which is essential, otherwise your machine will not work properly. Select '''''/dev/sdx1/''''' (probably /dev/sda1), format it, and type ''/boot''.
Now simply install slackware as you normally would until you get to 

'''Install LILO'''

To install the bootloader Lilo select '''''expert''''', then begin. Ignore the optional LILO Append, you probably don’t need to do anything with that.
Select ''mbr'', hit confirm when it asks you to confirm /dev/sdx (probably /dev/sda), and keep going through the options until you’re back at the screen where you selected “begin”.

Now you have to select '''''Linux: Add a linux partition'''''... and select /dev/cryptvg/root. (/dev/cryptvg/root, NOT /boot).

Once that’s been selected, install lilo. . Continue with the installation until you reach a screen listing slackwares installation steps.

Eit the installer and select '''''No''''' to get dropped to a command prompt.

'''Creating an initrd'''

Now we have to fix lilo because of our encryption scheme.

chroot /mnt 

The simple explanation for this command is that you basically just entered the installed system, which is mounted at /mnt. Now you can work on things that are installed on the system. 

The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. to create an initrd run

 /usr/share/mkinitrd/mkinitrd_command_generator.sh

it will look similar to this

 mkinitrd -c -k 4.19.0 -f ext4 -r /dev/cryptvg/root -m usb-storage:xhci-
 hcd:usbhid:hid_generic:mbcache:jbd2:ext4 -C /dev/sda2 -h /dev/cryptvg/swap 
 -L -u -o /boot/initrd.gz

Run the resulting command (yours will surely be different  from the example). This will write an image to /boot/initrd.gz in your system which we will use for booting. The '''''-h /dev/cryptvg/swap''''' has been added to enable hibernation. it was not part of the resulting mikinitrd_command_generator.sh command

If you need to know what kernel you just installed try

 uname -a

'''Fixing LILO'''

Next, you have to edit lilo’s configuration file and point it to the correct places so it knows what to boot with. Don’t forget the initrd line here.
(use your preferred editor)

 vim /etc/lilo.conf

Edit the pertinent parts to look like this:

image = /boot/vmlinuz-generic-4.19.0
 initrd = /boot/initrd.gz
 root = /dev/cryptvg/root
 label = Slackware
 read-only  # Partitions should be mounted read-only for checking

Above that, there’s an “append” line. Edit it to look something like this:

 append = "vt.default_utf8=0 resume=/dev/cryptvg/swap"

Of course, substituting your kernel where necessary. You can check what you need to put for “image = ” by going to /boot and checking which generic kernel you want to use to boot. Save your changes and exit.

Run

 lilo -v

You may get an error or two from lilo, but you can usually ignore these.
type 
 exit
to leave the chroot and then
 reboot


If something went wrong, you probably configured something incorrectly along the way. To get back into your system and repair lilo or some other part of the system, follow these steps to chroot from installation media


 cryptsetup luksOpen /dev/sdx2 slackcrypt
 vgscan --mknodes
 vgchange -ay
 lvscan 
 mount /dev/cryptvg/root /mnt
 mount /dev/cryptvg/home /mnt/home
 mount /dev/sdx1 /mnt/boot
 mount -o bind /proc /mnt/proc
 mount -o bind /sys /mnt/sys
 mount -o bind /dev /mnt/dev
 chroot /mnt</text>
    <sha1>9fa0de54db4e282b74d320a52961a7d1e689963e</sha1>
  </revision>
  <revision>
    <id>3203</id>
    <parentid>3202</parentid>
    <timestamp>2018-11-05T19:25:22Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8770" xml:space="preserve">[[Category:Tutorials]]

'''LVM'''

LVM is a tool for logical volume management which includes allocating disks, striping, mirroring and resizing logical volumes. With LVM, a hard drive or set of hard drives is allocated to one or more physical volumes. LVM physical volumes can be placed on other block devices which might span two or more disks.

'''LUKS'''

LUKS is the standard for Linux hard disk encryption. By providing a standard on-disk-format, it does not
only facilitate compatibility among distributions, but also provides secure management of multiple user passwords.
LUKS stores all necessary setup information in the partition header, enabling you to transport or migrate data seamlessly.

This article assumes that this will be the only operating system installed. Also wherever you see '''''sdx2''''' it is referring to the single large partition (probably /dev/sda2) made in the first step. It also assumes you know your way around the slackware installer.
Swap space setup is documented here but note its only needed if you plan to hibernate e.g. a laptop.

'''Partitioning'''

Boot the installer. Login as '''''root''''' and run 

 cfdisk

What you’re doing here is setting up the partitions. Essentially, we’re dividing up the hard drive into a few logical partitions so that certain things can run in certain places, and not be affected by others. In order to create a bootable encrypted drive there needs to be a small partition that is not encrypted, it’s unencrypted and readable, so the computer can use it to figure out how to start the operating system.

The first partition to make is a boot partition. Delete every other existing partition (if there are any) and write (again, assuming this will be your only OS). Next, select new and create a primary partition that is relatively small, I usually do 1G (which is rather large but i often juggle multiple kernels). Select ''Beginning'', which puts the partition at the front of the disk. DO NOT forget to make the first partition bootable, otherwise the installation won’t know to use this partition to install the boot scripts and such.

Next, create another partition with the remaining space. Follow the same steps, except do not make it bootable and use the rest of the available space. Just hit enter when it asks how much space to use. After you’ve done this, make sure you go down and select '''''write''''' to ensure the changes are made. Then exit cfdisk.

It's a good idea for you to rewrite the entire large partition with random data. This is so computer forensics folks cannot determine where encryption starts and stops, making it harder to find out a way to circumvent the encryption and stuff. To do this, run

 dd if=/dev/urandom of=/dev/sdx2

'''NOTE***'''  this can take quite some time.

'''LVM / Luks Config'''

LVM or Logical Volume Manager is used here to configure volumes inside of the large partition set up earlier (sdx2). LVM makes it easy to separate things internally and keep it all encrypted as one partition. 

 cryptsetup -s 512 -y luksFormat /dev/sdx2

Type '''''YES''''', then decide on a password and type it. Be careful, later on if you put stuff on the drive and you forget your password, it’s gone forever. Such is the nature of encryption. 

Basically this is setting up luks encryption on /dev/sdx2.

 cryptsetup luksOpen /dev/sdx2 slackcrypt

pvcreate is a linux command used to initialize physical volumes for use by logical volume management (lvm) later.

 pvcreate /dev/mapper/slackcrypt 

This creates the volume group “cryptvg”.

 vgcreate cryptvg /dev/mapper/slackcrypt

Create three internal logical volumes, '''''root''''', '''''home''''', and '''''swap'''''. If you have a unique setup and prefer it a different way, just follow the same steps and size them how you want. the sizes used are example only

 lvcreate -L 20G -n root cryptvg

 lvcreate -L 2G -n swap cryptvg

 lvcreate -l 100%FREE -n home cryptvg


These will be your '''''/root''''', '''''/home''''', and '''''/swap''''' “partitions”. You can adjust the sizes to whatever you want them to be. I use a pretty large amount of space in root because I have run out of space installing tons of programs before, but I’ve also used tiny root partitions on machines where I didn’t plan on installing much. It really depends, but if you have the extra space I’d do like 20+ just to be on the safe side. The home directory gets everything that’s not allocated to swap or root.

Next thing we’ve got to do is make sure some nodes get set so everything knows where things are and what not

 vgscan --mknodes

 vgchange -ay

make sure the slackware installer can detect the swap partition

 mkswap /dev/cryptvg/swap

'''Slack Setup and Installation'''

Run the slackware installer

 setup 

the installer will walk you through it from here. it should auto-detect the swap partition we designated

Selecting '''''root''''' partition

Make sure you select /dev/cryptvg/root here, because that’ll be your LVM root partition. Pick whichever file-system you like. After that it should bring you back to the same screen. It’s important to designate your other partitions here.

Select /dev/cryptvg/home and format it.

Next designate boot, which is essential, otherwise your machine will not work properly. Select '''''/dev/sdx1/''''' (probably /dev/sda1), format it, and type ''/boot''.
Now simply install slackware as you normally would until you get to 

'''Install LILO'''

To install the bootloader Lilo select '''''expert''''', then begin. Ignore the optional LILO Append, you probably don’t need to do anything with that.
Select ''mbr'', hit confirm when it asks you to confirm /dev/sdx (probably /dev/sda), and keep going through the options until you’re back at the screen where you selected “begin”.

Now you have to select '''''Linux: Add a linux partition'''''... and select /dev/cryptvg/root. (/dev/cryptvg/root, NOT /boot).

Once that’s been selected, install lilo. . Continue with the installation until you reach a screen listing slackwares installation steps.

Eit the installer and select '''''No''''' to get dropped to a command prompt.

'''Creating an initrd'''

Now we have to fix lilo because of our encryption scheme.

chroot /mnt 

The simple explanation for this command is that you basically just entered the installed system, which is mounted at /mnt. Now you can work on things that are installed on the system. 

The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. to create an initrd run

 /usr/share/mkinitrd/mkinitrd_command_generator.sh

it will look similar to this

 mkinitrd -c -k 4.19.0 -f ext4 -r /dev/cryptvg/root -m usb-storage:xhci-
 hcd:usbhid:hid_generic:mbcache:jbd2:ext4 -C /dev/sda2 -h /dev/cryptvg/swap 
 -L -u -o /boot/initrd.gz

Run the resulting command (yours will surely be different  from the example). This will write an image to /boot/initrd.gz in your system which we will use for booting. The '''''-h /dev/cryptvg/swap''''' has been added to enable hibernation. it was not part of the resulting mikinitrd_command_generator.sh command

If you need to know what kernel you just installed try

 uname -a

'''Fixing LILO'''

Next, you have to edit lilo’s configuration file and point it to the correct places so it knows what to boot with. Don’t forget the initrd line here.
(use your preferred editor)

 vim /etc/lilo.conf

Edit the pertinent parts to look like this:

image = /boot/vmlinuz-generic-4.19.0
 initrd = /boot/initrd.gz
 root = /dev/cryptvg/root
 label = Slackware
 read-only  # Partitions should be mounted read-only for checking

Above that, there’s an “append” line. Edit it to look something like this:

 append = "vt.default_utf8=0 resume=/dev/cryptvg/swap"

Of course, substituting your kernel where necessary. You can check what you need to put for “image = ” by going to /boot and checking which generic kernel you want to use to boot. Save your changes and exit.

Run

 lilo -v

You may get an error or two from lilo, but you can usually ignore these.
type 
 exit
to leave the chroot and then
 reboot


If something went wrong, you probably configured something incorrectly along the way. To get back into your system and repair lilo or some other part of the system, follow these steps to chroot from installation media


 cryptsetup luksOpen /dev/sdx2 slackcrypt
 vgscan --mknodes
 vgchange -ay
 lvscan 
 mount /dev/cryptvg/root /mnt
 mount /dev/cryptvg/home /mnt/home
 mount /dev/sdx1 /mnt/boot
 mount -o bind /proc /mnt/proc
 mount -o bind /sys /mnt/sys
 mount -o bind /dev /mnt/dev
 chroot /mnt</text>
    <sha1>8498f42f2e0fea36ea6cbefc613734c5feb2af6d</sha1>
  </revision>
  <revision>
    <id>3204</id>
    <parentid>3203</parentid>
    <timestamp>2018-11-05T19:45:40Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="8771" xml:space="preserve">[[Category:Tutorials]]

'''LVM'''

LVM is a tool for logical volume management which includes allocating disks, striping, mirroring and resizing logical volumes. With LVM, a hard drive or set of hard drives is allocated to one or more physical volumes. LVM physical volumes can be placed on other block devices which might span two or more disks.

'''LUKS'''

LUKS is the standard for Linux hard disk encryption. By providing a standard on-disk-format, it does not
only facilitate compatibility among distributions, but also provides secure management of multiple user passwords.
LUKS stores all necessary setup information in the partition header, enabling you to transport or migrate data seamlessly.

This article assumes that this will be the only operating system installed. Also wherever you see '''''sdx2''''' it is referring to the single large partition (probably /dev/sda2) made in the first step. It also assumes you know your way around the slackware installer.
Swap space setup is documented here but note its only needed if you plan to hibernate e.g. a laptop.

'''Partitioning'''

Boot the installer. Login as '''''root''''' and run 

 cfdisk

What you’re doing here is setting up the partitions. Essentially, we’re dividing up the hard drive into a few logical partitions so that certain things can run in certain places, and not be affected by others. In order to create a bootable encrypted drive there needs to be a small partition that is not encrypted, it’s unencrypted and readable, so the computer can use it to figure out how to start the operating system.

The first partition to make is a boot partition. Delete every other existing partition (if there are any) and write (again, assuming this will be your only OS). Next, select new and create a primary partition that is relatively small, I usually do 1G (which is rather large but i often juggle multiple kernels). Select ''Beginning'', which puts the partition at the front of the disk. DO NOT forget to make the first partition bootable, otherwise the installation won’t know to use this partition to install the boot scripts and such.

Next, create another partition with the remaining space. Follow the same steps, except do not make it bootable and use the rest of the available space. Just hit enter when it asks how much space to use. After you’ve done this, make sure you go down and select '''''write''''' to ensure the changes are made. Then exit cfdisk.

It's a good idea for you to rewrite the entire large partition with random data. This is so computer forensics folks cannot determine where encryption starts and stops, making it harder to find out a way to circumvent the encryption and stuff. To do this, run

 dd if=/dev/urandom of=/dev/sdx2

'''NOTE***'''  this can take quite some time.

'''LVM / Luks Config'''

LVM or Logical Volume Manager is used here to configure volumes inside of the large partition set up earlier (sdx2). LVM makes it easy to separate things internally and keep it all encrypted as one partition. 

 cryptsetup -s 512 -y luksFormat /dev/sdx2

Type '''''YES''''', then decide on a password and type it. Be careful, later on if you put stuff on the drive and you forget your password, it’s gone forever. Such is the nature of encryption. 

Basically this is setting up luks encryption on /dev/sdx2.

 cryptsetup luksOpen /dev/sdx2 slackcrypt

pvcreate is a linux command used to initialize physical volumes for use by logical volume management (lvm) later.

 pvcreate /dev/mapper/slackcrypt 

This creates the volume group “cryptvg”.

 vgcreate cryptvg /dev/mapper/slackcrypt

Create three internal logical volumes, '''''root''''', '''''home''''', and '''''swap'''''. If you have a unique setup and prefer it a different way, just follow the same steps and size them how you want. the sizes used are example only

 lvcreate -L 20G -n root cryptvg

 lvcreate -L 2G -n swap cryptvg

 lvcreate -l 100%FREE -n home cryptvg


These will be your '''''/root''''', '''''/home''''', and '''''/swap''''' “partitions”. You can adjust the sizes to whatever you want them to be. I use a pretty large amount of space in root because I have run out of space installing tons of programs before, but I’ve also used tiny root partitions on machines where I didn’t plan on installing much. It really depends, but if you have the extra space I’d do like 20+ just to be on the safe side. The home directory gets everything that’s not allocated to swap or root.

Next thing we’ve got to do is make sure some nodes get set so everything knows where things are and what not

 vgscan --mknodes

 vgchange -ay

make sure the slackware installer can detect the swap partition

 mkswap /dev/cryptvg/swap

'''Slack Setup and Installation'''

Run the slackware installer

 setup 

the installer will walk you through it from here. it should auto-detect the swap partition we designated

Selecting '''''root''''' partition

Make sure you select /dev/cryptvg/root here, because that’ll be your LVM root partition. Pick whichever file-system you like. After that it should bring you back to the same screen. It’s important to designate your other partitions here.

Select /dev/cryptvg/home and format it.

Next designate boot, which is essential, otherwise your machine will not work properly. Select '''''/dev/sdx1/''''' (probably /dev/sda1), format it, and type ''/boot''.
Now simply install slackware as you normally would until you get to 

'''Install LILO'''

To install the bootloader Lilo select '''''expert''''', then begin. Ignore the optional LILO Append, you probably don’t need to do anything with that.
Select ''mbr'', hit confirm when it asks you to confirm /dev/sdx (probably /dev/sda), and keep going through the options until you’re back at the screen where you selected “begin”.

Now you have to select '''''Linux: Add a linux partition'''''... and select /dev/cryptvg/root. (/dev/cryptvg/root, NOT /boot).

Once that’s been selected, install lilo. . Continue with the installation until you reach a screen listing slackwares installation steps.

Eit the installer and select '''''No''''' to get dropped to a command prompt.

'''Creating an initrd'''

Now we have to fix lilo because of our encryption scheme.

chroot /mnt 

The simple explanation for this command is that you basically just entered the installed system, which is mounted at /mnt. Now you can work on things that are installed on the system. 

The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. to create an initrd run

 /usr/share/mkinitrd/mkinitrd_command_generator.sh

it will look similar to this

 mkinitrd -c -k 4.19.0 -f ext4 -r /dev/cryptvg/root -m usb-storage:xhci-
 hcd:usbhid:hid_generic:mbcache:jbd2:ext4 -C /dev/sda2 -h /dev/cryptvg/swap 
 -L -u -o /boot/initrd.gz

Run the resulting command (yours will surely be different  from the example). This will write an image to /boot/initrd.gz in your system which we will use for booting. The '''''-h /dev/cryptvg/swap''''' has been added to enable hibernation. it was not part of the resulting mikinitrd_command_generator.sh command

If you need to know what kernel you just installed try

 uname -a

'''Fixing LILO'''

Next, you have to edit lilo’s configuration file and point it to the correct places so it knows what to boot with. Don’t forget the initrd line here.
(use your preferred editor)

 vim /etc/lilo.conf

Edit the pertinent parts to look like this:

 image = /boot/vmlinuz-generic-4.19.0
 initrd = /boot/initrd.gz
 root = /dev/cryptvg/root
 label = Slackware
 read-only  # Partitions should be mounted read-only for checking

Above that, there’s an “append” line. Edit it to look something like this:

 append = "vt.default_utf8=0 resume=/dev/cryptvg/swap"

Of course, substituting your kernel where necessary. You can check what you need to put for “image = ” by going to /boot and checking which generic kernel you want to use to boot. Save your changes and exit.

Run

 lilo -v

You may get an error or two from lilo, but you can usually ignore these.
type 
 exit
to leave the chroot and then
 reboot


If something went wrong, you probably configured something incorrectly along the way. To get back into your system and repair lilo or some other part of the system, follow these steps to chroot from installation media


 cryptsetup luksOpen /dev/sdx2 slackcrypt
 vgscan --mknodes
 vgchange -ay
 lvscan 
 mount /dev/cryptvg/root /mnt
 mount /dev/cryptvg/home /mnt/home
 mount /dev/sdx1 /mnt/boot
 mount -o bind /proc /mnt/proc
 mount -o bind /sys /mnt/sys
 mount -o bind /dev /mnt/dev
 chroot /mnt</text>
    <sha1>f97c40a9c73a3c460cc8c68cbfbfc75cc9fedb89</sha1>
  </revision>
  <revision>
    <id>3205</id>
    <parentid>3204</parentid>
    <timestamp>2018-11-14T20:24:22Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="9000" xml:space="preserve">[[Category:Tutorials]]

'''LVM'''

LVM is a tool for logical volume management which includes allocating disks, striping, mirroring and resizing logical volumes. With LVM, a hard drive or set of hard drives is allocated to one or more physical volumes. LVM physical volumes can be placed on other block devices which might span two or more disks.

'''LUKS'''

LUKS is the standard for Linux hard disk encryption. By providing a standard on-disk-format, it does not
only facilitate compatibility among distributions, but also provides secure management of multiple user passwords.
LUKS stores all necessary setup information in the partition header, enabling you to transport or migrate data seamlessly.

This article assumes that this will be the only operating system installed. Also wherever you see '''''sdx2''''' it is referring to the single large partition (probably /dev/sda2) made in the first step. It also assumes you know your way around the slackware installer.
Swap space setup is documented here but note its only needed if you plan to hibernate e.g. a laptop.

'''Partitioning'''

Boot the installer. Login as '''''root''''' and run 

 cfdisk

What you’re doing here is setting up the partitions. Essentially, we’re dividing up the hard drive into a few logical partitions so that certain things can run in certain places, and not be affected by others. In order to create a bootable encrypted drive there needs to be a small partition that is not encrypted, it’s unencrypted and readable, so the computer can use it to figure out how to start the operating system.

The first partition to make is a boot partition. Delete every other existing partition (if there are any) and write (again, assuming this will be your only OS). Next, select new and create a primary partition that is relatively small, I usually do 1G (which is rather large but i often juggle multiple kernels). Select ''Beginning'', which puts the partition at the front of the disk. DO NOT forget to make the first partition bootable, otherwise the installation won’t know to use this partition to install the boot scripts and such.

Next, create another partition with the remaining space. Follow the same steps, except do not make it bootable and use the rest of the available space. Just hit enter when it asks how much space to use. After you’ve done this, make sure you go down and select '''''write''''' to ensure the changes are made. Then exit cfdisk.

It's a good idea for you to rewrite the entire large partition with random data. This is so computer forensics folks cannot determine where encryption starts and stops, making it harder to find out a way to circumvent the encryption and stuff. To do this, run

 dd if=/dev/urandom of=/dev/sdx2

'''NOTE***'''  this can take quite some time.

'''LVM / Luks Config'''

LVM or Logical Volume Manager is used here to configure volumes inside of the large partition set up earlier (sdx2). LVM makes it easy to separate things internally and keep it all encrypted as one partition. 

 cryptsetup -s 512 -y luksFormat /dev/sdx2

Type '''''YES''''', then decide on a password and type it. Be careful, later on if you put stuff on the drive and you forget your password, it’s gone forever. Such is the nature of encryption. 

Basically this is setting up luks encryption on /dev/sdx2.

 cryptsetup luksOpen /dev/sdx2 slackcrypt

pvcreate is a linux command used to initialize physical volumes for use by logical volume management (lvm) later.

 pvcreate /dev/mapper/slackcrypt 

This creates the volume group “cryptvg”.

 vgcreate cryptvg /dev/mapper/slackcrypt

Create three internal logical volumes, '''''root''''', '''''home''''', and '''''swap'''''. If you have a unique setup and prefer it a different way, just follow the same steps and size them how you want. the sizes used are example only

 lvcreate -L 20G -n root cryptvg

 lvcreate -L 2G -n swap cryptvg

 lvcreate -l 100%FREE -n home cryptvg


These will be your '''''/root''''', '''''/home''''', and '''''/swap''''' “partitions”. You can adjust the sizes to whatever you want them to be. I use a pretty large amount of space in root because I have run out of space installing tons of programs before, but I’ve also used tiny root partitions on machines where I didn’t plan on installing much. It really depends, but if you have the extra space I’d do like 20+ just to be on the safe side. The home directory gets everything that’s not allocated to swap or root.

Next thing we’ve got to do is make sure some nodes get set so everything knows where things are and what not

 vgscan --mknodes

 vgchange -ay

make sure the slackware installer can detect the swap partition

 mkswap /dev/cryptvg/swap

'''Slack Setup and Installation'''

Run the slackware installer

 setup 

the installer will walk you through it from here. it should auto-detect the swap partition we designated

Selecting '''''root''''' partition

Make sure you select /dev/cryptvg/root here, because that’ll be your LVM root partition. Pick whichever file-system you like. After that it should bring you back to the same screen. It’s important to designate your other partitions here.

Select /dev/cryptvg/home and format it.

Next designate boot, which is essential, otherwise your machine will not work properly. Select '''''/dev/sdx1/''''' (probably /dev/sda1), format it, and type ''/boot''.
Now simply install slackware as you normally would until you get to 

'''Install LILO'''

To install the bootloader Lilo select '''''expert''''', then begin. Ignore the optional LILO Append, you probably don’t need to do anything with that.
Select ''mbr'', hit confirm when it asks you to confirm /dev/sdx (probably /dev/sda), and keep going through the options until you’re back at the screen where you selected “begin”.

Now you have to select '''''Linux: Add a linux partition'''''... and select /dev/cryptvg/root. (/dev/cryptvg/root, NOT /boot).

Once that’s been selected, install lilo. . Continue with the installation until you reach a screen listing slackwares installation steps.

Eit the installer and select '''''No''''' to get dropped to a command prompt.

'''Creating an initrd'''

Now we have to fix lilo because of our encryption scheme.

chroot /mnt 

The simple explanation for this command is that you basically just entered the installed system, which is mounted at /mnt. Now you can work on things that are installed on the system. 

The initial RAM disk (initrd) is an initial root file system that is mounted prior to when the real root file system is available. The initrd is bound to the kernel and loaded as part of the kernel boot procedure. to create an initrd run

 /usr/share/mkinitrd/mkinitrd_command_generator.sh

it will look similar to this

 mkinitrd -c -k 4.19.0 -f ext4 -r /dev/cryptvg/root -m usb-storage:xhci-
 hcd:usbhid:hid_generic:mbcache:jbd2:ext4 -C /dev/sda2 -h /dev/cryptvg/swap 
 -L -u -o /boot/initrd.gz

Run the resulting command (yours will surely be different  from the example). This will write an image to /boot/initrd.gz in your system which we will use for booting. The '''''-h /dev/cryptvg/swap''''' has been added to enable hibernation. it was not part of the resulting mikinitrd_command_generator.sh command

If you need to know what kernel you just installed try

 uname -a

'''Fixing LILO'''

Next, you have to edit lilo’s configuration file and point it to the correct places so it knows what to boot with. Don’t forget the initrd line here.
(use your preferred editor)

 vim /etc/lilo.conf

Edit the pertinent parts to look like this:

 image = /boot/vmlinuz-generic-4.19.0
 initrd = /boot/initrd.gz
 root = /dev/cryptvg/root
 label = Slackware
 read-only  # Partitions should be mounted read-only for checking

Above that, there’s an “append” line. Edit it to look something like this:

 append = "vt.default_utf8=0 resume=/dev/cryptvg/swap"

Of course, substituting your kernel where necessary. You can check what you need to put for “image = ” by going to /boot and checking which generic kernel you want to use to boot. Save your changes and exit.

Run

 lilo -v

You may get an error or two from lilo, but you can usually ignore these.
type 
 exit
to leave the chroot and then
 reboot


If something went wrong, you probably configured something incorrectly along the way. To get back into your system and repair lilo or some other part of the system, follow these steps to chroot from installation media


 cryptsetup luksOpen /dev/sdx2 slackcrypt
 vgscan --mknodes
 vgchange -ay
 lvscan 
 mount /dev/cryptvg/root /mnt
 mount /dev/cryptvg/home /mnt/home
 mount /dev/sdx1 /mnt/boot
 mount -o bind /proc /mnt/proc
 mount -o bind /sys /mnt/sys
 mount -o bind /dev /mnt/dev
 chroot /mnt


When you update your kernel all you have to do is make another initrd (run the same command mkinitrd_commaand_generator.sh gave you earlier with updated kernel info),
edit /etc/lilo.conf to reflect the new kernel and run lilo</text>
    <sha1>324d2628d537576e0429b45530a767d5bc6df7a0</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Reinstalling Lilo</title>
  <ns>0</ns>
  <id>140</id>
  <revision>
    <id>3206</id>
    <parentid>3196</parentid>
    <timestamp>2018-11-16T14:06:08Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1397" xml:space="preserve">this covers straight unencrypted installs. just a simple installation with everything 
installed under / mounted under /dev/sda1. No LVM or additional drives. if you're encrypted 
or have an otherwise fancy install this wiki expects that you understand the intricacies of 
your own system. for a more in depth look at how to chroot your installation 
media (which can be extremely useful for more that just lilo)
see [https://docs.slackware.com/howtos:slackware_admin:how_to_chroot_from_media here]

'''Chroot method'''

insert and boot your installation media

login as root when prompted but do not run setup

'''Mounting'''

 ''mount /dev/sdX1 /mnt''   (where /dev/sdx1 is your / partition)
 ''mount -o bind /dev /mnt/dev''
 ''mount -o bind /proc /mnt/proc''
 ''mount -o bind /sys /mnt/sys''
 
'''Chrooting'''

Once everything is mounted, we can chroot to it:

 ''chroot /mnt /bin/bash''

now simply run ''liloconfig'' and follow the prompts


'''Booting your system from the installation media'''

often times you can boot your system from the installation media as well
simply boot the installation media and on the very first page are the following instructions


 In a pinch, you can boot your system from here with a command like:
 boot: huge.s root=/dev/sda1 rdinit= ro 
 
In the example above, /dev/sda1 is the / Linux partition.

once booted run ''liloconfig''


[[Category:Tutorials]]</text>
    <sha1>bc337ade0f53f830e2954018029c5a0907bb5044</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>3207</id>
    <parentid>3176</parentid>
    <timestamp>2019-06-07T17:06:12Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>MediaWiki Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4790" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)

MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)

MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>48e9c1857413b230f6e7131af66c61f10bb00d2b</sha1>
  </revision>
  <revision>
    <id>3220</id>
    <parentid>3207</parentid>
    <timestamp>2020-03-27T02:15:34Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>MediaWiki Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="4899" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)

MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)

MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)

MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>35bb326679b6aa2a1ffe0c371da14d6944fd45ce</sha1>
  </revision>
  <revision>
    <id>3277</id>
    <parentid>3220</parentid>
    <timestamp>2021-09-23T13:46:22Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Update</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5012" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on irc.freenode.net. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Freenode ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.36.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:46, 23 September 2021 (UTC)

MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)

MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)

MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)

MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>585a1ba0b87caf519e8b982f087aeeb9091f1387</sha1>
  </revision>
  <revision>
    <id>3278</id>
    <parentid>3277</parentid>
    <timestamp>2021-09-23T13:51:47Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Freenode is dead.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5040" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on [ircs://irc.libera.chat:6697 Libera Chat]. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Libera Chat ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.36.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:46, 23 September 2021 (UTC)

MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)

MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)

MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)

MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>5d17ff5998096527c08cfb144964dd4e41570750</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Talk:Writing A SlackBuild Script</title>
  <ns>1</ns>
  <id>329</id>
  <revision>
    <id>3208</id>
    <timestamp>2019-06-16T19:23:43Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <comment>maybe document needs updating</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1042" xml:space="preserve">
 in a recent post on linux.org someone asked how to go about writing a slackbuild script. I thought I would follow this documentation &amp; see how things worked out.

The most recent release on github is v2019.2 release date 6th June 2o19. Thus i edited wget link to that download.

I've tested $ wget   -O   latex2html-2019.2.tar.gz      https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  and it downloads the tar.gz to my home folder with the name latex2html-2019.2.tar.gz. 

Also i have successfully created a package latex2html-2019.2-i486-1_SBo.tgz which launched on my 14.2 32 bit slackware box.

Now when it came to the actual slackbuild file i used, i tried different approaches including Alien slackbuild kit , mksb and another.

Eventually i downloaded latex2html from slackbuild.org for slackware 13 or thereabouts and edited it.

Since this slackbuild document references latex2html  my thinking is that to further help understand a slackbuild maybe the actual slackbuild for latex would be dissected with explanation.</text>
    <sha1>713edbd209236bd00d314caa1c4cc7081600607c</sha1>
  </revision>
  <revision>
    <id>3213</id>
    <parentid>3208</parentid>
    <timestamp>2019-06-18T09:22:20Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <minor/>
    <comment>using page mainly as appendix to main slackbuild doc</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1263" xml:space="preserve">
 in a recent post on linux.org someone asked how to go about writing a slackbuild script. I thought I would follow this documentation &amp; see how things worked out. I successfully wrote slackbuild and got package visible in /var/log/packages as: /var/log/packages/latex2html-2019.2-i486-1_arb

Example  GNU general public licence 

Slackware build script latex2html
converts latex docs to html 
Copyright (C) 2019  &lt;name&gt;      &lt;email&gt; 
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program.  If not, see &lt;https://www.gnu.org/licenses/&gt;.

--[[User:Captain-sensible|Captain-sensible]] ([[User talk:Captain-sensible|talk]]) 09:22, 18 June 2019 (UTC)--[[User:Captain-sensible|Captain-sensible]] ([[User talk:Captain-sensible|talk]]) 09:22, 18 June 2019 (UTC)</text>
    <sha1>6c8549de04552e1d5e4737628afd1e55fe5ddfb7</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Writing A SlackBuild Script</title>
  <ns>0</ns>
  <id>16</id>
  <revision>
    <id>3209</id>
    <parentid>1021</parentid>
    <timestamp>2019-06-16T19:33:45Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <minor/>
    <comment>/* Getting Started */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19453" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 $ tar -xzf latex2html-2002-2-1.tar.gz || exit 1

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>97772372f581555dfa918fb939b1f72d66f4315e</sha1>
  </revision>
  <revision>
    <id>3210</id>
    <parentid>3209</parentid>
    <timestamp>2019-06-17T10:36:28Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <comment>/* Getting Started */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19511" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 
 $  tar xvzf latex2html-2019.2.tar.gz || exit 1 

 x -extract
 v -verbose
 f -file 
 z -basically ungzip

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>5ebac7e93eceedaba173f70a61df375f24a550cf</sha1>
  </revision>
  <revision>
    <id>3211</id>
    <parentid>3210</parentid>
    <timestamp>2019-06-18T08:21:07Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <minor/>
    <comment>/* Introduction */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19911" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)
 Those that really know what they are doing are unlikely to need to read this document; as a noob I've read through and  successfully created a slackbuild and package.Some of the text needs updating,which i will have a go at in the knowledge that it should be able to be reversed via the history data. I will update from the perspective that a noob is reading and they may need some spoon feeding!  

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 
 $  tar xvzf latex2html-2019.2.tar.gz || exit 1 

 x -extract
 v -verbose
 f -file 
 z -basically ungzip

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>03330c8046c6490fa3f7ba905d456c329a4bf044</sha1>
  </revision>
  <revision>
    <id>3212</id>
    <parentid>3211</parentid>
    <timestamp>2019-06-18T09:13:18Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <minor/>
    <comment>/* Initial Setup */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="19979" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)
 Those that really know what they are doing are unlikely to need to read this document; as a noob I've read through and  successfully created a slackbuild and package.Some of the text needs updating,which i will have a go at in the knowledge that it should be able to be reversed via the history data. I will update from the perspective that a noob is reading and they may need some spoon feeding!  

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 
 $  tar xvzf latex2html-2019.2.tar.gz || exit 1 

 x -extract
 v -verbose
 f -file 
 z -basically ungzip

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license.For the sake of brevity an example has been put on discussion page ), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=2002-2-1 	
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 
 ARCH=${ARCH:-i486} # the architecture on which you want to build your package	
 
 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

 if [ "$ARCH" = "i486" ]; then
   SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  elif [ "$ARCH" = "x86_64" ]; then
   SLKCFLAGS="-O2 -fPIC"
 fi

The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>b435e0b851ee34783912c0b251b9b5613dd7e85f</sha1>
  </revision>
  <revision>
    <id>3214</id>
    <parentid>3212</parentid>
    <timestamp>2019-06-18T09:46:31Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <minor/>
    <comment>/* Writing the SlackBuild script */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20363" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)
 Those that really know what they are doing are unlikely to need to read this document; as a noob I've read through and  successfully created a slackbuild and package.Some of the text needs updating,which i will have a go at in the knowledge that it should be able to be reversed via the history data. I will update from the perspective that a noob is reading and they may need some spoon feeding!  

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 
 $  tar xvzf latex2html-2019.2.tar.gz || exit 1 

 x -extract
 v -verbose
 f -file 
 z -basically ungzip

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license.For the sake of brevity an example has been put on discussion page ), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=${VERSION:-2019-2}
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 

 # Automatically determine the architecture we're building on:
 if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) ARCH=$( uname -m ) ;;
  esac
 fi


 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

  if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
  else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
  fi


The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>3b367e13682ca475f41e0a7ea715ba9cdb2229cc</sha1>
  </revision>
  <revision>
    <id>3215</id>
    <parentid>3214</parentid>
    <timestamp>2019-06-18T09:48:44Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <minor/>
    <comment>/* Initial Setup */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20363" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)
 Those that really know what they are doing are unlikely to need to read this document; as a noob I've read through and  successfully created a slackbuild and package.Some of the text needs updating,which i will have a go at in the knowledge that it should be able to be reversed via the history data. I will update from the perspective that a noob is reading and they may need some spoon feeding!  

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 
 $  tar xvzf latex2html-2019.2.tar.gz || exit 1 

 x -extract
 v -verbose
 f -file 
 z -basically ungzip

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license.For the sake of brevity an example has been put on discussion page ), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=${VERSION:-2019.2}
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 

 # Automatically determine the architecture we're building on:
 if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) ARCH=$( uname -m ) ;;
  esac
 fi


 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

  if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
  else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
  fi


The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/</text>
    <sha1>b16ab5e503c7e426c71f077672f6b39cc6662e55</sha1>
  </revision>
  <revision>
    <id>3216</id>
    <parentid>3215</parentid>
    <timestamp>2019-06-18T13:46:13Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <minor/>
    <comment>/* SlackBuild Script Repositories */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20633" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)
 Those that really know what they are doing are unlikely to need to read this document; as a noob I've read through and  successfully created a slackbuild and package.Some of the text needs updating,which i will have a go at in the knowledge that it should be able to be reversed via the history data. I will update from the perspective that a noob is reading and they may need some spoon feeding!  

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 
 $  tar xvzf latex2html-2019.2.tar.gz || exit 1 

 x -extract
 v -verbose
 f -file 
 z -basically ungzip

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license.For the sake of brevity an example has been put on discussion page ), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=${VERSION:-2019.2}
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 

 # Automatically determine the architecture we're building on:
 if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) ARCH=$( uname -m ) ;;
  esac
 fi


 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

  if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
  else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
  fi


The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;*https://github.com/captain-sensible/latex2html.SlackBuild

the last link is intended for noobs reading this document and wanting to download a working  slackbuild for latex2html which was based on this tutorial. Its been tested on current stable Slackware 14.2 32 bit</text>
    <sha1>852a6d8ec77415842ce6b3c2e2474d284bf48174</sha1>
  </revision>
  <revision>
    <id>3217</id>
    <parentid>3216</parentid>
    <timestamp>2019-06-23T14:40:54Z</timestamp>
    <contributor>
      <username>Captain-sensible</username>
      <id>614</id>
    </contributor>
    <minor/>
    <comment>/* SlackBuild Script Repositories */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20655" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)
 Those that really know what they are doing are unlikely to need to read this document; as a noob I've read through and  successfully created a slackbuild and package.Some of the text needs updating,which i will have a go at in the knowledge that it should be able to be reversed via the history data. I will update from the perspective that a noob is reading and they may need some spoon feeding!  

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 
 $  tar xvzf latex2html-2019.2.tar.gz || exit 1 

 x -extract
 v -verbose
 f -file 
 z -basically ungzip

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license.For the sake of brevity an example has been put on discussion page ), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=${VERSION:-2019.2}
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 

 # Automatically determine the architecture we're building on:
 if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) ARCH=$( uname -m ) ;;
  esac
 fi


 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

  if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
  else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
  fi


The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;*https://slackbuilds.org/repository/14.2/academic/latex2html/?search=latex2html

the last link is  intended for noobs reading this document and wanting to download a working  slackbuild for latex2html which was based on this tutorial. Its been tested on current stable Slackware 14.2 32 bit</text>
    <sha1>201c4462532f81152dde05877070dd68a5e75230</sha1>
  </revision>
  <revision>
    <id>3218</id>
    <parentid>3217</parentid>
    <timestamp>2019-11-04T20:25:53Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <comment>Undo revision 3211 by [[Special:Contributions/Captain-sensible|Captain-sensible]] ([[User talk:Captain-sensible|talk]]) - I'm not necessarily opposed to this text, but it needs attribution - as it was, it appeared to be written by me. -RW</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="20255" xml:space="preserve">[[Category:Tutorials]]

= Introduction =

 Originally written by Florian Mueller jjdm@jjdm.org
 Substantial cleanup and enhancement by Robby Workman (rworkman)

If you use slackware as your main operating system, you have probably wanted to install quite a few applications which are not available in the official slackware.com or even third-party repositories like pkgs.org, or perhaps you just don't like using third-party packages.  In this situation, you have several options on how to install the application:

 * ./configure &amp;&amp; make &amp;&amp; make install
 * use checkinstall
 * use installwatch
 * compile and use makepkg by hand
 * write a SlackBuild script

I will go through the last option: writing [[SlackBuild Scripts]] (which combines the best qualities of all the other aforementioned methods). With a SlackBuild script, you have the build process automated, which will allow you to easily do later upgrades or patches to the package. SlackBuild scripts are also the method by which Patrick Volkerding builds all of the official packages for Slackware. If you look at the various scripts from different sources, you will notice that there is generally an application-independent portion of a script and an application-specific portion of the script.

I cannot teach you how to build the "perfect" package, as reaching that goal requires fairly in-depth knowledge of the Slackware operating system.  You must consider the interactions of your proposed package with all of the other packages within the distribution; they must be integrated seamlessly.  What I can teach you is how to build a package that works and which stays true to the "Slackware Way."

"But it takes so much time!"

It will take approximately thirty minutes to go through this tutorial and about fifteen minutes to create each package (actual compile process not included), but the time you save in the future (you want to create a newer version of the package) makes the initial time expenditure worth it.

= The Slackware package structure =

See [[Packages#Slackware Package Layout]]

= Setting up your build environment =

See [[Build_Environment]] for examples of how various users do this.

= Getting Started =

Hopefully, everything is now clear about Slackware package structure, and you have set up a clean build environment, so we'll begin the process of building a package with a SlackBuild script.

For this example, we'll create a package of latex2html - I made my homepage with that tool.

First, you have to create a directory named &lt;build_environment&gt;/latex2html/. Get the most recent source code release of latex2html place it in this directory.  Note that use of wget below to obtain the most recent source code is optional - you can just as well use your favorite web browser to download it, and then move it into the correct directory.

 $ cd &lt;build_environment&gt;
 $ mkdir latex2html
 $ cd latex2html
 $ wget  -O latex2html-2019.2.tar.gz [https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz  https://github.com/latex2html/latex2html/archive/v2019.2.tar.gz] #6 th June 2019 release
 
Next, we'll create some other needed files with touch.  If you're not familiar with touch, see:
 man touch
Note that the *.SlackBuild file will always contain the name of the application for which it's written; for example, gaim would have gaim.SlackBuild.

 $ touch latex2html.SlackBuild
 $ touch slack-desc

Extract the source code of the application, because we'll need to look at the configure script later on to determine what options we need to pass to it.

 
 $  tar xvzf latex2html-2019.2.tar.gz || exit 1 

 x -extract
 v -verbose
 f -file 
 z -basically ungzip

= Writing the slack-desc file =

See this [[Slack-desc]] page on SlackWiki.org for instructions on how to write a proper slack-desc file.

= Writing the SlackBuild script =

This is the section which takes the most time, and I'll go through it with you step by step.  When you build more packages, you'll probably be able to just copy an existing SlackBuild script and customize it. First, you need to understand that you can write your SlackBuild script in any manner you choose so long as it creates a working package; the method described here is more or less the way Pat Volkerding [[http://slackware.com/~volkerdi]] does it, but even Pat has several different styles for writing the official SlackBuild scripts.  Therefore, if you see something you would do a different way, feel free to do it that way - it's okay.

===Initial Setup===

Open the file latex2html.SlackBuild with your favourite editor.  What follows below is a piece by piece walk-through of a working SlackBuild script.  You may certainly paste the exact contents of those pieces, but in the author's opinion, you have a better chance of understanding it if you write everything yourself.

First, you'll need to set your shell interpreter.  This should be /bin/sh, as *every* Slackware system is guaranteed to have this shell installed, and you want maximum portability.  For this same reason, be careful not to use any extensions and/or syntax that is customized for your particular shell (bash, zsh, or whatever), as it won't be interpreted correctly.  The '-e' flag tells the shell to exit on any error; this helps with both debugging your script as well as ensuring your script does not proceed in an unknown state.

 #!/bin/sh -e

You might want to include a license of some sort with your SlackBuild script (preferably a GPL or BSD-style license.For the sake of brevity an example has been put on discussion page ), but at a minimum, you'll want something like this:

 #&lt;your name&gt; revision date yyyy/mm/dd

With the next few lines, we set some variables that will be used throughout the script. First is the "CWD" variable; in our case, CWD will be &lt;build_environment&gt;/latex2html/. We also test if the TMP variable is set, and if not, we set it to /tmp.

 #Set initial variables:	
 
 CWD=$(pwd)
 if [ "$TMP" = "" ]; then
   TMP=/tmp
 fi

Some people like to build in a subdirectory of /tmp (such as /tmp/build), but that's up to you.
 
 # The version which appears in the application's filename
 VERSION=${VERSION:-2019.2}
 
 # If the version conflicts with the Slackware package standard
 # The dash character ("-") is not allowed in the VERSION string
 # You can set the PKG_VERSION to something else than VERSION
 PKG_VERSION=2002.2.1 # the version which appears in the package name. 
 

 # Automatically determine the architecture we're building on:
 if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i486 ;;
    arm*) ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) ARCH=$( uname -m ) ;;
  esac
 fi


 # First digit is the build number, which specifies how many times it has been built.	
 # Second string is the short form of the authors name, typical three initials:w
 BUILD=${BUILD:-1_rlw}
 
 # The application's name
 APP=latex2html
 
 # The installation directory of the package (where its actual directory
 # structure will be created) 
 PKG=$TMP/package-$APP

Set SLKCFLAGS (which will be used for both CFLAGS and CXXFLAGS).  If you are building on a system with an earlier version of gcc than 3.4.x, then you'll need to use "-mcpu" instead of "-mtune" below.

  if [ "$ARCH" = "i486" ]; then
  SLKCFLAGS="-O2 -march=i486 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "i686" ]; then
  SLKCFLAGS="-O2 -march=i686 -mtune=i686"
  LIBDIRSUFFIX=""
  elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
  else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
  fi


The section just finished sets up a few application-specific variables. When you want to create a package of some other application, you can usually just change the variables, and most of the further steps will work automatically.

=== Extract Sources ===

 # Delete the leftover directories if they exist (due to a previous build)
 # and (re)create the packaging directory
 rm -rf $PKG 
 mkdir -p $TMP $PKG
 rm -rf $TMP/$APP-$VERSION
 
 # Change to the TMP directory
 cd $TMP || exit 1
  
 # Extract the application source in TMP
 # Note: if your application comes as a tar.bz2, you need tar -jxvf
 tar -zxvf $CWD/$APP-$VERSION.tar.gz || exit 1
 
 # Change to the application source directory
 cd $APP-$VERSION || exit 1
  
 # Change ownership and permissions if necessary
 # This may not be needed in some source tarballs, but it never hurts
 chown -R root:root .
 chmod -R u+w,go+r-w,a-s .

===Configure and Compile Sources===

 # Set configure options
 # If your app is written in C++, you'll also need to add a line for CXXFLAGS
 CFLAGS="$SLKCFLAGS" \
   ./configure \
   --prefix=/usr \
   --sysconfdir=/etc \
   --localstatedir=/var \
   --with-perl=/usr/bin/perl \
   --enable-eps \
   --enable-gif \
   --enable-png \
   --build=$ARCH-slackware-linux \
   --host=$ARCH-slackware-linux 
 
 # compile the source, but exit if anything goes wrong
 make || exit
  
 # Install everything into the package directory, but exit if anything goes wrong
 make install DESTDIR=$PKG || exit

There are three configure options I always set:

* --prefix=/usr
* --sysconfdir=/etc
* --localstatedir=/var

This makes configuration files go to /etc, state files (such as log files) go to /var, and the rest goes to /usr. That's the usual Slackware way, but it's your system, so you can certainly install everything in /usr/local or some other location.  See the Unix Filesystem Hierarchy Standard [[http://www.pathname.com/fhs/]] for more information on "correct" locations of various filetypes.

You notice that there were several other options passed to the configure script, and for each application you compile, you have to figure those out for yourself - that's why you were told to extract the sources earlier in this process.  You simply cd into the source directory and run:
 ./configure --help
This will produce a page or two (sometimes more, though) of information about various options that are specific to the application.  Read through this information and figure out what you need (I like to pipe that command through lpr to get a printed copy, but you can certainly use some sort of pager as well:
 ./configure --help | lpr
 ./configure --help | less

The DESTDIR variable is very important in this script because it specifies the directory in which the files should be installed.  This should always be our package directory ($PKG).  Unfortunately, some applications' Makefiles will not support the DESTDIR variable, so you can't use it for those apps.  A simple line like this:
 grep DESTDIR Makefile*
while inside the source directory should tell you whether it supports DESTDIR or not.  If you get some lines of output with $DESTDIR in them, you're in good shape.  If the command returns no output, then the Makefile does not support the DESTDIR variable.

Here's a piece of advice: ALWAYS go through the ./configure &amp;&amp; make &amp;&amp; make install DESTDIR=/somedir process manually and as a NORMAL USER account BEFORE you run your SlackBuild script.  There are quite a few applications out there which try to do "funny stuff" during the installation phase.
 For example, apcupsd will attempt to patch your /etc/rc.d/rc.6 init script
 Yes, it's possible to avoid this with a configure option, but it's not obvious that you would need
 to do so until you look at all of the Makefiles for apcupsd (or watch the install process)
Anyway, if you go through the process as a normal user, you will get "Permission Denied" errors and such if the install process tries to write anywhere it's not allowed to do so.

=== Install Documentation ===

 # Create a directory for documentation
 mkdir -p $PKG/usr/doc/$APP-$VERSION
 
 # Copy documentation to the docs directory and fix permissions
 cp -a BUGS Changes FAQ INSTALL LICENSE MANIFEST README TODO docs/ $PKG/usr/doc/$APP-$VERSION
 find $PKG/usr/doc/$APP-$VERSION -type f -exec chmod 644 {} \;

I (rworkman) also like to place a copy of my SlackBuild script in this directory
 cat $CWD/$APP.SlackBuild &gt; $PKG/usr/doc/$APP-$VERSION/$APP.SlackBuild

Make sure you look inside the actual source archive of the application, because some applications won't have all of the documentation files specified above, and some applications will have additional files.  In other words, don't just copy/paste what you see above into your SlackBuild script - you *must* customize this section for each individual application.

=== Final Touches ===

 # Create the ./install directory and copy the slack-desc into it
 mkdir -p $PKG/install
 cat $CWD/slack-desc &gt; $PKG/install/slack-desc

NOTE: In some cases, you will have some sort of command or setup that
needs to run after the package contents are installed - for this, you
would add a file to $CWD called "doinst.sh" which contains the needed
commands, and then compress that file with gzip.  The SlackBuild script
will zcat (which means to gunzip and cat its contents) that file and 
write the output to a doinst.sh file in the $PKG/install directory.

 # Add doinst.sh to package (if it exists)
 if [ -e $CWD/doinst.sh.gz ]; then
   zcat $CWD/doinst.sh.gz &gt; $PKG/install/doinst.sh
 fi

Let's conserve space if we can; strip libraries and binaries and compress man pages with gzip
Note that you might be able to use "make install-strip" instead of "make install" above instead to accomplish the same purpose

 # Strip some libraries and binaries
 ( cd $PKG
    find . | xargs file | grep "executable" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
    find . | xargs file | grep "shared object" | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2&gt; /dev/null
 )
 
 # Compress man pages if they exist
 if [ -d $PKG/usr/man ]; then
   ( cd $PKG/usr/man
   find . -type f -exec gzip -9 {} \;
   for i in $(find . -type l) ; do ln -s $(readlink $i).gz $i.gz ; rm $i ; done
   ) 
 fi
 
 # Compress info pages if they exist (and remove the dir file)
 if [ -d $PKG/usr/info ]; then
   gzip -9 $PKG/usr/info/*.info
   rm -f $PKG/usr/info/dir
 fi

=== Build the Package ===

 # Build the package
 cd $PKG
 /sbin/makepkg -l y -c n $TMP/$APP-$PKG_VERSION-$ARCH-$BUILD.tgz

= Other Concerns =

=== DESTDIR Option Not Available ===

As mentioned above, there are quite a few applications whose Makefiles do not support the DESTDIR option for make install.  On some applications the DESTDIR Makefile variable has another name.  For example, some Qt applications use the variable INSTALL_ROOT for the same purpose.  If you can understand Makefiles, it is probably worth your time to take a look at its contents and try to find out which actions are performed in the install rule.  Sometimes there will be no DESTDIR equivalent at all.  The &lt;strong&gt;best&lt;/strong&gt; thing you can do in this situation is write a patch for the Makefile.in or equivalent, and submit it to the developer(s) for inclusion in the source, but I realize that everyone doesn't have the ability to do that.  The second best thing you can do it write to the developer(s) and ask them to include that functionality in future releases.  In the meantime, here are some thoughts on the subject...

==== Example 1: ====
Configure the build with:
 ./configure --prefix=$PKG/usr
along with your other configure options.  This will install *all* of the package contents in that directory.  If the package creates $PKG/usr/etc and $PKG/usr/var directories (or any other directories that should be elsewhere), you can probably just move them to their correct location within the package directory tree and everything will be fine.  You might also try this along with your other configure options.
 ./configure --prefix=$PKG/usr \
    --sysconfdir=$PKG/etc \
    --localstatedir=$PKG/var 
There are some applications, however, which "hard-code" configuration files based on configure/Makefile parameters.  In those cases, you'll have to figure out a way to patch the config file prior to packaging it, or in worst-case scenario, include instructions for the end user on how to make the necessary changes.

==== Example 2: ====
This example makes use of the ability to override any Makefile variable, which is called a '''macro''' in the Makefile terminology, on the command line and not have to worry about patching the Makefile to include a '''DESTDIR''' macro in the Makefile.  This approach makes it a bit easier for those not familiar with Makefiles.

If the Makefile does not honor '''DESTDIR''' for the 'make install' command, you can change the prefix macro, instead:
 make prefix=$PKG/usr install
This will override the $(prefix) variable inside the Makefile and install to the location you supplied on the command line.  Therefore, you can configure with the standard ''./configure --prefix=/usr'' (or ''./configure --prefix=/usr/local'') syntax, yet install to a different location as if you supplied a ''DESTDIR=$PKG/usr'' for the 'make install' command.

IMPORTANT NOTE: Macro names are case-sensitive (at least for GNU make).  Some Makefiles may use a "'''PREFIX ='''" macro instead of the usual "'''prefix ='''", so the 'make install' command would look like this:
 make PREFIX=$PKG/usr install
Therefore, it's necessary to look inside the Makefile to be sure which form was used for the prefix.  For large, complex makefiles, the easiest way is to 'grep' the Makefile, like so:
 grep -i '^prefix \?=' Makefile{,.in}
The ''-i'' option makes the search case-insensitive and the ''{,.in}'' part at the end will search "Makefile" or "Makefile.in" files, the second one being a template for the "configure" script.  Grep's search term is a basic regular expression, so the escaped question mark after the space (\?) means there may or may not be a space in between when searching.

Once in a while, there may be a "'''PREFIX ='''" in a Makefile that is not defined which you are to edit and supply the location. Use the usual ''/usr'' (or ''/usr/local''), in this case, and then use 'make PREFIX=$PKG/usr install' to install to the package's build location.

=== Patching the Sources ===

Sooner or later, there will be some reason to patch the source code prior to building a package, and you'll want to be able to do this automatically.  

===== Obtaining the Patch =====

In most cases, the patch will be provided by the author of the source code, so we're not going to discuss patch *creation* here.  Download the patch and place it in the same directory as the SlackBuild script, slack-desc file, and other related files (in $CWD from above).
 $ wget http://someapplication.org/files/patches/bigsecuritypatch.diff
It's not necessary to do the next step, but because developers generally want to conserve space if possible, it's conventional to do this:
 $ gzip -9 bigsecuritypatch.diff
This will result in a new file called bigsecuritypatch.diff.gz -- we'll use that in the SlackBuild script in just a moment.

===== Applying the Patch =====

You will now need to edit your &lt;application&gt;.SlackBuild script so that it applies the patch before it runs configure, make, and make install.  To do this, you'll want something like this to run before the configure script, but after extracting the sources:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p1 || exit
Depending on how the patch was created, you might use a different patchlevel on that line, as in:
 zcat $CWD/bigsecuritypatch.diff.gz | patch -p0 || exit
It's a bit beyond the scope of this HOWTO, but essentially, the -p# specifies the number of trailing directories to skip when looking for the file to patch.  You'll often need to skip the top-level directory, but not always (hence the -p0).

= See Also =

* [[SlackBuild_Scripts]]
* [[Different_Approach_To_Buildscripts]]
* [[Building_A_Package]]
* [[Slack-desc]]
* [[Checkinstall]]
* [[Compiling]]

= SlackBuild Script Repositories =

;* http://slackbuilds.org
;* http://www.slackware.com/~alien/slackbuilds/
;* http://slackbuilds.slackadelic.com/
;* http://slackbuilds.rlworkman.net/
;*https://slackbuilds.org/repository/14.2/academic/latex2html/?search=latex2html

the last link is  intended for noobs reading this document and wanting to download a working  slackbuild for latex2html which was based on this tutorial. Its been tested on current stable Slackware 14.2 32 bit</text>
    <sha1>627282d3b2b543bc9efbfffc94b9fb318fac6095</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Icecream</title>
  <ns>0</ns>
  <id>330</id>
  <revision>
    <id>3219</id>
    <timestamp>2020-02-09T16:10:59Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>Created page with "Icecream was created by SUSE based on distcc. Like distcc, Icecream takes compile jobs from a build and distributes it among remote machines allowing a parallel build. But unl..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1290" xml:space="preserve">Icecream was created by SUSE based on distcc. Like distcc, Icecream takes compile jobs from a build and distributes it among remote machines allowing a parallel build. But unlike distcc, Icecream uses a central server that dynamically schedules the compile jobs to the fastest free server. This advantage pays off mostly for shared computers, if you're the only user on x machines, you have full control over them.


icecream comes installed on slackware and is super easy to setup

you need one master and atleast one slave but you may have many many slaves.
also all your machines need to use the same domain such as .localdomain or i just use .org

you need the rc.iceccd running on all machines even the master so

 chmod +x /etc/rc.d/rc.iceccd

and make sure its running

 /etc.rc.d.rc.iceccd restart

and on the master machine you need the scheduler running

 chmod +x /etc/rc.d/rc.icecc-scheduler

and make sure the shceduler is running on the master machine

 /etc/rc.d/rc.icecc-scheduler restart


now you need to set your make jobs. this is a big topic and wont be covered here. however as an example i use sbotools so in its sbotools.conf
i set '''JOBS=N+1''' where N is the total number of cores across all machines. you may set MAKE -jN elsewhere

thats it. now build something</text>
    <sha1>2e3757e997613b4e860d7dfb609d3cec0339c126</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Talk:ZFS root</title>
  <ns>1</ns>
  <id>331</id>
  <revision>
    <id>3221</id>
    <timestamp>2020-05-20T14:07:29Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>Created page with "This is a very good tutorial/HOWTO, though would need to be updated (some things have changed.)  I'd also like to see one for ZFS more in general, like for any/all partitions,..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="543" xml:space="preserve">This is a very good tutorial/HOWTO, though would need to be updated (some things have changed.)  I'd also like to see one for ZFS more in general, like for any/all partitions, particularly /home, maybe a swap partition, and in the case one also uses both on classic *BSD.  I wish it was as simple as mkfs.zfs but it seems like there's a set of 100+ options (and in the case of dual-boot, you have to choose the intersection of both... if you even want many such options, and it probably only works to setup on one first... probably Slackware.)</text>
    <sha1>6db6a8ad0fb5c21c0b529bab3f800017cb211b1d</sha1>
  </revision>
  <revision>
    <id>3222</id>
    <parentid>3221</parentid>
    <timestamp>2020-05-20T14:09:03Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="616" xml:space="preserve">This is a very good tutorial/HOWTO, though would need to updating (some things changed.)  I'd also like to see one for ZFS in general, like any/all partitions, particularly /home and maybe swap partition, and in the case one uses both with classic *BSD dual-boot with Slackware.  I wish it was as simple as mkfs.zfs but seems like there's a set of 100+ options (and in case of dual-boot, one must choose intersection of both... if one even wants many such options, and probably only works to setup on one first... probably Slackware)--[[User:Dchmelik|Dchmelik]] ([[User talk:Dchmelik|talk]]) 14:09, 20 May 2020 (UTC)</text>
    <sha1>b7bce85498de8552604b135698090c1d56b70044</sha1>
  </revision>
  <revision>
    <id>3224</id>
    <parentid>3222</parentid>
    <timestamp>2020-05-20T14:12:55Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="606" xml:space="preserve">This is a very good tutorial/HOWTO, though would need updating (things changed.)  I'd also like to see a general ZFS one, like any/all partitions, particularly /home and maybe swap partitions, and in case one uses both with classic *BSD Unix &amp; Slackware dual-boot.  I wish it was as simple as mkfs.zfs but seems there's a set of 100+ options varying by operating system (OS, and in case of dual-boot, one must choose sets' intersection... if one even wants many options, and probably only works to setup on Slackware first)--[[User:Dchmelik|Dchmelik]] ([[User talk:Dchmelik|talk]]) 14:12, 20 May 2020 (UTC)</text>
    <sha1>4823452d8f2123c20a09efaf245eb203a39915c3</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>3223</id>
    <parentid>867</parentid>
    <timestamp>2020-05-20T14:09:45Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>/* Others */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1537" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Adioe3|adioe3]]
* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[User:Clientkill|Clientkill]]
* [[USer:codermaniac|codermaniac]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|DarwinElf]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:Erik|erik]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[User:natex|natex]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>970328ddc7685fa1abcfbc23018c2f9640d3b163</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Fonts update</title>
  <ns>0</ns>
  <id>332</id>
  <revision>
    <id>3225</id>
    <timestamp>2020-05-20T14:17:43Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>script to update fonts</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="59" xml:space="preserve">#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
fc-cache -f -v</text>
    <sha1>980ec289ea64858ddd7f9f071df228e2a3696374</sha1>
  </revision>
  <revision>
    <id>3226</id>
    <parentid>3225</parentid>
    <timestamp>2020-05-20T14:18:09Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="70" xml:space="preserve">&lt;pre&gt;#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
fc-cache -f -v&lt;/pre&gt;</text>
    <sha1>979e05d6acee075857c0c04a4ee9605c0ee4bafd</sha1>
  </revision>
  <revision>
    <id>3227</id>
    <parentid>3226</parentid>
    <timestamp>2020-05-20T14:20:42Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="187" xml:space="preserve">&lt;pre&gt;#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
#Scan directories with apparently valid caches (-f, --force,) verbose (-v, --verbose) (see also (-r, really-force: )
fc-cache -f -v&lt;/pre&gt;</text>
    <sha1>77a84e826e2452a13dd59747ef71fcd3bd6b024f</sha1>
  </revision>
  <revision>
    <id>3228</id>
    <parentid>3227</parentid>
    <timestamp>2020-05-20T14:21:15Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="205" xml:space="preserve">&lt;pre&gt;#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
#Scan directories with apparently valid caches (-f, --force,) verbose (-v, --verbose) (see also (-r, really-force, -s --system-only: )
fc-cache -f -v&lt;/pre&gt;</text>
    <sha1>4f94863b404de50b5cc1d393ac7817f08f77b14b</sha1>
  </revision>
  <revision>
    <id>3229</id>
    <parentid>3228</parentid>
    <timestamp>2020-05-20T14:21:51Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="181" xml:space="preserve">&lt;pre&gt;#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
#Scan directories with apparently valid caches (-f, --force,) verbose (-v, --verbose) (see also man fc-cache:)
fc-cache -f -v&lt;/pre&gt;</text>
    <sha1>321af9ddd59e334f2f8fcfe58e12a17dacf0ba42</sha1>
  </revision>
  <revision>
    <id>3230</id>
    <parentid>3229</parentid>
    <timestamp>2020-05-20T14:22:00Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="182" xml:space="preserve">&lt;pre&gt;#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
#Scan directories with apparently valid caches (-f, --force,) verbose (-v, --verbose) (see also man fc-cache: )
fc-cache -f -v&lt;/pre&gt;</text>
    <sha1>49e73b3230474ad58a27879c1a9c3baa4f752a3c</sha1>
  </revision>
  <revision>
    <id>3231</id>
    <parentid>3230</parentid>
    <timestamp>2020-05-20T14:23:20Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="200" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
#Scan directories with apparently valid caches (-f, --force,) verbose (-v, --verbose) (see also man fc-cache: )
fc-cache -f -v&lt;/pre&gt;</text>
    <sha1>634d1cf8d8ae2e36bd2f4ac2d308a134d9fd6dcf</sha1>
  </revision>
  <revision>
    <id>3234</id>
    <parentid>3231</parentid>
    <timestamp>2020-05-20T14:46:50Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="202" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
#Scan directories with apparently valid caches (-f, --force,) verbose (-v, --verbose) (see also man fc-cache: )
fc-cache -f -v
&lt;/pre&gt;</text>
    <sha1>647f82e605ce823520f886e0054cc0f1072e1b9b</sha1>
  </revision>
  <revision>
    <id>3238</id>
    <parentid>3234</parentid>
    <timestamp>2020-05-20T15:04:46Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <minor/>
    <comment>Dchmelik moved page [[Fonts]] to [[Fonts update]]: better title</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="202" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#!/bin/sh
#updatefonts
mkfontdir
mkfontscale
#Scan directories with apparently valid caches (-f, --force,) verbose (-v, --verbose) (see also man fc-cache: )
fc-cache -f -v
&lt;/pre&gt;</text>
    <sha1>647f82e605ce823520f886e0054cc0f1072e1b9b</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Thumbnails</title>
  <ns>0</ns>
  <id>333</id>
  <revision>
    <id>3232</id>
    <timestamp>2020-05-20T14:45:59Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>Created page with "#!/bin/sh #For every .jpg in a directory, create a thumbnail (smaller) image at 280 pixels high (or comment out, uncomment similar line, for width: ) #Resize to 280 pixels hei..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="338" xml:space="preserve">#!/bin/sh
#For every .jpg in a directory, create a thumbnail (smaller) image at 280 pixels high (or comment out, uncomment similar line, for width: )
#Resize to 280 pixels height
for file in *.jpg; do convert -resize x280 "$file" "t$file"; done
#resize to 280 pixels width
#for file in *.jpg; do convert -resize 280 "$file" "t$file"; done</text>
    <sha1>b3a6840caf0be86d235bdd2344d9a94868406e9c</sha1>
  </revision>
  <revision>
    <id>3233</id>
    <parentid>3232</parentid>
    <timestamp>2020-05-20T14:46:15Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="349" xml:space="preserve">&lt;pre&gt;#!/bin/sh
#For every .jpg in a directory, create a thumbnail (smaller) image at 280 pixels high (or comment out, uncomment similar line, for width: )
#Resize to 280 pixels height
for file in *.jpg; do convert -resize x280 "$file" "t$file"; done
#resize to 280 pixels width
#for file in *.jpg; do convert -resize 280 "$file" "t$file"; done&lt;/pre&gt;</text>
    <sha1>2147a63a186b60beb7c3c84806d68d27808b645c</sha1>
  </revision>
  <revision>
    <id>3235</id>
    <parentid>3233</parentid>
    <timestamp>2020-05-20T14:47:04Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="369" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#!/bin/sh
#For every .jpg in a directory, create a thumbnail (smaller) image at 280 pixels high (or comment out, uncomment similar line, for width: )
#Resize to 280 pixels height
for file in *.jpg; do convert -resize x280 "$file" "t$file"; done
#resize to 280 pixels width
#for file in *.jpg; do convert -resize 280 "$file" "t$file"; done
&lt;/pre&gt;</text>
    <sha1>3cb2d135bbbe6dbb01f02b3dc7f4170c0e534806</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>User:Dchmelik</title>
  <ns>2</ns>
  <id>334</id>
  <revision>
    <id>3236</id>
    <timestamp>2020-05-20T14:52:45Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>Created page with "IRC ##slackware &amp; #slackbuilds DarwinElf&lt;br&gt; mathematician/computer-scientist&lt;br&gt; http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik&lt;br&gt; http://davidchmelik.com"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="178" xml:space="preserve">IRC ##slackware &amp; #slackbuilds DarwinElf&lt;br&gt;
mathematician/computer-scientist&lt;br&gt;
http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik&lt;br&gt;
http://davidchmelik.com</text>
    <sha1>22a89bec8dc6db7c074148845eab5156897e03b6</sha1>
  </revision>
  <revision>
    <id>3243</id>
    <parentid>3236</parentid>
    <timestamp>2020-06-06T02:10:27Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="601" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
Editor/creator of some wiki material since '00s.&lt;br&gt;
IRC [[irc://freenode/##slackware ##slackware]] &amp; [[irc://freenode/#slackbuilds #slackbuilds]] &amp; [[irc://freenode/#slackdocs #slackdocs]] DarwinElf&lt;br&gt;
Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
[[https://docs.slackware.com/howtos:zfs_home HOWTO: ZFS /home]]</text>
    <sha1>46c6f570e5fedbc5d42d908da91fd66debd51222</sha1>
  </revision>
  <revision>
    <id>3244</id>
    <parentid>3243</parentid>
    <timestamp>2020-06-06T02:12:14Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="665" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
Editor/creator of some wiki material since '00s.&lt;br&gt;
IRC [[irc://freenode/##slackware ##slackware]] &amp; [[irc://freenode/#slackbuilds #slackbuilds]] &amp; [[irc://freenode/#slackdocs #slackdocs]] DarwinElf&lt;br&gt;
Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
[[http://docs.slackware.com/wiki:user:dchmelil Slackware docs: ]][[http://docs.slackware.com/howtos:zfs_home HOWTO: ZFS /home]]</text>
    <sha1>88aa17eb95fda2db23b7a0bfd60645cd78130768</sha1>
  </revision>
  <revision>
    <id>3246</id>
    <parentid>3244</parentid>
    <timestamp>2020-06-19T03:37:16Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="755" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
Editor/creator of some wiki material since '00s.&lt;br&gt;
IRC [[irc://freenode/##slackware ##slackware]] &amp; [[irc://freenode/#slackbuilds #slackbuilds]] &amp; [[irc://freenode/#slackdocs #slackdocs]] DarwinElf&lt;br&gt;
Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
[[Decompress many]]&lt;br&gt;
[[Fonts update]]&lt;br&gt;
[[Git pull writable]]&lt;br&gt;
[[Thumbnails]]&lt;br&gt;
[[http://docs.slackware.com/wiki:user:dchmelil Slackware docs: ]][[http://docs.slackware.com/howtos:zfs_home HOWTO: ZFS /home]]</text>
    <sha1>74077356e621b5eaf66bdbd550d980cd220525d8</sha1>
  </revision>
  <revision>
    <id>3247</id>
    <parentid>3246</parentid>
    <timestamp>2020-06-19T03:37:34Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="759" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
Editor/creator of some wiki material since '00s.&lt;br&gt;
IRC [[irc://freenode/##slackware ##slackware]] &amp; [[irc://freenode/#slackbuilds #slackbuilds]] &amp; [[irc://freenode/#slackdocs #slackdocs]] DarwinElf&lt;br&gt;
Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
[[Decompress many]]&lt;br&gt;
[[Fonts update]]&lt;br&gt;
[[Git pull writable]]&lt;br&gt;
[[Thumbnails]]&lt;br&gt;
[[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ]][[http://docs.slackware.com/howtos:zfs_home HOWTO: ZFS /home]]</text>
    <sha1>18a2a9998ea88108ad44bceb98a47256d24a50e7</sha1>
  </revision>
  <revision>
    <id>3248</id>
    <parentid>3247</parentid>
    <timestamp>2020-06-19T03:37:59Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="766" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
Editor/creator of some wiki material since '00s.&lt;br&gt;
IRC [[irc://freenode/##slackware ##slackware]] &amp; [[irc://freenode/#slackbuilds #slackbuilds]] &amp; [[irc://freenode/#slackdocs #slackdocs]] DarwinElf&lt;br&gt;
Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
*HOWTOS
[[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ]][[http://docs.slackware.com/howtos:zfs_home ZFS /home]]
*tips
[[Decompress many]]&lt;br&gt;
[[Fonts update]]&lt;br&gt;
[[Git pull writable]]&lt;br&gt;
[[Thumbnails]]&lt;br&gt;</text>
    <sha1>2d8856d03c6f4a3aea4a169e093e0b007f1853c9</sha1>
  </revision>
  <revision>
    <id>3249</id>
    <parentid>3248</parentid>
    <timestamp>2020-06-19T03:38:15Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="762" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
Editor/creator of some wiki material since '00s.&lt;br&gt;
IRC [[irc://freenode/##slackware ##slackware]] &amp; [[irc://freenode/#slackbuilds #slackbuilds]] &amp; [[irc://freenode/#slackdocs #slackdocs]] DarwinElf&lt;br&gt;
Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
*HOWTOS
[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
*tips
[[Decompress many]]&lt;br&gt;
[[Fonts update]]&lt;br&gt;
[[Git pull writable]]&lt;br&gt;
[[Thumbnails]]&lt;br&gt;</text>
    <sha1>4f4a7edefe0a4dc3e5e196d8f32e9c74ef641c5b</sha1>
  </revision>
  <revision>
    <id>3250</id>
    <parentid>3249</parentid>
    <timestamp>2020-06-19T03:41:45Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="769" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
*Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
*Editor/creator of some wiki material since '00s.&lt;br&gt;
*IRC [[irc://freenode/##slackware ##slackware]] &amp; [[irc://freenode/#slackbuilds #slackbuilds]] &amp; [[irc://freenode/#slackdocs #slackdocs]] DarwinElf&lt;br&gt;
*Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
HOWTOS
*[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
tips
*[[Decompress many]]&lt;br&gt;
*[[Fonts update]]&lt;br&gt;
*[[Git pull writable]]&lt;br&gt;
*[[Thumbnails]]&lt;br&gt;</text>
    <sha1>58f687a00712475235426267dd9b1582ac925d01</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Git clone writable</title>
  <ns>0</ns>
  <id>335</id>
  <revision>
    <id>3237</id>
    <timestamp>2020-05-20T15:03:28Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>Created page with "[[Category:Tips]] &lt;pre&gt; #Bash function to make git clone writable (annoyingly, if you clone repository, some files are non-user-writable... which after compiling dangerously t..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="356" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#Bash function to make git clone writable (annoyingly, if you clone repository, some files are non-user-writable... which after compiling dangerously tempts 'sudo rm -rf!')
git()
{
  if [[ $1=="clone" ]]; then
    command git "$@" &amp;&amp; find */.git -type f -perm ! -u=w -exec chmod u+w {} \;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>28df6874379f3357987bea1a9fcee9fcbadddeac</sha1>
  </revision>
  <revision>
    <id>3241</id>
    <parentid>3237</parentid>
    <timestamp>2020-05-21T11:07:45Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="355" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#Bash function to make git clone writable (annoyingly, if you clone repository, some files are non-user-writable... which after compiling dangerously tempts 'sudo rm -rf!')
git()
{
  if [ $1 = "clone" ]; then
    command git "$@" &amp;&amp; find */.git -type f -perm ! -u=w -exec chmod u+w {} \;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>bf68f3ebbc55d80c12c8b5cf7d527ddf32d1abda</sha1>
  </revision>
  <revision>
    <id>3242</id>
    <parentid>3241</parentid>
    <timestamp>2020-05-21T11:09:30Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="356" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#Bash function to make git clones writable (annoyingly, if you clone repository, some files are non-user-writable... which after compiling dangerously tempts 'sudo rm -rf!')
git()
{
  if [ $1 = "clone" ]; then
    command git "$@" &amp;&amp; find */.git -type f -perm ! -u=w -exec chmod u+w {} \;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>c9fdab2a872768ce668418543a9e7b15466415b6</sha1>
  </revision>
  <revision>
    <id>3245</id>
    <parentid>3242</parentid>
    <timestamp>2020-06-19T03:16:19Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="347" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#Bash function to make git clones writable (annoyingly, if you clone repository, some files are non-user-writable... which after compiling dangerously tempts 'sudo rm -rf!')
git()
{
  if [ $1 = "clone" ]; then
    command git "$@" &amp;&amp; find */.git -perm u-w -exec chmod u+w "{}" \;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>b817aa19b32c2ebfa7d04aa0ddce321e2e5f41b4</sha1>
  </revision>
  <revision>
    <id>3251</id>
    <parentid>3245</parentid>
    <timestamp>2020-06-23T07:22:24Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="322" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#Bash function to make git clones writable (annoyingly, if you clone repository, some files are non-user-writable... which after compiling dangerously tempts 'sudo rm -rf!')
git()
{
  if [ $1 = "clone" ]; then
    command git "$@" &amp;&amp; chmod -R u+w */.git;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>6a4e1bb3bf426e479ce6dfe67c3a8234c6142713</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Fonts</title>
  <ns>0</ns>
  <id>336</id>
  <revision>
    <id>3239</id>
    <timestamp>2020-05-20T15:04:46Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>Dchmelik moved page [[Fonts]] to [[Fonts update]]: better title</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="26" xml:space="preserve">#REDIRECT [[Fonts update]]</text>
    <sha1>00c6b3e9e07ebe6cb2b7bc35f724cb1e968caaaf</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>Decompress many</title>
  <ns>0</ns>
  <id>337</id>
  <revision>
    <id>3240</id>
    <timestamp>2020-05-20T15:32:40Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>Created page with "[[Category:Tips]] &lt;pre&gt; #Bash function to decompress (unarchive) may formats. function unarc() {   if [ -f $1 ]; then     case $1 in       *.tar.*) tar xvf $1;;       *.bz2) b..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="707" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#Bash function to decompress (unarchive) may formats.
function unarc()
{
  if [ -f $1 ]; then
    case $1 in
      *.tar.*) tar xvf $1;;
      *.bz2) bunzip2 $1;;
      *.gz) gunzip $1;;
      *.jar) jar xvf $1;;
      *.lha) lha e $1;;
      *.tar) tar xvf $1;;
      *.tar.bz2) tar xvf $1;;
      *.tar.gz) tar xvf $1;;
      *.tar.xz) tar xvf $1;;
      *.tar.Z) tar xvf $1;;
      *.rar) rar x $1;;
      *.7z) 7z x $1;;
      *.tbz2) tar xvf $1;;
      *.tgz) tar xvf $1;;
      *.txz) tar xvf $1;;
      *.xz) unxz $1;;
      *.Z) uncompress $1;;
      *.zip) unzip $1;;
      *) echo '"$1" cannot be extracted.';;
    esac
  else echo '"1" cannot be extracted.';
  fi
}
&lt;/pre&gt;</text>
    <sha1>e2cbbc74e9d0b02bb5bcd72fa2be1b323c38a66e</sha1>
  </revision>
</page>
<page arvcontinue="20181116140608|3206">
  <title>User talk:Erik</title>
  <ns>3</ns>
  <id>338</id>
  <revision>
    <id>3252</id>
    <timestamp>2021-03-08T00:01:00Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>Created page with "Is it possible you could make available the wiki logo image so people (such as me) could link to it graphically from their public homepages?--~~~~"</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="224" xml:space="preserve">Is it possible you could make available the wiki logo image so people (such as me) could link to it graphically from their public homepages?--[[User:Dchmelik|Dchmelik]] ([[User talk:Dchmelik|talk]]) 00:01, 8 March 2021 (UTC)</text>
    <sha1>9e89d522a5b3c949d97e541e7753783f65a676af</sha1>
  </revision>
  <revision>
    <id>3253</id>
    <parentid>3252</parentid>
    <timestamp>2021-03-08T13:39:05Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>reply</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="393" xml:space="preserve">Is it possible you could make available the wiki logo image so people (such as me) could link to it graphically from their public homepages?--[[User:Dchmelik|Dchmelik]] ([[User talk:Dchmelik|talk]]) 00:01, 8 March 2021 (UTC)
: The logo URL is [https://slackwiki.com/images/logo.png https://slackwiki.com/images/logo.png] --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:39, 8 March 2021 (UTC)</text>
    <sha1>ed05315116271a367fea58dc930c21fc8b876812</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Irssi</title>
  <ns>0</ns>
  <id>99</id>
  <revision>
    <id>3279</id>
    <parentid>121</parentid>
    <timestamp>2021-09-23T13:53:50Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Freenode is dead.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2395" xml:space="preserve">Irssi Quick tutorial - Based on http://www.irssi.org/documentation

== Installation ==
If you did a full install of Slackware, you may already have irssi, and you can skip to the next section of this guide. However, if typing 'irssi' at the command line returns nothing, you will need to install the program. Irssi is located in the 'n' folder of Slackware mirrors - and once you have downloaded it, you only need to run 'installpkg irssi[tab]' as root to install it.

== Usage ==
To start the client, "irssi" is entered from either the console or any xterm.

Connecting is done by the /server command
/server irc.libera.chat:6697 , would connect to the libera chat server
/connect does the same thing but is used to open a new connection in a new window
/disconnect is to leave that server.

If the nick or handle is already chosen, just issue /nick somenewhandle , this will change to a new name.

Names that are registered on NickServ must be identified by /msg NickServ IDENTIFY &lt;password&gt;
Or you can select window #2 by the alt key and number 2 and enter IDENTIFY &lt;password&gt;.
N.B alt key 0-10 is for  windows 0-10, Alt-q through Alt-o is for 11-19.

To join a channel, issue /j #slackware, that will bring you to the wonderful people on Slackware's official channel on the Libera Chat IRC network.

Ctrl-X is used to switch between network connections, if you are connected to multiple servers, e.g. irc.libera.chat and another server.

/query and /q are used to initiate private convesationa with people. eg. /query linus would open a private chat window with the user 'linus'.

/set in the first window, shows all the settings, where by help is found by issuing the command. e.g. /help dcc would bring up information on the dcc commmand.

Window management

/WINDOW NEW , splits the screen in half
this new window will have a number assigned to it, to access just type alt 4, if the window is number 4.
/WINDOW CLOSE   , this closes the current window.
/WINDOW BALANCE , this i am constantly using to keep the windows the same size.
/window name hilight, whenever someone types your name in the channel, the line is highlighted in another colour.

Don't forget to run the /save command, so that next time irssi loads, all the windows will be there.

SET term_force_colors ON, is a very useful command, as certain xterms need this to display the colours correctly.


[[Category:Tutorials]]</text>
    <sha1>4e772e3d66f0474324cac83d78f64fbafd0be873</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>User:Erik</title>
  <ns>2</ns>
  <id>2</id>
  <revision>
    <id>3280</id>
    <parentid>597</parentid>
    <timestamp>2021-09-25T00:36:48Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>Freenode is dead.</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="345" xml:space="preserve">Name: [mailto:erik@sl1200.org Erik Hanson]&lt;br&gt;
Web: [http://sl1200.org/~erik/ http://sl1200s.org/~erik/]&lt;br&gt;
IRC: [ircs://irc.libera.chat:6697 Libera Chat]&lt;br&gt;


&lt;math&gt;\phi_n(\kappa) = \frac{1}{4\pi^2\kappa^2} \int_0^\infty \frac{\sin(\kappa R)}{\kappa R} \frac{\partial}{\partial R}\left[R^2\frac{\partial D_n(R)}{\partial R}\right]\,dR&lt;/math&gt;</text>
    <sha1>4382bb7196356e45bf7909e9d2c5f45418bfe43a</sha1>
  </revision>
  <revision>
    <id>3316</id>
    <parentid>3280</parentid>
    <timestamp>2022-12-15T17:00:38Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>http to https</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="149" xml:space="preserve">Name: [mailto:erik@sl1200.org Erik Hanson]&lt;br&gt;
Web: [https://sl1200.org/ https://sl1200s.org/]&lt;br&gt;
IRC: [ircs://irc.libera.chat:6697 Libera Chat]&lt;br&gt;</text>
    <sha1>8596485293f622661ccf55d5928319c4929e2b4f</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Grub</title>
  <ns>0</ns>
  <id>339</id>
  <revision>
    <id>3281</id>
    <timestamp>2021-09-25T18:13:26Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>Created page with "'''installing grub on sackware'''    grub-install /dev/XXX     grub-mkconfig -o /boot/grub/grub.cfg    after updating kernel dont forget to run    grub-mkconfig -o /boot/grub/..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="183" xml:space="preserve">'''installing grub on sackware'''

  grub-install /dev/XXX
 
  grub-mkconfig -o /boot/grub/grub.cfg

  after updating kernel dont forget to run

  grub-mkconfig -o /boot/grub/grub.cfg</text>
    <sha1>0fd51f257a76997700bf967e108324793b29f587</sha1>
  </revision>
  <revision>
    <id>3282</id>
    <parentid>3281</parentid>
    <timestamp>2021-09-25T18:18:55Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="208" xml:space="preserve">[[Category:Tutorials]]


'''installing grub on sackware'''

  grub-install /dev/XXX
 
  grub-mkconfig -o /boot/grub/grub.cfg

  after updating kernel dont forget to run

  grub-mkconfig -o /boot/grub/grub.cfg</text>
    <sha1>16baed8a6f6b6f935f5dd0f925f182d30e6b108e</sha1>
  </revision>
  <revision>
    <id>3284</id>
    <parentid>3282</parentid>
    <timestamp>2021-10-05T02:00:12Z</timestamp>
    <contributor>
      <username>Rworkman</username>
      <id>13</id>
    </contributor>
    <minor/>
    <comment>speling is dificult</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="209" xml:space="preserve">[[Category:Tutorials]]


'''installing grub on slackware'''

  grub-install /dev/XXX
 
  grub-mkconfig -o /boot/grub/grub.cfg

  after updating kernel dont forget to run

  grub-mkconfig -o /boot/grub/grub.cfg</text>
    <sha1>e90a827d251be2edefa6095a0d8f8c0e890c614e</sha1>
  </revision>
  <revision>
    <id>3401</id>
    <parentid>3284</parentid>
    <timestamp>2025-01-09T14:36:39Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="467" xml:space="preserve">[[Category:Tutorials]]

GRUB2 is the latest version of GNU GRUB, the GRand Unified Bootloader. A bootloader is the first software program that runs when a computer starts. It is responsible for loading and transferring control to the operating system kernel.


'''installing grub on slackware'''

  grub-install /dev/XXX
 
  grub-mkconfig -o /boot/grub/grub.cfg

after updating kernel dont forget to update your initrd then run

  grub-mkconfig -o /boot/grub/grub.cfg</text>
    <sha1>7612265d243e3ec6e12b355439cda09b824a97aa</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Main Page</title>
  <ns>0</ns>
  <id>1</id>
  <revision>
    <id>3283</id>
    <parentid>3278</parentid>
    <timestamp>2021-10-02T15:55:11Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <minor/>
    <comment>Software Update</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5150" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on [ircs://irc.libera.chat:6697 Libera Chat]. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Libera Chat ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.36.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 15:55, 2 October 2021 (UTC)

MediaWiki was upgraded to 1.36.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:46, 23 September 2021 (UTC)

MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)

MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)

MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)

MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>1ac337e919a66c5dc252b547053ef36c62551d91</sha1>
  </revision>
  <revision>
    <id>3285</id>
    <parentid>3283</parentid>
    <timestamp>2021-11-25T18:02:36Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>MediaWiki Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5262" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on [ircs://irc.libera.chat:6697 Libera Chat]. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Libera Chat ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.37.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:02, 25 November 2021 (UTC)

MediaWiki was upgraded to 1.36.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 15:55, 2 October 2021 (UTC)

MediaWiki was upgraded to 1.36.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:46, 23 September 2021 (UTC)

MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)

MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)

MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)

MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>7500a7c5af483493c3dfede563f6c23493f0d0ea</sha1>
  </revision>
  <revision>
    <id>3291</id>
    <parentid>3285</parentid>
    <timestamp>2022-04-02T05:14:34Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>MediaWiki Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5370" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on [ircs://irc.libera.chat:6697 Libera Chat]. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Libera Chat ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.37.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 05:14, 2 April 2022 (UTC)

MediaWiki was upgraded to 1.37.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:02, 25 November 2021 (UTC)

MediaWiki was upgraded to 1.36.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 15:55, 2 October 2021 (UTC)

MediaWiki was upgraded to 1.36.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:46, 23 September 2021 (UTC)

MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)

MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)

MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)

MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)

MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)

MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)

MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)

MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>8975545b730697f96380701b266d9a401e4ac406</sha1>
  </revision>
  <revision>
    <id>3292</id>
    <parentid>3291</parentid>
    <timestamp>2022-07-09T19:40:52Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>MediaWiki Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5614" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on [ircs://irc.libera.chat:6697 Libera Chat]. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Libera Chat ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.37.4. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:40, 9 July 2022 (UTC)
{| class="mw-collapsible mw-collapsed wikitable"
|+ style=white-space:nowrap | Previous upgrades.
|-
|MediaWiki was upgraded to 1.37.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 05:14, 2 April 2022 (UTC)
|-
|MediaWiki was upgraded to 1.37.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:02, 25 November 2021 (UTC)
|-
|MediaWiki was upgraded to 1.36.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 15:55, 2 October 2021 (UTC)
|-
|MediaWiki was upgraded to 1.36.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:46, 23 September 2021 (UTC)
|-
|MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)
|-
|MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)
|-
|MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)
|-
|MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)
|-
|MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)
|-
|MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)
|-
|MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)
|-
|MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)
|}

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>df932fe54dfd52cfcd7aae860d900798945fc829</sha1>
  </revision>
  <revision>
    <id>3315</id>
    <parentid>3292</parentid>
    <timestamp>2022-10-01T19:30:17Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <comment>MediaWiki Upgrade</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5727" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on [ircs://irc.libera.chat:6697 Libera Chat]. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Libera Chat ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.38.4. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:30, 1 October 2022 (UTC)
{| class="mw-collapsible mw-collapsed wikitable"
|+ style=white-space:nowrap | Previous upgrades.
|-
|MediaWiki was upgraded to 1.37.4. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:40, 9 July 2022 (UTC)
|-
|MediaWiki was upgraded to 1.37.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 05:14, 2 April 2022 (UTC)
|-
|MediaWiki was upgraded to 1.37.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:02, 25 November 2021 (UTC)
|-
|MediaWiki was upgraded to 1.36.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 15:55, 2 October 2021 (UTC)
|-
|MediaWiki was upgraded to 1.36.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:46, 23 September 2021 (UTC)
|-
|MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)
|-
|MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)
|-
|MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)
|-
|MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)
|-
|MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)
|-
|MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)
|-
|MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)
|-
|MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)
|}

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>0ce16c3961aaee521f75182159e11ec52b370a10</sha1>
  </revision>
  <revision>
    <id>3317</id>
    <parentid>3315</parentid>
    <timestamp>2023-07-06T22:03:37Z</timestamp>
    <contributor>
      <username>Erik</username>
      <id>1</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="5837" xml:space="preserve">Welcome to slackwiki! Feel free to [[Special:Userlogin|Create an account or log in]] and edit any of the pages, or add your own (see [http://meta.wikimedia.org/wiki/Help:Starting_a_new_page Starting A New Page]). Come talk to some of us in ##slackware on [ircs://irc.libera.chat:6697 Libera Chat]. When saving changes, please provide a brief summary of your changes in the box provided - it's nice for those sad people who follow [[Special:Recentchanges|RecentChanges]] via RSS. Any questions about the wiki? See the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide].

==Main Sections==
Please [[Special:Userlogin|LOG IN]] before adding/editing pages.

* [[:Category:Information|Information]]
* [[:Category:Tutorials|Tutorials]]
* [[:Category:Tips|Tips]]
* [[:Category:Security|Security]]
* [[:Category:Hardware|Hardware]]
* [[Links]]
&lt;hr style="width:20em"/&gt;
* [[The Regulars|Regulars of Libera Chat ##slackware]]
* [[Contest|Logo Contest]] (Finished)

==Thanks==
* '''Anyone who contributes to the wiki :)'''

==News==
MediaWiki was upgraded to 1.40.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 22:03, 6 July 2023 (UTC)
{| class="mw-collapsible mw-collapsed wikitable"
|+ style=white-space:nowrap | Previous upgrades.
|-
|MediaWiki was upgraded to 1.38.4. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:30, 1 October 2022 (UTC)
|-
|MediaWiki was upgraded to 1.37.4. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:40, 9 July 2022 (UTC)
|-
|MediaWiki was upgraded to 1.37.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 05:14, 2 April 2022 (UTC)
|-
|MediaWiki was upgraded to 1.37.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:02, 25 November 2021 (UTC)
|-
|MediaWiki was upgraded to 1.36.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 15:55, 2 October 2021 (UTC)
|-
|MediaWiki was upgraded to 1.36.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 13:46, 23 September 2021 (UTC)
|-
|MediaWiki was upgraded to 1.31.7. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:15, 27 March 2020 (UTC)
|-
|MediaWiki was upgraded to 1.31.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:06, 7 June 2019 (UTC)
|-
|MediaWiki was upgraded to 1.31.1. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 18:42, 27 October 2018 (UTC)
|-
|MediaWiki was upgraded to 1.31.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 17:59, 16 June 2018 (UTC)
|-
|MediaWiki was upgraded to 1.30.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 20:21, 11 March 2018 (UTC)
|-
|MediaWiki was upgraded to 1.28.2. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 02:00, 12 May 2017 (UTC)
|-
|MediaWiki was upgraded to 1.23.5. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 19:34, 26 October 2014 (EDT)
|-
|MediaWiki was upgraded to 1.19.0. --[[User:Erik|Erik]] ([[User talk:Erik|talk]]) 00:30, 1 June 2012 (EDT)
|}

MediaWiki was upgraded to 1.18.0. --[[User:Erik|Erik]] 03:44, 17 December 2011 (CST)

Patched to 1.16.2. --[[User:Erik|Erik]] 18:53, 1 February 2011 (EST) | Patched to 1.16.5. --[[User:Erik|Erik]] 17:55, 13 June 2011 (CDT)

MediaWiki was upgraded to 1.16.1. --[[User:Erik|Erik]] 11:43, 5 January 2011 (CST)

Patched to 1.15.3. --[[User:Erik|Erik]] 09:33, 7 April 2010 (UTC) | Patched to 1.15.4. --[[User:Erik|Erik]] 08:31, 30 May 2010 (UTC)
| Patched to 1.15.5. --[[User:Erik|Erik]] 23:12, 28 July 2010 (UTC)

MediaWiki was upgraded to 1.15.2. --[[User:Erik|Erik]] 00:25, 9 March 2010 (UTC)

Sorry for the temporary downtime - we forgot to renew the domain name registration.   --[[User:rworkman|rworkman]] 0006, 3 November 2009 (UTC)

There has been a reset of the wiki. The database was corrupted. A few pages, all Talk/Discussion pages and all user accounts were lost. --[[User:Erik|Erik]] 23:44, 6 June 2009 (UTC)

MediaWiki was upgraded to 1.14.0 --[[User:Erik|Erik]] 16:49, 16 March 2009 (UTC)

We've moved! We're now hosted by [http://onyxlight.net/ http://onyxlight.net/] with an upgrade to MediaWiki 1.6.6 and
spambot prevention in place. --[[User:Erik|Erik]] 11:33, 22 May 2006 (GMT)

The contest has been won by [[User:Marcus|Marcus]]. Admire the logo :) --[[User:FredEmmott|FredEmmott]] 12:36, 24 Feb 2005 (GMT)

Updated SlackWiki to MediaWiki 1.4.7 --[[User:FredEmmott|FredEmmott]] 12:01, 21 Jul 2005 (GMT)

We're now sharing [http://cardinal.lizella.net cardinal.lizella.net] with several other Slackware projects such as [http://www.slacksec.org SlackSec], the [http://www.slackbook.org Slackware Book Project], and [http://www.slamd64.com Slamd64]. Hopefully this will mean a more reliable and faster wiki --[[User:FredEmmott|FredEmmott]] 19:42, 2 May 2005 (GMT)

We're back onto my little UML temporarily, but I've finally judged the contest,
congratulations to [[User:Marcus|Marcus]]. Next artwork contest comming soon, please use the [[Talk:Main_Page|main talk page]] for suggestions on more technical contests --[[User:FredEmmott|FredEmmott]] 18:36, 24 Feb 2005 (GMT)

Thanks to RackSpace and Michael Shuler - they've generously donated a dedicated server to http://www.slacksec.org, which slackwiki is sharing --[[User:FredEmmott|FredEmmott]] 15:06, 1 Dec 2004 (CST)

We are now sharing this server with http://www.slacksec.info - security updates in Pat's absence --[[User:FredEmmott|FredEmmott]] 22:22, 19 Nov 2004 (GMT)

We should not have as many problems with server now - I have no choice but to run debian on this server, and apparantly they missed backporting a security patch, so it's now on traditional non-debianified apache 1.3.33 :) --[[User:FredEmmott|FredEmmott]] 18:03, 2 Nov 2004 (GMT)

Please feel free to bring our old pages over from [http://slackwiki.org/old/index.php?pagename=HomePage the old site] --[[User:FredEmmott|FredEmmott]] 21:23, 31 Oct 2004 (GMT)

Swapped wiki software again because PHPWiki is too buggy --[[User:FredEmmott|FredEmmott]] 21:11, 31 Oct 2004 (GMT)</text>
    <sha1>2cdcf5969416cadf5cfdbdb6effecfabb912d452</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Jellyfin</title>
  <ns>0</ns>
  <id>340</id>
  <revision>
    <id>3286</id>
    <timestamp>2022-01-01T15:30:42Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>Created page with "''' jellyfin '''  Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support.   ''' Installation Process '''  Create a directory in /opt for jellyfin and its files, and en..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2262" xml:space="preserve">''' jellyfin '''

Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support.


''' Installation Process '''

Create a directory in /opt for jellyfin and its files, and enter that directory.

 mkdir /opt/jellyfin
 
 cd /opt/jellyfin


Download the latest generic Linux build from the release page. The generic Linux build ends with "linux-amd64.tar.gz". The rest of these instructions assume version 10.4.3 is being installed (i.e. jellyfin_10.4.3_linux-amd64.tar.gz). Download the generic build, then extract the archive:


 wget https://github.com/jellyfin/jellyfin/releases/download/v10.4.3/jellyfin_10.4.3_linux-amd64.tar.gz
 tar xvzf jellyfin_10.4.3_linux-amd64.tar.gz


Create a symbolic link to the Jellyfin 10.4.3 directory. This allows an upgrade by repeating the above steps and enabling it by simply re-creating the symbolic link to the new version.


 ln -s jellyfin_10.4.3 jellyfin

Create four sub-directories for Jellyfin data.


 mkdir data cache config log

Due to the number of command line options that must be passed, it is easiest to create a small script to run Jellyfin.

 nano jellyfin.sh


Then paste the following commands and modify as needed. (i didnt have to modify anything)

 #!/bin/bash
 JELLYFINDIR="/opt/jellyfin"
 FFMPEGDIR="/usr/share/jellyfin-ffmpeg"
 $JELLYFINDIR/jellyfin/jellyfin \
  -d $JELLYFINDIR/data \
  -C $JELLYFINDIR/cache \
  -c $JELLYFINDIR/config \
  -l $JELLYFINDIR/log \
  --ffmpeg $FFMPEGDIR/ffmpeg


Assuming you desire Jellyfin to run as a non-root user, chmod all files and directories to your normal login user and group. Also make the startup script above executable. (i run it as root. if you choose to run it as root omit the chown command)

 chown -R user:group *
 chmod u+x jellyfin.sh


Finally you can run it. You will see lots of log information when run, this is normal. Setup is as usual in the web browser.


 ./jellyfin.sh &amp;

in your browser go to

 localhost:8096

and set up as you wish</text>
    <sha1>1714bcb8186fa5f1c58ae96d66ecda3c7efc1579</sha1>
  </revision>
  <revision>
    <id>3287</id>
    <parentid>3286</parentid>
    <timestamp>2022-01-01T15:34:02Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2287" xml:space="preserve">[[Category:Tutorials]]


''' jellyfin '''

Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support.


''' Installation Process '''

Create a directory in /opt for jellyfin and its files, and enter that directory.

 mkdir /opt/jellyfin
 
 cd /opt/jellyfin


Download the latest generic Linux build from the release page. The generic Linux build ends with "linux-amd64.tar.gz". The rest of these instructions assume version 10.4.3 is being installed (i.e. jellyfin_10.4.3_linux-amd64.tar.gz). Download the generic build, then extract the archive:


 wget https://github.com/jellyfin/jellyfin/releases/download/v10.4.3/jellyfin_10.4.3_linux-amd64.tar.gz
 tar xvzf jellyfin_10.4.3_linux-amd64.tar.gz


Create a symbolic link to the Jellyfin 10.4.3 directory. This allows an upgrade by repeating the above steps and enabling it by simply re-creating the symbolic link to the new version.


 ln -s jellyfin_10.4.3 jellyfin

Create four sub-directories for Jellyfin data.


 mkdir data cache config log

Due to the number of command line options that must be passed, it is easiest to create a small script to run Jellyfin.

 nano jellyfin.sh


Then paste the following commands and modify as needed. (i didnt have to modify anything)

 #!/bin/bash
 JELLYFINDIR="/opt/jellyfin"
 FFMPEGDIR="/usr/share/jellyfin-ffmpeg"
 $JELLYFINDIR/jellyfin/jellyfin \
  -d $JELLYFINDIR/data \
  -C $JELLYFINDIR/cache \
  -c $JELLYFINDIR/config \
  -l $JELLYFINDIR/log \
  --ffmpeg $FFMPEGDIR/ffmpeg


Assuming you desire Jellyfin to run as a non-root user, chmod all files and directories to your normal login user and group. Also make the startup script above executable. (i run it as root. if you choose to run it as root omit the chown command)

 chown -R user:group *
 chmod u+x jellyfin.sh


Finally you can run it. You will see lots of log information when run, this is normal. Setup is as usual in the web browser.


 ./jellyfin.sh &amp;

in your browser go to

 localhost:8096

and set up as you wish</text>
    <sha1>ddbf83bb445699932bfd225c5449ff8baf323678</sha1>
  </revision>
  <revision>
    <id>3288</id>
    <parentid>3287</parentid>
    <timestamp>2022-01-01T15:35:29Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="2332" xml:space="preserve">[[Category:Tutorials]]


''' jellyfin '''

Jellyfin is a Free Software Media System that puts you in control of managing and streaming your media. It is an alternative to the proprietary Emby and Plex, to provide media from a dedicated server to end-user devices via multiple apps. Jellyfin is descended from Emby's 3.5.2 release and ported to the .NET Core framework to enable full cross-platform support.


''' Installation Process '''

this wiki assumes you are logged in as root

Create a directory in /opt for jellyfin and its files, and enter that directory.

 mkdir /opt/jellyfin
 
 cd /opt/jellyfin


Download the latest generic Linux build from the release page. The generic Linux build ends with "linux-amd64.tar.gz". The rest of these instructions assume version 10.4.3 is being installed (i.e. jellyfin_10.4.3_linux-amd64.tar.gz). Download the generic build, then extract the archive:


 wget https://github.com/jellyfin/jellyfin/releases/download/v10.4.3/jellyfin_10.4.3_linux-amd64.tar.gz
 tar xvzf jellyfin_10.4.3_linux-amd64.tar.gz


Create a symbolic link to the Jellyfin 10.4.3 directory. This allows an upgrade by repeating the above steps and enabling it by simply re-creating the symbolic link to the new version.


 ln -s jellyfin_10.4.3 jellyfin

Create four sub-directories for Jellyfin data.


 mkdir data cache config log

Due to the number of command line options that must be passed, it is easiest to create a small script to run Jellyfin.

 nano jellyfin.sh


Then paste the following commands and modify as needed. (i didnt have to modify anything)

 #!/bin/bash
 JELLYFINDIR="/opt/jellyfin"
 FFMPEGDIR="/usr/share/jellyfin-ffmpeg"
 $JELLYFINDIR/jellyfin/jellyfin \
  -d $JELLYFINDIR/data \
  -C $JELLYFINDIR/cache \
  -c $JELLYFINDIR/config \
  -l $JELLYFINDIR/log \
  --ffmpeg $FFMPEGDIR/ffmpeg


Assuming you desire Jellyfin to run as a non-root user, chmod all files and directories to your normal login user and group. Also make the startup script above executable. (i run it as root. if you choose to run it as root omit the chown command)

 chown -R user:group *
 chmod u+x jellyfin.sh


Finally you can run it. You will see lots of log information when run, this is normal. Setup is as usual in the web browser.


 ./jellyfin.sh &amp;

in your browser go to

 localhost:8096

and set up as you wish</text>
    <sha1>cbd39bc57cf1ce49d394e58fbf1ef717d9d4125a</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>User:Dchmelik</title>
  <ns>2</ns>
  <id>334</id>
  <revision>
    <id>3289</id>
    <parentid>3250</parentid>
    <timestamp>2022-03-24T02:35:15Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="778" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
*Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
*Editor/creator of some wiki material since '00s.&lt;br&gt;
*IRC [[irc://libera.chat/##slackware ##slackware]] &amp; [[irc://libera.chat/#slackbuilds #slackbuilds]] &amp; [[irc://libera.chat/#slackdocs #slackdocs]] DarwinElf&lt;br&gt;
*Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
HOWTOS
*[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
tips
*[[Decompress many]]&lt;br&gt;
*[[Fonts update]]&lt;br&gt;
*[[Git pull writable]]&lt;br&gt;
*[[Thumbnails]]&lt;br&gt;</text>
    <sha1>46a58484f746c41817de4f02701fa57cd4472b8f</sha1>
  </revision>
  <revision>
    <id>3290</id>
    <parentid>3289</parentid>
    <timestamp>2022-03-24T02:37:32Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="790" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
*Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
*Editor/creator of some wiki material since '00s.&lt;br&gt;
*IRC [irc://libera.chat/##slackware irc://libera.chat/##slackware] &amp; [irc://libera.chat/#slackbuilds #slackbuilds] &amp; [irc://libera.chat/#slackdocs #slackdocs] DarwinElf&lt;br&gt;
*Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
HOWTOS
*[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
tips
*[[Decompress many]]&lt;br&gt;
*[[Fonts update]]&lt;br&gt;
*[[Git pull writable]]&lt;br&gt;
*[[Thumbnails]]&lt;br&gt;</text>
    <sha1>3d2f0fdd996f698b40490fda94200698535dc7d9</sha1>
  </revision>
  <revision>
    <id>3300</id>
    <parentid>3290</parentid>
    <timestamp>2022-07-27T04:51:44Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="790" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], programmer since 1993 (CWU 2012 BSc.)&lt;br&gt;
*Unix &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
*Editor/creator of some wiki material since '00s.&lt;br&gt;
*IRC [irc://libera.chat/##slackware irc://libera.chat/##slackware] &amp; [irc://libera.chat/#slackbuilds #slackbuilds] &amp; [irc://libera.chat/#slackdocs #slackdocs] DarwinElf&lt;br&gt;
*Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
HOWTOS
*[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
tips
*[[decompress many]]&lt;br&gt;
*[[fonts update]]&lt;br&gt;
*[[git pull writable]]&lt;br&gt;
*[[thumbnails]]&lt;br&gt;</text>
    <sha1>7957978a80cfcbb32c6f2116d0d64e62134cb2f3</sha1>
  </revision>
  <revision>
    <id>3301</id>
    <parentid>3300</parentid>
    <timestamp>2022-07-27T04:54:14Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="792" xml:space="preserve">philosopher-mathematician-scientist [[http://davidchmelik.com David Chmelik]], BSc (CWU 2012), programmer since 1993&lt;br&gt;
*UNIX/*BSD &amp; Slackware user/programmer/scientist since 1997.&lt;br&gt;
*Editor/creator of some wiki material since '00s.&lt;br&gt;
*IRC [irc://libera.chat/##slackware irc://libera.chat/##slackware] &amp; [irc://libera.chat/#slackbuilds #slackbuilds] &amp; [irc://libera.chat/#slackdocs #slackdocs] darwin&lt;br&gt;
*Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10.&lt;br&gt;
HOWTOS
*[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
tips
*[[decompress many]]&lt;br&gt;
*[[fonts update]]&lt;br&gt;
*[[git pull writable]]&lt;br&gt;
*[[thumbnails]]&lt;br&gt;</text>
    <sha1>7ff8c330361fec1ff5e1b52a7b7c4fc2a3220b64</sha1>
  </revision>
  <revision>
    <id>3302</id>
    <parentid>3301</parentid>
    <timestamp>2022-07-27T04:55:50Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="787" xml:space="preserve">philosopher-mathematician-scientist [http://davidchmelik.com David Chmelik], BSc (CWU 2012), programmer since 1993&lt;br&gt;
*UNIX/*BSD &amp; Slackware user/programmer/scientist since 1997&lt;br&gt;
*Editor/creator of some wiki material since '00s&lt;br&gt;
*IRC [irc://libera.chat/##slackware irc://libera.chat/##slackware] &amp; [irc://libera.chat/#slackbuilds #slackbuilds] &amp; [irc://libera.chat/#slackdocs #slackdocs] darwin&lt;br&gt;
*Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10&lt;br&gt;
HOWTOS
*[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
tips
*[[decompress many]]&lt;br&gt;
*[[fonts update]]&lt;br&gt;
*[[git pull writable]]&lt;br&gt;
*[[thumbnails]]&lt;br&gt;</text>
    <sha1>2e7de18c908fceab86f2ad0bac307662050759b8</sha1>
  </revision>
  <revision>
    <id>3303</id>
    <parentid>3302</parentid>
    <timestamp>2022-07-27T04:56:25Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="786" xml:space="preserve">philosopher-mathematician-scientist [http://davidchmelik.com David Chmelik], BSc (CWU 2012), programmer since 1993&lt;br&gt;
*UNIX/*BSD &amp; Slackware user/programmer/scientist since 1997&lt;br&gt;
*Editor/creator of some wiki material since '0s&lt;br&gt;
*IRC [irc://libera.chat/##slackware irc://libera.chat/##slackware] &amp; [irc://libera.chat/#slackbuilds #slackbuilds] &amp; [irc://libera.chat/#slackdocs #slackdocs] darwin&lt;br&gt;
*Maintainer/creator of [[http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some]] [[http://SlackBuilds.org SlackBuilds]] since '10&lt;br&gt;
HOWTOS
*[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
tips
*[[decompress many]]&lt;br&gt;
*[[fonts update]]&lt;br&gt;
*[[git pull writable]]&lt;br&gt;
*[[thumbnails]]&lt;br&gt;</text>
    <sha1>d0af0bef5b7a65fe5bd9a91bde8720d529ecb75f</sha1>
  </revision>
  <revision>
    <id>3304</id>
    <parentid>3303</parentid>
    <timestamp>2022-07-27T04:56:36Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="782" xml:space="preserve">philosopher-mathematician-scientist [http://davidchmelik.com David Chmelik], BSc (CWU 2012), programmer since 1993&lt;br&gt;
*UNIX/*BSD &amp; Slackware user/programmer/scientist since 1997&lt;br&gt;
*Editor/creator of some wiki material since '0s&lt;br&gt;
*IRC [irc://libera.chat/##slackware irc://libera.chat/##slackware] &amp; [irc://libera.chat/#slackbuilds #slackbuilds] &amp; [irc://libera.chat/#slackdocs #slackdocs] darwin&lt;br&gt;
*Maintainer/creator of [http://slackbuilds.org/cgit/slackbuilds/log/?qt=author&amp;q=David+Melik some] [http://SlackBuilds.org SlackBuilds] since '10&lt;br&gt;
HOWTOS
*[http://docs.slackware.com/wiki:user:dchmelil Slackware.com Docs: ][http://docs.slackware.com/howtos:zfs_home ZFS /home]
tips
*[[decompress many]]&lt;br&gt;
*[[fonts update]]&lt;br&gt;
*[[git pull writable]]&lt;br&gt;
*[[thumbnails]]&lt;br&gt;</text>
    <sha1>5122408fd220d3e1609ec649e494cbbbeb18caa0</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Git clone writable</title>
  <ns>0</ns>
  <id>335</id>
  <revision>
    <id>3293</id>
    <parentid>3251</parentid>
    <timestamp>2022-07-23T05:49:49Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="389" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#Bash function to make git clones writable (annoyingly, if you clone repository, some files are non-user-writable... which after compiling dangerously tempts 'sudo rm -rf!')
git()
{
  if [ $1 = "clone" ]; then
    command git "$@" &amp;&amp; chmod -R u+w */.git;
  #you may prefer
  #  command git "$@" &amp;&amp; chmod -R rm -rf */.git;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>77ee6e5dc9123d7315e85f817d3287bd0036037a</sha1>
  </revision>
  <revision>
    <id>3294</id>
    <parentid>3293</parentid>
    <timestamp>2022-07-23T05:50:07Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="380" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#Bash function to make git clones writable (annoyingly, if you clone repository, some files are non-user-writable... which after compiling dangerously tempts 'sudo rm -rf!')
git()
{
  if [ $1 = "clone" ]; then
    command git "$@" &amp;&amp; chmod -R u+w */.git;
  #you may prefer
  #  command git "$@" &amp;&amp; rm -rf */.git;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>97690b017a72a72a0a21206903daecc4a81f7c4d</sha1>
  </revision>
  <revision>
    <id>3296</id>
    <parentid>3294</parentid>
    <timestamp>2022-07-27T04:46:05Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="363" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function to set git clones user-writable (annoyingly if you clone repository some files are non-user-writable... dangerously tempts 'sudo rm -rf'!)
git()
{
  if [ $1 = "clone" ]; then
    command git "$@" &amp;&amp; chmod -R u+w */.git*;
  #you may prefer
  #  command git "$@" &amp;&amp; rm -fR */.git*;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>f67654322603095cdfbb0bcdaf7608f40628d6e7</sha1>
  </revision>
  <revision>
    <id>3297</id>
    <parentid>3296</parentid>
    <timestamp>2022-07-27T04:48:36Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <minor/>
    <comment>Dchmelik moved page [[Git pull writable]] to [[Git clone writable]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="363" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function to set git clones user-writable (annoyingly if you clone repository some files are non-user-writable... dangerously tempts 'sudo rm -rf'!)
git()
{
  if [ $1 = "clone" ]; then
    command git "$@" &amp;&amp; chmod -R u+w */.git*;
  #you may prefer
  #  command git "$@" &amp;&amp; rm -fR */.git*;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>f67654322603095cdfbb0bcdaf7608f40628d6e7</sha1>
  </revision>
  <revision>
    <id>3307</id>
    <parentid>3297</parentid>
    <timestamp>2022-07-27T05:14:31Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="426" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function: set git clones user-writable (annoyingly if you clone some files are non-user-writable... dangerously tempts 'sudo rm -rf'!)
git()
{
  if [ $1 = "clone" ]; then
    # Might work.
    #find . -iname .git* -perm u-w -exec chmod u+w {} \+;
    command git "$@" &amp;&amp; chmod -R u+w */.git*;
  #you may prefer
  #  command git "$@" &amp;&amp; rm -fR */.git*;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>128fe1007f8db523a04076eb3a4f267a55c2ae68</sha1>
  </revision>
  <revision>
    <id>3308</id>
    <parentid>3307</parentid>
    <timestamp>2022-07-27T05:15:01Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="430" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function: set git clones user-writable (annoyingly if you clone some files are non-user-writable... dangerously tempts 'sudo rm -rf'!)
git()
{
  if [ $1 = "clone" ]; then
    # Might work.
    #find . -iname .git* -perm u-w -exec chmod u+w {} \+;
    command git "$@" &amp;&amp; chmod -R u+w */.git*;
    # You may prefer.
    #command git "$@" &amp;&amp; rm -fR */.git*;
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>9743649302ce0cd062569c164df385e75abd190e</sha1>
  </revision>
  <revision>
    <id>3309</id>
    <parentid>3308</parentid>
    <timestamp>2022-07-27T05:18:16Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="758" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function: set git clones user-writable (annoyingly if you clone some files are non-user-writable... dangerously tempts 'sudo rm -rf'!)
git()
{
  if [ $1 = "clone" ]; then
    # Might work.
    #sudo find . -iname .git* -perm u-w -exec chmod u+w {} \+;
    command git "$@" &amp;&amp; chmod -R u+w */.git*;
    # You may prefer.
    #command git "$@" &amp;&amp; rm -fR */.git*;
    # Uncomment section to SlackBuilds.org version naming convention compress.
    #d='$@' #d=https://github.com/user/project.git;
    #d=${d##*/}  
    #d=${d%.git}
    #cd $d
    #VERSION=$(git log --pretty=format:'%cd_%h' --date=format:'%Y%m%d' | head -n 1)
    #cd ..
    #tar --exclude-vcs -cJvf $d-$VERSION.tar.xz $d
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>35bf936c6ea6f5f2df41a82d3a970cf328012a88</sha1>
  </revision>
  <revision>
    <id>3310</id>
    <parentid>3309</parentid>
    <timestamp>2022-07-27T05:18:38Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="757" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function: set git clones user-writable (annoyingly if you clone some files are non-user-writable... dangerously tempts 'sudo rm -rf'!)
git()
{
  if [ $1 = "clone" ]; then
    # Might work.
    #sudo find . -iname .git* -perm u-w -exec chmod u+w {} \+;
    command git "$@" &amp;&amp; chmod -R u+w */.git*;
    # You may prefer.
    #command git "$@" &amp;&amp; rm -fR */.git*;
    # Uncomment section to SlackBuilds.org version naming convention compress.
    #d='$@' #d=https://github.com/user/project.git
    #d=${d##*/}  
    #d=${d%.git}
    #cd $d
    #VERSION=$(git log --pretty=format:'%cd_%h' --date=format:'%Y%m%d' | head -n 1)
    #cd ..
    #tar --exclude-vcs -cJvf $d-$VERSION.tar.xz $d
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>6d0d0361fe1287d859101cab578887207e8cf77d</sha1>
  </revision>
  <revision>
    <id>3311</id>
    <parentid>3310</parentid>
    <timestamp>2022-07-27T09:31:32Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="718" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function: set git clones user-writable (annoyingly if you clone some files are non-user-writable... dangerously tempts 'sudo rm -rf'!)
git()
{
  if [ $1 = "clone" ]; then
    # Might work.
    #sudo find . -iname .git* -perm u-w -exec chmod u+w {} \+;
    command git "$@" &amp;&amp; chmod -R u+w */.git*;
    # You may prefer.
    #command git "$@" &amp;&amp; rm -fR */.git*;
    # Uncomment section to SlackBuilds.org version naming convention compress.
    #d='$@'
    #d=${d##*/}  
    #d=${d%.git}
    #cd $d
    #VERSION=$(git log --pretty=format:'%cd_%h' --date=format:'%Y%m%d' | head -n 1)
    #cd ..
    #tar --exclude-vcs -cJvf $d-$VERSION.tar.xz $d
  else
    command git "$@";
  fi;
}
&lt;/pre&gt;</text>
    <sha1>49ede8393dad05869588443fbf082090941ec859</sha1>
  </revision>
  <revision>
    <id>3312</id>
    <parentid>3311</parentid>
    <timestamp>2022-08-28T11:29:50Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="715" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# Annoyingly some 'git clone' files aren't user-writable: dangerously tempts 'sudo rm -rf'!. Bash function.
# Writable git clone
git()
{
  command git "$@"
  if [ $1 = 'clone' ]; then
    d="$@"; d=${d##*/}; d=${d%.git}; d=${d##* }
    #read -p "dir: $d"
    if [ -d "$d" ]; then
      chmod -R u+w $d/.git*
      # Maybe faster than previous line.
      #find $d -iname .git* -perm u-w -exec chmod u+w {} \+
      cd $d
      VERSION=$(git log --pretty=format:'%cd_%h' --date=format:'%Y%m%d' | head -n 1)
      # Maybe faster than above chmod/find.
      #rm -fR .git*
      cd ..
      tar --exclude-vcs -cJvf $d-$VERSION.tar.xz $d
    else echo "save/download error"
    fi
  fi;
}
&lt;/pre&gt;</text>
    <sha1>5ee90660bd2caa611ea459d380ffac6dfe1e693f</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>The Regulars</title>
  <ns>0</ns>
  <id>4</id>
  <revision>
    <id>3295</id>
    <parentid>3223</parentid>
    <timestamp>2022-07-27T04:41:14Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1534" xml:space="preserve">==Staff==
* [[User:Alan_Hicks|Alan Hicks]]
* [[User:alienbob|alienBOB]]
* nachox/darkjoker
* [[User:phrag|phrag]]
* [[User:rworkman|rworkman]]
* [[User:Stx|Stx]]
* [[User:Unixfool|Unixfool/W|GGL|T]]

==Others==

* [[User:Adioe3|adioe3]]
* [[User:Alisonken1|Alisonken1]]
* [[User:Apeitheo|Apeitheo]]
* [[User:Boojit|boojit]]
* [[User:Michiel |BP{k}]]
* [[User:Buzzedlightyear|Buzzedlightyear]]
* [[User:chopp|chopp]]
* [[User:Chrismo|Chrismo]]
* [[User:clavius|clavius]]
* [[User:Clientkill|Clientkill]]
* [[USer:codermaniac|codermaniac]]
* [[User:Crudo|crudo]]
* [[User:Crypticlineage|crypticlineage]]
* [[User:dadexter|dadexter]]
* [[User:dchmelik|darwin]]
* [[User:derxob|derxob]]
* [[User:Dominian|Dominian]]
* dtanner
* [[eclipse75]]
* [[User:Erik|erik]]
* [[User:FredEmmott|fred]]
* [[User:giangy|giangy]]
* [[User:jcm |jcm]]
* [[User:jpipkin |jpipkin]]
* [[User:macavity|macavity]]
* [[User:Marcus | Marcus_]]
* [[User:Mmlj4|mmlj4]]
* [[User:natex|natex]]
* [[USer:Phoul|Phoul]]
* [[User:Dardan Fejzullahi |radiohead]]
* [[User:radi0head|radi0head]]
* Riddick
* [[User:robert-brown|robert-brown]]
* [[User:1337ln | ron1n]]
* [[User:Ryanx0r|Ryanx0r]]
* [[USer:slackmagic|slackmagic]]
* [[User:Slakmagik|slakmagik]]
* [[StevenR]]
* [[User:Straterra|Straterra]]
* [[USer:Strykar|Strykar]]
* [[User:tecky|tecky]]
* [[User:Tewmten|tewmten]]
* [[User:v3ctor|v3ctor]]
* [[User:Zordrak|Zordrak]]

==SlackWiki Admins==
There is a [[Special:Listadmins|list]] of SlackWiki admins. Please contact one if you think you'd be a suitable admin.</text>
    <sha1>457fb63209b1bbfe674c7942b61f7c196ab4eeaa</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Git pull writable</title>
  <ns>0</ns>
  <id>341</id>
  <revision>
    <id>3298</id>
    <timestamp>2022-07-27T04:48:36Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <comment>Dchmelik moved page [[Git pull writable]] to [[Git clone writable]]</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="32" xml:space="preserve">#REDIRECT [[Git clone writable]]</text>
    <sha1>8411865e774b1f47a2d4c41b79c1eab3b80cf212</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Decompress many</title>
  <ns>0</ns>
  <id>337</id>
  <revision>
    <id>3299</id>
    <parentid>3240</parentid>
    <timestamp>2022-07-27T04:51:30Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="709" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function to decompress (unarchive) many formats.
function unarc()
{
  if [ -f $1 ]; then
    case $1 in
      *.tar.*) tar xvf $1;;
      *.bz2) bunzip2 $1;;
      *.gz) gunzip $1;;
      *.jar) jar xvf $1;;
      *.lha) lha e $1;;
      *.tar) tar xvf $1;;
      *.tar.bz2) tar xvf $1;;
      *.tar.gz) tar xvf $1;;
      *.tar.xz) tar xvf $1;;
      *.tar.Z) tar xvf $1;;
      *.rar) rar x $1;;
      *.7z) 7z x $1;;
      *.tbz2) tar xvf $1;;
      *.tgz) tar xvf $1;;
      *.txz) tar xvf $1;;
      *.xz) unxz $1;;
      *.Z) uncompress $1;;
      *.zip) unzip $1;;
      *) echo '"$1" cannot be extracted.';;
    esac
  else echo '"1" cannot be extracted.';
  fi
}
&lt;/pre&gt;</text>
    <sha1>3c868c0d8071c2d7eea90e4cc371cef05681165e</sha1>
  </revision>
  <revision>
    <id>3313</id>
    <parentid>3299</parentid>
    <timestamp>2022-08-28T11:30:34Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="698" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function to decompress (unarchive) many formats.
function unarc()
{
  if [ -f $1 ]; then
    case $1 in
      *.tar.*) tar xvf $1;;
      *.bz2) bunzip2 $1;;
      *.gz) gunzip $1;;
      *.jar) jar xvf $1;;
      *.lha) lha e $1;;
      *.tar) tar xvf $1;;
      *.tar.bz2) tar xvf $1;;
      *.tar.gz) tar xvf $1;;
      *.tar.xz) tar xvf $1;;
      *.tar.Z) tar xvf $1;;
      *.rar) rar x $1;;
      *.7z) 7z x $1;;
      *.tbz2) tar xvf $1;;
      *.tgz) tar xvf $1;;
      *.txz) tar xvf $1;;
      *.xz) unxz $1;;
      *.Z) uncompress $1;;
      *.zip) unzip $1;;
      *) echo '"$1" extraction error.';;
    esac
  else echo '"1" nonexistent?';
  fi
}
&lt;/pre&gt;</text>
    <sha1>6257a51fe0fb011cc3e3983b27577fb1ef200982</sha1>
  </revision>
  <revision>
    <id>3314</id>
    <parentid>3313</parentid>
    <timestamp>2022-08-28T11:31:55Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="736" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
# bash function: decompress an archive file of any of many formats
# Decompress archive file.
function unarc()
{
  if [ -f $1 ]; then
    case $1 in
      *.tar.*) tar xvf $1;;
      *.bz2) bunzip2 $1;;
      *.gz) gunzip $1;;
      *.jar) jar xvf $1;;
      *.lha) lha e $1;;
      *.tar) tar xvf $1;;
      *.tar.bz2) tar xvf $1;;
      *.tar.gz) tar xvf $1;;
      *.tar.xz) tar xvf $1;;
      *.tar.Z) tar xvf $1;;
      *.rar) rar x $1;;
      *.7z) 7z x $1;;
      *.tbz2) tar xvf $1;;
      *.tgz) tar xvf $1;;
      *.txz) tar xvf $1;;
      *.xz) unxz $1;;
      *.Z) uncompress $1;;
      *.zip) unzip $1;;
      *) echo '"$1" extraction error.';;
    esac
  else echo '"1" nonexistent?';
  fi
}
&lt;/pre&gt;</text>
    <sha1>0a30f965f9fee518500c8e4c60e0eb3264c2a132</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Fonts update</title>
  <ns>0</ns>
  <id>332</id>
  <revision>
    <id>3305</id>
    <parentid>3238</parentid>
    <timestamp>2022-07-27T04:57:54Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="205" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#!/bin/sh
# Update fonts.
mkfontdir
mkfontscale
# Scan directories with apparently valid caches (-f, --force,) verbose (-v, --verbose) (see also man fc-cache):
fc-cache -f -v
&lt;/pre&gt;</text>
    <sha1>eb5de0a27fc23384b4cb49087ac7b0ed51302c9c</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Thumbnails</title>
  <ns>0</ns>
  <id>333</id>
  <revision>
    <id>3306</id>
    <parentid>3235</parentid>
    <timestamp>2022-07-27T04:58:45Z</timestamp>
    <contributor>
      <username>Dchmelik</username>
      <id>32</id>
    </contributor>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="373" xml:space="preserve">[[Category:Tips]]
&lt;pre&gt;
#!/bin/sh
# For every .jpg in a directory, create a thumbnail (smaller) image at 280 pixels high (or comment out, uncomment similar line, for width):
# Resize to 280 pixels height.
for file in *.jpg; do convert -resize x280 "$file" "t$file"; done
# Resize to 280 pixels width.
#for file in *.jpg; do convert -resize 280 "$file" "t$file"; done
&lt;/pre&gt;</text>
    <sha1>2eaea1ade6c0548c68b3ea7dc24547585953d4d5</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>User:Mmlj4</title>
  <ns>2</ns>
  <id>342</id>
  <revision>
    <id>3318</id>
    <timestamp>2023-07-12T15:14:51Z</timestamp>
    <contributor>
      <username>Mmlj4</username>
      <id>322</id>
    </contributor>
    <comment>Created page with "I'm Joey Kelly (http://joeykelly.net), a *nix admin/programmer and ordained minister of the gospel."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="99" xml:space="preserve">I'm Joey Kelly (http://joeykelly.net), a *nix admin/programmer and ordained minister of the gospel.</text>
    <sha1>bf3ae73574ebed94d6cf4f2e096e9d0aac5c5283</sha1>
  </revision>
</page>
<page arvcontinue="20210923135350|3279">
  <title>Plymouth</title>
  <ns>0</ns>
  <id>343</id>
  <revision>
    <id>3398</id>
    <timestamp>2025-01-09T01:36:26Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>Created page with "== plymouth ==   Plymouth is an application that runs very early in the boot process (even before the root filesystem is mounted!) that provides a graphical boot animation while the boot process happens in the background.   you can install plymouth on slackware from [https://slackbuilds.org/repository/15.0/system/plymouth/?search=plymouth plymouth] for which i use [[sbotools]] which is at [https://slackbuilds.org/repository/15.0/system/sbotools/ sbotools]  once plymouth..."</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1193" xml:space="preserve">== plymouth ==


Plymouth is an application that runs very early in the boot process (even before the root filesystem is mounted!) that provides a graphical boot animation while the boot process happens in the background. 

you can install plymouth on slackware from [https://slackbuilds.org/repository/15.0/system/plymouth/?search=plymouth plymouth] for which i use [[sbotools]] which is at [https://slackbuilds.org/repository/15.0/system/sbotools/ sbotools]

once plymouth is installed 

edit /etc/dracut.conf.d/myflags.conf and add this line

&lt;code&gt;add_dracutmodules+=" plymouth "&lt;/code&gt;

edit your /etc/default/grub to include
 
&lt;code&gt;GRUB_CMDLINE_LINUX_DEFAULT="splash"&lt;/code&gt;

themes are in /usr/share/plymouth/themes

to view available themes 

&lt;code&gt;plymouth-set-default-theme -l&lt;/code&gt;

to set the theme

&lt;code&gt;plymouth-set-default-theme &lt;theme-name&gt;&lt;/code&gt;

to list available themes

&lt;code&gt;dracut --list-modules&lt;/code&gt;

load plymouth module

&lt;code&gt;dracut --add-drivers plymouth&lt;/code&gt;

build new initrd

&lt;code&gt;dracut --force /boot/initrd-&lt;kernel-version&gt;.img&lt;/code&gt;

update your bootloader to use the new initrd. i use grub2

&lt;code&gt;grub-mkconfig -o /boot/grub/grub.cfg&lt;/code&gt;

reboot</text>
    <sha1>f67a170dd3356094404e7fded14d482efe193768</sha1>
  </revision>
  <revision>
    <id>3399</id>
    <parentid>3398</parentid>
    <timestamp>2025-01-09T01:43:53Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* plymouth */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1275" xml:space="preserve">== plymouth ==


Plymouth is an application that runs very early in the boot process (even before the root filesystem is mounted!) that provides a graphical boot animation while the boot process happens in the background. 

you can install plymouth on slackware from [https://slackbuilds.org/repository/15.0/system/plymouth/?search=plymouth plymouth] for which i use [[sbotools]] which is at [https://slackbuilds.org/repository/15.0/system/sbotools/ sbotools]

once plymouth is installed 

edit /etc/dracut.conf.d/myflags.conf and add this line

&lt;code&gt;add_dracutmodules+=" plymouth "&lt;/code&gt;

edit your /etc/default/grub to include
 
&lt;code&gt;GRUB_CMDLINE_LINUX_DEFAULT="splash"&lt;/code&gt;

themes are in /usr/share/plymouth/themes

to view available themes 

&lt;code&gt;plymouth-set-default-theme -l&lt;/code&gt;

to set the theme

&lt;code&gt;plymouth-set-default-theme &lt;theme-name&gt;&lt;/code&gt;

to list available themes

&lt;code&gt;dracut --list-modules&lt;/code&gt;

load plymouth module

&lt;code&gt;dracut --add-drivers plymouth&lt;/code&gt;

build new initrd

&lt;code&gt;dracut --force /boot/initrd-&lt;kernel-version&gt;.img&lt;/code&gt;

update your bootloader to use the new initrd. i use grub2

&lt;code&gt;grub-mkconfig -o /boot/grub/grub.cfg&lt;/code&gt;

reboot

--[[User:Wigums|Wigums]] ([[User talk:Wigums|talk]]) 01:43, 9 January 2025 (UTC)</text>
    <sha1>f02c721a3075329d2023569871d367b362a423af</sha1>
  </revision>
  <revision>
    <id>3400</id>
    <parentid>3399</parentid>
    <timestamp>2025-01-09T02:02:52Z</timestamp>
    <contributor>
      <username>Wigums</username>
      <id>609</id>
    </contributor>
    <comment>/* plymouth */</comment>
    <model>wikitext</model>
    <format>text/x-wiki</format>
    <text bytes="1299" xml:space="preserve">[[Category:Tutorials]]

== plymouth ==


Plymouth is an application that runs very early in the boot process (even before the root filesystem is mounted!) that provides a graphical boot animation while the boot process happens in the background. 

you can install plymouth on slackware from [https://slackbuilds.org/repository/15.0/system/plymouth/?search=plymouth plymouth] for which i use [[sbotools]] which is at [https://slackbuilds.org/repository/15.0/system/sbotools/ sbotools]

once plymouth is installed 

edit /etc/dracut.conf.d/myflags.conf and add this line

&lt;code&gt;add_dracutmodules+=" plymouth "&lt;/code&gt;

edit your /etc/default/grub to include
 
&lt;code&gt;GRUB_CMDLINE_LINUX_DEFAULT="splash"&lt;/code&gt;

themes are in /usr/share/plymouth/themes

to view available themes 

&lt;code&gt;plymouth-set-default-theme -l&lt;/code&gt;

to set the theme

&lt;code&gt;plymouth-set-default-theme &lt;theme-name&gt;&lt;/code&gt;

to list available themes

&lt;code&gt;dracut --list-modules&lt;/code&gt;

load plymouth module

&lt;code&gt;dracut --add-drivers plymouth&lt;/code&gt;

build new initrd

&lt;code&gt;dracut --force /boot/initrd-&lt;kernel-version&gt;.img&lt;/code&gt;

update your bootloader to use the new initrd. i use grub2

&lt;code&gt;grub-mkconfig -o /boot/grub/grub.cfg&lt;/code&gt;

reboot

--[[User:Wigums|Wigums]] ([[User talk:Wigums|talk]]) 01:43, 9 January 2025 (UTC)</text>
    <sha1>c3636497edb7de921db56a779d21e03dca6a99a7</sha1>
  </revision>
</page>
</mediawiki>